White Papers

16 Update 1803 for Cloud Platform System (CPS) Standard
4.2 Step 2: Run the 1803 Microsoft P&U package
IMPORTANT: You must run the DHCS_Run_First package before you run the 1803 Microsoft P&U
package.
Because of the size of this package, estimates for deployment duration are 12 to 18 hours. Run the 1803
Microsoft P&U update package by doing the following:
1. Browse to the shared folder PUShare on the console VM, and create a folder to store the 1803 Microsoft
update package, such as PU_MS#, where # is the number or some other identifier of the specific update
package. For example, where 1803 represents the year/month:
\\<Prefix>CON01\PUShare\PU_MS1803
IMPORTANT: Do not use the same folder name as an existing folder because you want to maintain a history
of each patching update.
Note: If the update package is larger than 2 GB, and the copy and paste operation fails, see
https://support.microsoft.com/en-us/kb/2258090.
2. While logged into the console VM, browse to location where you unzipped the Patch and Update package
and execute the file with the format DHCS_Update_1803_Run_Second.exe to extract the update. When
prompted, select the PU_MS1803 folder to store the extracted files.
3. Now that the patching environment is set up, you can start the patching process by running a Windows
PowerShell script. Run the following command:
\\<Prefix>CON01\PUShare\PU_MS1803\PU\Framework\PatchingUpgrade\Invoke-PURun.ps1 -
PUCredential (Get-Credential)
Note: The P&U (Patch and Update) engine automatically runs a health check as part of the update process.
You can control what happens if critical Operations Manager alerts are discovered. To do this, change the
value of the -ScomAlertAction parameter. For example, -ScomAlertAction "Continue"
4. When prompted, enter the account credentials of the account that you used to log in.
5. The Invoke-PURun script performs a one-time environment setup and may prompt you to restart
Windows PowerShell on its for invocation, for example:
PowerShell environment settings have changed. Please restart the PowerShell console before
proceeding.
If you see this message, close the current Windows PowerShell session, open a new elevated
Windows PowerShell session, and repeat steps 2 through 4 to start the health check process.
6. DPM agents on the DPM servers are in an enabled state. If this is the case, the health check output
indicates that you must run the Set-DPMBackupMode script to cancel the jobs and disable the agents.