Microsoft Enterprise Platforms Support: Windows Server Core Team
Virtual Machine Manager (“VMM”) is a manager of Windows Virtual Machines (“VM”) and the Hosts (physical machines) on which the VMs reside. Depending on hardware configuration, a single Host can house several VMs. A large volume of the calls we receive at Microsoft are around installation and operation - the goal of this blog is to cover each.
The predecessor to VMM was the web-based Virtual Server 2005. Its user interface is below.
Virtual Server 2005 Web Interface
Design Overview: System Center VMM....
The newer console-based VMM is faster, and adds several features, such as more reliable conversion of physical to virtual machines (“P2V”), faster deployment of VMs, and centralized monitoring of several hosts AND their VMs. You can tailor the VMM interface to several levels of granularity and filtering, making managing several hosts and their VMs customizable to what works best for you. VMM manages your virtual hard drives (“vhd”), images, deployment scripts, and HW configurations in a centralized “Library.”
Above is the VMM Manager Console interface. Highlighted in yellow are the two physical HOST machines the VMM manages. Displayed in green are the Virtual Machines on BOTH hosts. If we were to select only one of the Hosts on the left, we would see only the VMs on that particular Host. In blue, you’ll see the tasks, or “Actions” VMM can perform. Selecting any of these will start a respective wizard that will walk you through the task at hand.
Below, for example is the first page of the wizard that will create a new VM.
Don’t forget the Help File!
Your SCVMM product CD includes a Help folder with a “Setup” help file that provides similar information as is presented here. The English version is in the “1033” folder. Be sure to go through this before installing VMM.
The VMM Components
There are four main components to your VMM deployment:
1. Virtual Machine Manager Server
2. Virtual Machine Library Server
3. Virtual Machine Host
4. Virtual Machine Manager Console
You’ll want to understand each of these and what they do before beginning to set up your deployment.
The VMM server is the hub of a VMM deployment through which all other VMM components interact and communicate. Therefore the VMM server must be installed first. The VMM server runs the VMM service, which runs commands, transfers files, and controls communications with what is collectively referred to as managed computers and:
The VMM service is run through the VMM agents that are installed on the managed computers. The VMM server also connects to a SQL Server database that stores all VMM configuration information. This database is typically on the VMM Server, but you can also use a separate SQL server for especially large deployments. The VMM Administrator console accesses this information and configures it.
The VMM server is also the default library server, where virtual hard disks, templates, and ISO images can be stored. Typically you’ll want to set up an additional (or separate) VMM library server.
The Virtual Machine Manager Library Server has a catalog of resources that can be used to create and configure virtual machines. This library contains files stored on library shares, and can contain:
Keep in mind that the Library is a catalog, or pointer to, the resources it lists. They may be on the Library Server itself, or, more often, on the Hosts that make up the bulk of your deployment. If you’ve ever wondered, “now where did I put that VM’s vhd?” you’ll recognize the value of the Library right away.
This is the component we are all most likely the most familiar with. A virtual machine host is a physical computer that hosts one or usually several virtual machines. You can add one or more hosts to VMM by using the Add Hosts Wizard in the VMM Administrator Console. Until you add a host, you cannot use VMM to create virtual machines and many of the actions in the VMM Administrator Console are not available.
When you add a host, VMM automatically installs an agent on the host. You can then manage the host with either the VMM Console or the web interface, Virtual Server 2005 R2. If your Host is not R2 with SP1, VMM will install it when you add the Host to VMM.
This is the GUI shown above (third exhibit), that manages the Hosts, the Library, and the VMs. You install the VMM Administrator Console after installing the VMM server. Typically you’ll want to install it on the same computer as the VMM server, but it can be installed on a on a different computer.
Before installing the VMM Server and Console, you'll want to download and install the Windows PowerShell appropriate for your system (it's a Feature in 2008, and a web-download for earlier versions). You'll also want to install Windows Remote Management
How to Install the Virtual Machine Manager Server and Administrative Console
Before installing the System Center Virtual Machine Manager (VMM) server, ensure that the prerequisite software and hardware are installed. For more information about software and hardware prerequisites, see System Requirements for Deploying Virtual Machine Manager (http://go.microsoft.com/fwlink/?LinkId=69926).
The next screen will present the Setup Wizard which walks you through the remainder of the installation.
Anyway the defaults are below…
During installation, the Setup Wizard creates a folder named VHDs and two virtual hard disks, Blank Disk - Small (16 GB) and Blank Disk - Large (60 GB), that you can use to create a new virtual machine or as additional data disk drives. This is the beginning of your Library.
The port settings that you assign for the VMM server must identically match the port settings that you assign for the related VMM components that the VMM server communicates with. It’s unlikely you’ll want to change these.
Next, you’ll want to install the Administrative Console
1. On the product DVD or network share, double-click setup.exe and on the Setup menu, click Install administrator console.
2. Click next, and you’ll be asked to accept the licensing agreement, followed by the Microsoft Update opt-in screen. Next, on the Customer Experience Improvement Program (CEIP) page, click Yes to participate or No to opt out of the CEIP. You’ll then be prompted for User name & Company.
3. The Prerequisites Check will then run and present results, review any alerts or warnings about inadequate hardware or uninstalled software prerequisites. After these are resolved, select Check Again to proceed
4. On the Configuration Settings page, click Next to use the default port (8100) for the VMM Administrator Console to communicate with the VMM server or assign a different port that you want to use for the VMM Administrator Console to communicate with the VMM server, and then click Next.
The port settings that you assign for the VMM Administrator console must identically match the port settings that you assigned for the VMM Administrator Console in the VMM server.
5. On the Summary of Settings page, review your settings and click Previous to change any settings or click Install to install the VMM Administrator Console.
6. On the Installation page, after setup is complete, click the link in the Status window to check for the latest VMM updates.
· The Connect to Server dialog box opens the first time you open the console. In the Connect to Server dialog box select either of
· If you installed the VMM Administrator Console on the same computer as the VMM server, click Connect to connect to the local VMM server (localhost) using the default port (8100).
Unfortunately, it’s possible you’ll get all this way and still get an error…
But wait; didn’t we install .NET Framework 3.0 back in the Server service installation?
If you check the “Error” tab, you might see something not especially helpful as far as what happened, but at least it tells you what to do, in this case, download .NET from the web and install. Unfortunately, you’ll need to repeat the Administrative Console installation.
Otherwise, a successful installation will look like this (you'll need to select "Open the Virtual Machine Manager..."
7. When you hit close, you'll be presented with a "Connect to Server" dialog. In the Server name box, type the name of the computer where the VMM server is installed, followed by a colon and the port that you want to use to connect the VMM Administrator Console to the VMM server, and then click Connect. By default, you'll be presented with "localhost:8100" the selection to use in the present demontration. If all has gone well, you’ll be presented with the Console depicted at the beginning of this blog (third exhibit).
In the next blog, we’ll cover adding Host servers and Virtual Machines. If you don’t want to wait and are starting to get the hang of this, check out the Help.chm in the Help\1033 folder on your product CD. Here’s a head start on what you’re looking for…
Author: Tom Acker tomac
Microsoft Enterprise Support
PingBack from http://www.ditii.com/2008/07/28/virtual-machine-manager-2007-installation/
On a Windows 2008 Member Server, I installed SCVMM. SCVMM was running fine - no Virtual machines have been created - until the time I ran DCPROMO to promote Windows 2008 Member server to a WIndows 2008 DC. From that point on, SCVMM has stopped functioning.
So, I tried to unistall SCVMM. But no luck. The following message appears "an error occurred while trying to configure virtual machine manager ID:257".
Please advise how to uninstall (automatically or MANUALLY) SCVMM.
Thanks in advance.
Theofanis Giotis, BA, MSc, PhD Cand., PMP
ITEC, Co-Founder, CEO & VP
PMI-GREECE, Co-Founder & President