Skip to main content

Installing System Center Virtual Machine Manager

System Center Virtual Machine Manager (SCVMM) allows you to manage multiple virtualization hosts from one console.  With other virtual management software, you can only manage the virtual machines (VMs) on the local host.  With SCVMM, you can manage the VMs on hosts running Hyper-V, Virtual Server 2005 R2, and VMWare ESX Server.

First off, you need a copy of SCVMM.  You can download a 180 day trial version here. 
Once you download a copy, you simple need to install it.  First, execute the installation file with administrative level permissions.

Click VMM Server

image

Select I accept the terms of this agreement and click Next

On the Microsoft Update window, click what is appropriate for your environment and then click Next.

On the Customer Experience Improvement Program window, click what is appropriate for you and then click Next.

On the Product Registration page, enter your name and organization.  Click Next.

The Prerequisites Check page will automatically check for required components.  Fix any errors it detects. 

Click Next to continue.

On the Installation Location page, set the installation path and click Next.

On the SQL Server Settings page, choose the SQL installation that is appropriate for you.  Provide any required information for your organizations SQL setup.  Click Next.

On the Library Share Settings page, accept the defaults and click Next.

On the Installation Settings page, accept the defaults and click Next.

On the Summary of Settings page, click Install.

It is recommended that you leave Check for the latest Virtual Machine Manager updates checked. 

Click Close.

That’s all it takes.

Comments

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...