What's New

Branding Your MDT Image


I was asked on how I customize my image for each client I deal with in deploying operating systems. There isn't really a good or bad way in doing this, but the way I customize my image is by inserting a "cookie" file stating the image version and date of deployment. I also like playing around in the computer's system properties and adding the version - what I'm really doing is changing the OEM information.

The “cookie” approach is pretty simple. I normally create a *.bat file and enter cmd command within the MDT Task Sequence to deploy it

2-6-2014 8-56-21 AM

Within your MDT task sequence you will need to create a new “Run Command Line” variable and call out your *.bat file

2-6-2014 8-54-05 AM

Now, if you have any custom scripts for your MDT deployment I like to separate them and create a folder within “deploymentshare\script” path and drop all of them in there

2-6-2014 8-54-37 AM

When your deployment runs and the task sequence hits your custom “stamp” task the end result will look something like this

As you can see this machine was imaged on 12/22/2011 with image v1.00

Now, for the OEM information setup. I store *.bat in my custom folder inside the “deployment\script” path and the registry file that does the editing on the OEM side of Windows.

2-6-2014 9-50-08 AM

Here is what I have on my oeminfo.reg file

2-6-2014 9-29-16 AMI use a *.bat file to run the registry file – I find that MDT runs best when you use batch files.

2-6-2014 9-50-26 AMWithin MDT you will have to create a “Run Command Line” and call out your batch file to run your registry hack file. It’s the same concept as the “stamp” approach.

About BjTechNews (1057 Articles)
An IT guy trying to learn everything about technology and sharing it with you all. I'm a blogger and video blogger who highlights daily news in the tech industry, promoting tips and hacks for fellow techies.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: