Microsoft Universal Print Queues are not visible on some PCs

If a the Microsoft Universal Print queue created in the Celiveo 365 web portal does not appear on the list of available printers for a user:

1. Verify the Universal Print has the “synchronized” green flag status in the Celiveo 365 printer list
2. Verify you see the printer in the Universal Print blade in Azure management portal, available at https://portal.azure.com
3. Verify the user has an activated Microsoft Universal Print license
4. Verify the user is not connected to two domains on his PC (this is a known issue with Universal Print)
5. If your IT is federated with local AD and Azure Entra ID, you need to verify the federation is without error and that the domain/tenant the PC is connected to matches the domain/tenant that hosts Microsoft 365 and Microsoft Universal Print.

• In a prompt console, run the following command: dsregcmd /status /verbose /debug
• verify you have AzureAdJoined : YES for the device State and AzureAdPrt : YES (and no error) for the SSO State

Example of test that returns an error (in that example, all tenant and information ID are dummy):

AzureAdPrtUpdateTime : 2024-12-12 06:20:42.000 UTC AzureAdPrtExpiryTime : 2024-12-26 06:20:58.000 UTC AzureAdPrtAuthority : https://login.microsoftonline.com/e93eb12a-9483-b442-29EF-8830ec5e672a AcquirePrtDiagnostics : PRESENT Previous Prt Attempt : 2024-12-12 07:53:47.875 UTC Attempt Status : 0xc00000d0 User Identity : johnsmith@main.contoso.corp.local Credential Type : Password Correlation ID : ff4E45fe-93be-1840-eafc-cf5455e9231f Endpoint URI : https://login.microsoftonline.com/e93eb12a-9483-b442-29EF-8830ec5f672a/oauth2/token HTTP Method : POST HTTP Error : 0×0 HTTP status : 400 Server Error Code : invalid_request Server Error Description : AADSTS90002: Tenant ‘main.contoso.corp.local’ not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant. Trace ID: e93eb12a-9483-b442-29ef-8830ec5e672a Correlation ID: eeb5131-0438-b32c-fe41-9784eefb2870 Timestamp: 2024-12-12 07:53:47Z

• In such error case (error AADSTS90002) here is the procedure recommended by Microsoft:

1. In the Windows search bar type: Settings > open settings > Accounts > Access to school or work > check if there are accounts there and unlink them all.
2. In any internet browser remove all browser cache and navigation history from “All time” select all options to clean, then go to: https://teams.microsoft.com/
3. Access with your Office 365 account, then verify if you can access through Teams “web-client”.
4. In the Windows search bar type: Settings > open settings > Accounts > Access to school or work > add your corporate domain, the one where you use Microsoft 365.
5. Reboot your PC
6. Verify
7. In a prompt console, run the following command: dsregcmd /status /verbose /debug
   and verify if you still face the error.

• If the error is still there contact your IT in charge of domains and Microsoft 365, provide the information produced by dsregcmd /status /verbose /debug

©2024 Celiveo Pte Ltd – All Rights Reserved