Terminal server printing

[Uraken]

Hi, all does anyone have any any vbs scripts that will map network printers from the application compabilty scripts folder on terminal services?
I want to map some printers but already use a login script in AD for my fat clients and don't really want to add to it.
Any help as always hugely appreciated.
regards
uraken.

[Ric_]

If you look at my script in the scripts forum, you will find that it works for both fat and thin clients.

[Uraken]

nice one mate which one (give us a clue)

[Ric_]

http://edugeek.net/index.php?name=Fo...iewtopic&t=404 is the link you want... there is also a list of the best scripts at http://edugeek.net/index.php?name=Fo...ewtopic&t=1076

Hope this helps

[Uraken]

nice one ric this is what i need, but i'm having problems modifying it i want the script to look at clientnames called english* and map a single network printer to it in TS, what bits do i need to get rid of ?
cheers for your time this far mate.

[Ric_]

There should be a line that reads

Select Case (Left(ComputerName, 4))

This looks at the first 4 characters of the computername (clientname in the case of thin clients) and then maps the printers accordingly. You could use the following after the Select...

Case "engl"
    WshNetwork.AddWindowsPrinterConnection "\\server\share"
...

[Uraken]

thanks ric managed to get it working, all be it running it locally, i had put it in my c:\WINDOWS\Application Compatibility Scripts\Logon folder named printers.vbs but this doesn't work which is odd because all my drive mappings work form here?

[Ric_]

You need to ru nthe script as a logon script (and make sure that the printer drivers are installed first - sometimes this can prevent the mappings working properly).

[Uraken]

i don't want to run it as a logon script (i already have a fat client one) but i have it sorted now i have to call it from a script in c:\windows\system32, thanks for all your help i could not have achieved this without your help mate.

[Ric_]

@Uraken: I don't see why you wouldn't want to use one script for both fat and thin clients...

Anyway... you can set a different logon script in the user properties pages for when they log onto terminal services.