Lior_Bela, thanks for sharing this information. It would be great if you can share some more information on the following:
- The new Device Preparation Policy will be targeted to users. How will we be able to handle the scenario where a user may be targeted with more than one profile? I understand we could use Filters (for example based on hardware model), and then it would just work through the different profiles by priority. But what if hardware attributes cannot be used to distinguish between use cases?
- How will the new AP profiles co-exist with the legacy profiles? If a device is targeted with a legacy profile and the user is targeted with the new profile type, how will OOBE work out which one to use?
- If an app/script is added to the new profile type, will that only run during the ESP? For example, if the script is updated in the future, will it rerun on existing devices or will it only run on new devices during the ESP? It sounds to me like the behavior is the same as with the legacy AP profile, but in addition to Apps we can now also specify which Scripts we want to include behind the ESP?
- The limit of 10 apps and 10 scripts feels arbitrary and limiting. I understand that you probably based this on telemetry data, but please consider increasing these limits to support more complex configurations in large enterprises.
- Please share some dates for the items in the ‘See what’s to come’ section soon. We need that to be able to plan ahead. For example, we will not be able to adopt the new profiles until you add the option to rename a device.
Thanks,
Jan
Microsoft