We have 4 networked printers that are identical in every respect except name. We have recently tried to set them to print in black as default, but this proved very difficult so we now have a script that sets the registry key appropriately for each computer.
The scripts are identical other than the name of the printer and I have checked this over and over.
What now happens is that three of them are absolutely fine - no problems - printing in black as required, but the fourth one is proving an issue.
When logging on as a student or staff member, the printer is visible for about 10 seconds and then it just vanishes!
Other than putting policies in to run the scripts in appropriate OUs nothing else has been changed
I've never seen this before and would appreciate some help.
There is no info in any event log that I can see. The computers are Windows XP and the Server is 2008R2.
This just sounds like XP not liking networked printers.
IIRC, when a printer is off for more than a few hours, the computer deletes it because it decided you no longer have it. [This is what I was told by the LA techs in response to our shared printers disappearing.]
thanks, but the printer isn't ever off and the other three printers are identical!
Originally Posted by X-13
It is definitely only an issue when the script to set the reg key is there.....
Does it only happen on certain computers, or is it a general problem?
If it's only on certain ones, it could be some sort of conflict.
Have you got the latest driver for these printers installed on the server and have you tried a different version of the driver like a pcl 5 instead of a pcl 5. We had a load of problems with a hp but I forget the model number off the top of my head and it will only run with one driver I think it was a pcl5.
Witch : Out of curiosity, when you say networked, do you mean connected via a network port or locally installed and shared?
If it's connected via a network port, check the server and see if it's actually there.
Sorry - I'm obviously not explaining myself very well..
Different OUs have different printers as default. This printer disappearing is where it is set as default.
It reappears if you take out the script setting the reg key to black.
The other identical printers have the same script (as I said, the difference is only the name of the printer) and they are NOT disappearing.
The printers are properly networked printers - installed on the server (so all of them use the same driver and they work fine)
To recap: the printer has worked for about 4 months in the set up we have, alongside its fellow 3 identical machines.
The share appears as long as the script isnt there!
Hope that makes sense!:)
these aren't kyocera by any chance?
possibly not an idea answer but one ive used in the past
find a mono only driver that works with the printer and set that as default then use the exisiting driver for colour means they have 2 printers installed but might solve your problem
I did wonder about doing this - but would the users be able to change to colour?
Originally Posted by sted
I really want to know WHY the current set up doesnt work for this one printer.
I deleted the script this morning and used one of the working ones, just changing the name of the printer - but no joy.
They are HP2025s
they will be able to change to colour by selecting the colour version of the printer so listed under printers you have hp2025s mono and hp2025s col as long as they select the colour one that will print in colour as it has a colour driver
Originally Posted by witch
hp2025 rings a bell but i cant think why
Is it the same user account that has the problem?
Could it be their profile which has become corrupted?
Does the user account have the necessary permissions to run the script?
Have you ran a GPResult on the workstations/laptop which are working and compared them with the one that is not?
I forget now (getting Old) but there is a free piece of software which will allow you to capture the boot process and any registry changes on boot up and login which may help you determine why the printer is being lost when this reg key is being added.
Good hunting :D
I set the default printer with the script:
REM **Example Printers.bat file **
REM ** Set a variable called 'Location' on each pc
REM ** This line removes any printers from the profile
REM ** These lines match the variable to a print share
IF %Location% == Room1 \\server\NETLOGON\CON2PRT /C \\server\printername1
IF %Location% == Room1 \\server\NETLOGON\CON2PRT /CD \\server\printername2
Create a print .bat with this in it.
In the netlogon share place the print.bat and the conrprt.exe
On the client go into the properties of My computer/advanced/enviromental variables/ Create a new system variable with location and Roomxxx no spaces. The Roomxxx is used in the script for that room. In the script is a c or cd cd=default printer. Please make sure no spaces in location name.
Now put the print.bat to run in the logon script of the users ou.
The problem is not confined to one user - it affects machines.
Thanks ricki but the default printer setting (cant remember how and I am a different school ATM) works fine so that really isnt the issue.
I have run GPresult with no obvious results (!)
I woul like to know about that software you mention, bossman, if anyone knows of it?
How can a script to set a registry key mean that a printer share disappears? I can't see any connection between the two at all. Maybe it is a Server 2008R2 thing!
perhaps its setting the reg key while the driver is still part initialized might be worth making the script that adds the reg key wait say 30 seconds cant harm
Originally Posted by witch