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

We have a problem with one of our clients where the default printer he uses isn't loaded by the time the app that he uses over terminal services is launched. If you check again a minute later the printer is there but the app reads the default printer at the time of launch.

Is it possible to get the login process to delay till all printers are loaded?

The user is in a remote location so we have no direct access to the printers.

share|improve this question
How exactly is the user printing? Is the client coming from a local network, or external? Is he printing through the RDP client, is the printer being added by a script while they connect? – Zoredache Dec 13 '10 at 21:03
External network, printing through the RDP client. The printers are being handled by the Remote Desktop client, not a script. – Robert Richardson Dec 14 '10 at 0:50

We 'fixed' this issue (slow printer mappings) by adding the printers locally to our terminal servers (Not going through a print server). That doesn't directly answer your question of 'how to make login seem slower', but it does somewhat resolves your original issue.

share|improve this answer

Could you set up his app shortcut if he uses that method or the setting in TS to run the app on startup to use one of the "timer tools" (wait.exe is an oldie that comes to mind) to delay the start of the app? e.g. set up a command file that will run "wait 60" and then "c:\program.exe"

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.