One of the hardest part in management dealing with Microsoft Deployment Toolkit is the Driver node. The number one question asked is how to manage all the drivers for all the different models in an infrastructure. The question is really hard to answer because it really depends on your environment and how many models you have in your office. I have three scenarios that works great for any situation, but it really depends on how you wants to make MDT work for your environment.
The first step is to take care of your WinPE drivers for booting
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.
I started to notice after doing a deployment of Windows 7 Service Pack 1 via MDT 2012 an NTFS partition of 300MB called BDEDrive was created.
There are many new features of MDT but one that I particularly use a lot many time in non-domain infrastructure is the ability to apply GPO Packs created using Security Compliance Manager (SCM) during the deployment process.
Microsoft Security Compliance Manager 3.0 is a great tool that allows you to create and manage group policy baselines in an easy to use interface. These polices are then able to be applied at the domain level or as “Local GPO Packs”.
MDT provides four default GPO packs for the following operating systems that are applied by default during deployment. 1. Windows 7 SP1 | 2. Windows Vista SP2 | 3. Windows 2008 SP2 | 4. Windows 2008 R2 SP1
All GPO packs are stored in the Templates folder within the Distribution Share. For example <Distribution Share>\Templates\GPOPacks\<GPO Pack Folder>.
When you specify your own GPO Pack you must override the default GPO pack using the GPOPackPath variable in the customsettings.ini file.
Microsoft Deployment Toolkit (MDT) 2013 is a Solution Accelerator for operating system and application deployment. MDT 2013 supports deployment of Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2.
- Deploy Windows and Office with Microsoft Deployment Toolkit 2013. MDT is the recommended process and toolset for automating desktop and server deployment. MDT provides you with the following benefits:
- Unified tools and processes, including a set of guidance, for deploying desktops and servers in a common deployment console.
- Reduced deployment time and standardized desktop and server images
Some of the key changes in MDT 2013 are:
- Support for the Windows Assessment and Deployment Kit (ADK) for Windows 8.1.
- Support for deployment of Windows 8.1 and Windows Server 2012 R2.
- Support for System Center 2012 R2 Configuration Manager.
- Improved support x86-based Unified Extensible Firmware Interface (UEFI) systems.
Microsoft came out with a new MDT version, check out the first part of every software and that’s the configuration part.
Download it from here: http://goo.gl/Anv2bz