Administrator Guide
Table Of Contents
- Dell Hybrid Cloud System for Microsoft Cloud Platform System Standard Version 1.5 Administrators Guide based on release 1803
- Overview
- Administration
- What to do first
- Next steps
- Managing Dell Hybrid Cloud System for Microsoft
- Creating tenant VM networks
- Adding tenant VM networks to the cloud
- Flagging the operating system VHD in the VM templates
- Enabling guest-specified IP addresses in VMM
- Creating additional tenant storage shares
- Using Windows Azure Pack
- Default Windows Azure Pack configuration
- Before you go into production
- Setting up tenant portal access on an isolated network
- Replacing self-signed certificates
- Disabling the tenant AuthSite and the admin Windows AuthSite websites
- Updating to a Security Token Service and re-establishing trust
- How to open the management portal for administrators
- How to open the management portal for tenants
- Offering services to tenants
- Optional configuration
- Automating tasks for efficiency
- Windows Azure Pack API reference content for developers
- Configuring disaster recovery protection
- Operations
- Monitoring
- Backup and recovery
- Onboard to Azure Backup
- Default backup schedule and retention policy
- DPM protection groups
- Disable machine account password rotation on management VMs
- Protecting tenant VMs
- Recovering VMs and databases—high level
- Recovering from management component failures
- Recovering a tenant VM
- Recovering DPM from DPM failures
- Adding extra disks to DPM
- Monitoring DPM
- Using the Dell Hybrid Cloud System for Microsoft data consistency runbooks
- Updating the Dell Hybrid Cloud System for Microsoft
- Shutting down and starting up the stamp
- Security
- Appendix A Expanding the stamp
- Appendix B Performing a factory reset
- Appendix C Retrieving cluster names, host names, and IP addresses
- Appendix D Ports and protocols

While you are logged in to the
<Prex>
CON01 console VM using the Domain Credentials (see the Solution Integration Document),
remotely connect to the
<Prex>
APA01 server using the PowerShell command Enter-Psession <Prex>APA01. When connected, use
the command Remove-SmaVariable -name "DPM-CongurationMap" -WebServiceEndpoint "https:\\localhost".
Figure 92. PowerShell Remove-SmaVariable
The SMA variable is removed from the
<Prex>
APA01 server.
6 Re-run
BackupDeployDriver.
Resetting the storage cluster
1 Open iDRAC consoles for each physical host.
The Field Engineer (FE) must be connected using the FE laptop. The laptop is connected to port TE 1/40 on one of the Top of Rack
switches.
2 Congure the FE lap
top with the IP address in the Solution Integration Document (SID).
3 Power down the JBODs.
These are the MD1420 or MD1400 storage enclosures.
4 Launch the iDRAC Virtual Console for the rst Storage Host.
5 Log on to the server with an account that has Local Administrator permissions, for example, as a member of the
<Prex>
-Diag-
Admins group.
6 Open an elevated command prompt, and run the reagentc /boottore command.
If you receive a message saying REAGENTC.EXE: Operations successful, continue to the next step. If you do not receive this
message, follow the escalation path.
NOTE: If this is not the rst time the server has been reset, you might receive the error message: REAGENTC.EXE:
Windows RE is disabled. In that case, open an elevated Windows PowerShell session, and run the following commands:
• Stop-Service clussvc
• reagentc /enable
• If you receive the message:REAGENTC.EXE: Operations successful, enter reagentc /boottore. If you do not receive the
Operations successful message, follow the escalation path.
7 In the open Command prompt window, type Shutdown –r –t 0.
The server restarts.
8 When the server restarts in the Windows Recovery Environment click Troubleshoot.
Appendix B Performing a factory reset 153