Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up my organization's first Terminal Server / Remote Desktop Session Host (RDSH) for Lab use. We are a college, and I am wanting to use this server (or more servers configured similarly in a farm) to power other labs on campus as well. Each of those labs will have its own shared printer.

Ideally, the thin clients would not need to have any knowledge of the printer that is in the area, as they won't be needing to print in the first place. Because the thin clients are re purposed hardware, we will be installing windows 7 on them, joining them to the domain, and using Group Policy to lock them down to minimal thin clients.

Is there some way that I can use Group Policy or Logon Scripts to have the thin client's location (Organizational Unit or something) determine which printer installed on the Server should be allowed/default to a user connecting from a given thin client?

A friend of mine in a similar situation (but unable to add the thin clients to active directory) was only able to accomplish this by having different terminal servers. In the case that we couldn't join the thin clients to the domain, is there any way that we can determine access / default printer appropriately?

share|improve this question
You could easily do this based on the user that's logging on but I'm stumped as to how to do it based on the computer they log on from. – joeqwerty Aug 11 '11 at 17:42

Do you have separate subnets for each of these labs? I would probably set up different profiles to be used depending on the different labs and dole the values out via DHCP. I've done similar at my employer except that it's separated by floors. Each floor has its own subnet, which is setup to a scope in DHCP. DHCP option 162 differs for each scope.

share|improve this answer

In order to programatically determine the location of a machine as it is logging in through scripting, two possible considerations:

  1. A naming schema which identifies the location (e.g. computer name = building-room-system)
  2. Creating AD containers that identify/group location and placing the systems into them accordingly

Scripting can then key off of the information and then assist in making adjustments as part of the login process.

share|improve this answer
It sounds like you know that this works. I'm thinking that I'll probably use OUs to signify locations of the thin clients, but I still am not sure how to obtain the info I require in a login script. Can you give some trivial example code that could get me the name of the computer, or perhaps a link to some code that already does searching through active directory? – Ryan H Aug 13 '11 at 5:12… – user48838 Aug 13 '11 at 10:36

I've tried the above method. The instructions are are well outlined here...

Obviously an ugly method that mentioned is basically having a double login. Login to the local system which already has local printers setup (or can easily be setup) and use the re-direction capabilities of Windows so that you can access locally available printers via RDP from the terminal server,

If you use system imaging/remote package management of the thin clients than obviously it won't be too tedious?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.