White Papers

6 Update 1703b for Cloud Platform System (CPS) Standard
1.1 New functionality
Update 1703b contains the following new features:
 Provides support for Windows Server 2016 as an operating system for tenant VMs. (This support is
provided through Windows Azure Pack UR11 and VMM UR12.)
 Includes an updated compliance scan implementation. Previously, a compliance scan (to verify
updates were installed through P&U) would show empty results if compliant.
 Provides additional logging during P&U for Hyper-V Network Virtualization (HNV) settings and VMM
trace logs. This will help troubleshoot failures during P&U, as described below:
> You can find the HNV logs in the same ‘temp’ location as the PUProgressDetails log on the
machine that is running P&U. For example, \\<Prefix>-CON-01\c$\Users\CPS-
Update-Admin\AppData\Local\Temp.
> You can find the VMM trace log files at the root of C: on the VMM servers.
> P&U deletes previous VMM trace logs each time a P&U run is started. If you encounter a
failure in P&U that requires additional investigation, copy these logs before you restart P&U.
1.2 Additional update information
In addition to the features listed above, Update 1703b also includes the following:
 Prevents SQL Server accounts from lock-out while running MCPasswordReset in high-load
scenarios.
 Updates to SQL Server components on DPM servers for greater resiliency in high-load scenarios.
 Updates all CPS hosts and infrastructure VMs to Windows Management Framework (WMF) 5.1.
 KB Article # 3000483 is a Windows Group Policy related security update (CVE-2015-0008). It
requires both the binary files (delivered in P&U 1611 and 1703b), and a Group Policy update. See the
KB article for details on the Group Policy changes, including a section titled “Minimum recommended
configuration for domain-joined computers”.
Note: Review the KB article, and decide whether you want to implement these changes for the CPS domain.
This procedure is optional.
1.3 How to check which update package is installed
To check the version of the update package that is currently installed on the stamp, do the following:
1. On the Console VM, open the DeploymentManifest.xml file at the path:
C:\Program Files\Microsoft Cloud Solutions\DeployDriver\Manifests.
2. At the top of the file, look for the following entries:
•“ This is the version of the Dell-provided update package.
• “ MicrosoftVersion= ”: This is the version of the Microsoft-specific updates that were incorporated in the Dell-
provided update package, for example: