I have Window Server 2012 DirectAccess deployed. I'm working on deploying a VDI through Server 2012 (on a different server). Internally I am able to go tohttps://vdiserver.domain.local/RDWeb and log in, then click the collection and be connected to one of the VM's. The problem is that when I do the same externally, it goes through most of the process of connecting to the RDP session (including "Loading virtual machine" and then dies on "Initiating Remote Connection". The general error message would lead you to believe that it's either turned off, remote access is not enabled or that the remote computer is not available on the network.
If I put the FQDN of one of the virtual machines (VDI-2.domain.local) into the RDP client, I can RDP to it, but it won’t use the User Profile Disks I have setup.
Therefore it seems like it’s something that doesn’t play nicely between the Remote Desktop Connection Broker and DirectAccess.
Does anyone have an idea of what the problem might be?