![]() I see something about LDAP but apparently that is just for scan-to-email to read in user accounts as scanning destinations?I don't know a better way, be it ridiculous or not. I see something about LDAP but apparently that is just for scan-to-email to read in user accounts as scanning destinations? Is there a faster or better way, that allows me to just enter usernames and ID codes in a list somewhere, perhaps as a user attribute within Active Directory itself, which the copier and driver can use directly without me having to mess with each individual user account by hand? What does a company with 1000 user accounts do? In the end I was forced to basically request every user's password, log on to their account, open their printer properties, and manually type in the User Code, log off the account, go to the next one. There does not appear to be a way for me to deploy user codes to individual accounts via registry settings or AD Group Policy, because the Ricoh universal PCL6 driver settings are stored in a single registry key as a huge binary blob. I've already had to do this at another location, where user codes (Prefs -> Job Setup -> User Code) were used in the Universal PCL6 driver, but the setup for that was just ridiculously labor-intensive. We want to identify print jobs with a department ID, and I want to be able to set this up with minimal fooling around. We have an Active Directory domain, with a Ricoh MP C6502, using the Ricoh Universal PCL6 driver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |