Local printer not redirected for all clients

  • Thread starter Thread starter Jonathan Wood
  • Start date Start date
J

Jonathan Wood

Guest
Hi all,

In our company we're using 2 Terminal servers each running Windows Server
2003 R2 + SP1 in a domain environment. Each server is used by approx. 60
users and 100 network-enabled printers (most of them are HP LaserJets) are
installed on the servers.

The oldest server was installed in 2004 and has been running fine without
any serious problems. However, at the beginning of this week its print
spooler kept on crashing. I suspected that corrupted drivers could be the
issue and deleted all printers from the server using the 'cleanspl.exe'
utility from the Support Tools.

I manually added all 100 printers to the system using the mainly the latest
version of the HP Universal driver (really saves a lot of disk space). All
printers installed on the server work fine again. However, clients with a
local attached printer cannot use their printer in the Terminal session
anymore because it's no longer redirected. If they login on the other server
their printers show up in the session and work perfectly.

Both servers are using the same Terminal Server settings and are affected by
the same GPO. A Fallback printer driver (default HP Deskjet 500) is
configured in the GPO and works fine on the TS without printer problems. The
TS experiencing the printer issues has the HP Deskjet 500 driver installed
and doesn't use the Fallback printer even though it should.

The event logs do show some printing errors but none relate to the
redirection of printers. I've checked all places where redirection can be
controlled: RDP client, user profile, TS Configuration, GPO, registry keys,
etc. All settings are identical on both servers, however printer redirection
works on one server and not the other.

I hope someone can help me solve this issue.

Thanx in advance,

Jonathan
 
Re: Local printer not redirected for all clients

On the second TS server, where redirection works fine, is the printer
redirected with fallback redirection or with matching printer redirection?

What are the printing event log errors reported on the server where
redirection fails, even if they are not redirection related?

--
Thanks,
Priya.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jonathan Wood" <j.wood62@gmail.com> wrote in message
news:O%23HYLrbWIHA.4880@TK2MSFTNGP03.phx.gbl...
> Hi all,
>
> In our company we're using 2 Terminal servers each running Windows Server
> 2003 R2 + SP1 in a domain environment. Each server is used by approx. 60
> users and 100 network-enabled printers (most of them are HP LaserJets) are
> installed on the servers.
>
> The oldest server was installed in 2004 and has been running fine without
> any serious problems. However, at the beginning of this week its print
> spooler kept on crashing. I suspected that corrupted drivers could be the
> issue and deleted all printers from the server using the 'cleanspl.exe'
> utility from the Support Tools.
>
> I manually added all 100 printers to the system using the mainly the
> latest version of the HP Universal driver (really saves a lot of disk
> space). All printers installed on the server work fine again. However,
> clients with a local attached printer cannot use their printer in the
> Terminal session anymore because it's no longer redirected. If they login
> on the other server their printers show up in the session and work
> perfectly.
>
> Both servers are using the same Terminal Server settings and are affected
> by the same GPO. A Fallback printer driver (default HP Deskjet 500) is
> configured in the GPO and works fine on the TS without printer problems.
> The TS experiencing the printer issues has the HP Deskjet 500 driver
> installed and doesn't use the Fallback printer even though it should.
>
> The event logs do show some printing errors but none relate to the
> redirection of printers. I've checked all places where redirection can be
> controlled: RDP client, user profile, TS Configuration, GPO, registry
> keys, etc. All settings are identical on both servers, however printer
> redirection works on one server and not the other.
>
> I hope someone can help me solve this issue.
>
> Thanx in advance,
>
> Jonathan
>
 
Re: Local printer not redirected for all clients

The second (working) TS server redirects the printers with the matching
printer driver.

However, the problem on the malfunctioning TS server seems to be fixed. When
I used the cleanspl utility I was overzealous and deleted the following
print monitors as well:

- BJ Language print monitor

- USB Monitor print monitor

which proved to be a stupid move. Once I added these print monitor back to
the server again the redirection worked flawlessly.

Thanx for the effort though :)

- Jonathan

"Priya Raghavan [MSFT]" <priyadr@online.microsoft.com> wrote in message
news:%23EVSg3%23WIHA.4828@TK2MSFTNGP05.phx.gbl...
> On the second TS server, where redirection works fine, is the printer
> redirected with fallback redirection or with matching printer redirection?
>
> What are the printing event log errors reported on the server where
> redirection fails, even if they are not redirection related?
>
> --
> Thanks,
> Priya.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jonathan Wood" <j.wood62@gmail.com> wrote in message
> news:O%23HYLrbWIHA.4880@TK2MSFTNGP03.phx.gbl...
>> Hi all,
>>
>> In our company we're using 2 Terminal servers each running Windows Server
>> 2003 R2 + SP1 in a domain environment. Each server is used by approx. 60
>> users and 100 network-enabled printers (most of them are HP LaserJets)
>> are installed on the servers.
>>
>> The oldest server was installed in 2004 and has been running fine without
>> any serious problems. However, at the beginning of this week its print
>> spooler kept on crashing. I suspected that corrupted drivers could be the
>> issue and deleted all printers from the server using the 'cleanspl.exe'
>> utility from the Support Tools.
>>
>> I manually added all 100 printers to the system using the mainly the
>> latest version of the HP Universal driver (really saves a lot of disk
>> space). All printers installed on the server work fine again. However,
>> clients with a local attached printer cannot use their printer in the
>> Terminal session anymore because it's no longer redirected. If they login
>> on the other server their printers show up in the session and work
>> perfectly.
>>
>> Both servers are using the same Terminal Server settings and are affected
>> by the same GPO. A Fallback printer driver (default HP Deskjet 500) is
>> configured in the GPO and works fine on the TS without printer problems.
>> The TS experiencing the printer issues has the HP Deskjet 500 driver
>> installed and doesn't use the Fallback printer even though it should.
>>
>> The event logs do show some printing errors but none relate to the
>> redirection of printers. I've checked all places where redirection can be
>> controlled: RDP client, user profile, TS Configuration, GPO, registry
>> keys, etc. All settings are identical on both servers, however printer
>> redirection works on one server and not the other.
>>
>> I hope someone can help me solve this issue.
>>
>> Thanx in advance,
>>
>> Jonathan
>>
>
 
Re: Local printer not redirected for all clients

Thanks for the update.

--
Thanks,
Priya.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jonathan Wood" <j.wood62@gmail.com> wrote in message
news:e$GKPLOXIHA.4432@TK2MSFTNGP05.phx.gbl...
> The second (working) TS server redirects the printers with the matching
> printer driver.
>
> However, the problem on the malfunctioning TS server seems to be fixed.
> When I used the cleanspl utility I was overzealous and deleted the
> following print monitors as well:
>
> - BJ Language print monitor
>
> - USB Monitor print monitor
>
> which proved to be a stupid move. Once I added these print monitor back to
> the server again the redirection worked flawlessly.
>
> Thanx for the effort though :)
>
> - Jonathan
>
> "Priya Raghavan [MSFT]" <priyadr@online.microsoft.com> wrote in message
> news:%23EVSg3%23WIHA.4828@TK2MSFTNGP05.phx.gbl...
>> On the second TS server, where redirection works fine, is the printer
>> redirected with fallback redirection or with matching printer
>> redirection?
>>
>> What are the printing event log errors reported on the server where
>> redirection fails, even if they are not redirection related?
>>
>> --
>> Thanks,
>> Priya.
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Jonathan Wood" <j.wood62@gmail.com> wrote in message
>> news:O%23HYLrbWIHA.4880@TK2MSFTNGP03.phx.gbl...
>>> Hi all,
>>>
>>> In our company we're using 2 Terminal servers each running Windows
>>> Server 2003 R2 + SP1 in a domain environment. Each server is used by
>>> approx. 60 users and 100 network-enabled printers (most of them are HP
>>> LaserJets) are installed on the servers.
>>>
>>> The oldest server was installed in 2004 and has been running fine
>>> without any serious problems. However, at the beginning of this week its
>>> print spooler kept on crashing. I suspected that corrupted drivers could
>>> be the issue and deleted all printers from the server using the
>>> 'cleanspl.exe' utility from the Support Tools.
>>>
>>> I manually added all 100 printers to the system using the mainly the
>>> latest version of the HP Universal driver (really saves a lot of disk
>>> space). All printers installed on the server work fine again. However,
>>> clients with a local attached printer cannot use their printer in the
>>> Terminal session anymore because it's no longer redirected. If they
>>> login on the other server their printers show up in the session and work
>>> perfectly.
>>>
>>> Both servers are using the same Terminal Server settings and are
>>> affected by the same GPO. A Fallback printer driver (default HP Deskjet
>>> 500) is configured in the GPO and works fine on the TS without printer
>>> problems. The TS experiencing the printer issues has the HP Deskjet 500
>>> driver installed and doesn't use the Fallback printer even though it
>>> should.
>>>
>>> The event logs do show some printing errors but none relate to the
>>> redirection of printers. I've checked all places where redirection can
>>> be controlled: RDP client, user profile, TS Configuration, GPO, registry
>>> keys, etc. All settings are identical on both servers, however printer
>>> redirection works on one server and not the other.
>>>
>>> I hope someone can help me solve this issue.
>>>
>>> Thanx in advance,
>>>
>>> Jonathan
>>>
>>
>
>
 
Back
Top