How to Enumerate the Available Operating System Deployment Task Sequences
In brief
The page metadata now identifies the service as `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
What Intune admins need to know
No administrator action is required.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
How to Enumerate the Available Operating System Deployment Task Sequences
You enumerate the available operating system deployment task sequences, in Configuration Manager, by querying the available task sequence packages. Configuration Manager does not maintain instances of the SMS_TaskSequence class for task sequences, but there is one instance of the SMS_TaskSequencePackage class for each task sequence.
@@ -5,7 +5,7 @@ ms.date: 09/20/2016 ms.subservice: sdk ms.topic: how-to ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # How to Enumerate the Available Operating System Deployment Task Sequences You enumerate the available operating system deployment task sequences, in Configuration Manager, by querying the available task sequence packages. Configuration Manager does not maintain instances of the [SMS_TaskSequence](../../develop/reference/osd/sms_tasksequence-server-wmi-class.md) class for task sequences, but there is one instance of the [SMS_TaskSequencePackage](../../develop/reference/osd/sms_tasksequencepackage-server-wmi-class.md) class for each task sequence.