SCCM-Script to get some MDT Variables

SCCM-Script to get some MDT Variables
5 (100%) 1 vote

Hi All,

Every time when I go to customer to perform Operating System Deployment, customer always ask about MDT, so I’m here to try to clarify things:

– MDT is a great tool, however, it only does OS Deployment, nothing else. It also only does LTI (or Little Touch)
– SCCM does what MDT does and much more, it does application deployment, inventory, compliance, as well as OSD (LTI as well as ZTI – Zero Touch)

But why there is always this talk?!?!

For companies that do not have any tool that can do OS Deployment, MDT can be used. it is really easy to install and configure, in couple of hours you can have an environment ready to start deploying your 1st Windows.

But remember what i said, for companies that do not have any tool that can do OS Deployment. If you have SCCM, MDT is not for you. Your company has invested lots of money in a solution to manage devices and is really powerful OS Deployment tool, so why not use SCCM?

you may say that SCCM does not work, but the reality, is that you don’t know how to use SCCM. SCCM is a complex solution, more than MDT, so it is not that SCCM does/does not work, it is you that don’t know how to operate SCCM (assuming here that your SCCM is health :))

So now that we got this out of the way, lets discuss the MDT integration with SCCM, should we do or not?

The integration brings lots of benefits for the OSD via SCCM, things that SCCM does not have out of the box and we normally create scripts.

From my experience, MDT brings lots of benefits, but the following are the most common:
– Variables (isDesktop, isLaptop, isVM, etc)
– Logs (multiple logs, one for each script as well as copy lots to central location if using slshare variable)
– Apply Offline Stuff (language, sw update)
– Custom Task Sequence templates
– Lots of extra scripts, including LTI UI

as you can see, MDT brings lots of benefits, so an easy decision, integrate, however, are you going to use all of these extras?

From my experience, 100% of the integration are looking for the variables, 70%+ are looking for the copy lots feature and for the other features, we’re looking for less than 20%…

as historical, a new version of SCCM would, normally, cause a new version of MDT being released, however, this release would take about 30-45 days to happen, so you would have an old SCCM for a while, waiting MDT to be released and then update your SCCM and MDT.

now, with the increase of speed of updates for SCCM, updates being released every 4 months, waiting a month and 1/2 for MDT to be updated (if required), would not help. so because of this, I’ve starting to recommend not integrating MDT with SCCM in most cases. as you saw below, most of the integration are only looking after the variables, so i created a script that can be called at the beginning of your task sequence and it will give you lots of variables that MDT gives you. The list is below:
– TD-IsTMPEnabled
– TD-IsTPMActivated
– TD-Architecture
– TD-ProcessArchitect
– TD-OSArchitecture
– TD-OSCurrentVersion
– TD-OSCurrentBuild
– TD-ProductType
– TD-IsServerOS
– TD-IsDomainController
– TD-IsWorkstation
– TD-SKU
– TD-BiosVersion
– TD-Make
– TD-Model
– TD-ModelAlias
– TD-Memory
– TD-ChassisType
– TD-isLaptop
– TD-isDesktop
– TD-isServer
– TD-isVM

as you can see, all variables have the “TD-“, this is to make sure the variable will not cause any issue with other scripts/tools you already have in place.

so, if you only use the MDT integration because of the variables, be happy and if there is anything not working or missing, let me know

 

 

Comments are closed.
%d bloggers like this: