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
Within your MDT task sequence you will need to create a new “Run Command Line” variable and call out your *.bat file
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
When your deployment runs and the task sequence hits your custom “stamp” task the end result will look something like this
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.
Here is what I have on my oeminfo.reg file