tabs-not-spaces
commented
3 years ago The actual tool itself doesn't specifically have anything to do with Intune or Autopilot other than allowing you to inject the offline autopilot json file into the operating system. This is what is known as "offline onboarding". It allows you to onboard a device without first harvesting the hash and uploading it. It's not a GREAT experience because any device targeted policies will not be applied during AP or ESP, but it gets the device enrolled, which is more than enough in most scenarios.
You can however use this tool WITHOUT doing the offline join process - if the devices (or devices) are already enrolled, simply forcing the OS onto the machine is going to make the device go through the onboarding process naturally.
To answer your other question, yes, you can use this on as many machines as you want. It's nothing more than a glorified way to very rapidly load a clean build of Windows onto the device.
Closing this as it's not raising any issues with the project.
On Fri, Oct 22, 2021 at 2:47 AM c3rberus @.***> wrote:
This is an interesting tool that solves an important issue with Autopilot, that is devices that don't have the OS installed or its unbootable/corrupt.
One thing I was not clear on, when the USB image is created can I use this on multiple devices?
How about registration of new hardware hash to Intune? We have out-of-box devices that don't have the OS and don't have their hardware registered in Intune. Is this handled automatically (similar to what Get-WindowsAutoPilotInfo does)?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/Intune.USB.Creator/issues/43, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LNF2QVU246K3JSAO7DUIAY25ANCNFSM5GOOMKVQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This is an interesting tool that solves an important issue with Autopilot, that is devices that don't have the OS installed or its unbootable/corrupt.
One thing I was not clear on, when the USB image is created can I use this on multiple devices?
How about registration of new hardware hash to Intune? We have out-of-box devices that don't have the OS and don't have their hardware registered in Intune. Is this handled automatically (similar to what Get-WindowsAutoPilotInfo does)?