Here at UVM, we have been using MDT in “LTI”, or “Lite Touch Installation” mode for many years (for those in the know, we used LTI back when MDT was called “BDD”, or the “Microsoft Solution Accelerator for Business Desktop Deployment”). We used MDT throughout the XP, Vista and Windows 7 lifecycle.
However, these steps often are radicaly different in implementation.
Most notably, injection of drivers, installation of applications, and application of operating system images are handled in ways that utterly shattered our exiting task sequence logic.
The whole process of adapting MDT/LTI to SCCM/UDI was, at the very least, educational.
By migrating to UDI, we can drop all of the LTI work.
In recent months, some additional pressures have come about which make this migration a bit more pressing: of custom logic built into our current MDT/LTI environment.
Remapping our current workflows into UDI land is a difficult and time consuming task.
Additionally, while it is true that MDT/LTI and SCCM/UDI share a great deal of code, it is important to understand that they are very similar and share nearly identical names.
This post if the first installation in a series on migrating to Configuration Manager UDI from MDT “Lite Touch”. Well then, this blog series is likely of little interest to you.
(Hint: This is all about deploying Windows operating systems using Microsoft’s own deployment technologies.) “SCCM UDI for OSD”… Such snappy product names that we Windows Sys Admins get to work with!