Configure Output Manager with Chromebook

Output Manager can be used with Chromebook devices with a few configuration steps that ensure that user and document names are transferred properly.

Enroll the Chromebook in Chrome Enterprise.

If you do not want to enroll the Chromebook in Chrome Enterprise, you can skip this step, and associate the device with the related user as described in step 2.
This method can be used for Chromebooks, that are not Enterprise enrolled, which can be an advantage for customers who do not want to use Chrome Enterprise.
1. In the Chrome Enterprise admin console, select Devices > Chrome > Settings.
2. Set Native Print Job Information to Include User Account And Filename In Print Job.
  
  The printers must use IPPS so that this setting works properly. It ensures that the transmission, including the user name, is encrypted.
Enable the IPPUserName document property.

This setting makes Chromebook send the user name during the IPP transmission. Output Manager uses this user name to set the document owner.

If Chrome Enterprise is not tied to Active Directory and has a different domain name or user name, Output Manager cannot resolve the username. To resolve the user name, do one of the following:
- Set user mapping: add a Business Rule with the Set Document Owner Advanced action. The IPPUserName property returns the Chrome user.
- Associate a device with a user: In Manage Users, add the MAC address of the device to the Mobile Devices list of the user.
  
  Output Manager can get the MAC address of the device only if the device is on the same network segment as the Output Manager server, which means ARP must work.
Add a certificate bound to the port used by the IPP source.
1. Install a trusted certificate in a trusted store on the Output Manager server. Using self-signed certificate is not recommended.
2. Open a command prompt and enter the following command:
  netsh http add sslcert ipport=<ip_address>:<port> certhash=<cert_thumbprint> appid={1D196DD2-F1FD-4052-87EB-35F0DC7551FB}
3. If the certificate is bound to the socket after the IPP source has been created, restart the Input service so it creates a listener with the new configuration.