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
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
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.
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
An internal error has occurred trying to contact an agent on the Server.Domain.Local server: NO_PARAM: NO_PARAM.
Unknown error (0x80072f0d)
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
When creating the integration between Virtual Machine Manager 2012 R2 and Operations Manager 2012 R2 , the integration fails with the following error:
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.
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 http://go.microsoft.com/fwlink/?LinkId=86411
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.
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 /m:scperfprovider.man
this will unregister perfcounters
4. test to register counters.
5. if all ok unregister counters unlodctr.exe /m:scperfprovider.man
6. Run agent setup.
In Case that you missed that when you try to start P2V process using VMM 2012 R2 you will get error
VMM cannot find a required object.
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: http://technet.microsoft.com/en-us/library/dn303329.aspx
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.
Microsoft just release new test lab guide “Test Lab Guides: System Center 2012 SP1 – Virtual Machine Manager”
These guides contain instructions for setting up a test lab that uses System Center 2012 Service Pack 1 (SP1) – Virtual Machine Manager (VMM). The guides describe how to deploy a VMM management server and a host in the test lab, and then tell how to use those servers to deploy multiple virtual machines that can work together to provide services. The virtual machines that you can deploy include web servers and servers running SQL Server 2012. After you create VMM profiles and templates, such as the ones described in these guides, it is a straightforward process to deploy as many sets of virtual machines as needed.
Download include two files
1- Test Lab Guide: Deploy Virtual Machine Manager in System Center 2012 SP1
This guide explains how to set up a test lab that deploys VMM using two physical servers. This can help you learn to deploy VMM, and provide a foundation for learning how you might use VMM in your environment. The guide also shows how to use VMM to create a virtual machine and deploy it on a host system in the test lab. The guide includes a small amount of information and some links that are related to the deployment of virtual machines. This guide is designed to provide a foundation for other procedures and guides for VMM
2-Test Lab Guide: Use VMM to Deploy a Web-Based Application that Requires Multiple Virtual Machines
This guide contains procedures for setting up a test lab that is based on the foundation provided by the Test Lab Guide: Deploy Virtual Machine Manager. The procedures show how to deploy virtual machines by using profiles (such as application profiles) and templates (such as virtual machine templates and service templates).
The guide represent the templates and profiles that you can create when you perform the steps in this guide. With these templates and profiles, you can first deploy a web server, and then a pair of virtual machines—a web server and an instance of SQL Server—to represent virtual machines that could work together as a service that you provide to users.
You can get it from there