Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

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

Sign up to Post


Quick Hyper-V Question...

Setting up a small customer with two Hyper-V hosts to run a few VM's The hosts will not be domain joined

When I set up management NIC's can they be on the same subnet as the VM's as long as they have dedicated NIC's?

Trying to keep the setup as simple as possible or is same subnet a definite no-no?

Cloud Class® Course: Microsoft Exchange Server
LVL 12
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

WE are trying to convert a Physical SBS2011 and a server 2012 R2  standard to virtual
We have not had any luck with using disk2vhd.

We are getting BSOD with the SBS2011 with error 0x0000007B
I looked up this error and tried everything to running fixmbr and boot commands.

Now I'm trying Microsoft Virtual Machine Converter.

Does anyone know of any other fixes for there errors or better conversion tools that will work?

How can I enable the dedup module in Windows 10? It should be possible: https://docs.microsoft.com/en-us/powershell/module/deduplication/enable-dedupvolume?view=win10-ps
But I don't have the enable-dedup cmdlet or import module dedup.
I'd like to use it for running hyper-v machines.

Please advise.

I have a dc and i have used VMware converter standalone to get my secondary dc and mail server online in vmware workstation. I am able to ping mail server and secondary dc.

Problem: When I create a vm for my primary DC i get the following error when it is booted in vmware workstation 0xc00002e2

What can i do to fix this.

I have tried using other tools like disk2vhd as well and ls it works fine in hyperv without any errors. If i install hyperv on the same machine i get errors when vm's load up in vmware

I have also used shadow protect to backup but it was unable to boot on vmware and gave the same error 0xc00002e2

I have also tried the following

exact error
Your PC ran into a problem and needs to restart. We're just collecting some error info, and the we'll restart for you. (%% complete)
If you'd like to know more, you can search online later for this error 0xc00002e2
Can I change the IP address of a Domain Controller without messing things up?
Windows 2016 Hyper-V Manager, 2 guest VMs (one DC and one Database) and a bunch of Windows 7 Pro PCs (DHCP)
We are setting up our First Virtual enviroment in Hyper-v.

We want to know if its best practice to have the file server separate from the DC.

Or should we just create a C: drive and a separate Partition E: on the DC for the shared folders.

we do have enough licenses for 3 VM's.

Also we would like to know what is the difference between raid 5 and 10 for redundancy?
Ultimate goal is to have RDS running on server 2016.  Per Experts advice, I have now re-created new physical server as Server 2016 standard running the Hyper-V role; created 1st vm as serverA running Server 2016 with roles of ADDC, DNS, DHCP; 2nd vm as serverB with Server 2016 and attempting to add RDS role quickstart deployment.  I see this server but it states that cannot deploy because "unable to connect to server by using Windows Powershell remoting".  Both servers are in same domain, can see one another, have only 1 user, administrator, so far, firewalls on both are turned off, tried Powershell Enable-psremoting -force on both.  I am new to virtualization and don't know if I have missed steps in the setup of these 2 servers that would cause this issue?  Are there networking issues I am missing?  Where do I go from here?  Any help is appreciated.
I am wanting to set a user up with a roaming profile. they have a surface they use at the office. When they are out they vpn in to connect to resources. I am setting them up a hyper v machine that I want to look and feel like there current desktop. Any ideas on this one.
I've got a Win 10 Pro laptop with 16 GB of ram. I've got Hyper V installed & another Win 10 VM running on it, for working with point of sale software.
In settings, I've specified 8 GB of ram, dynamic is enabled, 512MB min & 1048576 max (not sure where I came up with that).
System properties shows 7.91 GB installed & 1.88 available, which is about what task manager shows.
How can I increase this? Uncheck dynamic?
I'm in the middle of a project & didn't want to start tinkering with things, being wary of the Murphy's law thing...
I have a Hyper-V Manager in a workgroup on and a Freecom NAS drive on Both are in a workgroup called JGL.
When creating a new VM I point the .iso location to \\\Software\server2016.iso which it accepts but when I click finish I get the error:
From Windows Explorer I can map to \\\Software and I'm prompted for a username and password and I click "remember" (subsequent connects don't require credentials)
I can't see anywhere in Hyper-V where I can enter credentials.
Get expert help—faster!
LVL 12
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Server 2016 Standard with two running Hyper-V VM's. One running as the PDC and the other as the Exchange server. Months ago we had to turn off the original Exchange server because it was having problems and Dell didn't ship the operating system. To get exchange up and running  we installed a third VM using a trial version of Server 2016 Standard. This configuration has been running for months without any errors. To clarify VM's; 1. PDC, 2 Exchange (original), 3. Exchange2 (2016 trial version).

The VM running the trial version of Server 2016 (Exchange2) we want to power down and migrate the exchange server, or EDB to the original Exchange VM.

What is the best way to move the exchange server from one VM to the other? Ideally with the least or no downtime to end users? Is this possible?

As of now I've copied the EDB from Exchange2 and am thinking of using a tool to migrate this from EDB directly into the new server.
I have a Windows 2016 Hyper-V manager with two guest VMs. One guest VM is a Domain Controller and the other is a SQL DB server which is a member of the domain.
The Hyper-v server is in a Workgroup. Should I make the Hyper-V server a Domain Controller for a separate domain and then make resources such as a NAS, members of that domain?
I'd like to access the NAS from the Hyper-V manager for VM builds and Disaster Recovery and I'd also like to access the NAS from the Guest VMs for software images.
Using Server 2016 Hyper-V, I'm comparing Dynamic vs. Fixed Disks using 10,000 RPM SAS drives and a Dell PERC H730.  
I have currently set all four partitions on the two VM's to dynamic disks but wondering if it is worth the effort to convert them all to fixed disks.
The partitions are all using VHDX files (two partitions for each VM--operating system and data for each).   According to this web page, dynamic disks are actually faster in "overwriting" than fixed disks so perhaps I should keep the disks to dynamic:
Thank you.
Can two Hyper V Hosts be configured to see the same shared SAN storage like vCentre does for clustered Esxi hosts ?
I have a management console on a Windows 7 VM. I need to create on for a new site. The software is exactly the same, just needs a IP change and a few configuration changes to create on for a new site. Can I copy the VM I have an reconfigure it for the new site. It will set on the same Host. I know how to import and export the VMs but not sure what I need to do for the domain to see it as a new PC. Please advise. We use Windows Server 2012 R2 standard and Hyper-V.

New creating VMs so any recommend links would be appreciated as well.


I was reading the above mentioned article, and it appears to suggest not using dynamic disks if at all possible.  It suggests not using dynamically expanding disks because of reduced performance by increased overhead and fragmentation.

I usually assign the guest VM OS as a fixed disk.  This also applies to virtual disks with databases.  However, for growing company file storage, I usually assign the virtual disk as dynamically expanding with a cap imposed.

I will be installing a new Windows 2016 hyper-v server with two vms.  On one of the two vms I was going to assign the guest os (80Gbs) and a database virtual disk (150Gbs) as fixed virtual disks.  Their company data is currently at 330Gbs, and growing, and I was going assign it as a dynamically expanding disk with a cap of 800Gbs.   As a rough estimate the amount of disk space will probably double within 4 or 5 years.

After reading this article, I may want to consider assigning this virtual disk as fixed (800Gbs), and be done with it.  I understand, a large fixed disk has drawbacks when it comes to moving/restoring the entire drive should that be necessary.  However, fragmentation is just as an important issue over the near/distant future.  Also, I purchased this server with a more than adequate amount of overall disk space to last many years, so disk space is not …
I would like to know from expert who have experience to convert physical server which is running window server 2018 r2 to hyper-v 2016 virtual machine .

I check on the hyper-v 2012requirement the guest machine is atlease window server 2012.
I have 2 windows 2016 hyper-v hosts in a workgroup and I plan to join those 2 hosts to domain.
Hosts have 2 DCs(2008r2) as a guests VMs and couple other member servers.
Reading this article I dont expect problems running DCs on domain joined hosts
Should I expect any problem if I join hyper-v hosts to domain?
I plan to shutdown guests VMs and join host(s) to domain and than power on guest VMs.
Using Windows 2016 Hyper-V I have created a couple of VMs and a Test VM so that I can prove my backup and restore process.
I have successfully backed up my Test VM and so have now deleted it using the Hyper-V Manager. Using Windows Explorer I have also deleted its associated Test.vhdx file. However, there are some .VMRS files that I can't delete because they are in use
Delete errorHow can I remove these files
The 14th Annual Expert Award Winners
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!


2 windows 2016 with hyper-v role in a workgroup(2 hosts in a workgroup)

I have 2 guest DCs(2008r2) on one host and I need to migrate one DC on another host.

Since hosts are in a workgroup live migration is not an option?

Is this proper way to migrate DC on another workgroup host?


Its DC server,so Im careful because I dont want to change SID or something like that J

So,I just need to copy(or cut and paste?) vhd disk(without configuration files?) to another host and attached to new VM?

Is there anything in this process to pay attention?

I got an rdp session to a Windows 2016 server which has hyper-v.
When I connect to a Hyper-v vm and go in full screen, this works fine, but I cannot exit! Whatever I try ctrl + alt + home, ctrl + alt + break, it just gets me out of the rdp session not out of the hyper-v!

Please advise.
Hyper-V server with two Windows 2016 VMs.
BackupAssist on the Hyper-V manager and attempting to perform a System Protection backup to a LAN connected NAS drive.
The Hyper-V Manager is in a Workgroup. The two VMs are in a domain - VM#1 is the PDC01 and VM#2 is DB01 (SQL Server).
When I run the backup for PDC01 I get error "The backup of volume (EFI System Partition) (100.00 MB) could not be completed."
Running a HYPER-V host (Windows Server 2012 R2 Data Center), with 11 vm's connected via NIC Teaming connected to an Aruba 2920-48G Switch, 3 of the vm's are suddenly not able to connect (yellow explanation sign reads 'no Internet connection'). NIC cards shows no issues and NIC Teaming has all green up arrows. No issues in the event logs.

I removed the static IP's from the servers but they still won't connect to DHCP (with error 'unidentified'
I deleted the virtual NICs and recreated (same issue)
I checked DNS and there are no issues jumping out at me
I replaced all of the Ethernet cables on all NIC's on the server
I logged into the switch and didn't see any issues

I have never seen anything like this. Is there another area that I should be looking at? My fear is that more servers will lose connection and I am at a loss as to why.
We are assessing a server that has two virtual servers (SBS and a remote desktop server).  The host is running Win2008 R2 standard.  In the Hyper-V setup, there are two virtual switch.  One for each virtual server, SBS and the Remote desktop server.  Is this necessary or a misconfigurations?  From my understanding, we just need one virtual switch to accommodate both VMs correct?
I have a Windows 2016 server(Domain Controller and Certification Authority).  I am running Hyper-V.  I have two virtual machines.  The first virtual machine is I have installed and configured Remote Access Server(setup for VPN only) role.  The second virtual machine I have installed the NPS (radius server).  I the needed certificates enrolled.
My goal is to have the Remote Access Server function as a VPN server.  I want to have a BRANCH office have the ability to:
1.      Connect to the VPN server
2.      Use Remote Desktop Connection to connect to a domain computer at the MAIN office.
Both offices have the Xycel VMG4325-B10A routers sitting on the edge of the network.  
Both offices have access to the Internet through the Xycel router.
I have VPN ports(UDP and TCP) on an ACL list and I have Port Forwarded.
When I set up the client for VPN I am using the FQDN name of the VPN server. I am unable to connect
I am missing something?  Asking for assistance.


Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.