I need to set a test lab with MS Virtual Desktop Infrastructure. I have no free hardware server which could support Windows Server 2012 Hyper-V, so I have to stick to Windows Server 2008 R2.
I've set up all the components needed to support MS VDI: virtualization host (Windows Server 2008 R2), Connection Broker server (Windows Server 2008 R2 as well) and several VMs with Windows 7. I've configured Connection Broker and assigned a personal desktop to an user. All the servers are joined to AD and have certificates generated by domain enterprise CA.
I can access assigned workstation using RDWeb portal by clicking on "My Desktop" item. However, I cannot access it when entering Connection Broker server name into address field of Terminal Services Client. The client connects to the server, then gets redirected to the assigned workstation, and then shows the following error message:
"The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name."
This message is generated on Windows 7 client. On Windows 8 workstation the message contains more information:
"Remote Desktop Connection cannot connect to the remote computer.
The remote computer vdi.test.local that you are trying to connect to is redirecting you to another remote computer named WS01.test.local. Remote Desktop Connection cannot verify that the computers belong to the same RD Session Host server farm. You must use the farm name, not the computer name, when you connect to an RD Session Host server farm."
I've found several topics and TechNet articles discussing the similar issues, but they all are referincing classic TS server farms, not VDI infrastructure. There is no farm name to that I can connect, and I cannot configure RDP connection settings on virtual desktops. Just in case I tried to clear local DNS cache on all workstations and servers involved, but to no luck.