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

What would be a good SAN recommendation to back-end (3) Dell R440 servers running VMware or Hyper-V?  Solution is not only for running VM load, but disk backups and Azure copy. 80tb would cover storage load that includes double growth.  And what would be best connectivity option for them?
I have a Hyper-V VM with Server 2016 and added the role for AD.
I added my first user and tried to connect but that the AD Domain Controller could not be contacted.
... an error occurred when DNS was queried for the service location..... DNS name does not exist. BTW my domain name is AGHSRV.LOCAL    
Not sure if using local is good or not??

So in my VM under the DNS section is error id 4013 ,  The DNS server is waiting for Active Directory Domain Services to signal that the initial synchronization of the directory has been completed.

I'm not sure if this error is playing into it or not.
Step 5.5 of https://www.tenforums.com/tutorials/143381-windows-sandbox-how-configure-windows-10-a.html shows how to do a FRESH install Google Chrome each time I start my Windows Sandbox.

Does anyone have a QUICK way to load a "SANDBOX" without having to reinstall the software I want on my "SANDBOX" each time I am scanning a file for viruses/etc ?

 1. start "SANDBOX"
 2. scan file via Symantec AntiVirus installed on "SANDBOX"
 3. if Symantec does not find a virus, then open Word/Excel/etc file on "SANDBOX"
I've been trying to research this, but don't have the right terms. I have a 3-node Hyper-V 2019 cluster. I have read that directly connecting Nic ports is possible, and that you have the benefit of a 10Gb NIC for migrations if you set this up correctly. Any idea what this is called? Here is the equipment I am working with:
3x HP DL360 Gen10 servers with 8x1Gb NICs(I believe Broadcom but not sure- branded as HPe)
3-switch stack of HP Aruba 3810m switches
I was thinking of taking two NIC's on each server for this and connecting as follows: Server 1 port a to server 2 port a
Server 1 port b to server 3 port a
Server 2 port b to server 3 port b
Which should allow for a fault-tolerant Hyper-V network.... but I can't find much on this- Do I need to use a crossover cable for each connection? How do I configure this? What are the terms involved (You would be amazed how many web pages contain the words "shared" and "Nothing"!)
I appreciate any ideas.
I'm creating two Hyper-V  VM's.  One for AD and one for Exchange.
The underlying OS is Server 2016 Standard.

I've installed the first VM with Server 2016 in prep for AD first before Exchange.

I have one built in Gigabit Ethernet port and I have installed a Ethernet card that has two ethernet ports.

What I don't know is how to use that 2 port Ethernet card with each having a static ip for the two VM's and how that all plays into the Virtual Switch (if it does?)
Looking for a backup solution for multiple servers at multiple clients. We have a 40tb server with ftp at our office as the hosting server. Need to be able to do incremental backups, restore via web would be nice, the clients need to be able to access a web interface and see their backups, logs etc. Email notifications are essential. We tried duplicati but it crashes on most clients (files in use maybe). Trying URBackup but its slow. Hyper-V support is a plus as well as MS SQL backups. Free or Paid is fine.

Just as the title states, we have nearly 80 Hyper-V workstations and servers and are considering moving all non-DCs to Azure.  Is there a checklist, good read and/or best-practice guides out there I can go through and pitch to my superiors?  I like Azure for it's availability sets, fault tolerance, backup, and the ability to scale up and/or out - dynamically.   Do we also save "significant" money on licensing?

  Sign In Error in Windows Server 2016 EssentialsTemporary ProfileProfile List in RegeditI am getting a Sign In Error when I log into Windows Server 2016 Essentials that is running Hyper-V. The computer name is HYPERV.
When I open C:\users folder, I see three TEMP folders - TEMP, TEMP.HYPERV and TEMP.HYPERV.000.
 I don't know why they are there and how they are created.
 There are only two accounts that I created - administrator and wgladmin.
 How can I remove these TEMP profiles and prevent this from happening?

Create a new blank virtual hard diskDynamically expanding vhdxVirtual Hard DiskDisk ManagementMy ComputerHi,

 I have a question about how "dynamically expanding virtual hard disk" in Hyper-V server.
 In the past, whenever I create a virtual machine in Hyper-V, I always used "Fixed Disk".  
 This time I decided to "dynamically expanding vhdx" after reading some articles favoring "dynamically expanding virtual hard disk" over "fixed hard disk".  
 In this particular virtual machine, I decided to create two vhdx. For OS, I created fixed 50GB vhdx as you can see in "My Computer" screenshot.
 For Data partition, I created a new hard disk in Hyper-V Manager by choosing VHDX format & Dynamically expandin & entering 127GB (default value) in Create a new blank virtual hard disk.VM Settings After adding this 2nd vhdx "DC1-1.vhdx" in under SCSI Controller in VM settings, I started the VM "DC1". When it came up, I added this vhdx file and assigned drive letter "E".

 My questions is this:
 I will need much more than 127GB eventually. But instead of trying to create 400GB Fixed VHDX which took forever, I chose dynamically expanding vhdx, after reading those articles that favored dynamically expanding vhdx over fixed vhdx.
 I will need to copy files/folders (over 150GB)  from old server to this E Drive (which shows ONLY 126GB free space in My Computer,
 Since this VHDX file is supposedly expand automatically, would I be OK when I copy 150GB files from old server to  this E drive (126GB)?
I have Windows Server 2016 Hyperv Host with 2 internal 10Gbps NICS.  I also have an added a 3rd server 1Gbps network card in PCIe slot to use specifically for management of my HyperV Host.  I have 6 guest OS windows server VMs running on that HyperV Host.
I have 2 virtual network switches created using each of the two 10Gbps physical nics that exist on the Host HyperV Windows Server.  Lets call each Virtual Switch and physical network card NIC1 and NIC2.  I have 2 guest OS servers pointing to NIC1 and 4 guest OS VMs pointing to NIC2.  I did this so the 2 guest OS have 10Gbps available and the other 4 guest OS have the other 10Gbps.  I think i have something wrong with my setup because the 4 guest OS servers pointing to NIC2 seem to have restricted internet bandwidth issues.  The other 2 guest OS servers pointing to NIC1 have no bandwidth issues.

on the hyperv host i setup a static IP with gateway and static DNS on Virtualized NIC2.  I also setup a static IP address with gateway on virtualized NIC2 but i got that gateway warning message and the NIC2 setup without any gateway address. It left that blank.  and yes these are on the same subnet.
I did watch some performance live in task manager and it appears that traffic was only going out NIC2 which makes sense since NIC1 force setup without a gateway.

What is the best way to setup my virtual switchs and the now virtualized physical nics and their IP addresses.  I want to have my 2 guest VMs to have 10Gbps available and…
Hey Experts,
I’m a huge fan of your site and have been using you guys for years now and I absolutely love your Experts. Thanks for all the help throughout the years.
I have a dilemma that I hope you all can help me with... I consider myself quite good with Exchange (all versions since 2000) … but I still can’t create my “best environment” I could probably manage because of all  the Pros and Cons… so little advice will be very helpful.
Here is my current environment:
-      Single Hyper-V VM machine with 20 CPU’s and 32Gb RAM, replicating that VM every 15min as well as doing Altaro full backups every day.
-      Single Exchange 2010 with 7 database stores each store on different drive with 400Gb space for each drive (at least 100Gb free on each drive)
-      I’m running multi-tenant environment for about 15 small customers totaling to about 700 mailboxes

I’m in a process of upgrading the above environment and that’s where I need a little bit of an advice. I’m planning to upgrade above environment as follows:
-      New Hyper-V machine, quite powerful again (like above, even better as far as resources) with replication running every 15 min and Altaro full backups at night
-      I’m planning to have Windows Server 2019 Standard operating system on it, install Exchange 2016 in co-existence with above Exchange 2010 environment and then move over my existing 2010 Exchange environment to the new environment. Then remove/demolish the Exchange 2010 and upgrade to Exchange 2019 (in-pace upgrade …
 I have a virtual machine running Windows 2003 server and another virtual machine running Windows Server 2008 in VMWare.
 I like to run those VMs in HyperV Server, so I did the following:
 From W2003 VM, using Windows Server backup program, I created a backup file "W2003.bkf".
 From W2008 VM, using Windows Server Backup program, I created a backup folder "WindowsImageBackup".
 Now I like to create new virtual machines - 2003VM and 2008VM in HyperV 2012 server using"W2003.bkf" file and "WindowsImageBackup" backup folder.
 How do I do that?

 To accomplish the above, I used to create VHDX files using Disk2VHD, but my experience with those is that I have to manually populate IP addresses in TCP/IP properties and it has not been always smooth, so I like to try backup & restore method this time around.

Hi, i just want to check the usage rights for Windows Server licensing and failover / disaster recovery.

I have 3x 16 core data centre licenses with SA that we use on a HCI cluster.

I want to know if i can have any "standby" machines for failover in case this cluster fails.

Ideally what i would have is a server with hyper-v replicas syncing to it that i can turn on if anything happens to my cluster and all i need to do is change DFS and DNS to redirect users to these.

Is this a supported scenario as long as nothing accesses the DR server unless it is needed (including backup servers etc)
Now running Microsoft SQL server 2017 (Windows 2016 server) on physical server, is it good\ no good to virtualize the SQL server to VMware? Any concern about this?
windows 10 hyper-v create
restore windows 7 system image to Window10 hyper-v machine
New installation consisting of:
1 2016 Hyper-V Host hosting one 2016 DC
1 2019 Hyper-v Host hosting exchange 2019
I am in the process of testing  backups, disaster recovery, etc . . .
with a spare 2016 Hyper-V Host  I was able to export and import the 2016 DC , but I was not able to import the Exchange 2019
Host not finding the hard drive file.  
My understanding that it is supported: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-windows-guest-operating-systems-for-hyper-v-on-windows
Not sure if it is relating to Production Checkpoint vs Standard checkpoint
Server: 2016

I was changing the allotted memory on a Virtual Machine (which I have done without issue many times in the past) and it first gave me a SCSI permission error which I fixed with this article: https://itblog.ldlnet.net/index.php/2019/06/11/hyper-v-general-access-denied-error-when-trying-to-load-a-virtual-hard-drive-and-start-a-vm/

It then started without issue. Now I'm trying to export it and again getting a permission error. Is there any way to resolve all of this at once?

Recently I have added the host to a domain network, however, I'm still using the local account (it takes the server 3 hours to switch accounts and I'm not generally locally onsite.

Even though the local account has all the permissions for Hyper-V and the VHDXs, could this be the cause? Or did something else cause it to bug out?

Edit: I've recently testing changing the settings on another virtual machine and it seems to be fine. It seems to be limited to this VM. Also it seems like I can export it when it's off, just not when it's running.
ValidationValidation FailHi,
 I am getting on error in Storage Migration Service  when I run "Validate source and destination devices" at Cut-Over to new servers stage.
 Validate process passed all categories except the on for "We can connect to the source computer using a local user account". Here are the machines involved in migration.
 FT1 - SBS2011/Source Server
 FT2 - Windows 2019/Orchestrater
 FT3 - Windows 2019/Destination Server.
 I am using Windows 10 computer to run Windows Admin Center.

 The files and folders of FT1 have been duplicated on FT3 and I can confirm that \\FT1 and press [Enter] key produces the same result as \\FT3 and press [Enter] now.
  In order to troubleshoot this error, I did two things:
 (1) Since it was complaining about "LOCAL user account", I opened Active Directory users in FT1 and set the password of "administrator" to match domain administrator's account "ftadmin" password. Note,  I have never used "administrator" account login on SBS2011 ever since I created domain admin account "ftadmin" during SBS setup process.
 (2) In regedit,  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System, changed the value to 1 in LocalAccountTokenFilterPolicy and rebooted FT1.
 (3) I rebooted FT2 and FT3 too.

 Can you help?
I rebooted a Windows Server 2016 with Hyper-V.  Now, None of my virtual machines will start.  They say "Starting..." but never get any further.
I'm new to virtualization and I am having trouble with booting from a virtual drive.   I have setup a Hyper-V VM machine installing Windows server 2019 from a bootable usb drive to a  virtual drive I created.  I am finding after installing that I need to have the usb drive in place in order for the virtual machine to boot up even if I change the boot order in hyper-V manager to boot from the virtual drive,   How can I change/fix this to where I can remove the USB drive and boot from the virtual?
Hey virtulization experts,

I need urgent help !!

We have an old terminal server which we need to keep around but have to move to a virtual server (for all sorts of reasons)

The problems are multifold, my limited knowledge being one of them.

Here is the spec of the physical server.

1. HP Proliant server with RAID 5 configuration running Windows Server 2012 R2 foundation.
2. The disk partition is 2.7 TB in size and server has UEFI boot. Only 700 GB is in use however.
3. It has 6 cores and 12 virtual processors.

The virtual server is Hyper-V on Windows Server 2019 Std.

Here is what i have tried and why it hasn't worked.

1. Microsoft Virtual Machine converter: It doesn't support physical machines with UEFI boot for conversion.

2. Disk2VHD: This utility converts disk partition to VHDX which is 661GB in size since it is dynamically expanding disk. But the capacity of the partition is obviously 2.7TB.

I created a new VM of Gen2 (needed for UEFI support) with that vhdx file but it simply doesn't boot. It opens the VM with a blinking cursor.
So I went through the process of bcdedit /fixboot, fixmbr, scanos and rebuild mbr options. I even did the whole formatting of the 100mb system partition and creating the efi boot directory etc. Here is the link to the Article

Now it's attempting to boot but crashes saying your …
I have a 3 node Hyper V Failover Cluster which has a production network subnet of

Most of the guest VMs I want to migrate to this cluster are in that subnet - fine - got that.

I have a few that are on a and I am confused on how to make this work.

If I wasn't running a cluster - if it was just a hyper v host - I could assign a 172.16.0.x IP on the NIC (or on another physical NIC) and the host could communicate to the as well as the and I can have a mix of both guest VMs there.

Now that I have these 3 hosts in a failover cluster and each host has 4 NICs and each is are assigned separate subnets - none of which are the - storage subnet (, production subnet (, heartbeat subnet, 4th looks to be a vEthernet -maybe from the HyperV Role being installed - I'm not sure if I'm trying to add a 172.16.0.x IP on a NIC, adjusting something in the cluster properties, both, changing the subnet mask from to a, adding a new  etc.

Sorry - am I making sense with the question here?
I have three virtual machines in Hyper-V server in 10 user network.
(1) Domain Controller (Active Directory/DNS/DHCP)
(2) File Server (User Files & Folders & Printers)
(3) Terminal Server 1 (Allow users to connect and run business specific application software)
(4) Terminal Server 2 (Allow users to connect and run another business specific application software)

 I like to add VPN server (LT2P connection) to the network.
 On average, there would be 2-3 users connecting to either Terminal Server 1 or Terminal Server 2 from outside of the office via VPN connection.

Which virtual machines (between 1 and 4) would be appropriate and why?

I am using Veeam Backup Community Edition to backup 10 VMs. The VMs are Hyper-V and I back them up to a Synology NAS. Started getting e-mails recently with the following errors:

Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\Hyper-V\VM-SQL2014\Virtual Hard Disks\VM-SQL2014.VHDX Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\Hyper-V\VM-SQL2014\Virtual Hard Disks\VM-SQL2014_5760AF95-929B-4D38-8C19-0D091DB3858E.avhdx
Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\Hyper-V\VM-SQL2014\Virtual Hard Disks\VM-SQL2014-DDRIVE.VHDX Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\Hyper-V\VM-SQL2014\Virtual Hard Disks\VM-SQL2014-DDrive_6DFABD66-EE0A-49D6-999B-232634394313.avhdx

Any ideas?


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.