My memory is fairly shit, but I remember having a similar issue. I had to increase the allowed data size of a field in the SQL database. It has something to do with the size of the driver it's tryng to capture. Xerox drivers are huge. I'm sorry that this is vague, I cannot remember the specific solution off the top of my head.

I made a policy where I install the Xerox driver pkg which you can download for Xerox.com and made a post-script using lpadmin to create the printer. We have a follow-me system so I just have to script 1 printer.

I too deploy the drivers on all systems at imaging time and then use lpadmin to add the printers and set the options via script. We have ColorQube printers, WorkCenters, and 3 color 570s with Fiery controllers, and this method works for all of them. I can share my scripts if you'd like.

The person in charge of the Casper server is going to try changing the SQL data size setting but either way I would love to get a copy of the scripts Steve.

@stevewood We're looking to install Xerox ColorQube 9303 that is using a windows print server. I'd love to see the script you are using to map these printers.

@jasontucker It's a fairly simple one line script:

lpadmin -p <printername> -L "<location info>" -E -o printer-is-shared=false -v lpd://<printer-IP> -P /Library/Printers/PPDs/Contents/Resources/Xerox ColorQube 9303.gz

If you want to configure any of the options you can use the -o option with the printer name:

lpadmin -p <printername> -o duplex=none
lpadmin -p <printername> -o XROutputDestination=MainStackerTray

Hope that helps.

Is there a way to prompt the user to put in their four digit accounting code to get that setup?