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
7 After all SQL Server instances are online, in Failover Cluster Manager, connect back to the compute cluster, and start the remaining
in
frastructure VMs in the following order:
a <
Prex>VMM01
b <
Prex>OM01
c <
Prex>APA01
d <
Prex>APT01
8 In Failover Cluster Manager, while connected to the compute cluster, ensure you select all tenant VMs and start them as well.
9 Clear rule-based generated alerts that were created during the startup process. To do this, open the Operations Manager Shell from
the Console VM, and run the f
ollowing commands:
$InstanceObject = Get-SCOMClass -Name Microsoft.SystemCenter.ManagementServersGroup | Get-SCOMClassInstance | Get-
SCOMMonit
oringObject
Start-SCOMTask -Task (Get-SCOMTask -Name Microsoft.Cloud.Overrides.Tasks.ResolveAlertsPerMP) –Instance $InstanceObject
Step 5 Validate the stamp
1 On the Console VM, open the Operations console.
2 In the
Monitoring workspace, expand Microsoft Cloud Dashboard, and then click Microsoft Cloud Dashboard.
3 Make sure all components are healthy.
See Known issues for any expected issues and their resolution steps.
Ensure that the Windows Azure Pack portals are working.
The Windows Azure Pack portals depend on a security token service such as AD FS or an external third-party identity system for your
domain.
Make sure that you can access the Windows Azure Pack management and tenant portals.
Step 6 Power on the backup hosts
After the entire stamp is powered up, start all the backup hosts. Follow these steps:
1 Power on the backup hosts by using either of the following methods:
• Use the on/o switch on the front of the server.
• If the iDRACs are connected, connect to the IPv4 iDRAC address of the hosts by using a browser, for example https://
192.168.164.150, on the laptop that is connected to port 39 or 40 of the switch.
2 Verify that each DPM server can communicate with all the compute hosts. To do so, perform the following steps:
a Log on to the Console VM with an account that is a member of the <
Prex
>-Setup-Admins.
b Open the DPM Administrator console, and then open the Management workspace.
c On the ribbon, in the
Agents group, click Refresh to refresh all agents.
Operations 107