I have 3 physical servers and am interested in virtualizing using Hyper-V in order to role out multiple technologies. We have Windows Server Standard Edition and want to do (2) VMs per machine but am not sure which virtual servers I should put together.

Here are the technologies I'd like to run:

Domain Controller / DNS/ print & file sharing

Exchange Server

SQL Server

SharePoint Foundation 2013

Office App Server

Remote Desktop Services

Can anyone offer a recommended server configuration and specific things that I should or shouldn't put together, or things I shouldn't virtualize at all?

Thanks

HV Host : Win Server 2012 R2 + Latest Updates Installed

Guest OS: Win Server 2012 + Exchange Server 2013 CU14 + Latest Updates Installed.

I set up VM backup using windows server backup, all vm's back up done successfully except Exchange VM. with following error:

Error: Component reports path on volume which has been excluded + Error Code: 0x8100010F and 0x80780049.

then i decided to upgrade integration services on Exchange VM (Win Server 2012 + Exchange Server 2013 CU14 + Latest Updates Installed+ Integration Services 6.3.9600.18080). to do so i did "Action > Insert Integration Services Setup Disk" and installed Integration services.

now! Exchange VM Stuck in boot saying "Please Wait" for a long time, any idea how fix this?

I can not compact as picture

the request operation can not be complete due to a file system limiation.

I want to copy a 333gb avhd file to NAS, several hours later, it can not copy and it say I should copy it again.

Any help?

Hi all,

I am prepping for an exam. I have a Dell t110 server with hyper-v installed.

The server only has one physical NIC.

I want to create a forest with 2 domains. 

I want each domain to reside in its own subnet.

Is this possible with hyper-v virtual switching?

My thought was to create a internal virtual switch and connect the child domain to it. Then user RRAS on the hyper-v host to route between the external virtual switch (bound to the physical NIC in the hyper-v host) and the internal virtual switch created logically within hyper-v switch manager.

This does not seem to work. 

Any help on how to set this up would be greatly appreciated.

Thanks

Hi,

We have an Hyper-V infrastructure which is composed of 6 nodes running on Windows 2012 R2 (HP servers with the same materials). 4 "Cluster Shared Volume" have been created, together with a Quorum.

When we assign a CSV to another node, we have no problem, except with the node n°5. In this case, when a CSV is assigned to node n°5, only the node n°5 can see the content of the volume in the Windows Explorer. The other nodes cannot.

From the other nodes, we have this error message :

"C:\ClusterStorage\VolumeXXX is not accessible. Logon failure : the user has not been granted the requested logon at this computer".

We also note that the size of the assigned volume doesn't appear on the other nodes in the Windows Explorer.

What is amazing is that we encountered no issues with the virtual machines.

I have read many forum on the Net. Talking about SMB which could be disabled, but like the storage is connected by Fibre Channel, it doesn't seem to apply to us. Furthermore, the components "Clients for Microsoft Network" and "File and Print Sharing..." are enabled on the network cards dedicated to the cluster.

One last information. The node n°5 has been reinstalled from a Sysprep image, but the problem is still there.

Can you help us ?

Best regards.

Laurent

Hi,

Can you please help me in getting step by step process for upgrading (full) Server 2012 R2 to Server 2016.

Thanks

Hello, its kinda late there and im stucked for a while.  
I cant connect to my guest VM (win10 as well) from my W10 machine running Hyper-V.

Host IP: 192.168.0.81/24, guest IP: 192.168.0.100/24. 

GW: 192.168.0.1 on both sides.

Using External Virtual switch in my guest OS.  The VM have no trouble acessing internet and so on. 

I can ping both machines from my router, ICMP echo is enabled for sure. I dont think its a firewall issue.

What am I missing? Is the same subnet (192.168.0.0/24) an issue?

I have 2 servers both running Windows Server 2012 R2. One server is currently running a Hyper-V instance. I have configured the running machine and checked the option under Processor > Compatibility, "Migrate to a physical computer with a different processor version". I shut the VM down, then exported it. After copying it to the new machine I've attempted to import it. I select the folder where I copied the files to and it recognizes the VM. I select "Register the virtual machine in-place". Then it prompts to select where the virtual hard disks are located. I pick the same folder I picked when adding the VM. As soon as I hit next, I get this message:

[Window Title]
Saved State Errors

[Main Instruction]
The following saved state errors were reported:
The processor settings for virtual machine 'PROD1VM - (4/15/2016 - 8:44:17 PM)' are not compatible with physical computer 'BACKUP'. To migrate this virtual machine, you must first shut it down. After shutdown, you can migrate this virtual machine or export it and then import it on the destination physical computer with the correct processor settings. (Virtual machine ID 21424D5E-BB09-4564-83B3-5DDD5C518482)
 The operation cannot proceed unless these errors are resolved.  Do you want to delete the save states producing these errors in order to continue?

[Delete Saved State] [Cancel]

The thing is, I HAVE done that. Multiple times. If I click "Delete Saved State", it then prompts me to select where the "C" drive for the VM is, the D drive, then the AVHDX file for the C drive, then finally the AVHDX for the D drive. After selecting those, it fails with this:

I'm not sure what else to try. Each time I retry this export/import cycle it takes the better part of a day to export the stopped VM (which takes a few hours), then another few hours to copy it to the other server/datacenter. If it matters, the total VM size is somewhere around 350GB.

Any ideas on what is causing this to fail?

I have a very simple setup. Two Hyper-V hosts running on two physical servers. One is running 2008 R2, the other Server 2016. On the 2016 server, I can't connect to the 2008 R2 server in Hyper-V Manager.

I get the dreaded "An error occurred while attempting to connect to server "". Check that the VMM service is running and that you are authorized to connect to the server."

The VMM service is running on both servers, and I am logged in as a Domain Admin on both servers.

Firewalls are completely off for testing and still not working.

Running Hyper-V Management on the 2008 R2 server, I can connect to the 2016 server, but no VMs are listed.

I have recently installed a new Hyper-V server into the 2008 R2 cluster.

The host can Connect to all of the other servers on the other nodes in the cluster. But it cannot connect to its own VMs, nor can any of the other nodes connect to any of the VMs on that new server either.

When attempting to connect (VMConnect.exe) the following error appears - "An authentication error occurred (Code: 0x607)". Screenshot below - 

Does anybody have any clue as to whats going wrong here? 

I'm having issues with vm internet connection using an internal switch.

A few days ago I was able to connect my vm to internet.  Now, without any settings changed, I can no longer access internet from within vm.

I have my Wi-Fi sharing set to vEthernet (Internal-Switch).  I have the vm's network adapter set to same switch, as well. 

I don't understand what is the issue as one day it was working fine, and the next day - not working.  The ip addresses were automatically assigned.  So previously I did not have to set ip, subnet mask, or gateway.

Also, my virtual machines had been getting an ip address in the 192.168.137.xxx range.  Now my vEthernet adapter is getting the 169.254.xxx.xxx ip. 

Nothing had been changed in settings, meaning I shutdown vm and when I went to use hyper-v again, the adapter was no longer getting a valid ip?

Have combed through the web, but not finding a solution to problem or a reason as to why the problem has arisen.

Thanks

Hi

I have a Host Guardian Server running correctly, with the following status:

PS C:\Users\Administrator.EXC> Get-HgsServer

Name                           Value
----                           -----
AttestationOperationMode       AD
AttestationUrl                 {http://hgs4.exc.dc/Attestation}
KeyProtectionUrl               {http://hgs4.exc.dc/KeyProtection}

Detailed diagnostics are as follows:

PS C:\Users\Administrator.EXC> Get-HgsTrace -RunDiagnostics -Detailed
Overall Result: Pass
    WIN-P54TEDPBAGD: Pass
        HGS Service Configuration: Pass
            Code Integrity Policies Installed: NotApplicable
            Baseline Policies Installed: NotApplicable
            Authorized Hosts Added: NotApplicable
            Authorized Host Groups Added: Pass
        Hardware: Pass
            Provisioned Memory: Pass
            Memory Usage: Pass
        HTTPS: Pass
            Key Protection Administration Certificate Validation: NotApplicable
            Bindings without SSL Certificates: NotApplicable
            Attestation Server Certificate Subject Verification: NotApplicable
            Key Protection Server Certificate Subject Verification: NotApplicable
        Certificates: Pass
            KPS Certificate Permissions: Pass
            Attestation Certificate Permissions: Pass
            Attestation Signing Certificates Valid: Pass
            Attestation Signing Certificates Registered: Pass

When I try to attest a host with this service, I get the following:

PS C:\Users\Administrator> Set-HgsClientConfiguration -KeyProtectionServerUrl "http://hgs4.exc.dc/KeyProtection" -AttestationServerUrl "http://hgs4.exc.dc/Attestation"


IsHostGuarded            : False
Mode                     : HostGuardianService
KeyProtectionServerUrl   : http://hgs4.exc.dc/KeyProtection
AttestationServerUrl     : http://hgs4.exc.dc/Attestation
AttestationOperationMode : ActiveDirectory
AttestationStatus        : InsecureHostConfiguration
AttestationSubstatus     : VirtualSecureMode

Further details are:

PS C:\Users\Administrator> Get-HgsTrace -RunDiagnostics -Detailed
Overall Result: Fail
    WIN-3LNHGUEVMU7: Fail
        Test Attestation: Fail
            Check Attestation Status: Fail>>> The host cannot attest because virtual secure mode could not be detected.  Please ensure that the>>> Isolated User Mode feature is installed and enabled, and that this is a physical machine (not a virtual>>> machine).
        HGS Client Configuration: Pass
            Code Integrity Policy Installed: NotApplicable
            Code Integrity Policy Active: NotApplicable
            Attestation Service Responds to Requests: Pass
            Key Protection Service Responds to Requests: Pass
            Valid VSM IDK Detected at Boot: NotApplicable
        Hardware: Fail
            Secure Boot: DependencyFailed
                UefiHardwareProfileCollector: Exception>>> Could not read the UEFI variable "SecureBoot".  This usually indicates a lack of administrator>>> privileges or a host that utilizes a legacy BIOS.  If you have sufficient privileges and are on a>>> UEFI-enabled host, verify you have the latest version of the manufacturer's firmware and drivers.>>> You may need to run this locally if the cmdlet was called remotely.
            Full Boot: NotApplicable
            TPM Presence: NotApplicable
            TPM Version: NotApplicable
            UEFI Setup Mode: DependencyFailed
                UefiHardwareProfileCollector: Exception>>> Could not read the UEFI variable "SecureBoot".  This usually indicates a lack of administrator>>> privileges or a host that utilizes a legacy BIOS.  If you have sufficient privileges and are on a>>> UEFI-enabled host, verify you have the latest version of the manufacturer's firmware and drivers.>>> You may need to run this locally if the cmdlet was called remotely.
        HTTPS: Pass
            Attestation Server Certificate Verification: NotApplicable
            Key Protection Server Certificate Verification: NotApplicable
        Network: Pass
            HGS Servers Reachable: Pass
            DNS Servers Reachable: Pass
            Resolves Service Hostname: Pass
            Service Hostname Resolves the Same on All DNS Servers: Pass
        Best Practices: Warning
            Local Mode: Pass
            Resolves Service Hostname to Multiple Addresses: Warning>>> DNS server at 192.168.2.110 cannot resolve "hgs4.exc.dc" to multiple IP addresses.  The recommended>>> configuration is to have multiple HGS servers available at "hgs4.exc.dc" for high availability.

My understanding is that this error should not appear since I am performing AD based attestation, and virtual secure mode should not be needed in this case. Kindly suggest resolution. If more information is needed to solve this, then where should I check?

Thanks in advance

Zawar

I have created several test VMs and moved a production VM away from a particular host machine.  the only remaining VM cannot start do to a lack of disk space.  there should be plenty, the problem is all of the old unused vhd files. But I cannot figure out how to delete them.  the Hyper-V Manager only allows me to select them.

I certainly have to be missing something simple.

Hi All,

I have Oracle Unbreakable Linux 6.5 which runs Oracle ERP application & Database it has three VHDs 80 GB , 600 GB and 120 GB on daily basis it creates RMAN backup approx 32 GB which stores on 120 GB VHD.This VM has more READ operations and around 1 MB / 1 Mins Write Operation other than Backup.

I have enable Hyper-V Replication on this machine with 60 Sec Cycle Exclude 120 GB VHD where RMAN data places but i have found that replication is not going on normal.

I can see that hyper-V replication fully utilizing 4 MB to 5 MB.

My Question :

1.If i excluded 120 GB VHD and i have very little write operations on replicating drives so why replication is not normal

2.Is read operations have impact on replication

Trying to access Hyper-V running on Server 2012 R2 from Windows 10 LTSB 2016 and I only get an error:

The Hyper-V Management Tools could not access an expected WMI class on computer....

Same server accessed from Windows 8.1 H-V Management Tools is working fine.

Anybody any idea?

According to this it should be no issue

Seb

I just installed a new 2016 server and added it to my failover cluster. This cluster has 4 2012 R2 machines that I plan on upgrading to 2016. I can add the server and everything looks fine, but when I try to live migrate machines vmms.exe will crash on the new 2016 server. I can randomly get machines to migrate over, but it is rare. I've also had 1 machine reboot on me during testing. Here is the event log:

Faulting application name: vmms.exe, version: 10.0.14393.351, time stamp: 0x5801a7cf
Faulting module name: vmms.exe, version: 10.0.14393.351, time stamp: 0x5801a7cf
Exception code: 0xc0000005
Fault offset: 0x00000000001e547f
Faulting process id: 0xe00
Faulting application start time: 0x01d233927a1cf2f9
Faulting application path: C:\Windows\system32\vmms.exe
Faulting module path: C:\Windows\system32\vmms.exe
Report Id: 3a054e2b-2f80-4b0d-ba8c-e076bb2171e6
Faulting package full name: 
Faulting package-relative application ID: 

WER Report:

Also, just to make sure everything was correct I wiped the server and reinstalled 2016 again. I am still getting the same crash.

So, we have a total of six Hyper-V servers in our environment. All six were installed from the same Server 2012 R2 Datacenter ISO. I have been managing these from my Windows 8.1 machine with no issues. I got ahold of Windows 10 build 10240, and I am running into an issue connecting to the servers now.

The strange thing is that I CAN connect to one of them. I cannot figure out what is different on this one server from the other five. Windows updates maybe? I migrated all the VMs off one of the servers I cannot manage remotely, performed all Windows Updates, and I still cannot connect to it.

I am reading that Windows 10 should be backward-compatible with managing Hyper-V on 2012, but on connection, it appears a WMI namespace is missing that the Windows 10 tools are trying to connect to.

I am not trying to use alternate credentials (I read this will NOT work from 10 to 2012 R2). Any ideas why this is not working? Several Google searches have not told me anything so far. I realize Windows 10 has not officially been released yet, but a few of us are testing the waters for compatibility issues.

I would appreciate any help anybody can offer.

Eric

Hi all,

I have a 2012R2 file server that has been in production for about 6 months now. It has a static IP of xxx.xxx.1.3

My plan is to install hyper-V on it to host a VM or two.

Once I install hyper-v, I know I will need to create a virtual switch. When that happens, I will lose network connectivity for a few seconds, so I will make sure it is off-hours.

Ok, here's the question: Once the virtual switch is created, do I assign it the original IP of xxx.xxx.1.3, or do I give it a whole new IP address?  From my understanding, there is no need to give the server's NIC it's own IP once the virtual switch is created?