scvmm

Unable to perform a Compliance Scan in SCVMM

In System Center Virtual Machine Manager (SCVMM) an Update (WSUS) Server is added, so VMM can be used to update the hosts with Windows patches.When trying to scan a cluster of hosts for compliance the following error occurred:

Error (24035)

Compliance scan failed with error: 80244017.

Recommended Action:

Ensure the WINHTTP proxy settings are correctly configured for the communications with WSUS. If WSUS is configured to use SSL ensure the WSUS certificate is installed in the trusted Root CA for the machine and then try the operation again.

image 

The cluster consist of several Microsoft Hyper-V Server 2012 R2 hosts. All the hosts are configured with a proxy server during the initial installation. After resetting the proxy server per host,  the SCVMM was able to perform a compliance scan without errors. The following command is used to reset the proxy server configuration on the core version:

netsh winhttp reset proxy

 

image

SCVMM library is unable to refesh a file because it is in use

In the jobs window in the System Center Virtual Machine Manager (SCVMM) console , the following warning appeared:

Warning (10803)
Unable to refresh \\server\share\ISO\Windows2012 R2\SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.ISO because the file is in use by another process.

Recommended Action
Wait for the next automatic library refresh, or manually refresh the library share after the process completes.

image

The warning means that the ISO file is in use by one or more VM’s. To find the VM’s that are using the ISO file I created the following PowerShell script:

Import-module VirtualMachineManager
Get-SCVMMServer -ComputerName VMMSERVER
Get-SCVirtualMachine | Get-SCVirtualDVDDrive | Where-Object {$_.Connection -eq "ISOImage"} | Select Name, Connection, ISO

The script displays all the VMs that have an ISO file attached. The script is tested against a SCVMM 2012 R2 server.

image

After changing the VMs Virtual DVD drive to “No media” the hourly (default) refresh of the library went without a warning.

image

Tips for deploying SCVMM 2012 R2 Rollup 2

Last week Update Rollup 2 (UR2) for System Center 2012 R2 Virtual Machine Manager is released. UR2 contains important fixes for SCVMM2012 R2.  Here are some deployment tips for UR2:

  • Wait a least couple of weeks before deploying Update Rollups in your production environment.  It happens that new Update Rollups contains huge bugs and are pulled back!
  • Make sure you have a backup of the SCVMM database before installing UR2
  • Install the UR2 by download the VMM management server and VMM admin console packages link (or use Windows Update /WSUS to install both packages). Older packages such as UR1 does not need to be removed. In a SCVMM HA environment install UR2 first on the passive node, perform a failover and install UR2 on the other node.

image

  • After installing UR2 update execute the SQL script listed in the KB2932926 article on the SCVMM database

image

  • In the VMM console check the version by selecting help. The UR2 must be 3.2.7634.0.
  • This step is often forgotten. In the VMM admin console perform a cluster refresh (Fabric-Cluster-Refesh). After the refresh job completes the host status is changed in “Needs Attention”. This means that the VMM agent must be updated on all the hosts.

image

  • Update the VMM agent by right click on the host en choose “Update Agent”. No reboot of the host is required. Using PowerShell the “Update-VMMManagedComputer” cmdlet can be used to update the agent

image

  • After the VMM agent is updated on the host check the version of the agent on the general tab on the host. The UR2 agent version must be 3.2.7634.0.

image

  • With PowerShell you can list all the agent versions by using:
Get-VMMMangedComputer | Select Name, AgentVersion

image

System Center Virtual Machine Manager (SCVMM) 2012 R2 builds and versions

Build Version
3.2.7510.0 System Center 2012 R2 Virtual Machine Manager RTM
3.2.7620.0 Update Rollup 1 (UR1)
3.2.7634.0 Update Rollup 2 (UR2)
3.2.7672.0 Update Rollup 3 (UR3)
3.2.7768.0 Update Rollup 4 (UR4)
3.2.7895.0 Update Rollup 5 (UR5)
3.2.8002.0 Update Rollup 6 (UR6)
3.2.8071.0 Update Rollup 7 (UR7)
3.2.8117.0 Update Rollup 8 (UR8)
3.2.8145.0 Update Rollup 9 (UR9)
3.2.8169.0 Update Rollup 10 (UR10)
3.2.8224.0 Update Rollup 11 (UR11)
3.2.8228.0 Update Rollup 11 (Hotfix 1)
3.2.8292.0 Update Rollup 12 (UR12)