Default printers

[Guest]

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

We are getting ready to roll out several Terminal Servers to various users
who will be connecting from multiple locations. We do not want roaming
profiles to be used, but rather a custom, mandatory profile that the user can
only modify while logged on. We have created a set of GPOs which seem to work
rather well in redirecting My Docs, Desktop, etc.

The only issue we are having is with the printing. We have approx 20
different printers which have all been configured to print via IP directly on
the terminal servers. Is there someway to script the default printer via
login script/AD user attribute or through some other means so the user
doesn't have to manually select their printers? Our user base seems to have
issues with that. I am not opposed to publishing the printers in AD but I
need to know where to go from there. Thanks.

 

[Guest]

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Hi
We have arond 30 printers based in various locations here. I have a script
that installs printers and sets default based on the computer name. (From the
computer name I know which is the closest printer). This is run at log on.
Also the first line of script deletes all currently mapped printers. For
locations where there are multiple printers I install both and set the most
desired as default. (For example where there are colour printers in addition
to the usual.

Is this a possible solution for you? Would you like me to forward some code?

Jason

"pls help" wrote:

> We are getting ready to roll out several Terminal Servers to various users
> who will be connecting from multiple locations. We do not want roaming
> profiles to be used, but rather a custom, mandatory profile that the user can
> only modify while logged on. We have created a set of GPOs which seem to work
> rather well in redirecting My Docs, Desktop, etc.
>
> The only issue we are having is with the printing. We have approx 20
> different printers which have all been configured to print via IP directly on
> the terminal servers. Is there someway to script the default printer via
> login script/AD user attribute or through some other means so the user
> doesn't have to manually select their printers? Our user base seems to have
> issues with that. I am not opposed to publishing the printers in AD but I
> need to know where to go from there. Thanks.

 

[Guest]

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

I think it would be very useful if you could post some code here, especially
the code for deleting all printers.

Regards

Oli


"Jason André" <JasonAndr@discussions.microsoft.com> wrote in message
news:16E2DDE8-A160-48F7-8410-4FF89CE128FA@microsoft.com...
> Hi
> We have arond 30 printers based in various locations here. I have a script
> that installs printers and sets default based on the computer name. (From
> the
> computer name I know which is the closest printer). This is run at log on.
> Also the first line of script deletes all currently mapped printers. For
> locations where there are multiple printers I install both and set the
> most
> desired as default. (For example where there are colour printers in
> addition
> to the usual.
>
> Is this a possible solution for you? Would you like me to forward some
> code?
>
> Jason
>
> "pls help" wrote:
>
>> We are getting ready to roll out several Terminal Servers to various
>> users
>> who will be connecting from multiple locations. We do not want roaming
>> profiles to be used, but rather a custom, mandatory profile that the user
>> can
>> only modify while logged on. We have created a set of GPOs which seem to
>> work
>> rather well in redirecting My Docs, Desktop, etc.
>>
>> The only issue we are having is with the printing. We have approx 20
>> different printers which have all been configured to print via IP
>> directly on
>> the terminal servers. Is there someway to script the default printer via
>> login script/AD user attribute or through some other means so the user
>> doesn't have to manually select their printers? Our user base seems to
>> have
>> issues with that. I am not opposed to publishing the printers in AD but I
>> need to know where to go from there. Thanks.

 

[Guest]

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Oli,
I am not in the office until Monday, but will certainly post the code then.

Jason

"Jason André" wrote:

> Hi
> We have arond 30 printers based in various locations here. I have a script
> that installs printers and sets default based on the computer name. (From the
> computer name I know which is the closest printer). This is run at log on.
> Also the first line of script deletes all currently mapped printers. For
> locations where there are multiple printers I install both and set the most
> desired as default. (For example where there are colour printers in addition
> to the usual.
>
> Is this a possible solution for you? Would you like me to forward some code?
>
> Jason
>
> "pls help" wrote:
>
> > We are getting ready to roll out several Terminal Servers to various users
> > who will be connecting from multiple locations. We do not want roaming
> > profiles to be used, but rather a custom, mandatory profile that the user can
> > only modify while logged on. We have created a set of GPOs which seem to work
> > rather well in redirecting My Docs, Desktop, etc.
> >
> > The only issue we are having is with the printing. We have approx 20
> > different printers which have all been configured to print via IP directly on
> > the terminal servers. Is there someway to script the default printer via
> > login script/AD user attribute or through some other means so the user
> > doesn't have to manually select their printers? Our user base seems to have
> > issues with that. I am not opposed to publishing the printers in AD but I
> > need to know where to go from there. Thanks.

 

[Guest]

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Great. Looking forward to seeing the code.

Oli


"Jason André" <JasonAndr@discussions.microsoft.com> wrote in message
news:731942F0-BAE3-4E65-BD18-AFEC7F284503@microsoft.com...
> Oli,
> I am not in the office until Monday, but will certainly post the code
> then.
>
> Jason
>
> "Jason André" wrote:
>
>> Hi
>> We have arond 30 printers based in various locations here. I have a
>> script
>> that installs printers and sets default based on the computer name. (From
>> the
>> computer name I know which is the closest printer). This is run at log
>> on.
>> Also the first line of script deletes all currently mapped printers. For
>> locations where there are multiple printers I install both and set the
>> most
>> desired as default. (For example where there are colour printers in
>> addition
>> to the usual.
>>
>> Is this a possible solution for you? Would you like me to forward some
>> code?
>>
>> Jason
>>
>> "pls help" wrote:
>>
>> > We are getting ready to roll out several Terminal Servers to various
>> > users
>> > who will be connecting from multiple locations. We do not want roaming
>> > profiles to be used, but rather a custom, mandatory profile that the
>> > user can
>> > only modify while logged on. We have created a set of GPOs which seem
>> > to work
>> > rather well in redirecting My Docs, Desktop, etc.
>> >
>> > The only issue we are having is with the printing. We have approx 20
>> > different printers which have all been configured to print via IP
>> > directly on
>> > the terminal servers. Is there someway to script the default printer
>> > via
>> > login script/AD user attribute or through some other means so the user
>> > doesn't have to manually select their printers? Our user base seems to
>> > have
>> > issues with that. I am not opposed to publishing the printers in AD but
>> > I
>> > need to know where to go from there. Thanks.