White Papers

49 Update 1611 for Cloud Platform System (CPS) Standard
 The temporary fix resolves the problem immediately, but does not prevent it from happening again. This
fix involves rebooting the SMA VM (<Prefix>APA01). This restarts any queued jobs in SMA.
 The more permanent fix, which is not recommended, has performance impacts to SMA, but will prevent
the issue from happening again.
To apply the more permanent fix, do the following:
1. On the SMA VM ((<Prefix>APA01), modify the following values in the Program Files\Microsoft
System Center 2012 R2\Service Management Automation\
Orchestrator.Settings.config file:
Old Values
New Values
<add key="MaxRunningJobs" value="30"/>
<add key="MaxRunningJobs" value="1"/>
<add key="TotalAllowedJobs"
value="1000"/>
<add key="TotalAllowedJobs" value="1"/>
2. After changing these two settings, reboot the SMA VM (<Prefix>APA01).
Issue 3
Symptoms:
Exclude external host from P&U.
Description:
If you have added a physical host to VMM that is not part of the CPS Standard stamp—in this case the stamp
includes backup infrastructure—you must exclude the host from P&U. If you do not, P&U will fail.
Detection:
The P&U process fails after adding a physical host to VMM that is not part of the CPS Standard stamp.
Resolution:
To exclude an external host from P&U:
1. In the VMM Console, open the Fabric workspace.
2. Under Servers, click All Hosts.