Some examples of model strings you will see are:ĭC 7900 FRGHU89m – we like the DC 7900 part, but the addition letters represent nothing to us and are just painĩ645-AM2 – Then we have the worst of the lot, the Lenovo’s…. Unfortunately, some hardware manufacturers decide to be, what can only be described as “not-deployment-focused”. Name mangler sequence driver#You have a large number of hardware make/models and instead of using driver categories, you prefer to apply driver packages based on model.ĭiscussed in detail above, but I think the quickest way is – from your full OS (XP/Vista/Win7/Win8.1) run the following command:įrom this you will get the model name as WMI (and therefore SCCM and MDT) sees it. Dump the variable values using a script, such as Įxample of using WMIC to get a computers model name:Įxample of using an SCCM query to get a computers model name:.On the client, in a full OS, use WMIC or VBScript WMI to get the values your after.On the client, after a gather task has completed, check the OSD logs (smsts.log and ztigather.log).Create an SCCM query and look in the database for existing models.The MDT variables are in a word document, which makes them easier to search Search through the documentation – unfortunately, the Microsoft web-documentation is all in the collapse/expand type format, which makes it hard to search nicely.View another my articles at, which provides a filter-able list of all variables.There are a number of ways to achieve this goal, you can: You want to perform a task sequence step based on the model of a machine, you know the model is a Dell Latitude E6520, but, what does SCCM see it as? How do you find out what a specific variable you want to use is? Name mangler sequence install#An example of usage here would be to define a variable called “Department”, and based on its value, install software specific to that department. User defined variables are passed to the Task Sequence when the Task Sequence starts execution, and can be stored either in an SCCM Resource, or an SCCM collection, and are anything you wish to define. MDT 2013 – (Located within Toolkit reference.doc) MDT 2012 – (Located within Toolkit reference.doc) It is important to stress that the MDT variables created by integrating MDT into SCCM are additional to the base SCCM variables – and present one of the main reasons for installing MDT on top of your SCCM install. The easiest way to get the additional variables offered by MDT 2010/2012/2013 is to configure MDT integration for SCCM, and use the MDT Task Sequence Wizard in the SCCM console to create a task sequence based on one of the MDT template task sequences (which I recommend to use anyway). 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: Name mangler sequence drivers#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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |