Q I have renamed my users in the domain (e.g. in Active Directory). How do I also rename my accounts in PaperCut?
PaperCut uses the username as the primary user identifier. In effect it’s the primary key in the database. Hence PaperCut treats a renamed Active Directory user account as a brand new account. It’s equivalent to deleting the old account and adding a new account. Due to limitations in the Windows API, and the need to be cross platform, it’s not possible for us to use things like SAM account UIDs to identify accounts. Hence we can’t support automatic renaming of Users in PaperCut..
PaperCut does however provide some advanced scripting tools that can be used to manage account renaming, usually as part of a user name change script that may change names in multiple systems in one go. The server-command program can be used either directly, or in a script to manually facilitate account renaming. The procedure is as follows:
1. Re-name the account in Active Directory.
2. ‘Run as Administrator’ the command prompt (cmd.exe) on the server running PaperCut and type:
cd c:\Program Files\PaperCut NG\server\bin\win
server-command rename-user <old_username> <new_username>
Note: Take care to make sure the old and new names are typed correctly.
If either of the usernames contains a space, you will be required to include quotation marks to differentiate the two names. For example:
server-command rename-user “john smith” “jsmith”
3. The user account should now appear in PaperCut with the new name and all historic print history, credit, print quotas and transaction audit logs should be carried over to the new name.
The same procedure may be used on Linux, Novell or Mac server systems. The path to server-command will however vary depending on the platform.
Advanced network/system administrators may wish to use server-command directly in a rename-user script or batch file. For example, this single script would rename the user in AD, PaperCut, email system, home drive names, and any other database/system around the organization all in one go.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.