Windows 10 Devices not Assigning to Windows AutoPilot Deployment Profile

Anonymous
2022-07-25T09:16:07.16+00:00

I have set up Windows AutoPilot Deployment Profile - WLP Windows Autopilot Deployment Profile

224278-screenshot-32.png224292-screenshot-31.png

I have set up Dynamic Device Group - WLP All AutoPilot Devices Group
224250-screenshot-33.png
224304-screenshot-34.png

However, devices are not assigning to the deployment profile
224305-screenshot-35.png

Question, suspect my query expression is wrong, but for the life of me cannot see why the devices are not assigning to the profile. Any nudges in the right direction would be appreciated.

Microsoft Security | Windows Autopilot
Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments
{count} votes

Accepted answer
  1. Crystal-MSFT 53,991 Reputation points Microsoft External Staff
    2022-07-26T01:00:45.257+00:00

    @Anonymous , From your description, it seems the Autopilot deployment profile is not assigned to the device. If there's any misunderstanding, feel free to let us know.

    I have tested the following rule syntex to build the Autopilot dynamic device group and see the device is a member of this group. You can try this to see if it works.
    (device.devicePhysicalIDs -any (_ -contains "[ZTDID]"))
    224672-image.png
    224673-image.png
    After that, I check the Windows Autopilot deployment profile->Assigned devices and find the device is there.
    224681-image.png

    Meanwhile, for the Windows Autopilot device side, this is a place to manually register device to Autopilot. In fact, there are 4 ways to do this:

    • OEM registration
    • Reseller, distributor, or partner registration
    • Automatic registration
    • Manual registration

    https://learn.microsoft.com/en-us/mem/autopilot/registration-overview

    if our device is already in our environment, we can manually register devices with Windows Autopilot. We can firstly collect hardware hash using the following script and then add the device into Windows Autopilot devices to register it to Autopilot. Here is an article with more details for the reference:

     New-Item -Type Directory -Path "C:\HWID"    #Create a folder under c driver  
     Set-Location -Path "C:\HWID"                #Change the location to C:\HWID  
     $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"   #Add environment variable  
     Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned   #Sets the PowerShell execution policies to allow our script running.  
     Install-Script -Name Get-WindowsAutopilotInfo               #Install the script  
     Get-WindowsAutopilotInfo -OutputFile AutopilotHWID.csv      #Collect hardware hash information with the command in the script  
    

    Note: Add some comments in the above commands.
    https://learn.microsoft.com/en-us/mem/autopilot/add-devices

    Hope it can help.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2022-07-25T14:11:26.897+00:00

    Folks sorted this one out the rule syntax in the dynamic group was incorrect. Looks like if you get the syntax wrong, it doesn't validate as such.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.