However, this hotfix is intended to correct only the problem that is described in this article. Hotfix informationĪ supported hotfix is available from Microsoft.
For more information about update 2955164, click the following article number to view the article in the Microsoft Knowledge Base:Ģ955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014 To resolve this issue in Windows Server 2008 R2, install the hotfix that is described in this article.
To resolve this issue in Windows Server 2012 R2, install update 2955164. This issue occurs because of a deadlock in Windows Management Instrumentation (WMI). Users randomly fail to connect to the remote applications that are hosted on a Windows Server 2012 R2 or Windows Server 2008 R2 Service Pack 1 (SP1)-based computer. I hope this article helps, and saves hours and hours of stepping through configuration issues with Server 2012 VDI.Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows Server 2012 R2 Standard Windows Server 2008 R2 Service Pack 1 Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Standard Windows Server 2008 R2 Foundation More. You must enable/accept Promiscuous Mode on the vSwitch. You need to edit the VMware vSwitch that the Windows Hyper-V VM is running on (and all others if you run vSphere and ever want to vMotion or migrate the VM). You may see this if you happen to be running the Hyper-V server on ESXi/vSphere (Not a supported configuration strictly speaking). This one took quite a while to figure out.
You may also find that if you boot the VM in Hyper-V, that you will get information via DHCP, but you will only be able to ping the host, and not the internet or other servers. “Remote Desktop Virtualization Host failed to verify domain connectivity of the virtual machine” with Event ID 8464 I had got through the first reboot of the RDS/VDI installation, but kept getting errors at the last stage (Creating the Remote Desktop Collection). I had tried to manually create the collection (using the tasks drop-down) in server manager->Remote Desktop Services->Collections, but no joy. So, you have managed all of the above, yet you STILL can’t complete the Remote Desktop collection to complete. Install the latest version of integration services from the Action menu when connected to the VM in Hyper-V. If you did, you may want to create a VM on the 2012 HyperV server and start it. VHD from another machine (or even VMware Workstation and use something like the (free) Starwind V2V Image Converter to convert from. The next thing to consider is: did you build the. You must enable nested VM’s by editing the VMX file
If after that, you still get a failure, and you are running ESX 5.1 as a host for this server, you may get this error: “ Hyper-V cannot be installed: A hypervisor is already running“. Rebuild the VM and install the RDS roles you need before updating the server! Well it may not be so easy, depending if you have installed windows updates (specifically KB2821895 ) or you have chosen VMware to host the RDS server.Īs of today, if you cannot install RDS on Server 2012 and you have installed windows updates including KB2821895, you will find that you cannot remove it, and have to rebuild the server to get Remote Desktop Services and VDI to install. There are a few articles explaining how easy it is to set up RDS or VDI in Server 2012. By Darryl Leaning on Augin Virtualization, Windows