Forum Discussion
Windows Autopilot and Configuration Management Client Installation Methods
I'm using Windows Autopilot to build my machines with AzureAD hybrid join. Currently as part of the ESP we deploy the configuration manager client and our VPN software (both Win32 apps) to them so we...
Since we are Hybrid joined I did the following:
- Create a custom Win32 app in tune and delivery as a blocking app in ESP phase of autopilot
- This app creates a scheduled task that runs on next reboot and installs the MECM agent on next boot then disables itselfWorks great!
Is you AP provisioning dependent on anything getting installed from ConfigMgr under Co-management? If not, then you can install the ConfigMgr agent right at the end by assigning to a user based group. Alternatively, since the device is being Hybrid joined, you can push the agent either using a GPO startup script or automatic push through ConfigMgr (Will depend on your current configuration of course).
- I do the same as the suggestion above in the few times we use AutoPilot for Hybrid Join one of the reasons is your question here. We add the CM client using a startup script as we don't want to make the autopilot time longer.
Moved all required apps to Intune added then as blocking apps in ESP.
Regards,
Jörgen- As a GPO startup script? Have you tried deploying it through Intune somehow? I'm about to try adding it as a script in Intune that creates a scheduled task that triggers at logon. Would be nice having the deployment in Intune if possible 🙂
