admSpotting
Junior Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Цитата:| что такое HP-инсталлер, где он находится и как его удалить для решения этой проблемы. |
Был на отдыхе, но сейчас все расскажу:
смысл следующий:
- надо установить все нужные дрова на сервер, стандартным способом (те если есть сервер печати, то с него)
- после этого зайти на сервере в папку C:\WINDOWS\system32\spool\drivers\x64\3 (или x32 в зависимости от винды). Найти файлы HPZBDI64.msi CIOUM64.msi и заменить их на нулевые файлы
- удалить ключи реестра
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Hewlett-Packard
HKU\ .DEFAULT\Software\Hewlett-Packard
- после этого перезапустить print spooler...
и все ОК...
но при установке нового принтера придется повторить процедуру, тк при установке HP восстанавливает свои инсталлеры
Добавлено:
Yes I'm experiencing the same problem as well--I didn't mention it in my original post because the spooler crashes were more pressing at the time.
I've got an open case with HP and Microsoft Premier support on this issue. Running processexplorer on the msiexec.exe events determined:
The HP MSI installer creates ~1.6 MILLION registry API calls as a result of over 4000 subkeys created in the registry for every printer mapped. This is what kills your system performance.
While there is no official fix (supposed to be fixed in UPD 4.7.2 (from what HP told me it is due December08).
However here is the work around for the MSINSTALLER service running every single time a printer is connected:
Stop the print spooler.
You need to 'zero-byte' the MSI files that keep running on both the Terminal Server and your thin clients (might not be necessary on thin clients since you are using RDP Printer mapping and not MS Point and Print, but better to do it anyways).
On XPe thin clients and Terminal Servers, go to the following directory:
c:\windows\system32\spool\drivers\w32x86\3\
find the following MSI files:
cioum32.msi
HPZBDI32.msi
FYI: if it is a x64 system, you will need to do this to the x64 printer driver folder. You will find corresponding 64-bit MSI installers for the CIO/BIDO components there.
Next step is to create a zero-byte file with the exact same name as the HP MSI's. You can create a zero byte TXT file and simply rename the file (make sure to rename the three letter extension as well).
Replace the original HP MSI's with the zerobyte MSI's you've 'created'.
Next step is to delete all the registry keys that were created by the HP MSI's.
On your thin clients, you need go in the the local registry and delete the following keys:
HKU\ .DEFAULT\Software\Hewlett-Packard
On your terminal servers you need to go into the local registry and delete the following TWO keys:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Hewlett-Packard
HKU\ .DEFAULT\Software\Hewlett-Packard
I *highly* recommend configuring GPO Client Side preferences to continuously delete these keys. These registry entries will pollute your the user profiles of customers logging into that terminal server; they can easily increase profile size by 30mb.
Restart the print spooler service.
Now, when a user logs into the terminal server, the HP driver will still attempt to run the MSI, however instead it will now find the zerobyte version you've put in. MSINSTALL will simply open file and process nothing.
Not the prettiest solution, but it seems to be working for us.
|
