Here's the situation:
we have 4 relevant servers in the setup:
SRVEXT2 is DC, DNS, AD-Cert, RDS-License-Server - Win2k8
SRVEXT3 & 4 are Virtualization-Hosts with Hyper-V (no other RDS-Roles installed) clustered to Failover with attached SAN-Storage - Win2k8 R2
SRVEXT5 is a VM running on SRVEXT3/4 with RD-CB, RD-WA, RD-RG installed, running also Win2k8 R2
The VMs were cloned through the PowerShell-Script from technet and WMI/RPC is configured via GPO.
Now everything runs nearly fine (VMs etc.). But I have a BIG issue:
When I'm trying to connect a personal assigned Desktop (In fact it's the Machine-Account in the Active Directory that's assigned to the user) I get this "Cannot verify remote that the remote computer you are redirected to belongs to the same farm"-error.
I tried pretty much (certificates, reconfiguring everything etc.) but I don't know what went wrong. If I try to connect via RDWA I get the same error as when connecting through direct remote connection from a Desktop. I recognized no differences by trying this from Win7, Win2k8R2, Win2k8-machines.
When i have a look at the event-log from the CB everything looks normal:
The CB gets the request for a login
The CB looks up the VDI-VM for me
The CB returns the endpoint with IP/FQDN/NetBIOS as "Non-Farm" from vmresource.2
But still every RDP-Client complains about my VM not beeing a farm-member, although there is no Farm - CB runs in Virtual-Machine-Redirection-Mode as described in every tutorial.
When trying to connect with a thin-client (Axel) it works (in my opinion it works because the thin-client is kinda dumb and doesn't try to verify the whole story as the Win-RDP-client does).
I hope here's someone who can figure out a solution (in the 99 threads goggle returned there was unfortunately no solution)...