Forum Discussion
Multiple autopilot profiles in TS for existing devices
as above - great points
I think a key thing to consider is to remove the mindset of custom images. They are no longer a great way to manage a device - Image native as possible (Autopilot ready from OEM is best) then layer on your Apps and Config
Hi Guys!
thank you all for clarification of my doubts and asks.
Finally I was able to deploy my custom image on VMs and run through autopilot with co-management and some applications installation using PROVISIONTS parameter and this work fine. However I have additional questions and concerns.
1. My custom image contains a set of preinstalled OS languages. When I deploy that image through SCCM after installation I can see menu that allows me to configure Windows with one of preinstalled language. However when I run task sequence with preparation for autopilot (sysprep at the end) I don't see this menu - is there a possibility to configure that setting to allow user to choose Windows language?
2. Do I need to do any additional steps before I run Autopilot Reset in order to configure previously autopiloted device again? I am asking because I try to do this with one of my machine - the process resets my machine, reinstalls Windows and now all steps under "Device Setup" are in "Identifying" state for a couple of hours.
Thank you and best regards
Damian
- DamianL1984Jul 16, 2022Brass Contributor
And one more concern. Is there any option to restart to autopilot that preservs apps included to custom image (Office in my case)? I noticed that Autopilot Reset for example leaves included language packs but removes Office. I am not sure but it seems that the only way is to run TS for existng devices again.