VB script may be showing its age, but it's still incredibly useful. Printer deployment at my district is handled by means of a VB script that collects various bits of information that is then used to determine who gets what printers; said bits of information include: username, user group membership, user LDAP path, AD site name, computer name, computer group membership, and computer LDAP path. Obviously you don't need to use all of this, but this script will still pull it out for you and you can
Updated 4th September 2012 at 09:16 PM by Duke5A
This has to be the most obnoxious printer I have used lately (with the exception of our new Ricoh at work but that's a photocopier and sits top of the evil hardware food chain automatically).
I can't think of any printer that will jam it's print jobs, make you so frustrated that you turn it off....then print what you wanted to when you turn it back on a week later. And it still refuses to print what you want to print even if you power cycle it.
This printer isn't just failing,
Updated 21st December 2011 at 10:08 AM by CAM