How to install MDT 2010 in Windows 7

Microsoft has decided to develop standardized solutions to achieve these actions. It is from here that the projects came Solutions Accelerators. Among the projects, the best known are the systems Zero Touch Installation and Lite Touch Installation. Microsoft put more emphasis on the first (for licenses to sell SMS 2003/SCCM 2007). I am using the Windows 7 operating system and I am not able to install it. So thought that someone out there must be knowing something about it. Please tell me some steps that can be useful for installing MDT 2010. I am expecting some quick response from your side. :notworthy

I would like to tell all basic users that the installation of a Microsoft operating system is often seen as a series of wizard screen where the only user action is the "Next" button. But what we often forget it is the actions that are then produced and yet is considered as not part of this installation. These additional actions include:

• The installation of device drivers
• The installation of additional applications (such as Microsoft Office)
• The configuration of system settings (Computer name, Domain Name, Etc..)

Microsoft has long had in place solutions to automate these processes through solutions such as response files (unattend) or systems of the System Preparation (Sysprep). These solutions were more oriented toward the configuration of the operating system and not the extra additions. Often, companies have implemented systems "homes" for these additional configurations with varying degrees of success. The biggest problem is that there was no standardization in these solutions, which often had the effect that a person with these solutions had to be completely redone to fit the new systems for example.

MDT is based on many tools to work. But for simple there are few prerequisites:

• Pack WAIK, MDT 2010 uses the different elements of the WAIK (Windows Automated Installation Kit) This kit contains all the elements needed to generate an image WinPE (Windows Pre installation Environment). It is available as an ISO image containing all the necessary installation and the prerequisites for installing the WAIK as MSXML. Version compatible with Windows 7 (and older versions of Windows) is available on the Microsoft site.
• Microsoft Powershell, one of the new MDT 2010 is that it uses PowerShell. That is installable directly from the operating system (Windows Vista or later) or by download.

Of course in addition the source of MDT 2010, when it will be available in RTM, it will be downloadable on the page of TDS . For those wishing to use the RC version, it is necessary to register on the site connected to the beta test MDT 2010 for download. Armed with these prerequisites, you can start installations MDT 2010. :thumbup1: One last word, despite what some think, it is never necessary to install on a TDM-like operating system server. Indeed, it suffices for TDM to be installed on a system that allows file sharing, which is possible on any Windows.

Before the installation of MDT 2010, WAIK installation package is very simple, just run the installation from the iso (either by extracting the contents and by launching its installation file, either by mounting / burning the file ISO). The only option to install the WAIK is simply the choice of installation location. Then simply start the installation of MDT 2010, and as for the WAIK, you have little choice After that installation, your computer is ready to start configuring MTD 2010.

In fact, you actually Rigged scripting engines used by MDT; All mTnd actually based on a shared directory that will be accessed from your computer. This directory is called Call Distribution (Distribution Share). This directory will contain various items used by your installation as the operating system or install applications, for example. To generate your distribution share, you must first launch the console MTD. That is accessible from the menu in the Microsoft Deployment Toolkit, then you just start Deployment Workbench. To create your partition, simply select Deployment Share in the cartridge and then right click on the link New Deployment Share. Select a path for the location, the path must always be empty (but it must exist!). Moreover, it is strongly advised to put on a different partition than the system, allowing you to move more easily if it turns out that sharing becomes too large. It is strongly recommended to use a name deployment hidden to limit security risks, here we use the share name DeploymentShare $. The description name is used mainly for you if you start to use multiple deployment share. The next steps for the question posed by the program at the time of installation through MDT. The next option allows you to request the user to choose the password for the administrator account. In our case, we will seek systematically to allow for minimal customization. To recap, in a default installation of Windows Vista / 7 the administrator password is blank. However, this account is disabled by default (it is active only in safe mode).

After you completed the first step in configuring MTD must then complete sharing with your items. If you go directly into the corresponding directory (ie D:\DeploymentShare) you can see the directories that were created. These directories contain the following information:

• $ OEM $: This directory is used for some unattended installation (unattended) on the old operating systems (Windows XP/2003 for example)
• Applications: This directory contains the sources from installations of the applications you add to your installation.
• Boot: This directory contains the WinPE ISO and WIM images start, here it will get the boot CD to access the share from the desktop to install
• Screenshots: This directory is writable and will catch made by MTD
• Control: This directory contains all the configuration files used for your custom installation is primarily a set of XM file (hence the need to have MSXML installed on the computer)
• Operating Systems: It contains all the installation source operating systems that you have added to the DOT.
• Out-of-Box Drivers: Inside this directory are copied all the drivers added to DOT and used by your installation.
• Packages: This directory is used for storing the security patches and the language packs that you've added in the MDT.
• Scripts: This directory is the "core" implementation of MDT, it contains all the scripts executed during deployment.
• Tools: This directory contains additional tools (such as USMT) added to the DOT.
• USMT: This directory is not useful in our case. It is used to manage USMT (User State Migration Tool) which allows the retention of part or all user settings. As we are performing a clean installation of Windows, this case does not apply.