If I understand what you're asking for correctly, I think it's something that I see fairly often. Do I understand the situation correctly if I say that you have some end-point devices that you'd like to use, but they should always connect to the same View desktop? It can be done, but it can get tricky if you want to have unique AD users authenticate using their own credentials. Essentially, it starts with a service account for each end-point device. You can then create a dedicated assignment pool with the correct number of desktops to meet your needs, and assign each service account to its respective VM in the pool. Then, you can either set a value in the Run key of the registry or have a script run in the background that launches the View client with the service account username and password, and connects directly to the dedicated assignment pool. The end-point device will always connect to the View desktop it's assigned to then.
The tricky part is if you'd like it to stop before logging into Windows, so that an AD user can enter credentials to authenticate to Windows. To do that, you'll have to disable single signon using a group policy object with the adm files included on the connection server. But if nobody has authenticated to the Windows VM in 15 minutes after the service account has connected to the View desktop, the session will timeout and the service account will have to reconnect again.
Let me know if this makes any sense, or if you have any questions about what I'm suggesting. I'm sorry if I'm not understanding your situation correctly, and maybe offering advice on a completely unrelated subject.
Dave
