The SCCM — ConfigMgr, Intune, Windows and PowerShell notes

Written by Zeng Yinghua (Sandy)

Get in touch

Contact Me

Questions, corrections or a topic you would like to see covered on The SCCM? This is the place to reach the site administrator, Zeng Yinghua (Sandy).

Extreme close-up photograph of a smooth dark surface with fine grain and soft amber highlights, calm and technical in mood

How to reach out

The SCCM is a personal technical blog, so the quickest way to get a reply is through the author's public Twitter account.

Twitter

@sandy_tsang

Follow along for new posts and short notes on ConfigMgr, Intune and Windows deployment, or send a message there.

Follow @sandy_tsang

Please keep messages on topic: technical questions, article feedback and corrections are all welcome.

Windows Autopilot represents a significant shift in how organizations approach device provisioning, moving away from traditional imaging workflows toward a cloud-driven, zero-touch deployment model. By leveraging Intune and Azure Active Directory, IT administrators can pre-configure devices so that end users simply unbox, power on, and connect to a network to complete the setup process. This approach reduces the overhead associated with maintaining on-premises infrastructure like MDT or Configuration Manager task sequences, while still allowing for granular application and policy assignments. For teams already invested in modern management, Autopilot streamlines the journey from factory floor to productive user, aligning with broader enterprise mobility strategies.

For administrators accustomed to managing Windows deployments through SCCM or MDT, transitioning to Autopilot requires a shift in mindset from image-based provisioning to a configuration-driven model. Rather than capturing and maintaining thick images, the focus turns to defining device profiles, enrollment status pages, and assignment policies within Intune. PowerShell scripts remain valuable for customizing settings and installing applications during the out-of-box experience, bridging the gap between legacy automation habits and modern management. Understanding how to structure hybrid Azure AD join scenarios and manage white glove or self-deploying modes ensures that the migration from traditional OSD to Autopilot is both practical and sustainable for diverse enterprise environments.

What to write about

  • ConfigMgr Task sequences, client deployment and site server setup
  • Intune Autopilot, policy CSP settings and Win32 applications
  • OSD Imaging, boot methods and task sequence error handling
  • PowerShell Scripts for monitoring and automation
  • Windows 10 Deployment and troubleshooting guides

About the author

Zeng Yinghua (Sandy) writes The SCCM about IT infrastructure, System Center Configuration Manager and modern management. The blog collects hands-on notes from day-to-day administration of enterprise Windows environments.

Topics range from SCCM backup and SQL database mail configuration to Azure AD self-service password reset, iPXE UEFI boot and PowerShell tooling for Microsoft Planner.

Read the latest posts