Drucker verschwinden während Terminal-Server-Session

Problem gelöst:

PART1: Installation HP Universal Printer Driver PCL6 v5.2 (x86 und x64) -> WICHTIG keine spätere Treiber-Version installieren, diese funktionieren in Kombination mit den im Workaround beschriebenen DLL-Files nicht und verursachen noch mehr Probleme.

PART2: siehe folgender Text (Copyright by HP)

HP LaserJet Printer Series - Discrete Driver, Bidirectional Components Channel, hpzbdi.dll or msi related issues

Issue
It has been reported that HP Bidirectional Channel components (hpzbdi32.msi /hpzbdi.dll or hpzbdi64.msi / hpzbdi.dll ) could be the potential cause
of various performance related issues within stand-alone print servers, Windows Cluster Server, Citrix, and/or Terminal Server environments resulting
in 10 minute delays during driver installation, intermittent print spooler crashes, performance issues, CPU spikes, etc. CIO MSI does not get installed
if a user with non-admin rights attempts to install the driver. The driver will attempt to install the MSI multiple times [5 times, with an interval of
2 min between each try] without checking the access permission. This multiple execution causes a delay with the installation and will launch multiple
instances of the MSI installer, which can contribute to the cause of poor performance on the server.

The Windows Event log will usually indicate a reference to: 32/64 Bit HP CIO Components Installer. Product Version: X.X.X. Product Language: XXXX. This
issue may manifest itself with discrete PCL 6, PCL 5, and Postscript drivers which are bundled with hpzbdiXX.msi/.dll components. As hpzbdi is considered
a legacy bidirectional component, there will not be any further updates or developments to this component. However, the following workarounds have been
reported to resolve the majority of issues concerning hpzbdi.dll/msi related circumstances.


Workarounds:
The following are the latest versions of hpzbdi.dll and are not publicly available on hp.com as they were not intended for public release. The updated
dll files will need to be delivered on a case by case basis via the standard escalation process from HP:
32-Bit: hpzbdi.dll (1.1.2.51)
64-Bit: hpzbdi.dll (1.2.2.51)
When the driver components are installed, the hpzbdi components are installed to the following paths by default:
32-Bit: C:\WINDOWS\system32\spool\drivers\w32x86\3
64-Bit: C:\WINDOWS\system32\spool\drivers\x64\3
NOTE: The hpzbdi files may also reside in additional folders named hewlett_packardhp_xxxxxx within the w32x86/x64 directories. It is not
necessary to make changes to the hpzbdi files located in these directories per the workaround instructions below.

The following products listed below have hpzbdi components installed as part of their driver package and would qualify for the following workarounds:
LaserJet 4250/4350 Series
LaserJet 9040/9050 Series
LaserJet 5200 Series
LaserJet P3005 Series
This issue as described above precedes release of Windows 7 and Windows 2008R2. The only HP supported solution concerning the aforementioned
LaserJet products within a Windows 7 and/or Windows 2008R2 environment is to use the HP Universal Print Driver. Microsoft inbox drivers may
also be used as is. The Microsoft inbox drivers are not compatible with workarounds 1 and 2 below.

Workaround #1
The current suggested workaround for customers that wish to continue to use the latest discrete PCL 6, PCL 5, or Postscript drivers from hp.com will need
to perform the following: Open Notepad and save the file as hpzbdi32.msi or hpzbdi64.msi. This zero-byte file will not contain any data.
Navigate to the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3 directory and locate the hpzbdi32.msi or hpzbdi64.msi file. Rename the file to hpzbdi32.old
or hpzbdi64.old. Copy and paste the newly created zero-byte file named hpzbdi32.msi or hpzbdi64.msi into the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3
directory. Verify functionality.
NOTE: Depending on configuration, it may be necessary to stop the spooler, perform the steps in the workaround, and restart the spooler once the steps
have been completed.

NOTE: Please note that if the customer performs this workaround and a reinstallation of the driver is performed, the zero-byte msi file will be
overwritten by the original msi file in the original driver package. All steps in the workaround would need to be performed again.

Workaround #2
If the customer is not able to perform the steps outlined in the previous workaround the recommendation is to perform the following:
Navigate to the hpzbdi.dll that is currently on the server and verify the version number. If it is a version older than the updated versions outlined above,
rename the file to hpzbdi.old. Copy and paste the updated version of hpzbdi.dll as outlined above into the same directory. Verify functionality.
NOTE: As noted above, the updated hpzbdi.dll files can be obtained via the standard escalation process.

Workaround #3
If the previous workarounds don’t alleviate the issue, the recommendation is to perform a clean installation or upgrade to the latest version of UPD 4.7.2 or
later, which will contain the updated and currently supported HP Bidirectional Channel components: cioum.dll/msi
NOTE: Please refer to http://www.hp.com/go/upd for documentation regarding UPD installation/upgrade procedures and best practices.

PART3: den installierten Druckern den neuen Treiber zuweisen

PART4: Drucker-Objekte auf den betroffenen Servern entfernen und neu vom Printserver verbinden


PS. Das Problem wird auch durch andere Drucker-Modelle verursacht also wer derartige Probleme hat kann versuchen ob Ihm diese Vorgehensweise weiter hilft.

lG N0Ki