Download from GitHub:
.Version 22.214.171.124 (2022-12-14)
– It is now possible to add multiple domains to the config-file.
– It is now possible to add a default tag to the config file
– Slightly new graphical interface
– Optional: It is now possible to add a group tag!
– Use the gather logs button to get autopilot logs as a CAB file
.Version 126.96.36.199 (2021-08-17)
It is now possible to set a default domain name. Get the latest version (188.8.131.52) from GitHub and you will find “config.txt” – edit as per your need. Thanks Dylan Brown for the idea!
It is now possible to use a custom logo. Place “logo.png” in the same directory as the .exe
Recommended logo size: 210×110 px
If you have been working with Windows Autopilot you know that manual upload of the hardware hash is a repetitive and time consuming task.
This tool will make your life easier by…
- Install the necessary PowerShell modules
- Connect to the tenant (MFA is supported)
- Import the hardware hash.csv-file to the tenant
- Run a sync
…. directly from the device!
No more need to struggle to manually get, move and import the csv-file from another device. All you need to do is run the tool (Shift+F10 when you get to pick your keyboard layout), start Autopilot Tool and sign in to Azure (when you get prompted) with an administrative user. This works well with MFA!
- Put “Autopilot Tool.exe”, “Logo.png” and “config.txt” in same directory on either a USB-stick or on a network location
- Press Shift+F10 when you are at the “pick your keyboard layout” screen
- Navigate to “Autopilot Tool.exe”, press Enter to start the tool
- Change yourDomain.onmicrosoft.com to your specific need
- Update: it is now possible to edit config.txt to add a default domain and tag
- Optional: add a group tag
- Press the OK-button
- Sign-on with an Intune Administrator account (or similar) when prompted
- The HW hash has now been uploaded and will be visible in the Windows Autopilot service
- Update: press “Gather Logs” to create a CAB-file with all autopilot logs. Use this to troubleshoot the autopilot deployment
Download the tool from Github:
This is a UI to Nickolaj Andersens script found at: https://github.com/MSEndpointMgr/Intune/blob/master/Autopilot/Upload-WindowsAutopilotDeviceInfo.ps1
|Windows 10 version||Supported|
Is the administrative user you are saying in azure or just in the local admin? Thanks
The administrative user is an Azure identity with Intune Admin privileges or similar. Thanks for your question I have updated the info text.
Is it possible to exchange your logo for that of our company for internal use?
It might be nicer for the users. Otherwise, your tool is gigantically good. Many thanks
That is fully possible with latest version
Thanks for the feedback! 🙂
A handy version of this would be for a (remote) end user to run, then automatically launching the default mail client with the hash CSV file as an attachment for forwarding to IT for importing.
Hi Jörn, Thanks for reaching out. That is a good idea for a future version 👍
What permissions/apps is this needing to contact? I have bypassed “microsoft intune powershell” application in my CA policies however I’m still being blocked. We require MFA AND hybrid join from global admin accounts, and despite excluding the app, these rules are still triggering on “microsoft intune powershell” despite being excluded.
The users running the tool should be “Intune admin” or similar. If your CA requires the device to be hybrid joined it will not work to you run it on a device before it has ben provisioned by Windows Autopilot, as the device is not hybrid joined at that point.