Hello,
Does anyone know if Windows 10 1607 is supported in a 2012 R2 RDS virtual desktop infrastructure?
We have been using pooled virtual desktops for our employees successfully since the arrival of Windows 10 10240. All servers involved are 2012 R2 and has been recently
updated. At another office we are running the same set up using Windows 10 1511, also without any problems.
Last week we decided to upgrade our reference image with Windows 10 1607. After the upgrade we ran in to a bunch of problems.
The VDI:s frequently loses network connection for no apparent reason, nothing is logged on the Hyper-V host. Disconnecting/connecting the virtual adapter solves it, but
it usually loses connection again in a couple of hours.
The user profile disks sometimes stick to the VM when the user logs out, this results in user getting a temporary profile on the next logon because the UPD is locked.
This occurs because the VM is not automatically reverted when the user logs out, I can fix this manually by reverting the VM.
When we updated the collection we got Event 4000 for every VM in the pool:
Hyper-V Volume Shadow Copy Requestor failed to connect to virtual machine 'OFFICE-VDI-01' because the version does not match the version expected by Hyper-V (Virtual machine
ID CB319BC0-CB86-4E97-8EC3-71A36EE4A062). Framework version: Negotiated (0.0) - Expected (3.0); Message version: Negotiated (0.0) - Expected (5.0). To fix this problem, you must upgrade the integration services. To upgrade, connect to the virtual machine and
select Insert Integration Services Setup Disk from the Action menu.
On the Connection Broker we get a lot of these errors:
Event 1296
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
Event 1306
Remote Desktop Connection Broker Client failed to redirect the user
Event 802
RD Connection Broker failed to process the connection request for user
Event 1285
Failed to spin VM OFFICE-VDI-01.office.it-hosting.se on host RDSHOST. Error: VM plugin failed to wakeup a VM.
Today we reverted all VMs back to 10240 and all went back to normal. From this I can only draw the conclusion that Windows 10 1607 is not supported in a Virtual Desktop
Infrastructure on Windows Server 2012 R2, but I cannot find any information on the subject.
My plan now is to keep running 10240 until server 2016 arrives, then I might give 1607 a new shot.
/Marcus