Re: When Virtual Print Server fails over it corrupts client drivers

Tech-Archive recommends: Fix windows errors by optimizing your registry



Information on the defaults are included as part of Q260142. So, anything other than the defaults are 3rd Party.

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.

<jimmy.parker@xxxxxxxxx> wrote in message news:1167733026.597346.188080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
How would one do this?

Chuck Timon [Microsoft] wrote:
You will also need to ensure there are no 3rd party print monitors being
used on the server.

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.

<jimmy.parker@xxxxxxxxx> wrote in message
news:1167406368.019231.177130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have done this
>
> Were added using print management on a R2 server connected to the
> virtual server. They are on the virtual server not the node.
>
> The printers are in start run \\ahtprntvs01
>
> The issue is that when the virtual server fails over then fails back,
> the machines that were on at the time seem to have problems printing to
> the printers. Removing the printer and readding it seems to solve the
> problem it's like something happened to the printer on the client
> during the fail over / fail back.
>
> Sometime going to the printer properties and clicking on the tabs but
> not changing anything seems to solve the issue, it's like that forces
> the client to update some setting/file from the prnt VS same as adding
> the printer again.
>
> Chuck Timon [Microsoft] wrote:
>> You need to ensure that you installed the printers in the context of >> the
>> virtual server and not the local node. If you go to
>> Start>Settings>Printers
>> and you see your printers listed, they were not installed correctly. >> If
>> you
>> go to Start>Run>\\<virtual_server_name> and you inspect the 'Printers'
>> folder, that is where you should see the printers if they were >> configured
>> correctly.
>>
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Longhorn Readiness Team
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <jimmy.parker@xxxxxxxxx> wrote in message
>> news:1167394040.169844.11960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> >I have a 2003 cluster and virtual server for printing, everytime this
>> > virtual print resource fails over I have to delete and readd the
>> > printers on some client machines. It's as if the local printer is
>> > somehow corrupted.
>> >
>> > Any ideas?
>> >
>


.



Relevant Pages

  • Re: When Virtual Print Server fails over it corrupts client drivers
    ... I'll just have to wait till it fails over to ... Chuck Timon, Jr. ... They are on the virtual server not the node. ... The printers are in start run \\ahtprntvs01 ...
    (microsoft.public.windows.server.clustering)
  • Re: When Virtual Print Server fails over it corrupts client drivers
    ... Were added using print management on a R2 server connected to the ... They are on the virtual server not the node. ... The printers are in start run \\ahtprntvs01 ... The issue is that when the virtual server fails over then fails back, ...
    (microsoft.public.windows.server.clustering)
  • Re: When Virtual Print Server fails over it corrupts client drivers
    ... Chuck Timon, Jr. ... Were added using print management on a R2 server connected to the ... The printers are in start run \\ahtprntvs01 ... The issue is that when the virtual server fails over then fails back, ...
    (microsoft.public.windows.server.clustering)
  • Re: When Virtual Print Server fails over it corrupts client drivers
    ... You will also need to ensure there are no 3rd party print monitors being used on the server. ... They are on the virtual server not the node. ... The printers are in start run \\ahtprntvs01 ... The issue is that when the virtual server fails over then fails back, ...
    (microsoft.public.windows.server.clustering)
  • Re: Issues with Windows Server 2003 Print Cluster
    ... There should be print event log entries for failing drivers and ports. ... According to the Print Migrator 3.1 ... I still see no printers on the virtual server when the second ...
    (microsoft.public.windows.server.clustering)