Hi,
I have a test environment with one Windows Server 2012. I created a Quick VM Collection, to test a few Zero Clients. When I tried to log on with a zero client, I recognized that I logged on to the VDI host through an RDP session, instead of a VM in the pool.
I searched for some time and I finally found a thread where a guy wrote that he created a registry key "DefaultTsvUrl" with the value "tsv://vmresource.1.<pool name here>." to this location: HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\ClusterSettings
Although it did the trick, now I have another problem.
When I was able to login to the Quick VM Collection (which is Pool Managed by design), I created another collection to the same VDI host (because I have only one server). It created successfully, but when I try to logon to a personal collection VM, I cannot because it connects to a Pool Managed vm. I think it is because of the registry setting I mentioned above.
So if I add the registry key, I'm able to logon only to Pool Managed VM's, if I don't add the registry key, I'm only able to logon to personal VM's.
If I'm looking at RDWeb, that is OK and everything works. But with zero client it's not worknig...
Any ideas?
Thanks,
Dvijne
Update:
I double check my settings and the behavior of the zero client. The results are:
With zero client I can use ONLY ONE collection, which I define in the registry with the "DefaultTsvUrl" key. It doesn't matter if it's a Pool Managed or a Personal collection...
