on our customer we have RDS farm and a print server. There is one printer which I have a problem installing when logged on a particular RDS member server. It seems I can install it on any other RDS member. Normally I click add printer, type \print-corp\printer name and it's added with driver HP LaserJet Pro M501 PCL-6. On that one RDS member when I do the same I get an error "Windows can't find a driver for HP LaserJet Pro M501 PCL-6 on the network." But I have no problem adding other printers published on the print server onto this server. All servers are Windows server 2012 Datacenter R2.
EDIT: So I found a logfile C:\Windows\Inf\setupapi.dev.log and this part seems to be whatever happens wrong when I try it.
dvi: Default installer: Enter 17:13:27.512
dvi: {Select Best Driver}
dvi: Class GUID of device changed to: {4d36e979-e325-11ce-bfc1-08002be10318}.
dvi: {DIF_DESTROYPRIVATEDATA} 17:13:27.512
dvi: Class installer: Enter 17:13:27.512
dvi: Class installer: Exit
dvi: Default installer: Enter 17:13:27.512
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 17:13:27.512
dvi: Selected:
dvi: Description - [HP LaserJet Pro M501 PCL-6]
dvi: InfFile - [c:\windows\system32\driverstore\filerepository\hpbi652a4_x64.inf_amd64_bde64df507bb4bdb\hpbi652a4_x64.inf]
dvi: Section - [INSTALL_SECTION]
dvi: Basic Driver Skipped:
dvi: Description - 'Microsoft enhanced Point and Print driver'
dvi: InfFile - C:\Windows\INF\prnms004.inf
dvi: Section - [MS_V4_UNISHARE]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 17:13:27.527
ndv: {Core Device Install} 17:13:27.527
dvi: {DIF_ALLOW_INSTALL} 17:13:27.543
dvi: Using exported function 'ClassInstall32' in module 'C:\Windows\system32\ntprint.dll'.
dvi: Class installer == ntprint.dll,ClassInstall32
dvi: No CoInstallers found
dvi: Class installer: Enter 17:13:27.543
dvi: Class installer: Exit
dvi: Default installer: Enter 17:13:27.543
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 17:13:27.559
dvi: {DIF_INSTALLDEVICEFILES} 17:13:27.559
dvi: Class installer: Enter 17:13:27.559 !!! dvi: Class installer: failed(0x00000002)! !!! dvi: Error 2: The system cannot find the file specified.
dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000002)} 17:13:27.590 ! ndv: Queueing up error report since device installation failed...
ndv: {Core Device Install - exit(0x00000002)} 17:13:27.590
dvi: {DIF_DESTROYPRIVATEDATA} 17:13:27.590
dvi: Class installer: Enter 17:13:27.590
dvi: Class installer: Exit
dvi: Default installer: Enter 17:13:27.590
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 17:13:27.590 <<< Section end 2019/12/30 17:13:27.637 <<< [Exit status: FAILURE(0x00000002)]
Funny thing is that I WAS able to install the printer when I clicked add printer - the printer is not listed - add local or network printer as administrator - add a local printer or network printer with manual settings. This way the printer was installed! Not sure if it is visible to user this way, but I think it should. Anyway it's just a workaround which non admin users cannot use.
User contributions licensed under CC BY-SA 3.0