Update 1605 for Cloud Platform System Premium

Step 1: Update network switch firmware

• Ignore any comments in the Administrators guide about applicability to CPS Premium with 2014 hardware. This switch firmware applies to all versions of CPS Premium hardware.
• The following is the download location of the AFM files for Update 1605:
  
  http://poweredgec.dell.com/cps/CPS_P_1605/Tools/AFM
  
  The following are the recommended firmware versions that switches should run after the update.
  
  

  Device	Recommended Firmware Version	CPS Premium Hardware Version
  S4048	9.9 (0.0P11)	2016
  S3048	9.9 (0.0P11)	2016
  S4810	9.9 (0.0P11)	2014
  S55	8.3.5.6	2014

Step 2: Install the prerequisite VMM hotfix

How to apply the Virtual Machine Manager (VMM) Hyper-V Network Virtualization policy hotfix

1. From the specified location, copy the System Center 2012 R2 VMM UR HotFix 6095474.exe file to a folder on a Console VM, such as C:\VMMHotfix.
2. Double-click the System Center 2012 R2 VMM UR HotFix 6095474.exe file, review the Microsoft Software License Terms, and then click Yes to accept.
3. Choose a folder to store the extracted files, such as C:\VMMHotfix, and then click OK.
4. Determine the passive VMM node. To do this, open a Windows PowerShell ISE session and then run the following script, where is your stamp prefix:
   

   $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 Green
   Write-Host "Passive Node: $passiveNodes" -ForegroundColor Green

   
   This script returns the server name of the passive VMM node. (In our example, we at first assume that Node2 is the passive node.)
   
   
5. In File Explorer, browse to the following folder on the passive node:
   
   \\Prefix-VMM-0#>\c$\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin
6. Make a backup copy of the ImgLibEngine.dll file in the \bin folder.
7. In the VMM console, determine which host (in the management cluster) the passive VMM node is running on.
8. Open Hyper-V Manager, connect to the management cluster host that you identified in the previous step, and connect to the passive VMM node.
9. On the VMM node, type powershell to open an elevated Windows PowerShell session, and then run the following command:
   
   Stop-Service SCVMMService Stop-Service SCVMMAgent
10. Verify that the service has stopped running. To do this, run the following command:
    
    Get-Service SCVMMService Get-Service SCVMMAgent
    
    Verify that the status is Stopped. If you're prompted to close the System Center Management Service Host process, click Ignore.
    
    
11. 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
12. In the \bin folder, replace the ImgLibEngine.dll file that has the new version of the files that you extracted from the hotfix package.
13. On the passive VMM node, run the following command to start the VMM Agent service:
    
    Start-Service SCVMMAgent
    
    Note The SCVMMService service will not start when the passive VMM server node is not active. The SCVMMService service starts only when the node becomes the Active node. This is by design.
    
    
14. In Failover Cluster Manager, begin a failover. This makes Node1 to become the new passive node and Node2 (which has already been updated) become the active node.
15. Open Failover Cluster Manager, and then connect to the Prefix-CL-VMM cluster.
16. Click Roles. The Roles pane displays the active node in the Owner Node column. Right-click the active node, point to Move, and then click Select Node. Select the other node, and make sure that the status changes to Running for the new active node. This may take several seconds.
17. Follow steps 5–13 to update the VMM file on the new passive node (in this example, Node1).

1. On the passive VMM node, stop the SCVMMService service, and then 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. Start the SCVMMService service.
5. In Failover Cluster Manager, start a failover of the Prefix-HA-VMM clustered role.
6. Repeat steps 1-4 on the new passive node.

Step 3: Prepare the package

Step 4: 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 then connect to the WSUS VM (Prefix-SUS-01).
3. In the navigation pane, expand Update Services, expand WSUS_Server, expand 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 and then click Refresh.
5. Select all updates.
6. Right-click the selection, and then click Decline.
7. In the navigation 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.

Step 5: Run the Patch & Update Health Check and address any discovered issues

Step 6: Run the P&U update package 1605-0

Step 7: Run the P&U update package 1605-1

Step 8: Run an optional compliance scan

Payload for Update 1605-0

Payload for Update 1605-1