As a PaperCut admin, I see ComputerName$ in my user list.
An intermittent Windows environment issue can occur where Windows print jobs have an owner set to the Computer account which the job was submitted from, not the User account. In most circumstances, the Computer account is obvious when viewed in the Windows print queue as the Owner field will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.
For example, “user3” prints from computer “alan-test3” and the print jobs are owned by “alan-test3$”, rather than “user3”.
This condition occurs when the print server is unable to validate the user credentials on the domain resulting in the job entering the print system using the Computer account credentials, which is also a valid account. This issue may occur when jobs are submitted to the print server when it is not available due to the Print Spooler service not running or when the Windows “Offline Printing” feature is used.
Once the client connection to the print server is restored, the pending print jobs are submitted in bulk to the server. Note: Jobs with Computer$ credentials generally enter the print system in rapid succession.
The behavior happens outside of PaperCut’s control and is generally only noticed because there is no PaperCut balance for the Computer account or the user who submitted the jobs cannot release them as they are not the Windows job owner thus the jobs are reported as missing.
Under the Windows print queue permissions, create a permissions object for “Domain Computers” and then explicitly deny permission for that object to Print. In all cases encountered by PaperCut technical support so far, this will, without any user interaction, prevent Computer accounts from creating the print job, and Windows will automatically switch to the User account.
Still have questions?
Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our Support Portal for further assistance.
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.