Archive for the ‘VMM2012’ Category

VMM Tips & Tricks: Add VM to User Role job fails with Error 20413

December 1, 2014 1 comment

In New VMM 2012 R2 with CU3 implementation when you try to add VM to existing user role you may see below error

Error (20413)
VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\SCVMM.4e32da1c-645d-42b3-8c79-612d502ca2ff\report.txt.

Recommended Action
See the report for more details and search user forums for well-known failure root causes for self-help.

VMM Refresh Error



After some investigation I found the error related to VMM DB, After applying the CU3 you need to run same SQL script described in CU1, CU2

Important After you install the update package, you must apply the following SQL script on your Virtual Machine Manager Microsoft SQL Server database for Update Rollup 2 to function correctly.


Please make sure to have a backup from VMM DB before any modification to it. Once script run successfully the VM can be added to user role without any issue

Categories: Tips&Tricks, VMM2012

System Center 2012 R2 is RTM..So What is New ?!!!

October 18, 2013 Leave a comment

As many of you already know System Center 2012 R2 release today and you can download from MSDN website. So this is a quick post about new features in each product


What’s New in VMM in System Center 2012 R2


What’s New in System Center 2012 R2 Operations Manager


What’s New in System Center 2012 R2 Service Manager


What’s New in System Center 2012 R2 App Controller


What’s New in System Center 2012 R2 Configuration Manager


What’s New in System Center 2012 R2 Orchestrator


What’s new in System Center 2012 R2 – DPM

Categories: DPM, Opalis 2012, SCCM, SCOM, VMM, VMM2012 Tags:

VMM Tricks: Upgrading from Currently installed of VMM to System Center VMM 2012 is Not Supported

October 13, 2013 6 comments

Some times when you try to Install/upgrade VMM 2012 “ or VMM 2012 with SP1” you get the error during install of SCVMM 2012.

“you cannot upgrade from the currently installed version of VMM to system center 2012 SP1 virtual machine manager. You must first uninstall VMM,  and then install SCVMM 2012 SP1. If you are running system center suite, when you uninstall VMM, you can retain the database. When you install System center 2012 SP1, use the retained database”


VMM error


to uninstall Old VMM Server from your environment please follow these steps

Action Plan 1:

1.Backup new VMM SP1 instance.
2.Uninstall new VMM SP1 instance.
3.Uninstall old VMM SP1 instance.
4.Install new VMM SP1.

Action Plan 2:

To force an uninstall via command, please follow these steps:

1.Find VMServerUninstall.ini from folder Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup.

2.Replace its content with following code:


If this VMM server’s SQL instance located on a remote server, please change the value of RemoteDatabaseImpersonation to 1.

3.Save this ini file to c:\temp.
4.Run command to locate the folder contain VMM Server setup file under command prompt: cd VMM_Setup_File_folder.
5.Run command to force uninstall VMM server:
setup.exe /server /x /f C:\Temp\VMServerUninstall.ini /
SqlDBAdminDomain DomainName /SqlDBAdminName SQLAdmin /SqlDBAdminPassword password

Note: DomainName is your domina name “Like “Contoso or Fabrikum”
Account Domain\SQLAdmin is  an SQL Server administrator account which is used to connect to backend SQL server.

Categories: VMM, VMM2012

VMM 2012 SP1 Error 2912 when Moving VM

October 3, 2013 2 comments

One of the most common error that I saw in many environment when you try to move VM from one Server to another you get this message

Error (2912)
An internal error has occurred trying to contact an agent on the Server.Domain.Local server: NO_PARAM: NO_PARAM.
Unknown error (0x80072f0d)

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

After checking SCVMM agent and services are running fine on hosts you have to check BITS related configuration, you can use these steps to adjust the BITS to remove this problem:

  1. On Server.Domain.Local , check if we have installed feature Background Intelligent Transfer Service (BITS) feature.
  2. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Locate the BITSTcpPort name on the right. It’s data value should be 443
      a. Double click BITSTcpPort in order to modify the data. Make sure the Base is set to ‘Decimal’
      b. Change 443 to 765, or any other number less than 32768. Do not use a port that another protocol uses such as RDP (3389)
      c. Click ‘OK’ to save this value
  4. Restart the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server. (On managed hosts simply restart the ‘Virtual Machine Manager Agent’ service’)
  5. Once complete on the SCVMM server and all Hosts you can continue using SCVMM


Categories: VMM, VMM2012 Tags:

#VMM 2012 R2 Integration with #SCOM 2012 R2 Error (10218)

September 28, 2013 Leave a comment

When creating the integration between Virtual Machine Manager 2012 R2 and Operations Manager 2012 R2 , the integration fails with the following error:

VMM SCOM Integration

Error (10218)
Setup could not import the System Center Virtual Machine Manager Management Pack into Operations Manager server because one or more required management packs are missing. The VMM Management Packs cannot be deployed unless the following component management packs are present in Operations Manager :
Windows Server Internet Information Services 2003,
Windows Server 2008 Internet Information Services 7,
Windows Server Internet Information Services Library,
SQL Server Core Library.

Recommended Action
To provide the missing component management packs, ensure that the following management packs have been imported into Operations Manager server:
Microsoft Windows Server 2003 Internet Information Services Management Pack for OpsMgr 2012 (version 6.0.6278.0 or later)
Microsoft SQL Server 2005 Management Pack(version 6.0.5000.0 or later)
You can download the management packs from the System Center Operations Manager Catalog at


VMM with Operations Manager Integration


Before you connect VMM with Operations Manager, perform the following actions:

  • Ensure that an appropriate version of Windows PowerShell is installed on all Operations Manager management servers:
    For System Center 2012: Windows PowerShell 2.0
    For System Center 2012 SP1: Windows PowerShell 3.0
    To determine which version of Windows PowerShell is on a server, run the following:
    Get-Host | Select-Object Version
  • Make sure that port 5724 is open between VMM and Operations Manager.
  • Install an Operations Manager Operations console on the VMM management server.
  • Install Operations Manager agents on the VMM management server and all hosts under management by VMM (managed hosts). For more information, see Operations Manager Agent Installation Methods.
  • Verify that the managed hosts on which you installed agents are visible in Operations Manager. To do this, in the Operations console, clickAdministration and then, in the Administration pane, under Device Management, click Agent Managed. Verify that the expected hosts are listed.
  • In Operations Manager, import the necessary management packs, as described in How to Import an Operations Manager Management Pack. Management packs, which in some cases are called “monitoring packs,” are available through the catalog at the Microsoft System Center Marketplace. The necessary management packs are as follows:
    Windows Server Internet Information Services 2003
    Management packs that are required by the management pack for Windows Server 2008 Internet Information Services 7:
    Windows Server 2008 Operating System (Discovery)
    Windows Server Operating System Library
    Windows Server 2008 Internet Information Services 7
    Windows Server Internet Information Services Library
    SQL Server Core Library
    I verified Prerequisites for integration as per Microsoft TechNet Link and make sure that I imported all needed MP

Conflict between exist old Microsoft Virtualization Core Library in Operations Manager. The cause of the problem is that SCVMM 2012 will import a newer version of the Microsoft Virtualization Core Library Management Pack and the old version cannot be present in order for integration to complete successfully


Remove the old version of the Microsoft Virtualization Core Library and try Integration again.



Categories: SCOM, VMM, VMM2012 Tags:

Install VMM 2012 on Windows 2012 Server fail after upgrade

September 8, 2013 Leave a comment

I had see that many times with different customers and on forums.

When you have Windows 2008 R2 managed by VMM 2012 and after upgrade the Hyper-v host to Windows 2012 and try to install the VMM agent you get error.

mostly this happens due to WMI or performance counters corruption. to fix this problem you can try

1. Unpack vmmAgent.msi it placed amd64\Setup\msi\Agent\

unpack like "msiexec /a vmmAgent.msi TARGETDIR=C:\1"

2 cd /D "C:\1\PFiles\Microsoft System Center 2012\Virtual Machine Manager\bin\"

3 unlodctr.exe /

this will unregister perfcounters

4. test to register counters.

lodctr.exe /

5. if all ok unregister counters  unlodctr.exe /

6. Run agent setup.

You can check


Categories: VMM, VMM2012 Tags:

VMM 2012 R2 P2V Error 20404

In Case that you missed that when you try to start P2V process using VMM 2012 R2 you will get error

Error (20404):
VMM cannot find a required object.

Recommended Action:
Ensure the object is valid, and then try the operation again.



From the Release Notes for Virtual Machine Manager in System Center 2012 R2 found here:

P2V functionality will be retired

Description: The Physical-to-Virtual (P2V) feature will be removed from the System Center 2012 R2 release.

Workaround: This is by design.


There are other 3rd  party options for P2V migration include Novell’s Platespin, DoubleTake Move, Acronis, or Microsoft Disk2VHD.

Categories: VMM, VMM2012
%d bloggers like this: