question

SwatiArora-4767 avatar image
0 Votes"
SwatiArora-4767 asked LuDaiMSFT-0289 commented

Windows Auto-pilot Hybrid Azure Ad join stuck at "Please wait while we're setting up device for you"

Hi All,

We are testing windows auto-pilot Hybrid Azure AD join for provisioning new devices using Org's network.

Steps we have followed:

 1. Set up users in AD and assign MS licenses (which has intune and azure ad premium)
 2. Add in groups 
 3. Uploaded auto-pilot device and assigned deployment profile to the device.
 5. Domain join configuration profile has been created .
 6. Installed Intune connector on server  connected server to domian.

7. Delegate OU access to computer object server where Intune connector has been installed.
8. ESP page was hidden as well

When we logged into the device, it got stuck at "Please wait screen".

By reading few blogs took below steps to resolve
1. Unassign user from the device
2. Re-uploaded autopilot device in Intune Portal
3. In the domain configuration profile, added all devices under assignments inplace of group

Nothing works.

Please advise.



mem-intune-enrollmentmem-autopilot
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

LuDaiMSFT-0289 avatar image
0 Votes"
LuDaiMSFT-0289 answered LuDaiMSFT-0289 commented

@SwatiArora-4767 Thanks for posting in our Q&A.

For this issue, I have done a lot of research. The following link describes the process of Windows Autopilot Hybrid Azure AD Join.
https://oofhours.com/2020/07/19/troubleshooting-windows-autopilot-hybrid-azure-ad-join/
Note: Non-Microsoft link, just for the reference.

In the "Please wait while we're setting up device for you" page, it seems that Step #3,#4,#5 will complete in this page. To find which causes this stuck situation, it is needed to check background logs. With Q&A limitation, it is better to create an online support ticket to handle this issue more effectively. It is free. Here is the online support link and hope it helpful.
https://docs.microsoft.com/en-us/mem/get-support

Thanks for understanding.


Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@LuDaiMSFT-0289
Thanks for the response.

We are finally able to get the device enrolled in Intune and joined to domain. But there are still couple of concerns and not sure how to fix them.
1. Device name is coming as some random characters not changing to exact device name like Companyname-kLeJEhWHK
2. Join type in Azure AD is showing only Azure AD join not Hybrid join.

Any advise on how to fix them ?



0 Votes 0 ·

@SwatiArora-4767 Thanks for your update.

For 1: Based on my understanding, we can apply device name template in Windows Autopilot deployment profile to Azure AD join type windows devices. And we can only provide a pre-fix for hybrid devices in a domain join profile.
https://docs.microsoft.com/en-us/mem/autopilot/profiles

For 2: Did you mean that it shows Azure AD join not Hybrid join when you complete the Windows Auto-pilot Hybrid Azure Ad join? Please check there are two different records about the same device. One is Azure AD joined and another is Hybrid Azure AD joined.

0 Votes 0 ·

For 1: yes right as per docs, we can't do anything for device name, it only adds prefix. Do you know of a way how can we fix device name for autopilot hybrid join devices ?
Usually when a new device is set up it autimaticaly takes up DESKTOP- XXXX, but here it does adding the prefix not then some random characters. Can we control device from Active Directory for these Hybrid join autopilot devices.


For 2: Yes now I can see 2 different records for same device.One is Azure AD joined and another is Hybrid Azure AD joined.
Will the record with Azure AD joined would be deleted or it will always remain ? Won't it affect the configuratio profiles and conditional
access policies that we would be creating.

0 Votes 0 ·
Show more comments