MDT 2010/2012/2013 variables are SCCM Task Sequence the variables that are gathered by MDT’s ZTIGather process and are documented in “Toolkit Reference.doc” that comes with the MDT 2010/2012/2013 install. SCCM OSD variables are built in Task Sequence variables that are available in any SCCM OSD deployment – most of these are set by SCCM and need not be changed (a lot of them are also read-only) – but, its handy to know what they are – in case, one day, you do need to manipulate one in order to get your task sequence working the way you want.Ī full list of these variables can be found at: This type of functionality minimises the amount of duplication of Task Sequences required and, in many cases, results in only requiring one task sequence for clients and one for servers being required.įor the purposes of this article, I’ll break Task Sequence variables down into 3 types: Task sequence variables can be leveraged within an SCCM task sequence to perform conditional branching and execution on SCCM Task Sequence Tasks and Groups, allowing us to execute tasks only on specific computers based on something identifiable about that computer.įor example, install VPN software only on laptops or specific drivers only on their corresponding models. Relevant to: SCCM 20 (including R2 and R3 versions), MDT 2010/2012/2013 This article is an updated version of SCCM OSD Task Sequence Variables – A beginners guide
