Today during class we worked on Refresh and Replace scenarios. We touched based on a tiny step in the Task Sequence that is actually really cool. In the Task Sequence for Lite Touch (MDT Standalone) there is one step that does not exist in Zero Touch and that is the “Generate Application Migration File” step.
That little step will do a really smart thing, it will basically make sure that registered file types that can be open with an application will automatically be saved by USMT. It does that by grabbing all non-default file types and then check if there is a corresponding application that can open the file by examining the registry.
So, what’s cool about that step?
If you open the file it states:
‘ // Purpose: Generate an XML file for automatically capturing user data
‘ // (documents) associated with installed applications.
And if you continue looking in the file you will see the flow, like this:
‘ Determine the version of USMT to use
‘ Create the file and write the standard header
‘ Get the list of all registry keys in HKCR
‘ Look at all file extensions to see if they map to an application
‘ Read the default value to see what app is associated with this extension
‘ See if the file can be opened (has a shell\open\command handler)
‘ Add it to the XML file
‘ Write the rest of the XML file
‘ Make sure the ZTIUserState.wsf script knows to use this script
‘ Cleanup and Exit
So, that is why you don’t need to spend a whole lot of time on USMT when doing Lite Touch.
Try It out
If you would like to see what it actually collects, you can run this interactive, that way it will generate a XML file. If you open it up you will then see what it would have migrated and not.
Open an elevated Command Prompt and execute the following:
cscript \\MDTSERVER\MDTSHARE\Scripts\ZTIAppXmlGen.wsf /capture
You will get an output that looks like this:
If you then open the XML (It is going to be located in C:\MININT\SMSOSD\OSDLOGS and named ZTIAppXmlGen.xml its going to look something like this