Category: SCVMM

VMM 2012 RC upgrade to VMM 2012 RTM

Today we have difficulties to change or better to upgrade to the new VMM 2012 RTM. What I did is to solve that problem is to change the Database Version from RC (3.0.5007.0) to the final version edition (3.0.6005.0). See below. After that the upgrade was working perfectly.


Happy new VMM 2012 RTM and don’t forget to upgrade the VMM hosts! Zwinkerndes Smiley


Today we found in our VL and Technet Subscription the final version of System Center 2012. So we will upgrade our full environment as soon as possible!

Great job Microsoft. Zwinkerndes Smiley

Last weekend we set up a cluster with seven Hyper-V servers and everything looked fine, but today some of our virtual machines in the cluster stopped without any cluster error message. After restarting them, they ran for a short period and stopped again.


So we looked in the Windows System Event log on the cluster owner and saw the following message:

Cluster Agent: The cluster resource Virtual Machine %hostname% has become degraded.


A google search led us to the HP SNMP TRAP documentation:

NT Event ID: 1167 (Hex)0x8435048f (cpqhsmsg.dll)
Log Severity: Warning (2)
Log Message: The cluster resource %4 has become degraded.
SNMP Trap: cpqClusterResourceDegraded – 15005 in CPQCLUS.MIB
Symptom: This trap is sent any time the condition of a cluster resource becomes degraded.

User Action: Make a note of the cluster resource name, and then check the resource for the cause of the degraded condition.
Supporting SNMP Trap Data:
• sysName
• cpqHoTrapFlags
• cpqClusterResourceName

Supporting SNMP Trap Description: “Cluster resource [cpqClusterResourceName] has become degraded.”


So we checked the resources (in our case the server) and saw, that the stopped machines ran out of the grace-period and needed a Windows Activation.

Solution: Activate the Machines again and be happy 🙂

Today it was impossible to convert a server (Windows 2003 Std. with SP2, x86) to the Hyper-V with VMM 2008 R2 SP1, till I found a solution.

The error was:

Error (13243)
The snapshot creation failed because VSS writer {e8132975-6f93-4464-a53e-1050253ae220} on source machine server.domain.local did not respond within the expected time interval.
(Internal error code: 0x809933BB)

Recommended Action
Ensure that VSS writer is functioning properly and then try the operation again.


I tried a couple of things:

  • I was checking, with the command vssadmin list writers if every writer was OK.  – The System Writer was missing.
  • I tried to register once again, but it was not working. The command would be:

CD c:\windows\system32

Takeown /f %windir%\winsxs\filemaps\* /a

icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"

icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"

icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"

  • I stopped the SQL VSS writer with no effect.
  • I tried also to start the cryptsvc, but I got back an error that it could not be started.

The cryptsvc was deactivated. Without that, the system writer will not start. So the solution for me was only to change the service to automatic and start it. Zwinkerndes Smiley

Today I wanted to add a new Virtual Machine after the VMM 2008 R2 server was offline for 3 weeks. The first problem was, that we were not able to connect to the VMM 2008 R2 console on any remote machine. It was only possible on the VMM Server. The solution was to reinstall the VMM server.

Continue reading

Warning 13210 – SCVMM 2008 R2 SP1

Today I got really frustrated, because I was not able to convert 4 physical servers from the brand Thomas Krenn (Intel, Windows 2003 x86 with SP2) to Virtual Machines through P2V converter of SCVMM.

Continue reading

Today I got into a very strange warning from VMM 2008 R2 SP1. And before of that I could not connect the network adapter in a VMM Guest to my internal network, it was greyed out.

Continue reading