Thanks for all your reply!!

I tested the following and it works.
-----------------------------------------
If @UserID = bob

AddPrinterConnection("\\lnx1\Brother_8860")
delPrinterConnection("\\lnx1\hp4000")
SetDefaultPrinter("\\lnx1\Brother_8860")

EndIf

If @UserID = jdole

delPrinterConnection("\\ps1\Brother_8860")
AddPrinterConnection("\\lnx1\hp4000")
AddPrinterConnection("\\lnx1\Brother_8860")
SetDefaultPrinter("\\lnx1\hp4000")

EndIf

*** I have a few questions ***.

1)

Select
Case @UserID = XXX
addprinter...
Case @UserID = YYY
addprinterconnection...
Case 1
;No match
Endselect

What does Case 1 mean at the 3rd line from the last line of the code above?

2) If I can recall in the past, if you specify the code below, you are just verifing if the printer connection exists (if not then add).

If AddPrinterConnection("\\lnx1\hp4000") = 0

3)On our indiviual user account, we currently specify a standard windows .bat file for mapping user's drive. For pushing out the printers, I plan to use kixtart and put it in the OU policy/user/logon. There shouldn't be any conflict with two different types of batch processing?

4) I have been out of the user side support for a while now. When you add printers via a script like kixtart vs adding the printers manually, do you lose the ability to see the printer's tray?

5) If deploying a script like kixtart, do i have to be concern about the drivers being loaded to the machine properly. All the workstation are windows xp pro. So far the user accounts I have tested didn't run into any problem without specifying the drivers. Seems like XP Pro reconized most of the printers we deploy. Both the old print server and new print server carry the same printers/drivers, but different share names.

6) For a large script like what we plan to use. Is there a code that we can specify if there is a problem the script skips to the next line of code?


TIA,
tt

Edited by Tony (2008-04-17 10:46 AM)