Posted October 15, 2024Oct 15 We have done all the configuration for OOBE following below KBs, however still OOBE is not working. Manual enrollment is working fine. Enrolling Windows Devices Using Azure AD: Workspace ONE UEM Operational Tutorial | Omnissa
October 15, 2024Oct 15 Community Expert Employee Any error you get during OOBE or is it just finishing without ever enrolling?
October 15, 2024Oct 15 Author It just finished without enrollment. Devices are getting registered in Azure but not in UEM.Â
October 17, 2024Oct 17 Community Expert Employee Usually only see that behavior if the scope is not set correctly and does not include the test user or the URLs are not correct. Check that the discovery and terms URL are copied in the correct order.
October 17, 2024Oct 17 Author Discovery and terms URL has been verified through Ominssa support agent and configured the Airwatch by Omnissa app in Azure and still same.
November 27, 2024Nov 27 Employee have you checked the Audit Log to see if Azure is complaining of no license? https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Audit You need to assign a P1 license minimum to the user
December 2, 2024Dec 2 Author On 11/28/2024 at 4:50 AM, Phillip Helmling said: have you checked the Audit Log to see if Azure is complaining of no license? https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Audit You need to assign a P1 license minimum to the user E3 was assigned for those users and later we encountered a stale entry of another Airwatch app in Azure. After removing it using the graph export function, the issue was resolved. Please find below the topic and solution: Â
_community.png.fc103fd33135c37173c833e0668f98ef_8b6b64.png)
_community.png.fc103fd33135c37173c833e0668f98ef_852a12.png)
Create an account or sign in to comment