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 converted a physical machine to a Hyper-V VM using:  https://www.experts-exchange.com/questions/29103396/Convert-physical-Server-SBS-2011-to-a-smaller-partition-into-Hyper-V.html#a42625473

Now when testing the VM I am having connectivity issues.  For starters I can ping the machine by ip address from some other servers on the network but from others it doesn't ping.  Also, from any device that I have tried I am unable to access the shares on the server.

Not sure how to go about diagnosing what is going on or why it is different now that it is running in as a VM.
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.


I recently deployed a new server running Windows Server 2016 with the Hyper-V role installed with 6 virtual machines.  The issue that I am noticing is when connecting to a VM through the console in Hyper-V Manager.  When I first try to connect to any VM it will usually take about 10 seconds to connect and display the screen, but any subsequent attempts to connect to any virtual machine, including the first one that had the delay, will be almost instant.  It will remain this way for a while actually and any attempt to connect any of the VM's are very fast.  I basically have to wait around 10-20 minutes without connecting to one of them before the delay will be noticed, and again only on the first attempt to connect the console.  It behaves like it has to cache certain things before it loads completely.

As for troubleshooting, I have disabled VMQ's and Large Send Offloads on all network adapters, which did seem to help with the delay time a bit, but did not fix the first initial console connection delay.  RDP sessions do not experience this problem and network ping times as well as data transfers are completely fine as well.  

In all honesty, the delay isn't horrendous, but I am curious as to why it would do it only when I first connect to a VM.

Any information is appreciated.  

Thank you
Our Datacenter Ops Team reported the following error regarding a NetBackup failure on one of our Hyper-V virtual machines that's a member of a cluster:

the NBU Client servername failed due to a media write error.

05/25/2018 13:09:38 - Critical bptm (pid=21444) image write failed: error 2060022: software error
05/25/2018 13:15:13 - Error bptm (pid=21444) cannot write image to disk, Invalid argument
Within all of my Server 2016 Hyper-V virtual servers the color of the PowerShell window is black (and isn't blue).

This makes it difficult to differentiate between the PowerShell window and the command line window.

What can I do to make the PowerShell window always appear blue (and not black)?

Is there any way of making this change via some kind of group policy or global setting so I don't have to manually make this change on each and every virtual server?

I have a Windows 2012 R2 Hyper-V server running 3 VMs.  2 VMs are Server 2012 and the third is Server 2008.  Sometimes, I can't communicate with the Server 2008 from any device on the network.  I cannot ping it (using its STATIC IP--not hostname) or connect to it through RD.  I can ping from the Server 2008 to the other servers.  I just disabled the firewall on the Server 2008 temporarily to take it out of the equation but still not accepting pings.  I tried a tracert to it and nothing as well.  Please let me know how I can diagnose this problem.  I haven't tried restarting either of the VMs because people are working on them.  And, actually, there is one user that's connected to the Server 2008 now so I know that they were able to access it earlier in the day.  Thanks for any suggestions.
2 Node, Server2016 Hyper V Cluster connecting to a SAN via iscsi.
The San has a total of 3 LUNS.  2 For the vm's to "live" and one for Quorum.

When I pause Node1 and drain the roles.  The VM's drain to Node2.

When I pause Node2 and drain the roles, both  Cluster Disks go offline and the VM's autopause.

During the outage, I was able to ping the iSCSI ports on the SAN and I disabled AV/Firewall on the hosts but that did not resolve anything.
Only resuming Node2 brought the CSV's online.

This cluster was able to failover properly in the past and my lab is failing over correctly as well.

I don't want to run the ClusterVal Wizard until my next maintenance window ( JUST IN CASE ). Before I do run the CLusterVal, has anyone ran into this scenario before?

Cluster.log attached

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!
I have two servers . Both are 2012 r2 servers . I have installed the latest updates on both , yet I get this message when I want to replicate ,

“The operating system version on the replica server must be the same or newer than the version on the primary server . “
Hello all,

I cannot make a Hyper-V backup because the backup software does not see Hyper-V / VM's. That is because when I do a : "vssadmin list writers" the Hyper-V writer is missing.

Anyone know how to resolve that?
Hyper-v Host: Concor-bexec
Hyper-v Host: Concor-A1
Virtual Machine: Concor-VM1 (created on Concor-bexec)
All Installed on windws2016

In AD Concor-bexec
Cift & Virtual system Migration Service Contrained delegrated Concor-A1
In AD Concor-A1
Cift & Virtual system Migration Service Contrained delegrated Concor-bexec

When I live migrate server bexec to A1 ok success
But if I want to live migrate back to exec from A1 (Using hyper-v manager on bexec), it fails

I though constrained delegation allow live migration from remote server using hyper-v manager.

Any idea ?????
Cloud Class® Course: Ruby Fundamentals
LVL 12
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

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
When I restart the Server 2016 Hyper-V base server (which has 5 Server 2016 virtual servers running) the virtual servers all have the "Shut Down event tracker" notification window that displays once the base server boots back up and I connect to these virtual servers.

Does this mean that the virtual servers aren't being shut down or restarting properly?

Shutdown event tracker

We have a Windows 2012 R2 domain controller Hyper V running on a Windows 2012 R2 server. We are getting speeds of 45mbps up & down but they Hyper V is barely reaching 8mbps.

The Hyper V has 2 processors & 16GB RAM so really more than enough for it. I have turned off VMQ's on the Hyper V (as per a quick google search) & this increased the speed a little but not very much.

Any ideas on what I am missing?
I am in the process of standing up a Ubuntu Linux server from a .vhd file.
The existing partitions are too small to handle the backup file thus I need to add extra partition space to the system.
This is a hyper-V hosted system.
I've never done this before. Can someone give me some guidance on what I will need to do?
Initially I was building a new server with 2 Tb of disk space but we decided to use a existing secured version of a .ova file which I converted over to a .vhd file.
Can anyone help me understand what I need to do?
We have more space available, the vhd was set to more than what the original image was configured for.
How can I expand the relevant partitions to take account of this extra available space?
Which partitions should get the extra space?  Opt is where the backups are stored via the main application so that one definitely needs to be expanded.
Filesystem                        Size  Used Avail Use% Mounted on
udev                               16G     0   16G   0% /dev
tmpfs                             3.1G  8.7M  3.1G   1% /run
/dev/mapper/vg00-root              19G  1.4G   17G   8% /
tmpfs                              16G  4.0K   16G   1% /dev/shm
tmpfs                             5.0M     0  5.0M   0% /run/lock
tmpfs                              16G     0   16G   0% /sys/fs/cgroup
/dev/sda1                         464M   58M  382M  14% /boot
/dev/mapper/vg00-opt               76G   76G     0 100% /opt
tmpfs                            …

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
Hi Experts,

I am testing the hyper v cluster availability on azure and wondering is someone from you did it before and can share some experience?

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.
Cloud Class® Course: Python 3 Fundamentals
LVL 12
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

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?  …
A client of mine wants the Direct Access role to be installed within a Server 2016 Hyper-V virtual machine.

I have already found instructions for setting up Direct Access but these guides don't include any instructions on how to set up the Hyper-V networking to support installing Direct Access within a Server 2016 Hyper-V virtual machine.

Please provide me with the instructions for installing Direct Access including setting up the Hyper-V virtual machine networking that is necessary for installing Direct Access within a Hyper-V virtual machine.

Direct Access will be installed on a server that has 4 physical RJ network ports.
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?
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.


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.