Intune - Remotely upload Autopilot Hardware ID in Out of Box Experience

Поделиться
HTML-код
  • Опубликовано: 21 окт 2024

Комментарии • 18

  • @3143iamsam
    @3143iamsam 2 года назад +1

    Marvellous work! Very nice real-world scenario! Merci John!

  • @gertbleus7276
    @gertbleus7276 Год назад +1

    This helped me a lot, thank you. But I have some other questions concerning Intune. Is there a way to ask them? Greetings from Belgium.

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  Год назад

      Hi Gert, I like the Benelux countries and visited only Antwerp a few times, lovely city.
      Happy it helped a lot, I usually try to answer any Intune related questions in my comments field, and sometimes if it is a topic many ask about I do a video about it. So please try it out here and I'll do my best to answer it.

    • @gertbleus7276
      @gertbleus7276 Год назад +1

      @@IntuneVitaDoctrina Hi John, thank for the reply. I did everything in the video. The device show up in my Endpoint Manager in the Autopilot devices. But when I reboot the device it just goes through the build in windows installation steps instead of using the implementation profile of Autopilot. The device has been assigned to a group and profile. So did I forget something? Greetings, Gert

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  Год назад +1

      Sounds to me you have done all correctly, specially if it says profile is assigned.
      To try to see if your profile is setup correct and all you can do a so called offline test.
      you create a json file named: AutoPilotConfigurationFile.json and copy it to C:\Windows\Provisioning\Autopilot\ and then restart, it should be the same procedure, to create this json file please follow this link:
      www.petervanderwoude.nl/post/offline-windows-autopilot-deployment-profile/
      Pretty cool way to learn what happens during Autopilot, all it does is to download that json file that points to your tenant.
      This wont solve your initial problem, but if this works, then we know that your setup is working and the problem is assignment of the profile to the device

    • @gertbleus7276
      @gertbleus7276 Год назад +1

      @@IntuneVitaDoctrina Thank you for the advice. Could the problem be, because the device starts with a Windows 11 Home edition? Greetings Gert

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  Год назад +1

      @@gertbleus7276 100% the reason! It has to be professional or enterprise- well done you found the issue

  • @HeyRadu
    @HeyRadu 2 года назад +1

    Excellent tutorial ! Suggestion if I may: Why not popularizing the links to these videos on Twitter as well ? Cheers.

  • @XwolfBane18
    @XwolfBane18 2 года назад +1

    Great video thanks , I intune alot of devices in work but I might give this. try ,please upload more video you think can benefit a technician which uses intune and endpoint management system

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  2 года назад

      Thank you so much for this comment. Best is if your manufacture like Lenovo, Dell, HP import the hardware hash/ID to your tenant when you buy machines but sometimes it shows up remote machines that isn't imported then this is gold.
      I'm thinking of doing a video to explain the Sync and all the many different way you can sync, and maybe also about howto read logs or troubleshooting installation errors.

  • @unkownuser2320
    @unkownuser2320 Год назад +1

    1) what is difference between machine reset and sysprep 2) please share script to upload hardware hash with multiple group tag GUI option example grouptag1, grouptag2 etc selected group tag has to be uploaded with hardware hash value

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  Год назад

      Good questions! Machine reset if you are speaking about the reset within Windows is to prefer, Sysprep was great in for example ConfigMgr when creating a base WIM to capture, that is no longer needed in Intune with Autopilot. You can still use sysprep but I don't see any reason, if you do be sure to use /generalize switch, read more here:
      learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-sysprep-windows-10-device-enrolled-mdm
      For Group tag:
      Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User
      ,,,,
      I have never used multiple group tags for one and same device an unsure if that is even possible since it is called "Group Tag" and NOT "Group tags" so you can have many tags but only one tag per device.

  • @stevebena
    @stevebena Год назад +1

    Hi, it look like MS deprecated the autopilotinfo -online, is there another way to do it?

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  Год назад +1

      Thanks a lot Steven for sharing this, I had missed that!
      There are some work arounds to make it work, the creator of the first scripts explains all here:
      oofhours.com/2023/06/09/get-windowsautopilotinfo-ps1-updated-but-not-by-microsoft/
      and the fix is to use this script instead:
      andrewstaylor.com/2023/06/08/updated-get-windowsautopilotinfo-with-groups-fix/

  • @philp7844
    @philp7844 2 года назад +1

    I do something similar but i just talk the user through the process or send an email with the 4 steps involved (no need to use QuickAssist).
    When user is at the OOBE screen have them press 'Shift + F10' to open the command prompt. The user then just needs to input the commands below:
    - Powershell.exe
    - Set-ExecutionPolicy Bypass
    - Install-Script -Name Get-WindowsAutoPilotInfo
    - Get-WindowsAutoPilotInfo.ps1 -Online
    Once the device id is shown and assigned in Intune i tell the user to reboot and Autopilot then takes care of the rest.

    • @IntuneVitaDoctrina
      @IntuneVitaDoctrina  2 года назад

      Gret idea! not possible for all companies due to security rules as most users aren't Intune admins and have permission to upload the hardware/hash with the online switch, but can be used to create a CSV and send by email, that is also a possible way.
      thanks for sharing!