Share iT…

If you have created an export of a virtual machine on a windows 2008 R2 server and try to import the export on a windows server 2012 R2 Hyper-V host, you get the following error:

“Hyper-V did not find virtual machines to import from location”

The Problem: After some searches I found this article “Windows Hyper-V 2012 & 8.1 Hyper-V Did Not Find Virtual Machine to Import” which describes the problem I ran into.

The problem is “WMI root\virtualization namespace v1 (used in Hyper-V)” has been removed in Windows Server 2012 R2, it was deprecated in Windows Server 2012 but still exist so you could import the export in Server 2012, but it is removed in Server 2012 R2. Since Server 2012 they introduced WMI namespace (version 2 or root\virtualization\v2.

Solution: There are a couple of workarounds possible,

• First you can just copy the VHD files and just built a new Virtual machine with the existing VHD files.
• Second if you have a windows Server 2012 server you can import the machine on this server and make an export and then copy that export to the 2012 R2 server.
• Last option if the existing Virtual Machine is still on the windows 2008 R2 server, stop the Virtual Machine, copy the complete directory with VHD and configuration to the 2012 R2 server and on then choose import on the 2012 R2 and point to the copied folder.

Because virtualization becomes more and more common use and with Microsoft Hyper-V included in Windows Server at no additional costs and most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 2011 installation and never get the full benefits of the hardware. It is worth considering to virtualize the SBS 2008 or 2011 server and run one or maybe two or more virtual servers beside it on the same hardware.

In this blog post I will put together some facts, tips and considerations you should look after before you start virtualizing a SBS 2008 or 2011 server. Of course a lot of this information can also be used for virtualizing non SBS servers.

Enable Hyper-V role on a SBS 2008 or 2011 server
So if you just want to add just one other server, why not install SBS 2008 or 2011 on the physical hardware and just enable the Hyper-V role?

The answer is really simple, because it is not supported!! Enabling the Hyper-V role on a SBS 2008 or 2011 server will break stuff, for some additional information read here: http://blogs.technet.com/b/sbs/archive/2009/08/07/you-cannot-install-the-hyper-v-role-on-the-sbs-2008-primary-server.aspx

Hyper-V Host
So as we cannot enable the Hyper-V role on a SBS 2008 or 2011 server we need to install a Windows Server version on the physical hardware to function as a Host for the Virtual Machines. It is recommended that the Hyper-V Host will only hold the Hyper-V role and not to include any other roles or tasks. Only exception maybe for some management or backup tasks.

The Windows Server version we will choose is a real important decision, so let’s see what choices we have:
Hyper-V is included within Windows Server since version 2008 this was a version 1.0 and has a lot of limitations. I would not recommend using Windows Server 2008 to host the virtual machines. So I will limit to choice between the different server versions based on Windows Server 2008 R2 and Windows Server 2012.

SBS 2011 Premium Add-on
When you already bought SBS 2011, you might have bought the SBS 2011 Premium Add-on (PAO) in addition. The SBS 2011 PAO includes a Windows Server 2008 R2 standard and SQL 2008 R2 license. With Windows Server 2008 R2 Standard you have the right to install the software on a physical machine and install one Virtual Machine with the same license. This is called virtualization rights (1+1), you may do this only when you do not install any other role on the Host installation other than the Hyper-V role. When you install another role you will lose this right and need to buy a separate license for the virtual installation.

This said the SBS 2011 PAO will be a perfect consideration to use for your Host installation and run SBS 2011 and a second Virtual Machine for SQL server and / or a LOB application or even a Remote Desktop Session Host (Terminal) Server.

Memory
So the SBS 2011 PAO looks like an ideal solution, but one limitation is worth naming. Windows Server 2008 R2 standard has a 32GB memory limitation, this might be a problem when running SBS 2011 standard and also have a memory consuming SQL / LOB application. SBS 2011 standard itself with especially Exchange 2010 is a very memory consuming product, if you also need to run a loaded SQL / LOB application server beside this 32 GB might not be enough.
The Windows Server 2008 R2 Host installation needs about 2 – 4 GB, a SBS 2011 Standard for 25 – 50 users will need at least 20 – 24 GB, so this only leaves 6 – 10 GB for your SQL / LOB application server, this might be a problem. So keep this in mind if you are a growing organization and see the limit coming it is not possible to just insert more memory in your server, Windows Server 2008 R2 standard has a hard limit of 32 GB memory.

Windows Server 2008 R2 Enterprise or Datacenter
If memory could be an issue you might consider Windows Server 2008 R2 Enterprise or Datacenter, they both have a memory limit of 2 TB, this is a significant improvement. Also if you need to run more than one additional Virtual Machine you might consider both, Windows Server 2008 R2 Enterprise has an 1 to 4 virtualization right and Windows Server 2008 R2 Datacenter even 1 to unlimited. So with both version you will be far more flexible, but will cost considerably more than a standard or PAO version. Because also Windows Server 2012 is available at this moment I would not recommend these option only if you already own a license for these products it might be worth considering.

Hyper-V Server
If you do not have the SBS 2011 PAO or already have a Windows Server 2008 R2 license the free Hyper-V server might be worth considering. The free Hyper-V Server is a stripped Windows Server version with only the Hyper-V role included, there aren’t any other roles included.
The Hyper-V Server 2008 R2 has a memory limit of 1 TB and the Hyper-V Server 2012 has even a memory limit of 4 TB. There are no limitations between the Hyper-V server and the full blown versions of Windows Server, only thing is there is no graphical user interface (gui) on the Hyper-V Server. There is a small configuration menu to do some basic tasks but furthermore you need to configure and administer the server via a command window or via a remote management console.

For additional information about the Hyper-V Server look here: http://technet.microsoft.com/en-us/library/hh923062.aspx

Windows Server 2012
If you are not comfortable with a non gui server or have no ability to remotely manage the server and also not have any license available the best option would be to go for a Windows Server 2012 edition. There are only 2 version applicable, the Standard and the Datacenter version, only difference between both versions are the Virtualization rights. Windows Server 2012 Standard has an 1 to 2 virtualization right and Datacenter even 1 to unlimited. Both version have a memory limit of 4 TB so no limitation anymore on the standard version.

Client Access Licenses
If you need one or two Virtual Machines beside the SBS 2008 or 2011 the Windows Server 2012 Standard is an ideal solution.
One thing to keep in mind is that when the Virtual Machines also are installed with Windows Server 2012, the SBS 2011 client access license (CALs) are not covered. SBS CALs cover for all servers in your SBS domain but up to the same version as is the base operating system (OS) of your SBS version. So with SBS 2008 this is Windows Server 2008 and for SBS 2011 this is Windows Server 2008 R2, if you install a newer version of Windows Server you need to buy separate CALs.

Overview
Enough considerations on which OS you could install on the physical hardware as Hyper-V Host. You have to keep in mind there is not one best choice available it all depends on your situation, do you already have licenses that can be used, are you comfortable using a server installation without a gui, how many Virtual Machines do you need to run, etc, etc. To make some choices easier here a little table with the different versions:

 
Because licensing is complex material I would recommend you contact your distributor or reseller if you have any doubt about the solution you would like to choose and verify if it fits your company.
If you want to read more about virtualization and licensing I would suggest reading this excellent post: http://www.aidanfinn.com/?p=13090

 
Let’s continue with some other considerations if you could or could not virtualize the SBS 2008 or 2011 server.

SBS Backup
With SBS 2008 Microsoft introduced a wizard for configuring a backup, SBS Backup it is based on the Windows Backup but has its own configuration and monitoring options via the SBS console. It is easy to use and has no additional costs, you can configure backup to multiple disks, only thing is it only uses USB disks.

Problem is Hyper-V does not support USB redirection so you cannot attach the USB disks to a Virtual Machine and use them for SBS Backup. Of course there are some workarounds possible to attach an USB disk to a Virtual Machine, see this blog post http://blog.ronnypot.nl/?p=721 for some information, but this is probably not a supported workaround.
You can also create VHD files and attach them to the Virtual Machine and use them for SBS backup, but these VHD files are not attached and detached automatic and are not stored offline by default. You have to consider if this is a good alternative for you. Another option would be not using the wizards and interface but create command scripts using the command version (wbadmin.exe) of Windows Backup.

So if you want to use SBS Backup the way it is intended with USB disks, virtualization is not a good option.

USB redirection
As said there is no USB redirection with Hyper-V, this is for USB hard disks, but also for all other USB hardware, so no USB printers, scanners, drivers, dongles or what so ever.

Hardware
As there is no USB redirection it also is not possible to redirect some other hardware like, Fax boards, other pci cards, hardware dongles, etc.

So if you have any specific hardware that needs to be connected to a Virtual Machine you have to make sure this is possible, but in most cases this might be a configuration where virtualization is not an option.

Conclusion
The question to virtualize or not to virtualize cannot be simply answered with just a true or false, it all depends on many factors, decisions and considerations. Hope the information given in this blog will help you making the decision if you would virtualize your SBS 2008 or 2011 server or not.

 

After installation of System Center Virtual Machine Manager 2012 SP1, setup finishes without any errors, but when you try to start the program it tells the Virtual Machine Manager (vmmservice)service is not started. When you take a look at services indeed the service is not started, when you try to start the service it starts but almost immediate it crashes.

Taking a look at the System Event Log there are a couple of Event ID 7031 source: Service Control Manager events:
“The System Center Virtual Machine Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service.”

In the Application Event Log you will see a Event ID: 19999 Source Virtual Machine Manager:
“Virtual Machine Manager (vmmservice:3620) has encountered an error and needed to exit the process. Windows generated an error report with the following parameters:
Event:VMM20
P1(appName):vmmservice
P2(appVersion):3.1.6011.0
P3(assemblyName):Engine.Common
P4(assemblyVer):3.1.6011.0
P5(methodName):M.V.E.SqmRefresher.IsRefreshRequired
P6(exceptionType):System.FormatException
P7(callstackHash):5104
.”

Also in the Application Event Log you will see a Event ID: 1 Source Virtual Machine Manager:
“System.FormatException: String was not recognized as a valid DateTime.
at System.DateTime.Parse(String s, IFormatProvider provider)
at System.Convert.ToDateTime(String value)
at Microsoft.VirtualManager.Engine.SqmRefresher.IsRefreshRequired(String refreshTime)
at Microsoft.VirtualManager.Engine.SqmRefresher.RefreshData(SQMSessionManager manager)
at Microsoft.VirtualManager.Engine.RefreshDriver`1.RefreshThreadFunction(Object obj)-2146233033

Problem signature:
P1: vmmservice
P2: 3.1.6011.0
P3: Engine.Common
P4: 3.1.6011.0
P5: M.V.E.SqmRefresher.IsRefreshRequired
P6: System.FormatException
P7: 5104
P8:
P9:
P10:”

Solution:
After a couple of different approaches and reinstallation the problem solution was that I installed the Windows Server 2012 server with the Dutch region setting. So the date and time were set to the Netherlands, when I changed the Region format to English (United States) and did a new installation setup finished a lot quicker and the services stays started.

So conclusion do not change the Date and Time setting when trying to install System Center Virtual Machine Manager 2012 SP1.

When you try to migrate a Virtual Machine with System Center Virtual Machine Manager 2008 R2 from one server to another you get a processor-specific feature not supported Rating Explanantion error message:

“virtual machine ServerName is using processor-specific features not supported on host vmhost.domain.local To allow for migration of this virtual machine to a server with a different processor, modify the virtual machine settings to limit the processor features used by the virtual machine.”

This message wil appear when you try to move between to different hardware processor types. If you want to migrate virtual machines between different processor types you can check the following option within the virtual machine properties. Choose Hardware Configuration, Processor and check “Allow migration to a virtual machine host with a different processor”

This option can only be set when the virtual machine is stopped. So shutdown the virtual machine, change the setting and start the virtual machine, now you are able to migrate the server using System Center Virtual Machine Manager. It would be wise to enable this option by default if you want to create a high available solution between servers with different hardware processor types.

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

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.

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

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 to put it offline before you can add it.

Note: before you set another disk offline be sure there are no operating, system or application files on it because otherwise these or your whole server will crash.

When finished choose OK on the bottom of the screen and the disk is added to your virtual machine.

When we are going to look at your virtual machine and open Disk Management.

You will see the disk directly attached and you can use it within your virtual machine

If you would remove the drive from the virtual machine, go back to your Hyper-V Manager virtual machine settings on your host server.

Select the drive and choose remove and choose Apply or OK at the bottom of the screen.

After you have removed the disk from the virtual machine go back to Disk Management

Right click the drive and choose Online. Now the drive is available on your host server.

You can use this if you need to copy some files directly from the usb disk to the virtual machine or vice versa. Another thing you could use this is for is Windows / SBS backup this needs a local attached disk, although I don’t think this is a supported configuration! You can even if you have chosen for the SCSI controller change the backup disk when your virtual machine is running.

On a Windows 2008 R2 Hyper-V configuration with 2 network adapters I experienced the following problem: I installed a Windows 2008 R2 guest this was no problem, but when I try to do windows updates I got an “Windows could not search for new updates, An error occurred while checking for new updates for your computer. Error(s) found: Code 80072EE2” error message.

Everthing else looks fine, dns resolving works fine, network browsing looks good, I could access internet pages even the windows update page, but trying to update gives this particulary error.
Tried the same on a windows 2003 guest and everything looks fine. Installed another Windows 2008 R2 server same problem occurres.

Solution: After some more trouble shooting I found that when I start the windows update I lost network connection on that particulary network adapter, even on all other VM’s using that adapter and on the Host. Now I was connected with the other adapter so I didn’t see this behaviour in first place. So I bound the other network adapter to one of the Windows 2008 R2 guests and I could windows update with no error.

Because I would like to know what was causing this problem I found after some more troubleshooting and testing that the problem was caused by the Large send Offload setting enabled on the network adapter. After disabling this setting everything works fine.

The network adapter was causing the trouble was a D-Link DGE-528T Gigabit Ethernet Adapter.

When you try to to start a Hyper-V virtual machine on a Windows 2008 R2 server, you receive the following error:

An error occurred while attempting to start the selected virtual machine(s).

‘ServerName’ could not create or access saved state file E:\Hyper-V\ServerName\Virtual Machine\”Virtual Machine GUID”.vsv.
(Virtual machine ID “Virtual Machine GUID”)

Solution: I have no clue what caused this issue but the solution is add list permissions to the “Authenticated Users” group on the root drive where the virtual machines are placed (in this case E:). You only have to add list rights for “this folder only”.
So go to the security tab and choose advanced permissions, add Authenticated users and choose at Apply to: “This folder only”, check List permission and be sure you don’t check the replace all child object permissions with inheritable permissions from this object, otherwise you may have to restore the rights on all virtual machines permissions.

When installing SBS 2008 or SBS 2011 in Hyper-V you get the error “The User Role Cannot be found. Select a different User Role” during installation.

Solution: Problem is caused by different time zone settings. If Hyper-V has enabled time synchronization, this is the default settings, the time zone of the host and the guest has to be the same. If not this error will occur and only solution is to start over and reinstall SBS.

Recommendation is to turn off time syncronization for the SBS Hyper-V.
Start Hyper-V manager, select your SBS server and choose settings.
At the management part choose Intergration Services.

Then uncheck Time synchronization.

More information can be found here: KB 2097035

Update: error also occurs with SBS 2011.

Acronis Backup and Recovery 10 is a great tool to create images of disks, volumes or files. You can make images when windows is running and restore then easy with a bootable media to physical hardware. When using Acronis Backup and Recovery 10 Advanced Server Virtual Edition you can recover directly to a Hyper-V or other virtual machine.

To recover a image to a Hyper-V virtual machine you need to start the acronis software and choose for recover point to the image files, choose what to recover, volumes or disk.

Then choose recover to: a new virtual machine (when installed on a machine with Hyper-V role installed it automatically chooses Hyper-V as vm type)

Now you have to set the virtual machine settings. When you use Hyper-V as virtual machine type here is where to take a good look. Because Hyper-V virtual machines can only boot from a IDE hard disk type, if you choose SCSI your virtual machine wont start!

Set all further options just as you wish and you are ready to create the virtual machine. Only thing to do after the image is recoverd to Hyper-V is to attach a network card when needed.

Another possibillity when your server doesn’t start after a recovery this works for physical and virtual machines is to use the universal restore option. Create a bootable media of acronis with the universal restore option and boot from this media. During the options you can choose to use universal restore. With universal restore you are able to restore a image on a different piece of hardware because it detects what hardware is used and updates the Hal. After that you even have the option to install or update disk, raid controller drivers, so your operating system can boot with the right drivers of your new hardware.