
This variable can be used as a condition to determine if the next step is run.
Mdt version list code#
Stores the return code that was returned by the last action that was run. You can test this task sequence variable to determine the current operating system environment. This variable is set to true when the current task sequence step is running in the Windows PE environment, and it is set to false if not. Set to true if the current task sequence is running in download-on-demand mode, which means the task sequence manager downloads content locally only when it must access the content. This variable is set before the task sequence manager runs each individual step. Specifies the name of the currently running task sequence step. This variable is not set if the task sequence is running from stand-alone media. Stores the value of Configuration Manager client GUID. The variable will not be set if no Configuration Manager boot image package is associated. Stores the Configuration Manager boot image package ID if a boot image package is associated with the current running task sequence. If the task sequence is running from stand-alone media, this variable is undefined.
Mdt version list software#
It uses the same format as a Configuration Manager software distribution deployment ID. Stores the current running task sequence deployment unique ID. as I’m only interested in the variables available when integrating MDT 2013 with SCCM
Mdt version list full#
After you have found the variable you think you need, head on over to the original documentation (linked above) to get the full detail There will be entries that are incomplete – sometimes because of flaws in my scraping process, other times for the sake of “making things fit”. This is a more easily searchable list of variables, not full documentation.

as the search function will work on all fields
