The first step in getting an Operating System into MDT is downloading it from Microsoft Volume Licensing Service Center (if you have access). It is very important to note the Release Date, as an Operating System can have multiple Release Dates, even without a Service Pack being added. These are typically released after Update Rollups.
MyInstall has been updated to support Server OS’s. Config files will be updated automatically and by default Server OS is set to False.
'====== Operating System Compatibility ================================= cOSWindowsXP = True cOSWindowsVista = True cOSWindows7 = True cOSWindows8 = True cOSWindows81 = True cOSWindows10 = True cOSServer2003 = False cOSServer2008 = False cOSServer2008R2 = False cOSServer2012 = False cOSServer2012R2 = False cOSServer10 = False
I recently had an issue where my MDT Drivers (DeploymentShare\Out-of-Box Drivers) had grown considerably when I added drivers for new models. After further checking I determined that it was my Media directory that was consuming 5.7GB (of 18 GB).
A friend of mine was kind enough to share her MDT Applications with Command Lines.
MyInstall.vbs makes quick work of BIOS Updates. For example I am working with a Latitude E6440 that has a BIOS of A05 and I need to get it updated to A12. All I need to do is know my BIOS Switches, add my Min and Max version, set my Hardware requirements . . . and assuming I added the proper configuration to ZTIApplications, my system will reboot if necessary.
Ok this is a challenge. For starters this is CCM Client, so I need to configure my cSetupFile and my cSetupSwitches.
I then decide that I want it copied locally, so I configure my cLocalPath to copy to C:\Windows\Local.
CCM Client will actually continue to the next Step in the MDT Task Sequence before it is really completed for some strange reason, so I need to configure cWaitForProcess to make sure that ccmsetup.exe is actually done running before exiting.
This is not that hard to do with MyInstall.vbs. Let’s say I need the Dell Feature Enhancement Pack
If your config files are not easy to read in Notepad++ and look like this
So Adobe Reader 11 is a pretty simple application, so let’s have a look and get it configured with MyInstall.
First create an Adobe Reader 11 directory. I place mine under DeploymentShare\Applications\Standard\Adobe Reader 11.
If you don’t have Adobe Reader 11 downloaded, go ahead and get a copy from http://get.adobe.com/reader/enterprise/
Place the Install EXE in a Source subdirectory. This helps keep the install separate from the Admin files. Next place URL link to your download in the Adobe Reader 11 directory. This will keep you from having to look it up later, and also it is a good practice to have some marker in here so you know (or anyone else) where the file came from.
A fresh copy of MyInstall.vbs should go in here as well.
So before we get too involved into the usage of MyInstall.vbs, lets make a Reference. I’ll try my hardest to keep this updated, so lets start out with this line: