This “issue” is by design. You can only “install the virtual guest services” while the machine is off or through Hyper-V manager which makes you reboot the computer. The install normally takes around 2 minutes but can vary due to the size of the VM.

Hope this helps.

You aren’t alone. I figured out this morning it is related to the integration components and that they are not at the same level as the server.  Months ago I create a new VM. After creating it I sys-prepped my machine and used the sys-prepped drive as part of my templates in the VMM library. Since creating the template my server got updated and so did the integration components. Because of this, when I went to go use the template I got heart beat errors because the VM and Host are not at the same level.

Lesson learned? Well, make sure that you always have the same integration components installed. Want to learn from my Hyper-V mishaps? Check out the Virtual Machine Manager & Hyper-V section of my blog.

You might be surprised that the Virtual Machine Manager Configuration Analyzer will spit this message out if you aren’t logged in as a domain admin when you run the tool!

Log off and log back on as a domain admin and you won’t have to worry about this issue anymore!

Hope this helps someone else.

I have partitioned the Machine’s drive into a smaller system drive and  much larger data drive that will house the VMM library data. I also make sure that the server has at least 2GB of ram. If you don’t the install will squawk at you but allow you to still install things. I also wanted to tell you I am installing this on a DC. Microsoft doesn’t like you installing this on a DC especially if you are wanting a self service portal. You’ve been warned.

You are going to need to download and install a few pieces of software (don’t run them just yet):

1. Microsoft Baseline Configuration Analyzer (this is needed by the SCVMM Configuration Analyzer)
2. System Center Virtual Machine Manager 2008, 2008 R2, and 2008 R2 SP1 Configuration Analyzer

Install IIS on the server

Open Server Manager and right click Roles. Click “Add Roles”.

Make sure IIS is checked off. Click Next.

Ensure that these additional IIS items are all checked off and hit Next and Install:

• Static Content
• Default Document
• Directory Browsing
• HTTP Errors
• ASP.NET
• .NET Extensibility
• ISAPI Extensions
• ISAPI Filters
• Request Filtering
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility

You should restart your machine since you just installed a feature. Once you have done this your machine should validate and everything should go very smoothly. To validate your machine run the VMM configuration Analyzer. This should now be in your start menu since you installed it in the previous steps.

If you followed my instructions you should see something like this:

Run setup on the VMM Disk

The install is easy. When it asks where to install the files I switched it from C: to E:

When it asks about SQL server I am just going to us SQL Express.

Specify a Share. Again I am moving things to E:

The rest of the install I just selected the defaults. Once it is finished updating I recommend that you run the machine through Windows Update and make sure everything is all patched and up to date.

You will most likely want to install the VMM Administrator Console. You can do this by running it off the setup program of VMM.

The install of the VMM Administrator Console is very simple. It’s your typical Next, Next, Next install. It will ask where you want to install it and what ports you want it to run on. I told it to install to the E: and I kept the ports the set to the default numbers.

Hope this helped you get VMM up and running a bit faster.

If you really want to remove the domain controller from the domain you will need to issue the command:

dcpromo /forceremoval

Hope this helps you get rid of the error: “The operation failed because: This Active Directory Controller is not the last AD DC in the domain. The server is unwilling to process the request.”

PS – Remember to uninstall the AD Binaries by using Server Manager.

Here’s the steps to setup a virtual network in Hyper-V.

Open the Hyper-V Manager and click on the the “Virtual Network Manager…” link in the far right Actions column.

Click “New Virtual Network – External – Add

Type a name into the Name field. If you only have one nic make sure that you select “Allow management OS to share this NIC”. Hit “OK”.

If you are prompted with any questions say yes. It’s going to disrupt the Virtual machine if it is running.

Go back to the properties of each virtual machine and make sure to select the network you just created and hit apply.

*NOTE* – Remember if you are installing a “dumb” OS where you can’t install MS Integration tools,  you will most likely have to remove the current NIC and create a legacy NIC instead.

pnputil –i –a E:\folder\driver.inf

You can actually use this command to install the rest of the server drivers as well

Once you type it in you’ll see the nice Microsoft Hyper-V Server Configuration tool load up.  Yup. It’s really that easy.

Some of the benefits of using Remote Desktop Connection Manager is:

• FREE!
• EASY to use!
• It allows you to group several servers into groups.
• Passwords are encrypted when you save them
• You can move fluently between many different servers at a time.
• Write notes about each server
• Save your configuration and copy them to other workstations

Being a consultant I can’t begin to tell you how much time this saves me. If you’ve never used Remote Desktop Connection Manager I don’t know what you are waiting for!

• Run the hardware diagnostic that comes on the install DVD(s) that came with the Mac (note: these will not be available on a "generic" OS X disc bought separately from the Mac). Depending on what version of OS X your computer shipped with, put in either Mac OS X Install Disc 1 (through 10.5.4) or Applications Install Disc 2 (10.5.5 or later), then boot holding down the D key; seeKB #HT1509 for details.
• If you have AppleCare, that should have come with TechTool Deluxe, which you can use to run some additional hardware tests.
• If you don’t find any hardware problems, Check the integrity on the disk. Boot from the install DVD (hold C this time, so it’ll boot the installer rather than diags), select a language, and then run Disk Utility from the Utilities menu. Select your boot volume in the sidebar, then the First Aid tab, then the Repair Disk button near the bottom right. This will run an integrity check on the volume structure (i.e. it won’t check the contents of the files, just make sure the data structures that keep track of them are consistent) and repair any problems it finds. If it finds problems, I’d recommend running it repeatedly until it gives a clean bill of health.
• While you’re still on the First Aid tab, run Repair Disk Permissions near the bottom left. This sill set the permissions on the OS files back to what the install packages specified form them. Note that it only fixes the OS itself, not user files or even third-party software. Ideally, this should be run from within the booted OS, because there are some slightly version-specific tweaks, and the OS version on the DVD is probably different from what’s on the hard drive; but it should get things 99.9% correct, and if that makes the system bootable you can then re-run it properly from the HD to fix anything the DVD version didn’t get right.
• If it’s still not booting properly after that, try some alternate boot modes to get a better idea what’s going wrong. I’d try verbose mode first: hold Command-V while booting, and (if it gets far enough) it’ll go to a text interface where it prints information about what’s happening as it boots. This won’t fix anything, but may give an idea what’s going wrong.
• Next, try running the computer in Safe Mode by booting with the Shift key down (see KB #HT1564 and#HT1455) — this disables noncritical system extensions, third-party daemons, and a bunch of other possibly-problematic system components. You’ll be missing some functionality (IIRC sound and wireless networking both get disabled), but if you can successfully boot in this mode, you’ll know the problem is coming from one of the things that get disabled in Safe Mode; play with disabling & reenabling them to isolate the problem further.
• Finally, if that doesn’t solve it, try booting in single-user mode by holding Command-S while booting. This interrupts the boot process early on, and drops you into a very minimal full-screen command-line interface. If you know a lot about how OS X works, you can dig around in this mode to find/fix problems, but at this point I’d just consider it a test: can the OS boot far enough to get to single-user mode? BTW, to get out of single-user mode, the standard thing is to use the "exit" command to continue the boot process where it left off; since that’s failing for you, I’d instead use "shutdown -h now" to shut the computer off.

Hope these steps help you trouble shoot your Mac boot Issues!