You Cannot Install the Hyper-V Role on the SBS 2008 Primary Server

You Cannot Install the Hyper-V Role on the SBS 2008 Primary Server

  • Comments 4
  • Likes

[Today's post comes to us courtesy of Martina Grom, Technet Team Blog Austria]

When you install the Hyper-V Role on your SBS 2008 Primary Server the DHCP Service will no longer be able to assign IP addresses to your client machines. The reason for this is that we do not support the Hyper-V role on the SBS 2008 Primary Server. The SBS wizard expects only one network adapter and binds DHCP to that network interface.  Similar problems with DHCP can be experienced if you are using 2 NICs, this is also an unsupported topology, for more information on support network topologies for SBS 2008 see


For more information, please read these KB Articles: KB968250 and KB958829.

We do support Hyper-V in SBS 2008 environments in three scenarios, which are described here:

For further reading concerning Hyper-V and SBS 2008, please refer to:

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Thanks for the comprehensive information! My mind is now cleared with the supported data but I still need to read further.

  • I just recently setup SBS 2008 with 2 NIC's.  Disable the second NIC, installed Hyper-V, rebooted, created a Hyper-V Network on the Second NIC, and then disabled the synthetic NIC on the Host OS.  So basically the VM's run through the Virtual Network provided by the Second NIC.  Disabling it on SBS doesn't affect the VM's

    and I've heard others have been successful in getting Hyper-V going.  Really useful especially since these days you can get quite powerful servers for peanuts.

  • John,

    It is not impossible to install Hyper-V on an SBS 2008 server. However for the reasons listed in this post, it is not supported by Microsoft. If you were to contact Microsoft Product Support Services with an issue on this particular server, we would not be able to support it in its current configuration.

  • I had this problem on an Standard 2008-Server. I dont see any reason why this is not working.

    on an other Server i have VMWARE-Server which did not interfere with DHCP it worked just fine.

    Greetings from Germany