Installing The Configuration Manager Client During Autopilot-SysManSquad | Systems Management Squad

[utterances-bot]

Installing The Configuration Manager Client During Autopilot-SysManSquad | Systems Management Squad

A community blog and subsidiary of WinAdmins.io

https://sysmansquad.com/2021/08/30/installing-the-configuration-manager-client-during-autopilot/

[Patel-Sheetal]

Hello Johannes,

Good work.

But, unable to see the full content of script from any of the sections.
Are you able to share me the full script for MECM-client.ps1 that you have created so that i can update necessary things from my end.

Thank you
Sheetal

[BluMoon77]

What is the purpose of adding the time to the scheduled task. During testing, the client doesn't install until the user logs out from the initial OOBE login then logs back in.

[jgkps]

I have updated the blog, no one should be using this solution anymore, I encourage you to use the new autopilot co-management feature, it will make the client install a breeze

[BluMoon77]

Actually, we still find it useful because the new feature in not supported in Hybrid AD environments.
"You can't deploy the Configuration Manager client while provisioning a new computer in Windows Autopilot user-driven mode for hybrid Azure AD join."
https://learn.microsoft.com/en-us/mem/configmgr/comanage/how-to-prepare-win10#windows-autopilot

[jgkps]

no one should use haadj in autopilot, its a terrible idea.

[BluMoon77]

I can't disagree but we have a specific client with very specific a very request and this solution is working for them. Thanks for putting it together. Going back to the time and logon question for the task, what was the original purpose of add the creation time as a trigger?

[jespinoza84]

We still have to use this solution as co-management does not support pre-provisioning yet.