Fix Autopilot Profile Status Shows Not Assigned | Stuck Assigning

In this post, I will share some basic steps to resolve issue where the Autopilot profile status shows Not Assigned. If you don’t see the status of Autopilot deployment profile for devices as assigned, I will share multiple solutions to resolve the issue.

When you create a Autopilot deployment profile, you assign the profile to a device group. This device group consists of computers that you have registered for Autopilot in Intune. The process of importing a device may take up to 15 minutes. You can run the refresh option to check if the device is imported successfully.

After you have assigned the autopilot deployment profile to a device group, the profile status for the devices changes from Updating to Assigned. In some cases, the Autopilot profile status for devices gets stuck at the Assigning step and finally shows as Not Assigned. This is a common issue but gets resolved after waiting for a few hours. If the Autopilot Profile status shows not resolved and if this issue persists for a longer duration, it requires troubleshooting.


https://regalketo17.lighthouseapp.com/projects/155506-regal-keto/tickets/74-k3-spark-mineral-updated-2022

https://test.tcz.x10.mx/mybb/showthread.php?tid=734

https://socalireefer.com/forum/showthread.php?mode=threaded&tid=183633&pid=344058

http://hondaikmciledug.co.id/HRIS/showthread.php?tid=108

https://australiantravelforum.com/travel/showthread.php?tid=96784

https://forum.metalheartradio.com/thread-3312.html

http://www.yypf.com/showthread.php?tid=1379

http://jl.kaoyanzhi.net/forum.php?mod=viewthread&tid=102969

http://jl.kaoyanzhi.net/forum.php?mod=viewthread&tid=60605

http://jl.kaoyanzhi.net/forum.php?mod=viewthread&tid=115275

http://jl.kaoyanzhi.net/forum.php?mod=viewthread&tid=105011

http://www.balsen.dk/YetAnotherForum.NET/yaf_postsm20600findlastpost_Amaze-CBD-Gummies-Shark-Tank-Amazon-For-ED--ALARMING-ALERT--You-Need-to-Know--Critical-Report.aspx#post20600

http://www.balsen.dk/YetAnotherForum.NET/yaf_postst19234_van-cleef-watch-replica.aspx

http://www.balsen.dk/YetAnotherForum.NET/yaf_postst16929findlastpost_Penguins-alive-without-Kris-Letang-but-only-techni.aspx#post17808

http://www.greenbr21.com/bbs/board.php?bo_table=data_br21&wr_id=1367&page=2&page=2


Fix Autopilot Profile Status Shows Not Assigned


If you are encountering the issues with Autopilot profile assignments for devices, you can try the solutions listed below. Ensure you have waited for at least an hour after you have assigned the deployment profile to devices. I have listed multiple solutions and I hope they will help you.


Solution 1: Ensure the Autopilot Device is part of the AAD Group


This is a very basic troubleshooting step and if you have performed the Autopilot before, you will be surely aware of this. When you run the get-windowsautopilotinfo script, it uploads the hardware hash and creates a device in AAD which is named as the serial number of the device (assuming the device isn’t already in AAD). That new device needs to be a member of the AAD group that you have assigned the deployment profile to.

If the device isn’t added to the AAD group, the device will never receive the deployment profile and thats when you see the profile status as Not assigned. In the screenshot below, we see one of the devices shows the profile status as Not assigned.

There are multiple ways to check if the device is added to the AAD group to which you have assigned the Autopilot deployment profile. The easiest method is going to Groups and select the Autopilot group and review the members. Make sure that the Autopilot device is a member of that group.


http://99982296.com/viewthread.php?tid=353047&extra=&frombbs=1

http://99982296.com/viewthread.php?tid=355489&extra=&frombbs=1

http://99982296.com/viewthread.php?tid=357757&extra=&frombbs=1

http://99982296.com/viewthread.php?tid=350578&extra=&frombbs=1

http://kick.gain.tw/viewthread.php?tid=213114&extra=

http://kick.gain.tw/viewthread.php?tid=197700&extra=

http://kick.gain.tw/viewthread.php?tid=2183601&extra

http://kick.gain.tw/viewthread.php?tid=2461981&extra=

https://www.cs-bg.org/forum/viewtopic.php?t=72

https://cs-bg.org/forum/viewtopic.php?t=664

https://cs-bg.org/forum/viewtopic.php?t=159

https://cs-bg.org/forum/viewtopic.php?p=890

http://eldoradofus.free.fr/forum/viewtopic.php?pid=7153

http://eldoradofus.free.fr/forum/viewtopic.php?pid=5360

http://eldoradofus.free.fr/forum/viewtopic.php?pid=12932

http://junlinro520.gain.tw/viewthread.php?tid=131303&extra=

http://junlinro520.gain.tw/viewthread.php?tid=316893&extra=

http://junlinro520.gain.tw/viewthread.php?tid=319106&extra=

https://www.punterforum.it/viewtopic.php?id=178400


Solution 2: Remove the Device and Reimport it again


If the device Autopilot profile status is stuck assigning or shows as not assigned, try removing the device and reimport it again. This method is preferred when you have manually imported a device for Windows Autopilot.

To delete the imported device from the list of Autopilot devices:


  • Sign in to the Intune admin center.
  • Go to Devices > Enroll Devices > Devices.
  • Select the Device that you wish to remove and click on Delete.


It normally takes around 15 minutes to delete the device from Windows Autopilot devices. Refer to the following guide if you are unable to delete the Autopilot device from Intune or Azure AD.

After the device has been removed from the list of Windows Autopilot devices, you can import the device manually using the Import option. Refer to the Windows Autopilot setup guide where I have covered the steps to import or register devices for Autopilot. After you reimport the device, don’t forget to add it to the AAD group to which the autopilot deployment profile is assigned.


Solution 3: Check Policy Conflicts with Autopilot Profile


If the imported devices are members of the dynamic group, then check if there’s any policy conflicts with the Autopilot profile. If you find any conflicts, make sure to remove them. Read the following guide to learn about the Windows Autopilot – Policy Conflicts. After you resolve the autopilot policy conflicts, wait some more time to see if the devices will go to assigned devices.


https://www.punterforum.it/viewtopic.php?id=196840

https://scort.vip/forum/viewtopic.php?t=2282

https://scort.vip/forum/viewtopic.php?t=2188

https://scort.vip/forum/viewtopic.php?t=2170

https://scort.vip/forum/viewtopic.php?t=2364

http://forum2.extremum.org/viewtopic.php?f=5&t=75446

http://forum2.extremum.org/viewtopic.php?t=84057

http://forum2.extremum.org/viewtopic.php?t=82099

http://forum2.extremum.org/viewtopic.php?t=20409


Solution 4: Force Assign the Autopilot Deployment Profile


I will show you another solution that you can try when the autopilot deployment profile for a device shows Not Assigned. Go to https://admin.microsoft.com/#/PrepareWindows and select the device and use the option Change assigned profile. You will now get the option to select the profile to assign. Click the drop-down and select the autopilot deployment profile and select Save.

I hope the solutions covered in this post will help you to resolve the issue where the Autopilot Profile status shows not assigned or assigning for the devices. In case something else worked for you, please let me know in the comments section.


Comments

Popular posts from this blog

Fix Intune Profile Installation Failed during macOS Enrollment

2 Best Solutions: Error Can’t Connect to Windows 365

2 Easy Ways to Remove Insider Preview Evaluation Copy Watermark