You can even tie MDT into Windows Deployment Services if you wish to help streamline the deployment process. To become familiar with the process of using MDT, you might want to check out these videos from the Springboard Series page on TechNet:ĭeployment Day Session 1: Introduction to MDT 2012 Opens a new windowĭeployment Day Session 2: MDT 2012 Advanced Opens a new window You can also import all user data into the new environment using the User State Migration Tool Opens a new window (also free). Using MDT, you can easily add both applications and drivers, manage Windows updates Opens a new window, create task sequences, join a domain, add a KMS or MAK product key, create an administrator account, specify time zone, etc.
MDT acts as a common console for all of your images plus, it’s free and it can be used to deploy Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows 2008 and Windows 2008R2. The first option you have that I recommend checking out is the Microsoft Deployment Toolkit (MDT) Opens a new window. While, I understand your end goal is to create a VM that is fully up-to-date that you can simply restore to multiple machines, I did want to bring two possible options to your attention. It also might become troublesome to keep track of 4 different images for the two workstations and 2 laptop models you mentioned. The points Galen in Laguna and Sean Wolsey made about creating a “universal image” using Sysprep and Ghost because of the differences in hardware configuration across multiple hardware types.
0 kommentar(er)
