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

Also, in the
<SystemDrive>\ProgramData\Microsoft Cloud Solutions\DeployDriver\Invoke-SiteRecoveryConguration.log, you may see this
error:
[Cloud 'Tenant Cloud' [ID: 'e4166c98-d1b9-4631-bb83-a8946d7821dd'] is not synced successfully with Azure. Check if SCVMMService is
running. W
ait for cloud to sync and run Azure Onboarding again.]
You can resolve this issue by doing the following:
1 Restart the VMM Service by entering the following commands:
Enter-PsSession -ComputerName <Prefix>vmm01
Stop-Service SCVMMService
Start-Service SCVMMService
2 Go to VMM Settings > Microsoft Azure Site Recovery.
3 Continue Azure onboarding from the Dell user interface.
Expansion of existing stamp fails with “Decryption failed” error message
Expansion of an existing Dell Hybrid Cloud System for Microsoft stamp fails in the following scenario:
• The Dell Hybrid Cloud System for Microsoft stamp is at Microsoft Update version 1603 or a later version.
• The nodes that you want to add are running an earlier version of the Windows Management Framework (WMF) than what is included
in Update 1603.
When these two conditions apply, the expansion deployment fails with the message “Decryption failed. LCM failed to start desired state
con
guration manually” in the verbose logs for the nodes that you want to add.
To avoid this issue, do the following before you run expansion:
1 Install WMF 5.0 RTM on the new nodes.
TIP: You can download WMF 5.0 RTM from https://www.microsoft.com/en-us/download/details.aspx?id=50395. You need
the Win8.1AndW2K12R2-KB3134758-x64.msu package.
2 Restart the new nodes.
Paging le no
t large enough for automatic memory dumps
NOTE: This section does not apply if the Microsoft update version of the Dell Hybrid Cloud System for Microsoft stamp at initial
deplo
yment is version 1603 or a later version. To check the update version, see
How to check which update package is installed.
The paging le on the ph
ysical hosts may not be large enough to support the creation of an automatic memory dump if a server crashes.
This le may be required for troubleshooting. Dell recommends that you set the paging le size to 16,384 MB (16 GB).
1 On the Console VM, open an elevated Windows PowerShell session, that is, run as Administrator.
2 Run the following command, where <
hostname1>,<hostname2>,… are the names of all physical hosts in the stamp (including any
backup hosts):
WARNING: The code set o
by “Begin – Long Line” and “End – Long Line” is one continuous line of code that
has been wrapped to t in this document. It should be a single line in the script that you save and run.
# Begin - Long Line
Invoke-Command <hostname1>,<hostname2>,...
{Set-ItemProperty -Path 'HKLM:\SYSTEM
Administration 23