I need a bit of advice from my more experienced peers.
We have a W2K8x32SP2 server running as print server and domain controller. The office is a Realtor office. Meaning, about 15 staff computers on domain, and about ~100 transient non domain users (realtors) coming in and out in a hurry needing to print stuff from their computer.
Domain users can map to the drivers easily simply by going to Devices and Printers and adding it from the list. They are the happy fews...
Initially, for non domain users, who also happen to be on a different subnet, we had to use network admin credentials to \\printserver and from there connect the users to the printers one by one. This caused in the end driver corruption, and usually things would work for a day. Shooting from the hips, I would bet that the credentials and connection evaporate with reboot? I don't know why, but this approach didn't work out. Also, doing it this way meant that the preferences of the driver when accessed were changed on the server, so any accounting code or other user preferences couldn't be localized.
So at this point I have an outsource IT that is coming in to install manually the drivers on each user and that's a huge step backward I feel. I read that one could create a guest domain user then use "net use printserver user password etc." something to that effect. I'm not sure if doing that would not cause the same problems we had when using network admin credentials to map the driver.
The business case here makes convenience more desirable than security. Hence I need to find a way to easily setup incoming users to print what they need. What would you recommend?
Any suggestion is greatly appreciated.
ps: The drivers are for a Xerox 560 with embedded fiery (drivers at http://goo.gl/mS9USN )
Edited by Orchus, 12 December 2014 - 10:45 AM.