White Papers

9 Update 1703b for Cloud Platform System (CPS) Standard
2.5 Step 4: Ensure that LaJollaDeploymentService is not running
in the background on the Console VM
You can ensure that the service LaJollaDeploymentService is stopped by doing the following:
1. On the Console VM, open up the services MMC console that is located under Control Panel-
>System and Security->Administrative Tools->Services.
2. Look for LaJollaDeploymentService.
3. Ensure that Status is Stopped.
2.6 Step 5: Clean up the WSUS server
To clean up the server:
1. On the Console VM, open the Windows Server Update Services console.
2. Right-click Update Services, click Connect to Server, and then connect to the WSUS VM
(<Prefix>VMM01).
3. In the left pane, expand Update Services > [WSUS Server]> Updates, and then click All Updates.
4. In the All Updates pane, in the Approval list, click Any except declined. In the Status list, click
Any. Then, click Refresh.
5. Select all updates.
6. Right-click the selection, and then click Decline.
7. In the left pane, expand the server name, and then click Options.
8. In the Options pane, click Server Cleanup Wizard.
9. Select all check boxes except for Computers not contacting the server.
10. Click Next.
11. Restart the Console VM.
2.7 Step 6 (Optional): Exclude external SOFS storage clusters from
P&U
IMPORTANT: This procedure applies only if you attached external Scale-Out File Server (SOFS) storage
clusters to the CPS Standard stamp.
If you attached external Scale-Out-File-Server (SOFS) storage clusters to the CPS Standard stamp (for
additional workload capacity), you must exclude them from P&U. If you do not, P&U will fail.
To exclude external storage clusters, do the following:
1. Open the VMM console.
2. In the Fabric workspace, under Storage, click File Servers.
3. In the File Servers, File Shares pane, right-click the external storage cluster, and then click
Properties.
4. On the General tab, in the Description box, enter {CPSExternal Component}, and then click OK.