[THIN] Re: Setting up network Printers on Windows 2003 Terminal Server issue
- From: "Rosemary Sarkis" <rosemary_sarkis@xxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Mon, 26 Jul 2004 23:18:06 +1000
Thanks for the replies.... I shall go with either Kix or VBS
The kix code below seems easy enough..
IF INGROUP ("Sample")
ADDPRINTERCONNECTION ("\\SERVER1\Sampleprinter1")
SETDEFAULTPRINTER ("\\SERVER1\Sampleprinter1")
ENDIF
The VBS Code is a little more confusing. How do I specify a if in group
.... then create printer. What is the VB code required for this logic (if
in group)?
Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.AddWindowsPrinterConnection "\\<servername>\<printername>"
WshNetwork.SetDefaultPrinter "\\<servername>\<printername>"
Is there any advantages in using either language for printer creation? Is
one faster or better than the other??
In regards to the printer that is created, is it a link to the printer on
our print server - eg will it retain the configuration of the existing
printers or do they need to be customised again
Thanks heaps. You have all been so helpful
Rose
-----Original Message-----
From: Jeff Durbin [mailto:techlists@xxxxxxxxxxxxx]
Sent: Monday, July 26, 2004 5:08 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Setting up network Printers on Windows 2003 Terminal
Server issue
You can add a script to the logon process that adds printer connections
for users based on group. If you want slow but easy, you can use
IFMEMBER from the ResKit, but calling an EXE 100 times (once for each
printer) from a CMD will take forever. You can also test group
membership and add printer connections in VBScript or Kix which will be
much faster than IFMEMBER.
JD
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Rosemary Sarkis
Sent: Monday, 26 July 2004 7:22 p.m.
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Setting up network Printers on Windows
2003 Terminal Server issue
Thanks for the replies
The user has rights as they can browse the printers on the print server and
connect/add them. Its a pity they are user specific. I was thinking of
maybe setting up all printers as a test user then copying that ntuser.dat
to the default user but that may be troublesoon when new printers come
onboard..
The users could browse the printers on the print server and select the
one they want to print to but they are not that bright. I want an easy way
to display all printers on our print server to each user. I don't want to
create new ports on the WTS either as Id have to configure all 100+
printers manually - too time consuming... Its so much easier with
Citrix...
Is there anything I can put maybe in a login script that would help - ie if
member of group ... add printer .... I really want a simple solution but
be flexible for new printers - does such a thing exist???
or do I have to recreate all printers on the WTS box...
Thanks guys
[THIN] Re: Setting up network Printers on Windows 2003 Terminal Server
issue
From: "cherie.watts" <cherie.watts@xxxxxxxxxxx>
To: thin@xxxxxxxxxxxxx
Date: Mon, 26 Jul 2004 14:11:39 +1000
Hi Rosemary
When you map a printer, the connection is created under HKCU. This isn't
available to any other users.
However all of the printer drivers are now installed onto the Windows 2003
tse server. So you could just allow your users to map whatever printers
they need.
I would enable policy's to prevent them from installing printer drivers.
The only other slightly sensible suggestion would be to create installed
printer queues but instead of going to the printer, create a
local port and connect it to the Server\printer sharename. This way there
is no contention for the printer. But you will have to re-setup your
printer settings.
That's all I can think of.
Cheers
Cherie
_________________________________________________________________
SEEK: Now with over 50,000 dream jobs! Click here:
http://ninemsn.seek.com.au?hotmail
********************************************************
This weeks sponsor Emergent Online Thinssentials Utilities
Using the latest software, hardware, networking technologies, proven technical expertise, proprietary software and best practices, EOL provides custom-tailored solutions for each client?s mission and specific goals.
http://www.go-eol.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
