Migration windows xp windows 7 using mdt

In other words, organizations sometimes discovered that the promised performance benefits of using bit Windows were not achieved. So where does this leave us today? Windows 7 has been released to manufacturing RTM and is already available for volume-licensed customers.

If your organization is currently running Windows XP on your client computers and you are eager to move forward with migrating your client computers to Windows 7, should you take the plunge and deploy only bit Windows 7 if the chipsets in all your systems support it?

My answer is a resounding YES and I suggest that there is virtually no reason any longer to prefer bit over bit Windows, provided you are going to deploy Windows 7 on x64 systems that are only a year or two old. Here is my short list of reasons why you should choose a bit Windows 7 edition over its corresponding bit edition:. MDT comes in two versions: x64 and x Both versions of MDT support deploying both x86 and x64 Windows operating systems.

And both versions of MDT require version 2. Windows AIK 2. On the other hand, if you are running bit version of Windows AIK 2. And you can not run the bit version of Windows AIK 2. Figure 3: Installing the Setup Support Files. Click Install to install the Setup Support files. Note that we get two warnings in this example.

First, installing SQL Server on a domain controller is not recommended, but it is actually fine to do this for a test environment like the one we are using here. And second, Windows Firewall is currently blocking remote computers from being able to access the SQL Server instance we are going to install—we will deal with this later in this article. Figure 5: Selecting features to install. On the Disk Space Requirements page, verify that the computer has sufficient disk space for the install Figure 7 :.

Figure 7: Disk Space Requirements page. Figure 8: Server Configuration page. For our test environment, we will use the same account for each SQL Server service. Since we are logged onto the computer using this account, you can add it to the list by clicking Add Current User. Leave the remaining settings as they are.

Accept the defaults on the Error and Usage Reporting page, then click Next to run the Installation Rules to determine whether the installation will succeed Figure 11 :. Figure The installation will succeed. Figure Verify installation options. Now click Install and view the progress of the installation. When the installation has finished, click Close to close the wizard. Then right-click on Named Pipes and select Enabled Figure 13 :. Enabling Named Pipes like this for SQL Server is needed so that the Deployment Workbench can connect to the database, and also to enable client computers to connect to the database.

The only way is to do a clean install. But what about users data? On the Select Template page go with the Standard Client Task Sequence , then on the next page select your operating system. Finish the wizard using the default settings.

If you need a more detailed guide on how to create a task sequence, follow this link. This is necessary, because the system will reboot, then start from a WinPE image. How to add drivers to MDT boot images, is showed in this guide. Here type the path of your Deployment Share. Open the Scripts folder and run the LiteTouch. This will launch the Windows Deployment Wizard. Select the Task Sequence tight to your Windows 7 image and click Next. In the first box, type a computer name if you want to change the existing one, then select if the Windows 7 future Windows 7 system will be part of the domain.

This is an important page, so you need to do this right, because user data is at stake. I recommend you use a file server for this operation, because the MDT machine will be busy enough deploying images. If you want to backup the Windows XP system before is wiped out, you can do this, again, locally or over the network.

The wizard will create a. WIM image from the current OS. If you want to enable BitLocker on the system, just select Enable BitLocker then choose where to store the recovery key. On the Ready to begin page click Details if you want to see all your selections, if not, just hit the Begin button to start the migration.

After all this, the system will be restarted and it will boot into a WinPE environment and start the deployment. OK, doing all this works better than copy and paste users data, and manually installing the Windows 7 system.

But for how long can you do this? Here I have one computer populated in the database. To create the rules right-click your Deployment Share and choose Properties. You will need to modify some of them to match your configuration and network.

Like the path where to save users data, the credentials used for joining machines to the domain Administrator in this case. Now right-click Database and choose Configure Database Rules.

On the Computer Options screen check only the first option, Query for computer-specific settings.