Administrator Guide

c <Prex>APA01
d <Prex>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 following commands:
$InstanceObject = Get-SCOMClass -Name Microsoft.SystemCenter.ManagementServersGroup | Get-SCOMClassInstance | Get-
SCOMMonitoringObject
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 < Prex >-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.
108
Operations