The printer driver is unknow: when users log into 2003 Terminal

[The Rev]

I run two .VBS scripts in AD that add printers to the users machines. It
works good when the users log into their computers at work. When the users
connect to the 2003 R2 SP2 term srv, they reveive a windows script host popup
that has the path to the policy and has code: 80070705. All they have to do
is click OK and it goes away. It has now become anoying to the partner group.

I loaded the printer drivers onto the term srv and this error yet appears.
All of my .bat script load good.

Is there a conflict with VBS scripts and term srv?

Thank you in advance.

 

[Frane]

Re: The printer driver is unknow: when users log into 2003 Terminal

Re: The printer driver is unknow: when users log into 2003 Terminal

Take a look at following article http://support.microsoft.com/kb/297454


_______________________________________________________
Frane Borozan
Terminal Services and Citrix Presentation Server user logging
www.terminalserviceslog.com

 

[Vera Noest [MVP]]

Re: The printer driver is unknow: when users log into 2003 Terminal

No, but it seems likely that you are assuming that users have the
same rights to the filesystem or the registry on the TS as on a
client. That's normally not the case.

On a sidenote: why do you need to manipulate the printers at all in
the user sessions on the TS? If they have the correct printers
configured on the client, why not rely on printer redirection?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGhlIFJldg==?= <TheRev@discussions.microsoft.com> wrote
on 02 apr 2008 in microsoft.public.windows.terminal_services:

> I run two .VBS scripts in AD that add printers to the users
> machines. It works good when the users log into their computers
> at work. When the users connect to the 2003 R2 SP2 term srv,
> they reveive a windows script host popup that has the path to
> the policy and has code: 80070705. All they have to do is click
> OK and it goes away. It has now become anoying to the partner
> group.
>
> I loaded the printer drivers onto the term srv and this error
> yet appears. All of my .bat script load good.
>
> Is there a conflict with VBS scripts and term srv?
>
> Thank you in advance.

 

[The Rev]

Re: The printer driver is unknow: when users log into 2003 Termin

Re: The printer driver is unknow: when users log into 2003 Termin

Article ID : 297454 does not work for me.
I do rely on print redirect. The users are picking up the login script from
their orginal OU policy. There isn't a printer install on the term srv OU
policy.
How do I go about canceling the users original OU printer policy and just
apply the Term OU policy? I'm using the Loopback also.

"Vera Noest [MVP]" wrote:

> No, but it seems likely that you are assuming that users have the
> same rights to the filesystem or the registry on the TS as on a
> client. That's normally not the case.
>
> On a sidenote: why do you need to manipulate the printers at all in
> the user sessions on the TS? If they have the correct printers
> configured on the client, why not rely on printer redirection?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?VGhlIFJldg==?= <TheRev@discussions.microsoft.com> wrote
> on 02 apr 2008 in microsoft.public.windows.terminal_services:
>
> > I run two .VBS scripts in AD that add printers to the users
> > machines. It works good when the users log into their computers
> > at work. When the users connect to the 2003 R2 SP2 term srv,
> > they reveive a windows script host popup that has the path to
> > the policy and has code: 80070705. All they have to do is click
> > OK and it goes away. It has now become anoying to the partner
> > group.
> >
> > I loaded the printer drivers onto the term srv and this error
> > yet appears. All of my .bat script load good.
> >
> > Is there a conflict with VBS scripts and term srv?
> >
> > Thank you in advance.
>

 

[The Rev]

RE: The printer driver is unknow: when users log into 2003 Terminal

Here is the .VS that is loading for the printers.

Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.AddWindowsPrinterConnection "\\Domain Controller\ColorPrinter"
set WshShell = CreateObject("WScript.Shell")

"The Rev" wrote:

> I run two .VBS scripts in AD that add printers to the users machines. It
> works good when the users log into their computers at work. When the users
> connect to the 2003 R2 SP2 term srv, they reveive a windows script host popup
> that has the path to the policy and has code: 80070705. All they have to do
> is click OK and it goes away. It has now become anoying to the partner group.
>
> I loaded the printer drivers onto the term srv and this error yet appears.
> All of my .bat script load good.
>
> Is there a conflict with VBS scripts and term srv?
>
> Thank you in advance.

 

[Vera Noest [MVP]]

Re: The printer driver is unknow: when users log into 2003 Termin

Re: The printer driver is unknow: when users log into 2003 Termin

If a GPO linked to the OU which contains the user accounts is still
applied to them when they logon to the TS, then your loopback
policy isn't functioning. Or maybe you configured it to "Merge" in
stead of "Replace"?

Use Resultant Set of Policies (RSoP) to see which GPOs are applied
to your users when they logon to the TS.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGhlIFJldg==?= <TheRev@discussions.microsoft.com> wrote
on 02 apr 2008 in microsoft.public.windows.terminal_services:

> Article ID : 297454 does not work for me.
> I do rely on print redirect. The users are picking up the login
> script from their orginal OU policy. There isn't a printer
> install on the term srv OU policy.
> How do I go about canceling the users original OU printer policy
> and just apply the Term OU policy? I'm using the Loopback also.
>
> "Vera Noest [MVP]" wrote:
>
>> No, but it seems likely that you are assuming that users have
>> the same rights to the filesystem or the registry on the TS as
>> on a client. That's normally not the case.
>>
>> On a sidenote: why do you need to manipulate the printers at
>> all in the user sessions on the TS? If they have the correct
>> printers configured on the client, why not rely on printer
>> redirection?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?VGhlIFJldg==?= <TheRev@discussions.microsoft.com>
>> wrote on 02 apr 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > I run two .VBS scripts in AD that add printers to the users
>> > machines. It works good when the users log into their
>> > computers at work. When the users connect to the 2003 R2 SP2
>> > term srv, they reveive a windows script host popup that has
>> > the path to the policy and has code: 80070705. All they have
>> > to do is click OK and it goes away. It has now become anoying
>> > to the partner group.
>> >
>> > I loaded the printer drivers onto the term srv and this error
>> > yet appears. All of my .bat script load good.
>> >
>> > Is there a conflict with VBS scripts and term srv?
>> >
>> > Thank you in advance.

 

[The Rev]

RE: The printer driver is unknow: when users log into 2003 Termin

RE: The printer driver is unknow: when users log into 2003 Termin

My loopback policy was set to Merge. It was also in a OU with a 2K Term Srv.
I had to change it to Replace and I moved it into an OU by it self. This
fixed my problem.
Thank you for your help.

"The Rev" wrote:

> Here is the .VS that is loading for the printers.
>
> Set WshNetwork = CreateObject("WScript.Network")
> WshNetwork.AddWindowsPrinterConnection "\\Domain Controller\ColorPrinter"
> set WshShell = CreateObject("WScript.Shell")
>
> "The Rev" wrote:
>
> > I run two .VBS scripts in AD that add printers to the users machines. It
> > works good when the users log into their computers at work. When the users
> > connect to the 2003 R2 SP2 term srv, they reveive a windows script host popup
> > that has the path to the policy and has code: 80070705. All they have to do
> > is click OK and it goes away. It has now become anoying to the partner group.
> >
> > I loaded the printer drivers onto the term srv and this error yet appears.
> > All of my .bat script load good.
> >
> > Is there a conflict with VBS scripts and term srv?
> >
> > Thank you in advance.