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 can ping both directions between hosts and VMs. RDP works fine in both directions as well. My Host can get to shares on the VMs

However, my VMs cannot get to network shares on the host. Thoughts at what i'm missing here?

Host is Windows Server 2016 Datacenter, VMs are a mix of 2008R2, 2012R2, and 2016
Veeam gives away 10 full conference passes
Veeam gives away 10 full conference passes

Veeam is a VMworld 2017 US & Europe Platinum Sponsor. Enter the raffle to get the full conference pass. Pass includes the admission to all general and breakout sessions, VMware Hands-On Labs, Solutions Exchange, exclusive giveaways and the great VMworld Customer Appreciation Part

Hi experts,

I would say my technical level as far as servers is about a 5 to 6 out of 10. The IT person setting up the server would be a 12. He makes sure I have good quality hardware and software, but he also doesn't always recommend the most expensive. For this reason, he has no issues using WSB, but I don't want something that bare bones, no matter how well it works. Plus, I am more willing to spend money. As a physician, I see myself working another seven years (which I know is bordering on too long for the server -- I guess I am misguided by the fact my Dell Edge 2900 lasted that long).

Just to give my setup, I am setting up a Dell T430 server with Windows Server Standard 2016 as the host, with two VM guests. One will run my SQL databases and the other will contains Essentials for Active Directory and will be the DC. I have only eight clients all Lenovos running Win 7 Pro. They are all identical. Modem is Arris by Spectrum with 70 down and 6 up. pfSense router (awesome, but I am glad he set it up) and a Cisco 26 port switch. I know this is more info than you need. My old server (Dell Edge 2900) will temporarily be the fax server, but it can be converted to something else -- maybe a replication machine? I can also get Azure for the cloud much cheaper than AWS.

So, now to my question. And, these are frustrating I know, because it is more about opinion. I generally end up splitting the points as there is no right or wrong answer. But, I am trying to decide among …
OK, I totally get how the cores of a host computer must be "fully" licensed before you can spin up any VM's.  If you have Windows Server 2016 Standard and you have 2 procs of 8 cores each, you need one copy of 2016 Standard and you get two VM's.  If you have a computer with 2 procs and 10 cores each, you have to get a copy of 2016 Standard and enough core packs then you get your two VM's.  If you want two more VM's, you have to get a copy of 2016 Standard and core packs again.  

Sounds awesome.  

Now for my question:  How many virtual vCPUS's can I assign to my Windows Server 2016 Standard guests?

Every licensing scenario I see talks all day about licensing the host's cores.  But how many vCPU's can I assign to the guests when I open up the Hyper-V management tool settings for a VM and it shows that field where I can type in a number for processors?

Hello there,

So in our environment, we get the calls from monitoring team whenever they get the alert in their system regarding the server being down. Most likely this is a hung situation where we (domain admins and vmware admins) have to reboot the particular vm. We want to automate this process so monitoring can do this task themselves. This is kind of urgent requested by management so i thought I can get the help faster here rather than spending sometime on scripting. Any help is appreciated meanwhile I figure this out. Thanks!
Thanks for your time and expertise.
Here's my scenario:  I have an old Server 2008 R2 Enterprise host with four VMs.  Two of the VMs are recent installs and they are running server 2012 R2 Standard.  The two recent installs (the server 2012 R2 Standard vms) need to be activated.  
My question is if I upgrade the host OS to 2008 R2 Datacenter or 2012 R2 Datacenter will this process active the two unlicensed vms, or do I have to purchase licenses for these vms separtely.
Your recommendations and advise are greatly appreciated.
Is it Safe to import more than one Hyper-V virtual machine within Server 2012 R2 at same time?

I would like to import two or more VMs at the same time but will only do this if it is safe and won't cause any problems.
Hi Experts,
Can somebody confirm to me the major advantages of using a Scale Out File Server with a Hyper V cluster over just using CSVs?

I understand that with regards to failover SOFS are active / active so there is "no" downtime of a failure, but how much slower is a failover using plain CSVs?

What are ther other reasons to go for SOFS or not!

We are hesitant to add SOFS just for the sake of it as it would be another level of complexity that I am not sure we need.

Thanks for your input.


PS  - we are talking about Server 2016 here
My physical host cannot talk to or see all hyper-v virtual machines and i'm not sure what i'm missing here configuration wise

1) No RDP available between physical host and VMs

2) VMs can ping each other, but cannot ping between physical host and VMs

3) Cannot access file share from VM to Physical Host and vice versa

4) network discovery on physical host and VMs is turned on

Each machine has internet access and can access the internet and windows update without issue. The physical host is windows server data center 2016 and the VMs are a mix of 2008, 2012, and 2016

There is a lot of conflicting information about whether to use Dynamic or Fixed VHDX. A lot of the drawbacks of dynamic seem not to apply to later versions of Hyper-V.

For a production enviroment with 2 VMs (Server 2016 DC and Server 2016 RDS server), which would be better?

In my Hyper-V client, every column has been added to the 'displayed columns' section, except from the 'replication health' column.
When I add the replication health column, and close and reopen Hyper-V, it disappears.
This means every single time I open Hyper-V, I need to add the replication health column to look at what I need to look at.
I've found that this is only affecting my machine in the workplace (another user has logged in on my machine and found the same issue, I have logged into a different machine and tested with no issues) and I have also found that it is only the replication health column that bares this curse. Every other column will stay where I tell it to.
I've tried disabling and re-enabling Hyper-V which hasn't worked.

I believe the most simplest fix would be to flatten the machine and set up as new (which is what I may just end up doing). Only problem is this would take time and I need to work on the PC for now so I thought I'd post the problem here in the meantime to see if anyone may have come across this issue before.

10 Questions to Ask when Buying Backup Software
10 Questions to Ask when Buying Backup Software

Choosing the right backup solution for your organization can be a daunting task. To make the selection process easier, ask solution providers these 10 key questions.

What's the difference between these two options?
I'm basically wanting to allow remote users to connect (via SonicWall VPN) & work in Quickbooks, if that matters in my choice.
After power failure my VM did stop working so I checked the folder it was in and saw this:
FolderI tried to rename the .tmp file to .vhdx but it came up corrupted.
Anyone seen this or know how to resolve ?
Good Afternoon,

I've one RDS 2012 R2 server sitting in my network, as this is getting used more I am concerned about only have one server and it being a single point of failure etc. There are about 30 users connecting to the server but not all at the same time, some user connect using Remote apps and some connect to a share desktop

The server has the RD Gateway installed, one collection which consists of 6 applications.

My main objective is to virtualise the above RDS server, or add a second virtual RDS server to for DR.

So far I've converted the above RDS server a virtual machine, remove it from the domain, renamed it and joined it back to the domain.

I've a message on the newly created virtual server under Remote Desktop Service Overview that displays

"The following servers in this deployment are not part of the server pool:
The servers must be added to the server pool

Thanks in advance

We are setting up a server with Windows 2016 Hyper-V server installed that will have two VMs running on it and I have some best practices questions regarding the setup. The server has a raid10 array setup with 2.4TB of usable space.

The current setup is a small C: partition for the Hyper-V server OS, formatted as NTFS, with the rest of the raid array assigned to a partition (~2.3TB) formatted as ReFS. All the VHDX files are stored on this partition.

The VMs are setup as dynamically expanding VHDX files split 80:20 over the two VMs (a small Windows server 2016 VM for DC/AD/DHCP/DNS, and a larger Windows server 2016 VM for Remote Desktop services and user files) all formatted as NTFS.

1. Would it be better to have everything on one partition on the Hyper-V server?
2. Would it be better to use NTFS over ReFS for the VHDX files?
2. At the moment we have each drive in the VMs split as separate VHDX files (e.g C:\ and D:\ in each VM is a separate VHDX). Is this better than having all drives as partitions on one VHDX?
4. The files will be setup on DFS and can be setup on either VM. Would they be better setup on the DC VM or the RD services VM?

I have following the instructions on a few different tutorials and am unable to get a working network connection in my Windows VM. I have two different VMs I want to run at the same time. A Windows 10 and a Windows 7 machine. Here are two I tried:


Every one I read provides different steps - and not one works. External switches, internal switches, Hyper-V switches, VM switches, and adapters in the VM itself. Dynamic IPs and static IPs. This is nuts!

Is there a definitive set of of instructions that actually works?

I've got 2 T430s, with an Intel Xeon E5-2630 v4 2.2GHz (10 core), 64 GB RAM, a mirrored 300 GB SAS drive for os & 6 2TB SATA in a RAID 10.
Looking to set up Exchange 2016, network version of Quickbooks enterprise, Trend Micro worry free business security, a remote access server, file & print server, as well as the MS stuff, DC (or 2?) DNS, DHCP, etc.
In complying with licensing, I gather the only role I can have on the host is Hyper-V, which is on my 300GB, would any other VM 'parts" go here, as well?
When setting up VMs, does one VM encompass the OS & data, which would normally be on 2 different arrays the 'old way'?
The two directories for VMs would both be on my RAID 10, correct?
Any suggestions on the best way to spread all my pieces between 4 VMs?
If I've got too much stuff here & would be better splitting between questions, lemme know.
For PCI compliance and self-certification, we'd like to know if our Windows Server 2012 (not R2) Hyper-V hosts would include any memory data from hosted VMs in a memory dump file?

While we store zero cardholder data to disk, it's certainly held in volatile physical memory on the host while our storefront VMs are running.  So, in the event the host crashes and writes a dump file, would it contain any memory data from the VMs that were running at the time of the crash?


Frederick, MD
We have a group of 2012r2 hyper-v servers, some of them in a failover cluster, some of them standalone.

I have a couple developers I want to give permission to open the hyper-v manager to restart their servers.  I have given them permissions through GPO that allows them to RDP and open hyper-v manager to manage the non-clustered hyper-v servers, but the same permissions won't work on the clustered hyper-v servers, they get an error saying they don't have permission to connect to the servers.

I have a security group called 'dev_admin', and on the OU for the hyper-v servers I have a GPO that is giving dev_admin rights for Log in Locally, log in through terminal services, and under restricted groups have put dev_admin into the remote desktop users, and Hyper-v administrators, and to test I even put them into the builtin\administrator group for local admin rights (I don't want to use this except to test, but still no joy)

BTW the iscsi SAN machine is also in the same OU, so all the servers are getting the same GPO settings.

What am I missing?
One of our customers is having a complex (multi-symptom) issue with a Server 2008 R2-based VM running in Hyper-V.  

Affected server:  Server 2008 R2 virtual machine on a Server 2012 R2 hypervisor.  VM functions as a file server, DC, DNS server, DHCP server, and application server (yes, we're aware this isn't a best practice, but we inherited it from another provider). Integration services are up to date for this VM.


--Client PCs on both of the customer's network segments suddenly and randomly (morning or evening) all lose the ability to reach the server's file shares (all clients timeout trying to connect).  App and system logs on the client PCs, file server VM, and hypervisor show no apparent problem.  In fact, the file server can be pinged just fine from every workstation, and curiously, I can browse to \\PCname\C$ of each PC on the network from that server!

--When the VM is restarted, it hangs on "shutting down", and the "turn off" function in Hyper-V Manager must be used to power it off (we've waited 1 hour and then 30 minutes the first 2 times this happened).  As soon as it is powered back on, Windows loads without incident, and client PCs can reconnect to all shares.  The app and system event logs for the VM show the transition from shutdown to restart, but there's nothing abnormal noted.

--When this VM experiences the issue, no other VMs on the same host have problems (we have an Exchange VM, terminal server VM, etc.).

I should mention that…
NFR key for Veeam Backup for Microsoft Office 365
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

I have a Hyper - V host that hosts 3 VM Servers.  Two of the servers have multiple checkpoints and a "Now" Checkpoint.  Everything is running well, but disk space is starting to concern me.  I would like to merge the current configuration (Now) into the .VHDX file and remove all of the .AVHDX files.  My understanding is that deleting the checkpoints will do this automatically, and that this can be done without shutting down the VM, but I am not sure in what order that should be done.  Oldest to newest?  Newest to oldest? or by some other method.

I have not been able to find documentation on how to accomplish this.
Typeperf is not working on one of my PC

It is not working here:
Motherboard:ASUSTeK COMPUTER INC. H81M-PLUS American Megatrends Inc. 0804
Command:typeperf -sc 2 -o outputfile.txt "\Processor(_Total)\% Processor Time"
Output:Error: No valid counters.
outputfile.txt does not exist

It is working here:
Motherboard:Gigabyte Technology Co., Ltd. H67MA-USB3-B3 Award Software International, Inc. F8
Command:typeperf -sc 2 -o outputfile.txt "\Processor(_Total)\% Processor Time"
Output:The command completed successfully.
outputfile.txt contains the %load of the CPU
I'm trying to install the evaluation version of MS System Center 2012 Virtual Machine Manager and get the following error at the end of the installation (see screen shot).

I did download install winrm 5.1 separately after looking at KB2742275 however that didn't help.  One requirement  MS has is being joined to a domain.  Is there any way to install this without a domain controller present?

I need to disable VMQ

I am using command

Set-VMNetworkAdapter –ManagementOS -Name <VirtualNetworkAdapterName> -VmqWeight 0

how do I get the VirtualNetworkAdapterName

How do I create a failover fileserver setup on my HyperV (VMM) environment? (Shared disks?)

Windows Server 2016

Any guides?

Im looking to convert one of my physical servers (server 2003 SPK2) to a VM to host on my hyper-V server (Server 2012 R2)

Is there a server backup software that can image the entire disk (1 physical disk 2 partitions) then restore the image to the Hyper-v server?


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.