Update 1609 for Cloud Platform System (CPS) Premium

Step 1: Update network switch firmware

Step 2: Update serial port concentrator firmware

• Avocent ACS 6000 Series:
  http://download2.emersonnetworkpower.com/SerialACS/ACS6000/ACS6000_v3.3.0.10/avoImage_avctacs-3.3.0-10.zip
• Digi CM 48:
  http://ftp1.digi.com/support/firmware/80007070_U.bin

Step 3: Install the VMM hotfixes for VM placement

• If you've already installed the VMM hotfix for virtual machine placement that was included in Update 1606, you do not have to install it again. If this is true, you can skip this step and go to Step 4.
• The highly available VMM clustered role (<Prefix>-HA-VMM) has two nodes, <Prefix>-VMM-01 and<Prefix>-VMM-02. In the instructions, we refer to these as Node1 and Node2.

1. For the new VMM placement hotfix, follow these steps:
   
   
   1. From the update file drop location, copy the "Placement_HF_UR9.exe" file to a folder on a Console VM, such as C:\VMMHotfix. (You can use the same folder that was used for the previous hotfix.)
   2. Double-click the "Placement_HF_UR9.EXE" file, review the End User License Agreement (EULA), and then click Yes to accept the terms.
   3. Select a folder in which to store the extracted files. For example, select C:\VMMHotfix. Then, click OK.
2. Determine the passive VMM node. To do this, open a Windows PowerShell ISE session, and then run the following script:

   $prefix = $ENV:COMPUTERNAME.split('-')[0]
   $VmmServerName = "$prefix-HA-VMM" 
   $vmmServer = Get-SCVMMServer -ComputerName $VmmServerName 
   $activeNode = $vmmServer.ActiveVMMNode 
   $passiveNodes = @() $vmmServer.FailoverVMMNodes | ForEach-Object { if($_.ToLower() -ne $activeNode.ToLower()){ $passiveNodes += $_ } } 
   Write-Host "Active Node: $activeNode" -ForegroundColor GreenWrite-Host "Passive Node: $passiveNodes" -ForegroundColor Green

   This script returns the server name of the passive VMM node. (In our example, we assume that Node2 is the default passive node.)
3. In File Explorer, locate the following folder on the passive node:
   \\<Prefix>-VMM-0#>\c$\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin
4. Make a backup copy of the following file in the \bin folder:
   
   Engine.Placement.ResourceModel.dll
5. In the VMM console, determine which host (in the management cluster) the passive VMM node is running on.
6. Open Hyper-V Manager, connect to the management cluster host that you identified in the previous step, and then connect to the passive VMM node.
7. On the VMM node, type powershell to open an elevated Windows PowerShell session, and then run the following commands:

   Stop-Service SCVMMService
   
   Stop-Service SCVMMAgent 

8. Verify that the services have stopped. To do this, run the following commands:

   Get-Service SCVMMService 
   
   Get-Service SCVMMAgent 

   Note If you're prompted to close the System Center Management Service Host process, click Ignore.
9. On the Console VM, browse to the following folder on the passive node:
   \\<Prefix>-VMM-0#\c$\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin
10. In the \bin folder, replace the following file by using the new version of the file that you extracted from the hotfix package:
    
    
    Engine.Placement.ResourceModel.dll
11. On the passive VMM node, run the following command to start the VMM Agent service:
    
    

    Start-Service SCVMMAgent 

    Note The SCVMMService service does not start if the passive VMM server node is not active. SCVMMService starts only when the node becomes the Active node. This behavior is by design.
12. In Failover Cluster Manager, initiate a failover. This will set Node1 as the new passive node and set Node2 (which has already been updated) as the active node.
13. Open Failover Cluster Manager, and then connect to the <Prefix>-CL-VMM cluster.
14. Click Roles.
    
    Note The Roles pane displays the active node in the Owner Node column.
15. Right-click the active node, point to Move, and then click Select Node.
16. Select the other node, and make sure that the status changes to Running for the new active node.
    
    Note The change may take a few seconds to occur.
17. Follow steps 511 to update the VMM file on the new passive node (in this example, Node1).

To revert the update (if necessary)

1. On the passive VMM node, stop the SCVMMAgent service.
2. Replace the files under your Virtual Machine Manager Install directory with your backup files.
3. Start the SCVMMAgent service.
4. In Failover Cluster Manager, initiate a failover of the <Prefix>-HA-VMM clustered role.
5. Repeat steps 1-4 on the new passive node.

Step 4: Prepare the package

Step 5: Clean up the WSUS server

1. On the Console VM, open the Windows Server Update Services console.
2. Right-click Update Services, click Connect to Server, and connect to WSUS VM (<Prefix>-SUS-01).
3. In the navigation pane, expand Update Services > [WSUS Server] > Updates, and then click All Updates.
4. In the All Updates pane, click Any except declined in the Approval list.
5. In the Status list, click Any, and then click Refresh.
6. Select all updates.
7. Right-click the selection, and then click Decline.
8. In the navigation pane, expand the server name, and then click Options.
9. In the Options pane, click Server Cleanup Wizard.
10. Select all check boxes except the Computers not contacting the server check box.
11. Click Next.

Step 6: Run a health check

Step 7: Run P&U update package 1609-0

Step 8: Run P&U update package 1609-1

Step 9: Run an optional compliance scan

\\SU1_InfrastructureShare1<CPSPU Folder 
Name>\Framework\PatchingUpgrade\Invoke-PURun.ps1 -PUCredential $cred -ComplianceScanOnly

<PURoot>\MissingUpdates.json 

Payload for Update 1609-0

Configuration changes (from previous updates)

Updates for Windows Server 2012 R2 (from previous updates)

Payload for Update 1609-1

Updates for Windows Server 2012 R2

System Center and Windows Azure Pack updates (from previous updates)

Hardware (driver/firmware) updates (from previous updates)

Updates for Windows Server 2012 R2 (from previous updates)

Updates for SQL Server 2012 (from previous updates)

Issue 1

Symptoms

Description

Detection

1. On the Console VM, open Cluster-Aware Updating.
2. In the Connect to a failover cluster list, click the SQL Server cluster (<Prefix>-HA-SQL), and then click Connect.
3. The Last Run status should show a Succeeded value for all four SQL Server nodes.

1. Open SQL Server Management Studio.
2. Connect to the <Prefix>-SH-SQL\SCSHAREDDB instance.
3. Click New Query.
4. Run the following command:

   SELECT @@VERSION 

5. The result should begin as follows:

   Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64) 

   Or as follows:

   Microsoft SQL Server 2012 (SP3-CU2) (KB3137746) - 11.0.6523.0 (X64) 

6. Repeat steps 25 for the following SQL Server instances:
   
   
   • <Prefix>-OM-SQL\SCOMDB
   • <Prefix>-KT-SQL\KATALDB
   • <Prefix>-DW-SQL\CPSDW
   • <Prefix>-AS-SQL\CPSSSAS

Resolution