Skip to content

Commit 1078b2a

Browse files
authored
Update autopilot-device-guidelines.md
Please see this ICM for the Intune Engineering Teams' proof that this doc change is needed: https://portal.microsofticm.com/imp/v3/incidents/details/260756690/home
1 parent ae01bb7 commit 1078b2a

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

memdocs/autopilot/autopilot-device-guidelines.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ The following best practices ensure that devices can easily be provisioned as pa
3636
- Before shipping devices to an Autopilot customer or channel partner, the OEM should upload 4K Hardware Hashes to Microsoft by using the CBR report. The hashes should be collected using the OA3 Tool RS3+ run in Audit mode on full OS.
3737
- Microsoft requires that OEM shipping drivers get published to Windows Update within 30 days of the CBR submission date. System firmware and driver updates are published to Windows Update within 14 days.
3838
- The OEM ensures that the PKID provisioned in the SMBIOS is passed on to the channel.
39+
- When using VMs for Autopilot testing, they must be a minimum of 2 processors with 4gb of memory, else you may run into application install issues after May 2021 builds of Windows 10. *Note the minimum system requirements for Windows 11 are 2 processors and 4gb memory.
3940

4041
## Software best practice guidelines for Windows Autopilot
4142

@@ -47,4 +48,4 @@ The following best practices ensure that devices can easily be provisioned as pa
4748
## Next steps
4849

4950
[Windows Autopilot customer consent](registration-auth.md)<br>
50-
[Motherboard replacement scenario guidance](autopilot-mbr.md)<br>
51+
[Motherboard replacement scenario guidance](autopilot-mbr.md)<br>

0 commit comments

Comments
 (0)