Microsoft Virtual Server

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Share tech news, updates, or what's on your mind.

Sign up to Post

Why should I virtualize? It’s a question that’s asked often enough. My response is usually “Why SHOULDN’T you virtualize?”
Nowadays, Virtual Machines are used equally by small and large scale organizations. However the issue is that VMDK files are also prone to corruption. So, in this article we are looking at how to recover VMDK files from hard disk of host operating system.

From Coral's  "So You Want To Play With Computers" Series

A bit of background first, so this story will make a little sense.

One day, probably because he needed a good laugh, Finagle hooked me up with a church to upgrade/run their Media Booth. {Yeah, I know. I've been to "Hell and back" so many times, I already have my spot picked out and homesteaded}.
Anyhow, getting time to work on their system is hard to do, so I've been dual booting to a clone of their hard drive, so I can check the music, fix/add lyrics, and set up the music schedules, at my place. Then copy the schedules for a couple of weeks to a USB stick to take in with me, and copy to their computer.
But lately they have been throwing new music at me, and booting back and forth between Vista (nic is blocked) and W7, to go online to chase down lyrics, is getting to be a pita.

So I thought I would move Vista to a VM, then I could just toggle between them. Which brings me to what follows:

After firing up my Googlefu, and doing some research, I had a few points I wanted clarified, so I posted a Q on EE, which Finagle promptly kept the VM Gurus from posting in. Looks like I'm on my own.
That's alright. I can do this. After all, I'm a self taught computer geek. I've been mucking with computers for over 25 years. And I recently took a ComTIA  A+  Cram Course, and set the new high A+ test score for that class. As a bonus, it kind of irritated the college boys …
LVL 32

Author Comment

added screenshot of Vista running in MS Virtual PC.    ; )
Few best practices specific to Network Configurations to be considered while deploying a Hyper-V infrastructure. It may not be the full list, but this could be a base line.

1. Dedicated Network

Always consider dedicated network/VLAN for Hyper-V data, CSV, Live Migration and Management.

Hyper-V Data - The NIC which will be allocated with the Hyper-V Virtual Switch and will be used by the VMs to route network traffic. Priority should be give to have dedicated network interface for Hyper-V Data.

CSV - Its good to have a dedicated interface for CSV traffic. This will be really a life saver if one of the node loose the connectivity to the storage. I had an experience where all cluster nodes except one lost the connectivity to the storage and all the VMs on the problematic nodes where have CSV on IO Redirected mode which was in fact using my CSV Network. This could be an idle mostly, however its like a health insurance - very much valuable when the accident happens.

Live Migration - This will be used only while Live Migration happens. As we have more bandwidth, the live migration can complete more faster. In short, this network will be used to transfer the Virtual Machine memory and state.

Management - Obviously, Need to RDP or access the server through remoting which needs network connectivity.

2. Bios/Firmware/Drivers

It is also very critical to make sure that the server BIOS and Firmware is updated with the …
LVL 47

Expert Comment

by:Philip Elder
I'm not sure what "dedicate an interface" means?



In one of my previous articles, I explained how to create a native Windows 2012 Cluster.  The method described in the linked article is fine as long as you don't want or need to manage your environment with this additional optional software known as System Center Virtual Machine Manager.

SCVMM brings in another layer of management not available through standard clustering, including the ability to create machines from Templates or Profiles - the ability to store virtual machines in a library for redeployment later, the ability to allow self service so that administrators can give permissions to users or departments to be able to manage and create their own machines, the ability to update virtual machines as well as virtual hosts, and even the ability to monitor software running inside virtual machines (Windows 2012 only).  Powerful stuff indeed, and I didn't mention the ability to organize your infrastructure into data-centres and clouds, which is what SCVMM can also offer.  SCVMM is a huge product - and it can do a lot of things - probably more than you need it to, but it is a vital product to help manage your virtual infrastructure.

This article is not here to teach you about SCVMM completely, because it is a huge product.  It is however here to help you install SCVMM, configuring your Fabric, and getting your first Hyper-V Cluster created through SCVMM.

Installing SCVMM 2012 Tips


Expert Comment

by:Rick Goodman
I know this was posted a while ago, wish I would have found it before I started setting up my environment. Great post. But if I already set up my NetApp with a separate LUN for each of my Standalone Hyper-V hosts and are running production machines on one of those hosts, is there a safe way without a lot of down time to create the proper storage on NetApp (which I have plenty of unassigned disks yet) and then cluster the Hyper-V hosts?
LVL 37

Administrative Comment


Since this is an article, we encourage you to open a question, once you have done so, you can post here so LesterClayton can have the opportunity to participate.
Every once-in-a-while, when you try to add a XenServer host to the System Center Virtual Machine Manager console, it will generate a certificate error, and the XenServer host will not be added to Virtual Machine Manager:
Certificate ErrorIf you are experiencing this issue when you try to add a XenServer host to System Center Virtual Machine Manager, here is the procedure you can follow to import the XenServer certificate to the the SCVMM server so that you can add the XenServer host to your System Center Virtual Machine Manager console.


Open WinSCP and connect to your XenServer via SFTP using your root login:
WinSCP Connect


Go up one directory level by clicking on the top folder in the pane on the right-hand side:
WinSCP Browse 1


Then go to the etc folder:
WinSCP Browse 2


Then go to the xensource folder:
WinSCP Browse 3


Copy the xapi-ssl.cer file from the XenServer to you SCVMM server:
WinSCP Copy Certificate


On your SCVMM server, rename the xapi-ssl.cer file to the FQDN of your XenServer (e.g. server.domain.local.cer)


Click on the Start menu, then click on Run (or hit the Windows Key + R), and type mmc in the Run dialog box and hit OK:


Click on FileAdd/Remove Snap-in... (or hit Ctrl + M):
Add Certificates Snap-in


Click on Certificates, then click Add >:
Add Certificates Snap-in 2


Select Computer account, then click Next:
Add Certificates Snap-in 3


Select Local computer, then click Finish:
Add Certificates Snap-in 4


Click OK:
Add Certificate Snap-in 5


Expand Certificates (Local Computer)Trusted People:
Import Certificate 1


Right-click on Certificates and select All TasksImport:
Import Certificate 2


Click Next:
Import Certificate 3


Click Browse:
Import Certificate 4


Select the server.domain.local.cer


RemoteFX is already in use today, but you're probably not aware of it.  With the advent of Windows 2012 and Windows 8, RDP has gotten a whole lot better due to the fact that RDP now uses even more RemoteFX technologies to make desktop sessions a lot smoother, faster and feature rich.  You could even stream a 720p video without RDP skipping a beat - how cool is that?

Of course, RemoteFX does rely on the underlying hardware to make things a bit zippy, but when you're delivering content through a server which generally has a poor graphics card, then the performance isn't that great.  Try it!  RDP to a physical Windows 2012 Server, and try to play a 720p video.  Performance is poor and choppy, despite you having a gigabit connection to the server.  That's because the server isn't designed for multimedia, and the graphics card is a built-in bog standard one with virtually no hardware acceleration.

Of course, the solution to this is to add a GPU.  So, take the same server, chuck in a reasonably decent graphics card, and play the same video - then voilà!  Brilliant display.  Lack of sound?  You probably should have remembered to enable the Windows Audio service!

Thing is - most organizations are retiring their physical servers running Remote Desktop, and replacing them with bigger, beefier servers which are becoming part of Hyper-V clusters and they're now running Virtual Servers to provide the Remote Desktop solutions.  

This article is intended …
LVL 19

Author Comment

Yes, but I think you may have done it already as I received an e-mail saying "Congratulations! Your article "Implementing RemoteFX in Windows 2012 Hyper-V" was voted helpful by one of your peers, earning 50 bonus points." :)  Thank you.
LVL 24

Expert Comment

Yep I bit the bullet and clicked it!! Cheers...


Windows 2012 is here - it is upon us, and I hope that like me, you will upgrade your Hyper-V to the new version which has been promised to be a lot more stable, flexible and powerful than its predecessor in Windows 2008 R2.  Setting up Hyper-V in a clustered environment is relatively easy, and this guide is intended to help you along the way.

I'm not going to bore you with screenshot after screenshot, and I'm only going to screenshot interesting or key bits.

This guide will not cover:
The installation of Windows 2012
The installation of SCVMM 2012


You will need the following:
One or more servers with one or more network interfaces in each
Windows 2012 installed (you can choose to use Standard or Datacenter, Gui or Core)
Shared Storage attached.  (Remember to install MPIO and DSM's where necessary)


If like me, you are intending to take advantage of Microsoft's Teaming which is a built in part of the Windows 2012 Operating system, then you should team the network interface now, ready for the Hyper-V Role installation.  Do it as follows:

NIC Teaming
Find "NIC Teaming" through Server Manager
Click on "Disbled" to bring up the teaming dialog box

Add To New Team
Select the ports you want to add to the team, right click and then select "Add to New Team"

New team
Enter a name for the team (this can be anything, and doesn't have to be the same name on all hosts in the cluster)
LVL 23

Expert Comment

by:Malli Boppe
Greate Article Lestar.
Really very helpful.
Was looking for some thing like this for last few weeks .

Expert Comment


   Thank you for posting the article and it has come out nice.

When working with Microsoft SCVMM (System Center Virtual Machine Manager) in a Hyper-V virtualization environment, we have run across scenarios in which the failed migration of a VM from one host to another may leave the VM in a failed state. Specifically, in the SCVMM console, the VM has a red 'X' beside it with the "Migration failed" under the status column. While the VM is in this failed state, SCVMM will only allow you to Repair, Delete, or View networking of the VM. Furthermore, if you right-click the VM and select 'Repair', the option to 'Ignore' is unavailable, and the 'Retry' and 'Undo' options fail. Even though you may have corrected the problem outside of VMM, for example using the Hyper-V Manager console, the repair options yield no results.

We have read many articles and posts on how to deal with this scenario, such as removing the host from VMM and adding it back. Or using SQL Server Management Studio to hide failed jobs (NOT a good idea as it can eventually lead to poor SCVMM performance since the VMM cleanup process will skip old jobs that are hidden!). Once you have corrected the problem and exhausted all possibilities to remedy the situation, here is a handy PowerShell script that will help you out of this jam, which we pieced together specifically for this situation.

First, a little peek under the hood:

- When the migration fails, the ObjectState field in SQL for the VM gets set to 220, indicating a failed state.
- If the ObjectState field for a VM…


I've already written articles on how to set up a Hyper-V Cluster (, and how we can benefit from Microsoft licensing grants within Hyper-V (, but there is really more that needs to be told - for everybody's benefit.  These that you see here are "gotchas" - which means you could easily be caught out.

Power Mode affects Performance

Windows Servers (and workstations) very thoughtfully set our power mode on all new installs to be "Balanced".  What does this mean exactly?  Well, take a look at the two screenshots below, and see if you can spot the difference (apart from the time).



The first image has the default power mode of "Balanced" and the second image has the power mode of "High Performance".  The difference between the two pictures is the value for "Speed".

Consider this:  Your physical server default installation has it's processing power reduced by half automatically.  Any guest machines you have also have their processing power reduced by half.  This is hardware assisted virtualization, sure, but the Hypervisor is still responsible for allocating time slices, so effectively, on a standard installation, your virtual machines may be operating at around one quarter of the maximum speed.

To get around this, change your power plan on all your physical hosts as well as virtual hosts to be "High …
LVL 10

Expert Comment

Hi, very usefull info.

I'm currently looking at implementing a Hyper-V cluster, but need to have some fault tolerance. Have you got any experience of using replication or syncronisation software and having redundant servers?

LVL 19

Author Comment

Hi there Wayne.  I sure do have experience in that field.  If you're about to implement a Hyper-V cluster may I suggest you read one of my other articles.

Guide: Creating a Hyper-V Cluster

If you have any specific questions, be sure to ask it on the site.  If I find it and nobody else has answered, I'd be happy to help.
Guide: Build a Hyper-V Cluster


We all know that Hyper-V is a cost effective solution (see, and now we want to take advantage of it, right?  Unfortunately, hardware fails, leading to downtime, angry people, and depression.  

We don't want that, so this guide is going to take you through building a fully fault tolerant Hyper-V Cluster.

This guide is intended for people who have at least a little experience with Windows Servers.


In order to follow this guide you will need:

2 or more Physical Servers
Shared Storage - iSCSI or Fiber Channel
A few cans of coke to keep you going.  Coffee is also acceptable.
Windows 2008 R2 SP1 Standard, Enterprise or Datacenter.  You can get away with Windows 2008, but I highly recommend at least Windows 2008 R2.  You can also perform these steps with demo versions of Windows 2008 R2, or Technet/MSDN subscription editions.
A domain and an account with Domain Admin privileges.

If you wish to cheat, and do this purely for fun, you can create two Virtual Machines in something like VMware or even Hyper-V - but you will still need access to shared storage.  In this situation, I would recommend a cheap NAS which supports iSCSI (for example, Synology or Drobo)

This article is not going to cover configuring or attaching the storage to the server - because…

Expert Comment

Do you any article for attaching or configuring storage to server ? please share with us if you have. thank you.
LVL 19

Expert Comment

I have two articles regarding storage, but the 2nd is in editorial review right now since I've made some modifications to it.

Storage Explored, Explained, and Exampled

HOWTO: iSCSI with Multi-Path in a Windows Server Environment


Many people don't know about it - and it's almost like a huge secret, but Hyper-V is one of the most cost-effective Virtual solutions out there, and I'll tell you why.

In a single word - Licensing.

The Breakdown

Microsoft give allowances for additional copies of its operating system for running in a Virtual Environment, and the breakdown is as follows:

Licensing Matrix
The good news is that you are also licensed for lesser editions of Windows too!  Scenarios of how you could utilize these license allowances are:

If you buy Windows Server Standard, then you can run Hyper-V inside it and install Windows Server Standard again.  A good example of this would be your Host Server can be a Domain Controller, and everybody knows that Exchange server is not recommended on a Domain Controller, so you can install Hyper-V, and run Exchange in your Virtual Server.
If you buy Windows Server Enterprise, then you can run this server and host 4 machines inside.  1 x Windows Enterprise for your Domain Controller/Certificate Authority, 1 x Windows Standard for another Domain Controller, 1 x Server for Exchange and 1 x Server for File & Print.

You can also combine the licensing allowances - For example, if you have two Enterprise licenses, you can run 8 Virtual machines across 1 server, or mix and match between the 2 servers.  2 + 6, 3 + 5 - it's all fine.

And the Ultimate Money Saving Hair-Brained …
LVL 20

Expert Comment

by:Svet Paperov
@Lester_Clayton, it is not correct to give licensing advices to the users here without at least providing your source.

You need to mention that if all Windows Server Standard or Enterprise virtual licences are used, you should not have any other role, except for Hyper-V role, running on the host.

Also, you CANNOT combine virtual Enterprise licences on a single server – this is a licence violation. With 2 Windows Server 2008 Enterprise you could have up to 8 virtual machines on 2 separated physical servers (2x4) but up to 5 Virtual machines on a single physical server.

Here is more information about licensing for virtual environment:   

In any cases, you, the user, should consult with a Microsoft sales representative before making decisions about Microsoft licensing.


There are many ways to achieving a goal - some are wrong, some are right - and some just appear to be right, but are wrong.  Hyper-V Clustering and VMM has taught me all three, and I'm here to share with you how to avoid the pitfalls I've fallen into when it comes to Pass-Through Disks.

What is a Pass-Through Disk?

A pass through disk is a disk which is given to a Virtual Machine using a partition visible on the host - and not through a VHD file.  The benefits of a Pass-Through disk includes:

Pass-Through disks can be increased on the fly without shutting the virtual machine down
Faster IO throughput than a VHD file, because of the lesser overhead
Defragging a pass-through disk actually is useful (as opposed to defragging a dynamically expanding VHD file)


This guide is assuming you already have shared storage in place, and have 1 or more hosts part of a cluster and connected to the same shared storage.  This guide is not here to deal with creating a cluster, configuring shared storage, or configuring Cluster Shared Volumes.

This guide also requires you to do most of it using Failover Cluster Manager - at the time of writing SCVMM does not have the ability to add pass-through disks, but fortunately does support Virtual Machines which have them.

Step 1: Creating and Preparing the volume

Naturally, a pass through disk needs - well, a disk…
LVL 70

Expert Comment

by:Jason C. Levine
Excellent.  This is not anywhere close to my area of expertise but I'm able to follow it and probably could implement it :)

Thank you.  
As the most of you know, Hyper-V does not support usb redirection. But with some relative easy steps we can redirect our usb disk to a Hyper-V virtual machine.

First on your Hyper-V Server host open Server Manager and select Disk Management

Attach USB disk to a Hyper-V 1
Then select your usb disk and right mouse click and choose Offline.

When done we close Server Management and open Hyper-V Manager. Select the settings of the virtual machine you would like to attach the usb drive to.

Attach USB disk to a Hyper-V 2
Select IDE Controller or SCSI Controller. Before you choose let me explain why I would choose the SCSI controller instead of the IDE controller for an usb redirected drive. A Hyper-V virtual machine can only boot from an IDE hard drive, you can only add a dvd drive on an IDE controller, you can only add 4 IDE devices. Another thing I would prefer to add an usb disk to the SCSI controller is I can add or remove disks to the virtual machine when it is running, to add an IDE controller disk I need to stop the virtual machine then add the disk and then start the virtual machine.

Now to add your usb disk to you virtual machine we choose Add

Attach USB disk to a Hyper-V 3
Now we choose for Physical hard disk: and choose the disk we would to add. If you have more disks available you can choose from a simple pull down list. You will only see here the disks that are set to offline so that was the first step we had to do. If you would like to add an internal hard disk you have…

Expert Comment

Anyway I can make a USB modem work. I have an application that faxes out invoices and need to use a fax modem and need to somehow figure this out. Thanks
LVL 26

Author Comment

Hi, as described there is no usb redirection in Hyper-V this is only a workarround to map usb disks not for other usb devices.
The purpose of this article is to help people install Ubuntu 10.04 on Windows 2008 R2 Hyper-V.

Some of the issues many people face in installing Ubuntu 10.0.4 on Hyper-V are the following:

1.      No Network Connection
2.      No Mouse functionality when using Remote desktop

First of all let me make it clear that when installing Ubuntu 10.04 you do not need the Linux Integration Components download from Microsoft.  That’s for earlier versions, not for Ubuntu 10.04.  

You will also need to run the install from the server box and not remotely unless you are using the keyboard keys only.  The mouse will not work if you do it remotely.  That will come later on in this article.

The first thing you must do is setup up your Virtual Machine correctly.  That’s pretty easy because the only thing different you’ll be doing is setting up the Network Adapter.  Instead of the regular Network Adapter that’s normally used in creating Windows VM’s, you’ll want to use the Legacy Network Adapter which is what will work correctly with Ubuntu 10.04.  

Once you add that hardware in, you can boot Ubuntu from the CD or ISO.  If you’re going to boot from the CD, create the VM first and select to install the OS later.  Once you have the VM created, go back to your settings and on the DVD Drive selection, select “Physical CD/DVD Drive”

Run the installation

Once the installation is complete, it’s time to configure the Network Connection.
You can choose to use DHCP or Static.  I chose …
Hopefully if you are reading this article you have NOT attempted to use an old Hyper-V snapshot on a Domain Controller.  If you have, you're probably beyond frustrated as you have searched Google relentlessly only to find out that doing a snapshot on a Domain Controller is NOT recommended.

Relax, things get better.

I just recently restored my Primary Domain Controller (PDC) back to it's original state after making the same mistake.  Hopefully this article will help you in order to solve your issues.

First thing first.  Let's discuss all the errors you're probably getting.  After I reverted back to my older snapshot, all hell broke loose.  I wasn't able to replicate to the other domain controllers, group policy was failing, I couldn't UNC (\\Servername) to other domain controllers but could do it only by IP Address, and things only got worse.

Sound familiar?  Good.  You're in the right place.  Let's move past all this reading because I'm sure you're just wanting to figure out how to resolve this issue.  This is the steps you're going to have to take.

1. Use Netdom.exe to Reset Machine Account Passwords
2. Transfer Roles to other Domain Controllers in the Domain
3. Demote Domain Controller
4. Remove Metadata
5. Promote Domain Controller

Okay, seems like a lot, but it's not that bad.  Let's delve into the specifics.

First thing I done was followed the article below on how to reset the password on all the domain controllers.


Expert Comment

Bookmarking this for future reference. Thanks for writing!
I have been plagued with this issue more than once, shut down my Hyper-V VM using the Hyper-V manager native to server 2008 because of disk space issues. This VM in question holds our office Sharepoint Server, the Sharepoint Databases are backed up using Backup exec.
So the machine is now shut down after a 6 hour merge (What it is merging I have yet to figure out as it did not even seem to help me), I selected Edit Disk from the Actions menu on the right side of Hyper-V manager browse to the disk and select it, this gives a little disclaimer that you should not edit a Virtual Machine if it has a snapshot or differencing disk. I admit I sometimes skip reading small unemphasized print like this, It is obvious that Microsoft knows this is an issue judging from all the posts on the and hopefully they will roll out a SP to fix this, many people have fallen into this trap and I am sure many more will until this is fixed. So here is where things went bad, made the disk 60GB from 50GB, thinking nothing of it I turned on the machine 5 minutes before quitting time and after 50% of starting I received this infamous error:

'SERVERNAME' Microsoft Emulated IDE Controller (Instance ID {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to power on with Error 'One or more arguments are invalid' (0x80070057). (Virtual machine CFB19551-4BB9-4B30-8EC7-1A461C2F6A33)

'SERVERNAME': Failed to open attachment 'D:\Images In Use\Server 2008 x64 …
Hyper-v Network Card not working

There are two common mistakes that people make when they setup a Hyper-V VM.

First problem is that they don't install the integration components before they start troubleshooting problems with the Hyper-V VM functionality. One thing the integration components do for the VM is to give the VM a network driver.

Second problem is that they assume that the network driver will be installed during the installation of the VM but that is incorrect you must install the integration components within the VM for the network driver support. If the VM needs to be installed through a PXE boot then you must install a Legacy Driver for this support before you install the OS.

Now I have ran into problems even with the Integration components being installed the Network driver installed by the integration components won't be recognized by the OS. What the fix for this issue is to use the Legacy Network Adapter.

To install the integration components

Before you start make sure you have installed the most current Service Pack and updates for the Guest OS. Make sure you restart the Guest OS after installing the updates.

1. Logon to the Guest VM with Administrative rights.
2. From the Hyper-V menu select the Action Menu and choose the Insert Integration    
    Services Setup Disk option within the menu.

Once you have done the two above steps the installation of the Integration Services should start automatically. After the installation you …

Expert Comment

Also, if you did try Install "Integration Services" to Windows Server 2008 or Vista without SP2 installed, you may have same kind of problem.

Follow trick was helpfull for me:
run msconfig
on "boot" page click "Adcanded options" click "Detect HAL" and reboot

Expert Comment

Make sure that when your using the Legacy Network adapter only use 1 cpu in your Hyper-V CPU settings.  Then once you have the Hyper-V Linux Integration Services installed then the multiple CPU works.  I spent a week trying to work this out.

Microsoft Virtual Server

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.