Device Registered is Pending

%3CLINGO-SUB%20id%3D%22lingo-sub-846655%22%20slang%3D%22en-US%22%3EDevice%20Registered%20is%20Pending%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-846655%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20some%20Hybrid%20Azure%20AD%20Join%20W10%20devices%2C%20auto%20enrolled%20in%20Intune%20via%20GPO%20however%20the%20Registered%20status%20equals%20pending.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMS%20docs%20state%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20device%20can%20also%20change%20from%20having%20a%20registered%20state%20to%20%22Pending%22%3C%2FP%3E%3CUL%3E%3CLI%3EIf%20a%20device%20is%20deleted%20and%20from%20Azure%20AD%20first%20and%20re-synchronized%20from%20on-premises%20AD.%3C%2FLI%3E%3CLI%3EIf%20a%20device%20is%20removed%20from%20a%20sync%20scope%20on%20Azure%20AD%20Connect%20and%20added%20back.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIn%20both%20cases%2C%20you%20must%20re-register%20the%20device%20manually%20on%20each%20of%20these%20devices.%20To%20review%20whether%20the%20device%20was%20previously%20registered%2C%20you%20can%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Ftroubleshoot-device-dsregcmd%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Etroubleshoot%20devices%20using%20the%20dsregcmd%20command%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERef%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Ffaq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Ffaq%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20elaborate%20on%20the%20%22you%20must%20re-register%20the%20device%20manually%20on%20each%20of%20these%20devices%22%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInfo%20appreciated%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-846655%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847537%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Registered%20is%20Pending%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847537%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20guess%20is%20to%20use%20psexec%20to%20run%20cmd%20as%20system%20user%20and%20then%20execute%20the%20command%20dsregcmd%20%2Fjoin%20%2Fdebug%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20should%20also%20give%20you%20more%20info%20about%20issues%20you%20might%20have%20with%20device%20enrollment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107468%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Registered%20is%20Pending%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107468%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F131657%22%20target%3D%22_blank%22%3E%40Stuart%20King%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20worked%20for%20me%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20dsregcmd%20%2Fdebug%20%2Fleave%3C%2FP%3E%3CP%3E2.%20Confirmation%20from%20Azure%20AD%20that%20device%20object%20was%20removed%3C%2FP%3E%3CP%3E3.%20Reboot%20machine%3C%2FP%3E%3CP%3E4.%20Confirmation%20that%20the%20device%20had%20been%20trying%20to%20register%20itself%20again%20to%20Azure%20AD%20(AAD%20audit%20logs)%3C%2FP%3E%3CP%3E5.%20Confirmation%20of%20device%20status%20from%20AAD%20(changed%20from%20pending%20to%20%22registered%20with%20timestamp%22)%3C%2FP%3E%3CP%3E6.%20dsregcmd%20%2Fstatus%20(which%20should%20now%20have%20PRT%20included)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20steps%20above%20today%20and%20the%20device%20state%20was%20successfully%20changed.%20After%20those%20were%20done%2C%20I%20had%20to%20wait%20for%20the%20next%20Azure%20AD%20Connect%20sync%20cycle%20to%20change%20the%20device%20status%20in%20Azure%20AD%20(working%20in%20a%20managed%20environment).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1213121%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Registered%20is%20Pending%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1213121%22%20slang%3D%22en-US%22%3EThanks%2C%20this%20worked%20for%20me%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2002356%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20Registered%20is%20Pending%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2002356%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F31071%22%20target%3D%22_blank%22%3E%40Sami%20Lamppu%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%20Sami%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20facing%20the%20same%20problem%20and%20have%20tried%20the%20command%20%22dsregcmd%20%2Fdebug%20%2Fleave%22and%20the%20device%20was%20removed%20from%20Azure%20AD%20but%20still%20it%20Show%20as%20Pending.%20Have%20checked%20the%20event%20logs%20and%20did%20not%20find%20any%20error.%20I%20thing%20which%20i%20noticed%20we%20have%20a%20.local%20domain%20will%20it%20have%20an%20affect%20as%20we%20have%20added%20a%20UPN%20suffix%20for%20our%20users.%3CBR%20%2F%3EAny%20help%20would%20be%20appreciated!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

Hi All

 

I have some Hybrid Azure AD Join W10 devices, auto enrolled in Intune via GPO however the Registered status equals pending.

 

MS docs state:

 

A device can also change from having a registered state to "Pending"

  • If a device is deleted and from Azure AD first and re-synchronized from on-premises AD.
  • If a device is removed from a sync scope on Azure AD Connect and added back.

In both cases, you must re-register the device manually on each of these devices. To review whether the device was previously registered, you can troubleshoot devices using the dsregcmd command.

 

Ref:

 

https://docs.microsoft.com/en-us/azure/active-directory/devices/faq

 

 

Can anyone elaborate on the "you must re-register the device manually on each of these devices"?

 

Info appreciated

4 Replies

My guess is to use psexec to run cmd as system user and then execute the command dsregcmd /join /debug

 

This should also give you more info about issues you might have with device enrollment

@Stuart King 

 

This worked for me:

 

1. dsregcmd /debug /leave

2. Confirmation from Azure AD that device object was removed

3. Reboot machine

4. Confirmation that the device had been trying to register itself again to Azure AD (AAD audit logs)

5. Confirmation of device status from AAD (changed from pending to "registered with timestamp")

6. dsregcmd /status (which should now have PRT included)

 

Did steps above today and the device state was successfully changed. After those were done, I had to wait for the next Azure AD Connect sync cycle to change the device status in Azure AD (working in a managed environment).

Thanks, this worked for me :)

@Sami Lamppu 

Hello Sami,

 

I am facing the same problem and have tried the command "dsregcmd /debug /leave"and the device was removed from Azure AD but still it Show as Pending. Have checked the event logs and did not find any error. I thing which i noticed we have a .local domain will it have an affect as we have added a UPN suffix for our users.
Any help would be appreciated!