Hello All,
I am desperately reaching out to you all in hopes someone out there has an answer to my problem. Currently, we have 5 terminal servers at one our clinical sites in which users connect to via RDP through thin clients. In short, the issue I have is:
Scenario:
User 'A' from Pediatrics connect via RDP to Terminal Server '1' in which a network printer is mapped via GPP using item targeting rules to match the TS client name.
In the meantime...user 'A' keeps her session open from Pediatrics and decides to open a new session at Internal Medicine. She RDP's to the same server which is Terminal Server '1'. The issue is instead of her RDP session being a new session she is connecting back to the same session when she was in Pediatrics.
Now we Single Session is disabled so multiple sessions are allowed on all of our Terminal Servers. The problem really comes down to the mapping of printers.
How prevent users from connecting to the same terminal server when using a load balancer (2x load balancing) or how to correctly enable users to create two sessions on the same terminal server (meaning build two user profiles--let's say user1.wmg...user1.wmg.wmg..etc)
Any help would be much appreciated!