32 bit print drivers keep updating on every printer access

[Brad Overstreet]

We recently installed a 64 bit file and print cluster. On the print spooler
I have both 32 bit and 64 bit drivers for each printer loaded. On all of my
32 bit clients (XP SP2), they download drivers causing Event ID 20 to be
logged each and every time they access a printer. I have also noticed that
if I am looking at the properties for printer A that it will download drivers
for printer A, B and C. This is causing quite a bit of lag when accessing
the printers and is particularly noticable for our wireless network users.
Does anyone have any idea where to begin looking for an answer to this? I
have seen several items posted on the web for this but no one has come up
with any absolute solutions.

What does the client computer do to determine if a driver should be
downloaded? I have compared the driver date and version keys in the client
registry with the values stored on the server and they match exactly. Any
help with this would be greatly appreciated.

 

[Meinolf Weber]

Hello Brad,

What do you mean with loaded on the print spooler? Did you add them as additional
driver under the printer properties?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> We recently installed a 64 bit file and print cluster. On the print
> spooler I have both 32 bit and 64 bit drivers for each printer loaded.
> On all of my 32 bit clients (XP SP2), they download drivers causing
> Event ID 20 to be logged each and every time they access a printer. I
> have also noticed that if I am looking at the properties for printer A
> that it will download drivers for printer A, B and C. This is causing
> quite a bit of lag when accessing the printers and is particularly
> noticable for our wireless network users. Does anyone have any idea
> where to begin looking for an answer to this? I have seen several
> items posted on the web for this but no one has come up with any
> absolute solutions.
>
> What does the client computer do to determine if a driver should be
> downloaded? I have compared the driver date and version keys in the
> client registry with the values stored on the server and they match
> exactly. Any help with this would be greatly appreciated.
>

 

[Brad Overstreet]

Yes I installed the 32 bit drivers as additional drivers.

"Meinolf Weber" wrote:

> Hello Brad,
>
> What do you mean with loaded on the print spooler? Did you add them as additional
> driver under the printer properties?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>
> > We recently installed a 64 bit file and print cluster. On the print
> > spooler I have both 32 bit and 64 bit drivers for each printer loaded.
> > On all of my 32 bit clients (XP SP2), they download drivers causing
> > Event ID 20 to be logged each and every time they access a printer. I
> > have also noticed that if I am looking at the properties for printer A
> > that it will download drivers for printer A, B and C. This is causing
> > quite a bit of lag when accessing the printers and is particularly
> > noticable for our wireless network users. Does anyone have any idea
> > where to begin looking for an answer to this? I have seen several
> > items posted on the web for this but no one has come up with any
> > absolute solutions.
> >
> > What does the client computer do to determine if a driver should be
> > downloaded? I have compared the driver date and version keys in the
> > client registry with the values stored on the server and they match
> > exactly. Any help with this would be greatly appreciated.
> >
>
>
>

 

[Meinolf Weber]

Hello Brad,

Have you checked this:
http://www.eventid.net/display.asp?eventid=20&eventno=42&source=Print&phase=1

I suggest you post this to:

microsoft.public.windows.server.clustering

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> Yes I installed the 32 bit drivers as additional drivers.
>
> "Meinolf Weber" wrote:
>
>> Hello Brad,
>>
>> What do you mean with loaded on the print spooler? Did you add them
>> as additional driver under the printer properties?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>>> We recently installed a 64 bit file and print cluster. On the print
>>> spooler I have both 32 bit and 64 bit drivers for each printer
>>> loaded. On all of my 32 bit clients (XP SP2), they download drivers
>>> causing Event ID 20 to be logged each and every time they access a
>>> printer. I have also noticed that if I am looking at the properties
>>> for printer A that it will download drivers for printer A, B and C.
>>> This is causing quite a bit of lag when accessing the printers and
>>> is particularly noticable for our wireless network users. Does
>>> anyone have any idea where to begin looking for an answer to this?
>>> I have seen several items posted on the web for this but no one has
>>> come up with any absolute solutions.
>>>
>>> What does the client computer do to determine if a driver should be
>>> downloaded? I have compared the driver date and version keys in the
>>> client registry with the values stored on the server and they match
>>> exactly. Any help with this would be greatly appreciated.
>>>

 

[Brad Overstreet]

Yes I have and did not find anything that helped. I can post this in the
cluster group but I really suspect that it is an issue with the interaction
between a 64 bit print server and 32 bit clients since I do not see this
issue on my 64 bit clients. If not this then it might be subtle differences
in how the printer manufacturer packaged the 32bit dirver versus the 64 bit
driver. I found during the install that certain names had to be identical
for the additional driver load to be successfull and I had to edit a couple
of inf files to get them to load.

"Meinolf Weber" wrote:

> Hello Brad,
>
> Have you checked this:
> http://www.eventid.net/display.asp?eventid=20&eventno=42&source=Print&phase=1
>
> I suggest you post this to:
>
> microsoft.public.windows.server.clustering
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>
> > Yes I installed the 32 bit drivers as additional drivers.
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello Brad,
> >>
> >> What do you mean with loaded on the print spooler? Did you add them
> >> as additional driver under the printer properties?
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
> >>> We recently installed a 64 bit file and print cluster. On the print
> >>> spooler I have both 32 bit and 64 bit drivers for each printer
> >>> loaded. On all of my 32 bit clients (XP SP2), they download drivers
> >>> causing Event ID 20 to be logged each and every time they access a
> >>> printer. I have also noticed that if I am looking at the properties
> >>> for printer A that it will download drivers for printer A, B and C.
> >>> This is causing quite a bit of lag when accessing the printers and
> >>> is particularly noticable for our wireless network users. Does
> >>> anyone have any idea where to begin looking for an answer to this?
> >>> I have seen several items posted on the web for this but no one has
> >>> come up with any absolute solutions.
> >>>
> >>> What does the client computer do to determine if a driver should be
> >>> downloaded? I have compared the driver date and version keys in the
> >>> client registry with the values stored on the server and they match
> >>> exactly. Any help with this would be greatly appreciated.
> >>>
>
>
>