Ruhul Azad Posted October 15 Share Posted October 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 Link to comment Share on other sites More sharing options...
Employee Sascha Warno Posted October 15 Employee Share Posted October 15 Any error you get during OOBE or is it just finishing without ever enrolling? Link to comment Share on other sites More sharing options...
Ruhul Azad Posted October 15 Author Share Posted October 15 It just finished without enrollment. Devices are getting registered in Azure but not in UEM. Link to comment Share on other sites More sharing options...
Employee Sascha Warno Posted October 17 Employee Share Posted October 17 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. Link to comment Share on other sites More sharing options...
Ruhul Azad Posted October 17 Author Share Posted October 17 Discovery and terms URL has been verified through Ominssa support agent and configured the Airwatch by Omnissa app in Azure and still same. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now