Cloud printer connector for windows install#
Cloud printer connector for windows license#

You can add more printers using the Add button: To get the name, use the Universal Print portal.

Printer Shared Name: Enter the Shared Name of the printer.

To get the ID, use the Universal Print portal.

Printer Shared ID: Enter the Shared ID of the printer.

This ID is created when the printer is registered in Azure AD using the Universal Print service.

Cloud Device ID: Enter the printer ID.

When users receive the policy, the printer will automatically install.

Cloud printer connector for windows install#

Action: Select Install to install a printer.In the settings picker, select Printer Provisioning, and select the settings you want to configure. In Configuration settings, select Add settings. This setting is optional, but recommended. Description: Enter a description for the profile.For example, a good profile name is Win11: Universal Print policy. Name your profiles so you can easily identify them later. Name: Enter a descriptive name for the profile.In Basics, enter the following properties: Select Devices > Configuration profiles > Create profile. Sign in to the Microsoft Intune admin center. Then, on their devices, users select a printer that you added. When you assign the policy, the printers are automatically installed. This policy includes your printer information. These settings use the UniversalPrint CSP. If the profile is assigned to an Azure AD user/user group that can't access the printers because of permissions, then Intune grants the assigned user/user group the permissions. Have access rights to the printer service and the Universal Print service.Intune Administrator or Global Administrator roles: Needed to create and assign Intune policies.įor more information on these roles, go to Role-based access control (RBAC) with Microsoft IntuneĮnd user accounts need the following permissions/licenses: Printer Administrator or Global Administrator roles: Needed to add printers.įor more information on these roles, go to Azure AD built-in roles. To create the Intune policy, you need the device ID, printer shared ID, and printer shared name.įor more specific information, go to What is printer registration?Īdmin accounts need the following roles/licenses: Microsoft Intune: For more specific information, go to Microsoft Intune licensing.Įvery printer must be registered in the Universal Print service (UP), which uses Azure AD.

Cloud printer connector for windows license#

Universal Print: For more specific information, go to License Universal Print.

To use this feature, you need the following subscriptions: Be sure to use the steps in this article to install universal printers. Bizarre.The PrintProvisioning tool and the printers.csv file process is deprecated. Update: The day after I posted this, all the device-level printers magically showed up and have been working since. But all the device-level printers scoped to Chromebooks just refuse to show up on the client devices. So everything on the backend looks fine, printers shared out to staff at user level via the /cloudprint interface are good.

I was able to scope them back out to various OUs at the device level (and actually last night, Google updated the admin console so now the print settings are only in the 'classic' interface, which very well may be part of the problem). Over the past couple of days we ended up basically ripping out GCP from our Ubuntu box, upgrading it from 16.04 to 18.04 (there were some cups bug fixes), then reinstalling GCP and recreating the JSON config file and setting the server to point to Google's DNS (rather than our internal).Īt this point, all our printers show up in /cloudprint, and are all appearing online in GAdmin console. We have been having several issues with this over the past couple of months (printers constantly turning into 'other printers' in the Google Admin console (at which point they have to be removed and re-added so the Chromebooks see them again).