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”

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

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

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

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

CauseConflict 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

Solution

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

About Zeros & Ones

Hi, I’m Mohamed Fawzi and I am working as Senior Infrastructure System Engineer for LINK development company. This blog covers Virtualization technology and Cloud Computing.
*All the usual disclaimers are applied :)
The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.