Updated Preparing for Autopilot Documentation #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Re-Wrote the doc to talk about Autopilot and Device Preparation. Fixed some spelling errors, added a table for OEMs. Linked out to Microsoft Documentation for mass registration of devices for Autopilot.
Removed `(v1)` and `(v2)` from the document.
Removed the personal verbiage now that Device Identifiers are now back up and working to get around the Enrollment Restriction change to allow for personal device enrollment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I updated the Preparing for Autopilot documentation to include some information and scope it to recommended/supported solutions. This would include Autopilot (v1) and Autopilot (v2), gathering the hardware hashes of devices in different ways, and fixing some markdown, as well as some spelling.
I removed things like the vender registration section since it didn't provide any value to the documentation.
I did look at the markdown in the actual Wiki to make sure formatting will still hold comparing to my preview in VSCode.