Task Sequences Software Center: OSD or Application Deployment?

Software Center groups task sequences into two different tabs — Operating Systems and Applications — and which one a task sequence lands in isn’t something you choose directly; it’s determined by what the task sequence actually does.

How SCCM Decides

A task sequence that includes OS deployment steps — specifically Apply Operating System Image and/or Apply Windows Settings — is treated as an OS deployment task sequence and shows up under the Operating Systems tab in Software Center. A task sequence built purely to install software, run scripts, or apply configuration (with no OS-imaging steps) is treated the same as a regular application deployment, and shows up under the Applications tab instead.

Why This Matters

If a task sequence you expect to see under “Operating Systems” is instead appearing under “Applications” (or vice versa), it’s worth checking the steps it actually contains rather than looking for a hidden toggle — there isn’t one. Removing an “Apply Operating System” step, for example, will move it out of the OS deployment category the next time policy refreshes on the client.

A Correction Worth Making (Updated for 2026)

Checking this against Microsoft’s current documentation turned up two things worth correcting here. First, the automatic list of steps that trigger “Operating Systems” classification is broader than just Apply Operating System Image/Apply Windows Settings — it also includes steps like Restart Computer, Join Domain or Workgroup, Format and Partition Disk, Apply Data Image, Setup Windows and ConfigMgr, Upgrade Operating System, Apply Driver Package, and Capture OS Image, among others, even when a matching step is present but disabled. Second, there actually is a manual override: on the task sequence deployment’s User Notification tab, checking “This is a high-impact task sequence” will move a deployment into the Operating Systems node in Software Center even for a task sequence with no OS-imaging steps at all — the opposite of what the original guidance here claimed. If a task sequence is showing up somewhere unexpected, check this setting before assuming the step list alone is the cause.