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


I have a Windows 2016 Server Standard with Hyper-V installed.  I have two VMs:  ADSRV and RDS (Active Directory Server and Remote Desktop Server).  Something happened the other night and now the RDS is in a Saved state.  I've seen this before and I was able to delete the saved state and continue on as usual on another server.  This time, if I try to delete the saved state, I get an error message:  An error occurred while attempting to delete the save state for the selected virtual machine.  RDS failed to turn off.  I've checked the details on the tskmgr and the only vwmp.exe that's running or showing up is the ADSRV.  Microsoft's website said something about deleting .bin and some other file.  I couldn't find those files in the VM folder.  I found the vmcx and vmrs files.  How can get this VM back up out of the saved state?  Any help is greatly appreciated!
Cloud Class® Course: MCSA MCSE Windows Server 2012
LVL 12
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

I have a Hyper-V server (windows 2012) that is joined to a domain.

I want to disjoin the Server but it has some VMs working on it and those were installed while the Server was joined to the domain.

My question is the following:
If I disjoing to Domain, will my Vms still run normally ? or the services of the Hyper-V are linked to the domain user...and I will run into some rights policy issues ?

I have a hyper V machine that I cannot login to. It says the trust relationship between this workstation and the primary domain failed. I do not know the local admin password or if its even enabled. What can I do??
I need to create a volume with "Bytes per Physical Sector" = 512 so I can use it as the staging location for Backup Exec (using GRT -Granular Recovery Technology) to restore Exchange (physical 2007) mailbox / items. (I know this setup is old. We are migrating.)
GRT requires the staging location have the same sector size as the volume from which the Exchange log files were backed up.
To do that, I added a new VHDX to the Backup Exec server (a 2012R2 VM on 2012 R2 Hyper-V host) and then I issued  
"Set-vhd VHDname.vhdx -PhysicalSectorSizeBytes 512"
to change its Physical Sector Size to 512 bytes. I did verify using "Get-vhd VHDname.vhdx" that it shows PhysicalSectroSize = 512.
But to my surprise when I got in to the VM and issued the following command on an elevated command prompt:
fsutil fsinfo ntfsinfo D:  (where D: is the VHDX I just created)
it shows the "Bytes Per Physical Sector" = 4096

I'm confused... Why are they different? Did I miss anything? How to create a vhdx with "Bytes Per Physical Sector" = 512

is it supported to put SQL server on hyper-v replica

I know that Exchange does not support the Hyper-V Replica feature,

but for SQL I have not found clear answer.
Thank you
I will be setting up Direct Access within my organization's network.

Please provide me with step-by-step instructions on how to set up a Server 2016 Network Location Server within a Hyper-V virtual machine in this network.
The following question deals with the bare metal restore of a Microsoft Hyper-V server running (amongst others) two virtual machines on which is installed a licensed Oracle 12c (Standard). I am not interested in an “Oracle for DR” installation scheme. There is exactly one backup scenario: the entire Hyper-V server is backup up to local media using Windows Server Backup. There are exactly two restore scenarios: (1) the entire server is restored on the original equipment  from backup media using the appropriate Microsoft Distribution Media and (2) a single VM is restored from backup media using Windows Server Backup.

I understand that Oracle’s default position is that all installations require licensing. The first scenario above implies that more than one physical machine may hold the Hyper-V server; the second scenario implies that restoring VMs could create more than the two licensed installations. To quote a post by Brian Lowinger (https://www.softwareone.com/en/blog/licensing-oracle-database-for-disaster-recovery) : “Oracle uses the term ‘failover’ to describe a scenario where, within a cluster of servers, a database running on a primary server could move to a secondary server when the primary server fails. Oracle allows for the database to run on the secondary server for up to 10 days without additional licensing requirements.” If we stick to the scope of the question and the 10 days grace period, all licensing is honored.

-      The OS is…
We are trying to setup a disaster recovery backup unit on our network (internal). We have a Hyper-V host with two VMs. Windows 2012R2 on all. Internal network switches are "dumb" non-managed switches and a Sophos SG firewall.
The backup unit will backup one of the VMs but not the second. The errors we are getting say that the unit cannot communicate through port 25568 (between the backup unit and the VM). The Windows firewalls are all turned off on the VMs and the host, and again, we don't have any managed switches to filter traffic.
My only assumption is that something in our Virtual Switch could be filtering. Is that possible? How do I test that?
I'm looking for clarification on how CPU allocations work with Hyper-V.  I've read a number of articles but still have a few questions.

The context is a Windows 2016 server for an office of 10-40 users.  My specs are vague as they apply to a number of different clients.  There would be the Host that doesn't do anything except host Hyper-V.  There would be 2 VMs: a DC (AD, DHCP, DNS) and an Application Server (file and print sharing, light-duty SQL, one other light-duty application).  The server has an 8-core Xeon and 32G of RAM.  The Host runs on a pair of SATA SSDs and the VMs run on NVMe SSDs.

To start with, let me state what I think I know:

1)  The "Number of virtual processors" (Nvp) setting for a VM is a minimum.  That is, if there are not that many cores available at a moment, Hyper-V won't give time to that VM.
2)  Overallocation of cores is reasonable when there are many VMs, but a poor idea with just 2 VMs.  With only 2 VMs, the likelihood of both VMs needing their cores at the same time is high.  With many VMs (say... 5 or more) averages will work out and it's far less likely that all VMs will need their cores at the same time.
3)  CPU cores matter, HyperThreads do not.  That is, a 8-core CPU with HT (8c/16t) only counts as 8 Nvp.
4)  The Host has ALL cores available to it.  This makes the allocation of cores somewhat challenging as it is an unknown number at any moment.

My questions are as follows:
1)  Can a VM use more than the setting for Nvp?  …
What steps need to be followed to migrate Hyper-V virtual machines (that are currently running off a Server's C: drive) to a Storage Area Network (SAN) or to a different drive on the same server?

I want to migrate both the virtual hard drive(s) used by the virtual machines as well as the data and configuration files and folders.

Is the best way of doing this by using the "Export" feature within the Hyper-V Manager console or should a different method be used?
Get your problem seen by more experts
LVL 12
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

I use the Microsoft Sysinternals Autologon program within my test network.

Lately, the Autologon program hasn't been automatically logging onto the Hyper-V virtual Server 2016 and Windows 10 computers (with the domain administrator (administrator) account like it used to.

I have uninstalled the Autologn program, rebooted, and then reinstalled it and retyped in the Administrator username and password but this hasn't fixed the problem.

This Autologon program is only being used within my test environment (which is behind several locked doors and is completely isolated from any production networks.

What can I do to fix this issue so that I can continue to use the Autologon program to automatically logon to these Server 2016 and Windows 10 computers? I need to be able to automatically login to these computers since they are older and take longer to do things and so that my testing can be done properly.

The homepage for Autologon is here.
2 hyper-v 2016 hosts.
Client wants me to set up replica between hosts.
Should I enable both hosts as replica server and than configure guest VMs on both hosts for replica
or just one host can be  replica(DR) server and other primary?

In this example one server is replica server and other primary
What if I need enable replication for guest VM on replica server host.
We currently have SBS2011 and We want to move to Server 2016 as our DC with Exchange 2016.
We don't need any advice for setting-up Server 2016 as a DC or Exchange 2016 - however

Should we-

Setup and configure Server 2016 as a DC on physical hardware - install the Hyper-V element and setup a VM to run Exchange 2016 (within the DC environment)?
Do we setup the host OS (Server 2016) on Physical hardware and install the Hyper-V element - THEN setup 2 VM's - one as the DC and the other as Exchange.

Which is the best configuration please.
Thank you
we have a domain controller and exchange 2016 server running on a windows 2016 std server, as Hyper-V virtual machines.

we have all of the servers configured with static IP addresses :-

Hyper-V host

The gateway on all is

Everything was working OK, but now we have a problem with DNS.

Running nslookup on our 2016serv produces :-
Default Server:  google-public-dns-a.google.com

running nslookup on exch2016 produces :-
Default Server: 2016serv.doman.local
Which is how we expect it to look.

We have forwarders setup on our DNS server pointing to & which is google, but the static IP settings on our NIC's for both 2016serv and exch2016 are pointing to our DC which runs DNS ie

I have just run nslookup again on our main DC and we now get :-

DNS request timed out
         timeout was 2 seconds
Default server: unknown
  Address: 2001:4860:4860::8888

I just cant work our why our main DC is not using DNS which it also runs, as nslookup shows rather than while it works perfectly on our exchange server??

Can anyone advise how I can trap this frustrating issue?
MVMC - Warning before runningMVMC ErrorHi,
  I am getting an error "The operating system of the VMware VM is NOT SUPPORTED.  This does not prevent conversion, but no support is provided for this conversion" when trying to convert VMWare VM running Windows 10 OS to MS HyperV Server using Microsoft Virtual Machine Converter program.
 Is Windows 10 OS not supported by Microsoft Virtual Machine Converter program?
I have recently installed Hyper-V Server 2016 on a Dell Poweredge T640.
This was on a new machine, with no other OS etc installed. I used an ISO burned to a DVD to install.
This is my first time working with Hyper-V.

The installation seemed to work fine. After installation, I used the sconfig utility to set up the network.
I have used a static IP address and the correct gateway & subnet mask settings. However, I can't ping anything from the server (nor can I ping the server from anywhere else).
I have disabled the firewall - using netsh advfirewall set allprofiles state off - on the Hyper-V Server installation.
I have enabled ping in sconfig under Configure Remote Management

I have tested the physical LAN cable by plugging another computer into it - it works fine.

I haven't proceeded with any VM installation as I thought I should get this sorted out first. Am I missing something? Shouldn't I be able to ping my gateway at this stage? I have read about Virtual Switches, but I shouldn't need one to ping my gateway, should I?

Thanks in advance for any help!

*** I forgot to mention:

When I use Network Settings in the Sconfig program, my adapter is listed as: Remote NDIS Compatible Device. Is this the problem?

Windows 2012 R2 Hyper-V host. It was running one VM for 2 years with no problems.

Added another VM and the new guest (PaperCut site server) starts to crash and eventually brings down the host. Pretty random. Can last a week or a day.

Performance shows plenty of hard drive space, RAM and no excessive CPU usage.

A reboot doesn't work. Only a forced shutdown.

Where is the best place start looking? Event Viewer.. Log files etc.

Any help would be greatly appreciated.

I have read many pages about production checkpoint and standard checkpoint but could not understand what is the major difference between production and standard checkpoints. Anybody can please tell me with small example?
I have an existing Hyper-V host server running server 2016.  There are currently 4 VMs running on it, one of which is a domain controller that is managed by another division and I do not have access to log into it.

Somehow the network interface associated with the virtual switch got pointed to a different network port (there are 4 on this server) and the Hyper-V Extensible Virtual Switch setting on that port wasn't enabled.  Now I can't enable it.

How does one go about recreating the virtual switch correctly?  I've shutdown all the VMs, deleted the virtual switch, reassigned a static IP to the interface to be used then recreated the virtual switch, but I never get the virtual switch setting on the physical network interface to be selected and I can't manually select it.
Cloud Class® Course: SQL Server Core 2016
LVL 12
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

I'm looking at purchasing a server to run hyper-v, originally i was going to go with 8 x 900Gb 15Kpm SAS drives in raid 10. then my boss mentioned about some more projects, meaning I have now needed to look at more space. I'm now looking at 10 x 1.2Tb 10Kpm SAS drives in raid 10.

due to the 1.2tb 10k being about the same price as a 900gb 15k, I'm stuck in a dilemma over space and speed.

so i looked up a raid calculator

8 x 900Gb RAID 10 will give me 3.6Tb with speed gain 8 x read and 4 x write - but note they run at 15k speed drives

10 x 1.2Tb RAID 10 will give me 6Tb with speed gain 10 x read and 5 x write - but note they run at 10k speed drives

does the rpm of the drive matter when you can see an increase in the bandwidth of the drives ?
I have a Hyper-V base server that has a total of 24 processors.

Is it possible to assign more than 24 total virtual processors among the Hyper-V virtual machines?

In other words, can the virtual machines share virtual processors?

I have a Synology with vmm, so like to import my vmware and hyper v vms on it.
If I m right, I could import ova files.

Is there a way to convert my vms in ova?

What does enabling "Secure boot" for Server 2016 Hyper-V virtual machines enable?

Can having "Secure boot" enabled lead to any problems or issues for the Hyper-V virtual machines, particularly Server 2016 Hyper-V virtual machines?

Secure boot
What steps do I need to follow to ensure that the integration tools are installed within a Server 2016 guest VM?
Does clicking on the "Shut down" button for a Hyper-V virtual machine in the Hyper-V management console initiate a normal Windows shutdown so the virtual OS will shut down normally?


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.