There is no reason to select "Begin", the printer is chosen from a dropdown below that section.
Reloading a printer does nothing to the Client PC drivers. The 2 things are not related.
The name at the machine is different when sending RAW vs LPR , that is most likely the reason behind the names changing.
At this point there is no reason to change anything on the print server, you go to the server and add an entirely new printer with the new driver on a new port and set its preferences and defaults and port as specified and test from the server. If successful, share the new one out and test from 1 client, if successful convert the old to match the new and you are done. Nobody is suggesting you just randomly change an in-use shared printer.
Ok. We click on Begin under "Generate a Configuration file" It didn't do anything more than pop a window saying that it is now in Write Mode.
We are hesitant to make any changes to the Server Printer Object.
Just to sum up. The issue at hand is: clients with a 5.3x version of the Global PCL5 Printer driver are getting only basic print functions. The Printer logs these user as a REMOTE USER instead of their AD username. The print server is Running Version 220.127.116.11.2N
These issues go away if we use the older Global print driver provided by the Windows Print Server.
These issues started when a Xerox Technician reset the copier to a default Configuration.
We are able to workaround the problem by removing the newer client print driver from deployed computers using printui /s /t2 Select the Xerox Global Driver and clicking Remove .
However this workaround it not scaleable. As newer machines have been deployed with the newer Global Print Driver installed on the new Image.
Everything is done on the server, then test from the server, if it works go to the client, refresh it and make sure it works there, if not working on the client and it is working on the server, there is an issue unreleated to the printer so we work on that end.
For instance, if the server is 32 bit and the client is 64 (or vice-versa) and printing preferences don't carry through.
Should I run this from the client or the printer Printer Object?
I would suggest calling 2nd level support. We cannot recreate your original issue. The only way I can is to have the Global driver not have the right printer configuration, which only typically happens when the Global is older than the printer so it cannot identify it.
Out of Curiosity, which PCL driver is it? 5 or 6? And does the same happen with the PS driver?
The issue printing in color or not, is with all printouts. It's not specifily with Adobe acrobat.
Even the OS Print Test Page doesn't adhear to the Xerox Black and white conversion option in the Driver Preferences.
I have since changed the Default optiopn in the Copiers Web UI. Default print jobs are printed in Black and white. However the users of the new 5.3.x Global Print Driver still cannot control color output within the Drivers Printing Preferences.
"The issue we have now is, some users a have a new version of global print driver than what is provided by print server . These users [newer global driver] now have an issue where their print outs are all in color. This is the case even if they enable Xerox Black and White Conversion in their printer object preferences in the control panel. Additionally, in the printer log, it shows the user as Remote user instead of their Active Directory Username."
Have them switch the port from RAW to LPR to solve the name issue. The color thing typically happens in Adobe products like Indesign and or Acrobat/Reader when the application is set to control the color.
print via Windows Print server.
Global Driver on Print Server: 5.2.73
Global Driver users: 5.3.47 and 18.104.22.168
A tech came out yesterday to resolve an issue with SecurePrint. His solution was to wipe out the device entirely and reconfigure it afterwards.
The issue we have now is, some users a have a new version of global print driver than what is provided by print server . These users [newer global driver] now have an issue where their print outs are all in color. This is the case even if they enable Xerox Black and White Conversion in their printer object preferences in the control panel. Additionally, in the printer log, it shows the user as Remote user instead of their Active Directory Username.
I can recreate the problem on my own machine. If I revert back to GPD 5.2.73 the ability to toggle color is back. These issues did not happen before the printer was wiped.
I have found another Customer thread "http://forum.support.xerox.com/t5/Printing/Always-printing-color/td-p/12817/highlight/true"
I did make a change per the thread suggestion here http://www.support.xerox.com/support/workcentre-7755-7765-7775/support/enus.html?objGUID=15843
However that doesn't fix the problem for us, because color output still cannot be controlled by the user on-demand. Now, printouts from these users will now come out in color even if Xerox Black and White Conversion is un checked.
IT was said in a another thread of mine that [quote]Yes the server holds a set of drivers that can be downloaded but will not conflict if they aren't, so the previous users have different drivers it will not matter.[/quote]
Also, I also tested the new global driver by print directly to IP, this issue doesn't see to take place.
I will also note that, when printing a "windows test page" The printer DOES log the username and comes out appropriately; even when prints from other applications are not.