![]() ![]() You can deploy the printer using the Google Admin console to immediately make it available to all users within an organisational unit. If however, the user also has a Windows device and an Active Directory account called johnsmith, then johnsmith will appear in the Logon code field and their email address must be entered into the Secondary logon code field so jobs sent from their Chrome OS device can be matched to the same record. If the user only has a Google Workspace account, and won’t be printing from other devices that might send a different username, then their email address can be entered into the Logon code field: So for example, a user with a Google Workspace account named will need this entered into the Logon code field or Secondary logon code field for their record in Resource Manager. Google account names are normally the same as the user’s email address. if they are not Google Workspace / GSuite accounts).Įnsure Google user account names are matched to the correct user record So our recommendation is to tick the Advertise checkbox only if the Chrome devices cannot have their printer deployed from Google Admin (e.g. We would create separate advertised queues with authentication enabled for these devices. Since the queue has authentication disabled, we wouldn’t want iOS or Android devices to use it. In fact, if there are iOS or Android devices on the network, it would be better NOT to advertise this queue. If we are going to deploy the printer via the Google Admin console, then there is no need to set the queue as Advertised. Now ensure the IPP Authentication drop down is set to Use supplied username. Double click the queue that will be used by the Chrome OS devices. Double click the server on the right and click the Print Queues tab. Open Resource Manager and click PDAgents. Take note of the IPPS port number as this will be used when configuring the printer deployment in the Google Admin console.ĭisable IPP authentication for the print queue on the server Ensure the Enable IPP Server checkbox is ticked. In Resource Manager open the PDAgent record for the print server and click the Services tab. Scroll all the way down to the Printing section and change the Native print job information drop-down to Include user account and filename in print job.Įnsure the IPPS service is enabled on the PDAgent Use your browser to log into the Google Admin Console by selecting it in the list of Google Applications or going to. Only printers using IPPS will be available. This means any printers using the LPD or IPP protocols will no longer be available. Note that once this setting has been changed, the version of Chrome OS at the time of publication, disables all printing via other protocols. This will apply to all Google Workspace accounts within the organisation. To allow Chrome OS to include this information, we need to change a setting for the Google Workspace organisation. All jobs are submitted with the same username ‘chronos’. ![]() Set the Google organisation setting to include usernames with print jobsīy default, Chrome OS will not include any user identifiable information with print jobs. Google account names must be stored in the user records Logon code or Secondary logon code fields.A ‘matched to device’ print queue that has IPP authentication disabled is required.IPPS service on the PDAgent must be enabled.Note this will block printing to non-IPPS printers even if previously added. Google organization settings: Include user account and filename in print job must be enabled.Chrome OS devices must be on the same network as the print server.Minimum Print Director version of 2.2.70.1.Supporting and deploying Print Director queues to Chrome OS devices have the following requirements: ![]() Created by: Karabo Kevin Moroka - Printsol Support ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |