you said: why not always set the users default printer to correct one

because this is a terminal server supporting many physical offices, there really is no way to identify the correct one cept by user edict. Plus users roam from office to office so default today may not be right default tomorrow.

You said: if not possible, alert the user that default printer is not available

Well because they (the printers) are all installed at the Terminal Server, technically they are all available. But they hit print and it shows up in Chicago...Mostly because they forget (or don't bother) to verify what their default is (was). I hope I'm making sense...

Example...I'm working in the Orland Office. Tricerat maps my local printers to the TS as *** Orlando - Laserjet 1 ***. I make it my default. End of day I close my laptop and head to Chicago. Log and Tricerat maps my *** Chicago - Laserjet 1 ***. I hit print and it goes to Orlando. OOps.

I must mention that part of my problem is this bug in TS where the deafult printer seems to change without rhyme or reason.I have really beat that dead horse to death. No one has any answers but many people have same problem. I figured this script would require "minor" user intervention but dramatically improve my helpdesk call volume as the number one gripe we get is the default printer bug.

I hope that makes more sense...