Forum Discussion
Universal Print Connector registration failed
Hi all,
i also experience the same issue.
Added my user to relevant AD roles (print administrator and global administrator) already a few days ago, but cant access the ressource: error 403.
any news about this topic so far?
dnienhaus hi there, for me the issue was that the machine I was trying to use it on was not AAD joined or AAD registered with our AAD tenant (it was just my personal home PC). When I tried on a different machine that was AAD joined (work laptop) I was able to register the printer with no issues.
I did not see anything about the registration failures in the Sign-In logs for the AAD user I was using, so I can't say it was our Conditional Access policies that were blocking it (arguably, the CA policies were *not* blocking because I was able to sign in and get the register printers step).
So, if you have the bandwidth, I'd say open a case and see if you can figure out what policy in the AAD tenant is blocking registering printers on non-AAD joined/registered machines. (Although to be fair, I'm only assuming AAD registered works, as it worked for me with an AAD joined machine)
Hopefully we can figure this out!
Carlos
- Rani_AbdellatifJul 15, 2020Former Employee
dnienhaus, is your AzureAD user account with which you sign in to the connector app assigned a UP license?
Carlos_Capellan, thanks for chiming in! I'd be interested to know if what worked for you also works for dnienhaus so we could document it as a prerequisite. dnienhaus, please let me know.
The official connector machines prerequisites don't require the machine to be AzureAD-joined. The test machine I use for a connector is not joined to AD or AzureAD, and I'm signed in to the machine using a local user. For printer registration, the identity that matters on the connector is the one used to sign in to the app. It must be Global Admin or/and Printer Admin.
- dnienhausJul 16, 2020Copper Contributor
Rani_Abdellatif and Carlos_Capellan thank you for the quick responses !
i double checked all the settings and group assignments and still couldn“t see any issue.
however, now - after one week - it seems to work.
No clue why, i dont think that the changes to our tenant should take that long ?
anyway, thank you for your advices !