Why does the printer not print in the morning?

E

Eko_O2014-12-01 09:11:39

Active Directory

Eko_O, 2014-12-01 09:11:39

So, dear friends, I work as a sys. Admin in a small organization, I work in it relatively recently, and I inherited a problem that was not solved by the previous admin, in fact, like me ...
We have: AD is spinning on a 2008 R2 server We have
a printer: HP LJ1530 connected over the network
problem:
Every morning, on the same computer, the printer refuses to print, referring to the fact that the driver is not installed correctly, it helps - logging in from under the administrator, and test printing on this MFP.
What I tried:
-I hooked it via USB
-I hooked it through shared access from one of the servers
-I installed different revisions of the drivers
-I deleted the monitors from the registry
What is most funny and interesting, the usual regular reboot, or turning off the computer - does not provoke this problem.
Who has ideas? :D

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

O

oia, 2014-12-01
@oia

what's in the logs?

S

Sergey, 2014-12-01
@bk0011m

Print manager up? Is the printer published in AD? Did you try the driver "not native" but universal?

V

Vladimir, 2014-12-01
@azrail_dev

Yell at the user, it will help.

Y

Yaroslav Golubev, 2014-12-18
@Linebrell

Try to clean all the drivers and install the printer in a new way under the administrator. Preferably through the port-last driver.
Brief algorithm: -
Remove printers from the list of devices, stop the spooler. If something is not removed - clean
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
-Clear branches from third-party drivers, if there are drivers at a higher level - them too.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86(x64)\Drivers\Version-3(4)
-Delete/Rename folder
C:\Windows\System32\spool\drivers\w32x86(x64)\3
- List packages pnputil.exe -e
Remove all containing printer drivers pnputil -d oemX.inf
-Start spooler, try again.
The problem is due to incorrect driver installation, for sure he is trying to pull up the missing one in the background from the print server, or somehow else. It can also be set incorrectly due to an already existing zoo installed, or lack of rights, or something else.