Jobs Owned By Computer

KB Home   |   Jobs Owned By Computer

Main.JobsOwnedByComputer History

Hide minor edits - Show changes to markup

November 22, 2019, at 02:32 AM by timg - Cross linking.
Added lines 17-18:

Note: If you’re seeing different issues with the job owner where you suspect the job owner is not correct or PaperCut is logging/tracking the wrong username, check in on the Troubleshooting a wrong username article.

October 11, 2018, at 09:01 PM by Alan Morris - Added screenshots and explained how this can occur
Changed line 12 from:

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 and when the Windows “Offline Printing” feature is used.

to:

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.

Added lines 24-26:

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.

Changed lines 6-7 from:

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 as the job owner as viewed in the Windows print queue will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

to:

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.

Changed line 10 from:

For example, “user3” may print from a computer “alan-test3”, and the print job will appear to be owned by “alan-test3$”, rather than “user3”.

to:

For example, “user3” prints from computer “alan-test3” and the print jobs are owned by “alan-test3$”, rather than “user3”.

Changed line 2 from:

As a PaperCut admin, I see ComputerName in my user list.

to:

As a PaperCut admin, I see ComputerName$ in my user list.

Changed lines 6-7 from:

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 as the owner will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

to:

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 as the job owner as viewed in the Windows print queue will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

Changed lines 12-16 from:

This condition occurs when the print server is unable to validate the user credentials on the domain and the job enters 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 and 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: the 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 job owner thus the jobs are reported as missing.

to:

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 and 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.

Changed line 6 from:

An intermittent Windows environment issue can occur where Windows print jobs have an owner set to the Computer account that the job was submitted from, not the User account. In most circumstances, the Computer account is obvious as the owner will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

to:

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 as the owner will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

Changed line 2 from:

As a PaperCut admin, I see “ComputerName$” in my user list.

to:

As a PaperCut admin, I see ComputerName in my user list.

Changed lines 4-5 from:

https://www.papercut.com/kb/uploads/Main/mymachine$user.png

to:


Changed lines 8-9 from:

https://www.papercut.com/kb/uploads/Main/mymachine$1.png

to:


Changed line 23 from:

https://www.papercut.com/kb/uploads/Main/myprintersecurity.png

to:


Changed line 14 from:

Once the client connection to the print server is restored, the pending print jobs are submitted in bulk to the server. Note: the jobs with Computer$ credentials enter the print system in rapid succession.

to:

Once the client connection to the print server is restored, the pending print jobs are submitted in bulk to the server. Note: the jobs with “Computer$” credentials generally enter the print system in rapid succession.

Changed lines 2-3 from:

As a PaperCut admin, I see ComputerName$ in my user list.

to:

As a PaperCut admin, I see “ComputerName$” in my user list.

Changed line 14 from:

Once the client connection to the print server is restored, the pending print jobs are submitted in bulk to the server. “ ”Note: the jobs with Computer$ credentials enter the print system in rapid succession.″

to:

Once the client connection to the print server is restored, the pending print jobs are submitted in bulk to the server. Note: the jobs with Computer$ credentials enter the print system in rapid succession.

Changed lines 2-8 from:

An intermittent Windows environment issue has been reported where Windows print jobs have an owner set to the Computer account that the job was submitted from, not the User account. In most circumstances, the Computer account is obvious as the owner will end with a $.

For example, a user “john” may print from a computer “john-pc”, and his print job will appear to be owned by “john-pc$”, rather than “john”.

The exact cause of this has not been confirmed despite significant investigation efforts by both PaperCut staff and customers, although the behaviour happens outside of PaperCut’s control and is generally only noticed because there is no PaperCut balance for the Computer account.

to:

As a PaperCut admin, I see ComputerName$ in my user list.

https://www.papercut.com/kb/uploads/Main/mymachine$user.png

An intermittent Windows environment issue can occur where Windows print jobs have an owner set to the Computer account that the job was submitted from, not the User account. In most circumstances, the Computer account is obvious as the owner will end with a $. PaperCut will add this account to the Users list due to the On Demand user creation feature.

https://www.papercut.com/kb/uploads/Main/mymachine$1.png

For example, “user3” may print from a computer “alan-test3”, and the print job will appear to be owned by “alan-test3$”, rather than “user3”.

This condition occurs when the print server is unable to validate the user credentials on the domain and the job enters 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 and 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: the jobs with Computer$ credentials 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 job owner thus the jobs are reported as missing.

Added lines 23-25:

https://www.papercut.com/kb/uploads/Main/myprintersecurity.png

Changed line 29 from:

Keywords: job logged as username, computer name, host name, machine name

to:

Keywords: job logged as username, computer name, host name, machine name, missing

September 23, 2013, at 10:07 PM by timg - Added host to keywords
Changed line 16 from:

Keywords: job logged as username, computer name, machine name

to:

Keywords: job logged as username, computer name, host name, machine name

Changed lines 11-12 from:

Under the Windows print queue permissions, create a permissions object for “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.

to:

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.

October 26, 2012, at 04:39 AM by ian - Add keyword.
Changed line 16 from:

Keywords: job logged as username, computer name

to:

Keywords: job logged as username, computer name, machine name

August 21, 2012, at 03:49 AM by ian - First cut.
Added lines 1-16:

(:title Jobs Owned By Computer:)

An intermittent Windows environment issue has been reported where Windows print jobs have an owner set to the Computer account that the job was submitted from, not the User account. In most circumstances, the Computer account is obvious as the owner will end with a $.

For example, a user “john” may print from a computer “john-pc”, and his print job will appear to be owned by “john-pc$”, rather than “john”.

The exact cause of this has not been confirmed despite significant investigation efforts by both PaperCut staff and customers, although the behaviour happens outside of PaperCut’s control and is generally only noticed because there is no PaperCut balance for the Computer account.

Solution

Under the Windows print queue permissions, create a permissions object for “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.


Categories: Troubleshooting, Configuration


Keywords: job logged as username, computer name

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on November 22, 2019, at 02:32 AM
Printable View   |   Article History   |   Edit Article