Greetings, fellow techies!!
I come to you with what may seem as an odd request.
My firm is considering building a thin-client solution for certain clients. We (I) normally operate with ESXi and other VMWare-related solutions. However, we have decided to go via Hyper-V Server 2012 (Core, not Windows Server with a Role) for this particular scenario. So, enough chatter.
Can anyone please inform me how or even if this can be done?: I would like to use the Hyper-V server as a "pointer" to VMs depending on what username is given. For example: On my thin-client, I would only specify the Hyper-V server. At that point, I want to enter Windows Domain credentials. Depending on what I enter as username, I want it to go to a certain VM.
Let's say I have 5 VMs in Hyper-V (Hyper-V IP is 192.168.1.200). One of their HostName is Tommy-PC, and its IP is 192.168.1.201. Now when the user boots their thin client, which is pointing to the Hyper-V at 192.168.1.200, he would type his username and password and it will automatically send him to HostPC "Tommy-PC(192.168.1.201)" without ever typing in or storing the IP or HostName. In a sense it would be ActiveDirectory/User-based connection, where the destination is pre-defined somewhere. Where is that somewhere?! :)
Thanks in advance for your replies.
Really, anything that will help me make Hyper-V as a HUB of sorts, rather than using RDP with direct IP's/hostnames to the hosts. We want as little user-error-margin as possible; so doing this as a pre-defined rule seems the best route.
*Update*Theory. Just remembered the Personal Virtual Desktop... Or rather I saw it in the AD and remembered haha. So I think if I make the DC into an RDS host or the Hyper-V, via the Remote Desktop Connection Manager, I should be able to point. Let's see!