-
Notifications
You must be signed in to change notification settings - Fork 5
cMDTBuildTaskSequence
Pavel Andreev edited this page Feb 1, 2019
·
2 revisions
cMDTBuildTaskSequence is a DscResource that enables management of Task Sequences with lifecycle management for MDT.
Available parameters:
- [Ensure] - Present/Absent
- [Name] - Name of Task Sequence
- [Path] - MDT folder for Task Sequence
- [OSName] - MDT path and name for OS image, imported with cMDTBuildOperatingSystem resource
- [Template] - Client.xml / Server.xml
- [Comments] - Optional comments
- [ID] - Task Sequence ID
- [Owner] - Optional Owner name
- [OrgName] - Organization Name of Windows Reference Image
- [PSDriveName] - The PSDrive name for the MDT deployment share
- [PSDrivePath] - The physical path to the MDT deployment share
The DscResource will create Task Sequences according to the following principle:
- Verify status present or absent
- If present:
- Check if Task Sequence exist in the MDT path
- If it does not exist the Task Sequence will be created
- If absent:
- The Task Sequence will be removed
Note: The Operating System must exist in the OSName path for the Task Sequence to be created correctly.
Desired State Configuration job example:
cMDTBuildTaskSequence Win10x64 {
Ensure = "Present"
Name = "Windows 10 x64"
Path = "Windows 10"
OSName = "Windows 10\Windows 10 Enterprise in Windows 10 x64 install.wim"
OrgName = "BuildLab"
Template = "Client.xml"
ID = "REFW10X64-001"
PSDriveName = $PSDriveName
PSDrivePath = $PSDrivePath
}
- Home
- Quick Start
- How to Update MDT Server
- Prepare Windows Update Server
- Version History
- The DSC Resources:
- References