MicrosoftIn its current form, the new Autopilot doesn't fully live up to the expectations of a true "v2." It seems more like an enhanced User Status Page with additional features.
The "Device Preparation Policy" appears reminiscent of the "Policy Sets," that none uses, with hopes of adding objects that run solely during Autopilot, but it likely just delays desktop access until all policies are applied.
The removal of the hardware hash requirement is touted as a feature, but it raises a critical question: How do you attach a device to a tenant? This concern is addressed in the "See What's to Come" section, highlighting a significant oversight in the current implementation.
The "Self-deploying and pre-provisioning mode" in the list of missing features highlights a fundamental flaw in Microsoft's vision: expecting users to install apps and configurations themselves, patching to the latest level, or handling a device that isn't ready to go. This concept clashes with real-world challenges like slow internet connections, unreliable user handling, and the need for devices to arrive pre-provisioned and ready for immediate use, underscoring the crucial role of pre-provisioning.
Microsoft reassures that "The features you know and love in Windows Autopilot aren't going anywhere!" This is crucial because replacing the existing Autopilot with the new version would be catastrophic.
The new Autopilot is essentially just a User Status Page on steroids.
Despite the concerns, there is hope that the "Device Preparation Policy" could effectively decouple provisioning from normal operations. Ideally, if apps can be added in a sequential order and run accordingly, it would significantly streamline the process. Wishful thinking? Perhaps. But we shall see how it unfolds.
