LZ1
asked on
Getting an error after printer is added to logon script
Hey Experts!!
I just purchased a new HP P4010 Printer and installed it on the server via the Server Management MMC. Afterwards, I added it to the script and tested it on my machine. Everything came up ok. When my other users came in this morning they said there was an error saying that the operation could not be completed.
Once again, this works on 2 PC's (the server and mine) but no one else's. Everyone is running XP Pro SP2
I added this printer and others via a logon script using the code below.
What is wrong?
Is it because the driver is only present on my machine and the server?
*******UPDATE********
Switched the driver to the Universal PCL 5 instead, because that's what the other HP's on my network use......still nothing. So then I switched back the driver to the PCL 6 driver.
I just purchased a new HP P4010 Printer and installed it on the server via the Server Management MMC. Afterwards, I added it to the script and tested it on my machine. Everything came up ok. When my other users came in this morning they said there was an error saying that the operation could not be completed.
Once again, this works on 2 PC's (the server and mine) but no one else's. Everyone is running XP Pro SP2
I added this printer and others via a logon script using the code below.
What is wrong?
Is it because the driver is only present on my machine and the server?
*******UPDATE********
Switched the driver to the Universal PCL 5 instead, because that's what the other HP's on my network use......still nothing. So then I switched back the driver to the PCL 6 driver.
RunDll32.exe printui.dll,PrintUIEntry /in /y /n \\ATIDC\HP4010
ASKER
So it is basically finding the path of the drivers on the server, then throwing them into the same line?
I didn't have to do this for the other printers, is there a reason I have to do it for this one?
I didn't have to do this for the other printers, is there a reason I have to do it for this one?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See http://support.microsoft.com/kb/189105