Mitch Tulloch, MVP
bullet Welcome
bullet About Us
bullet Latest News
bullet Books and Articles
bullet Resource Kit
bullet Course Development
bullet Contact Us

  

 

 

 

....................................................Windows 7 Resource Kit
                                                        Unofficial Support Site

Win7 Reskit > Part 2: Deployment > Chapter 4: Planning Deployment

Frequently Asked Questions: Planning for deployment using MDT 2010

Q-4. We have Windows XP desktops and laptops which are configured to have multiple partitions(local hard drive) of various sizes. If, MDT 2010 is used to roll out windows 7 on these systems, will the Windows 7 checks and get installed only on the system partition leaving other drive partition intact?

A-4. If you perform a Refresh Computer deployment scenario using MDT then MDT will delete the files on the partition that contains the Operating System and leave the other partitions intact. If you perform a New Computer deployment however then all the partitions are deleted. So you should be OK if you follow the instructions for Refresh Computer in the MDT 2010 Documentation Library but be sure to test first.

Q-3. Can you use answer files created for Windows Vista to perform unattended installs of Windows 7?

A-3. Maybe. The platforms are very similar and their answer files use the same XML format, but some subtle differences may apply. To find out whether the answer file you created for Vista will work with Windows 7, open the answer file using Windows System Image Manager (Windows SIM) on a computer on which Windows Automated Installation Kit (Windows AIK) 2.0 has been installed and validate the answer file against the Windows 7 catalog. Any errors or warnings will be displayed in the messages pane of Windows 7. 

Q-2. If you have multiple deployment shares set up on your network using MDT 2010, is it possible to choose which one to use from the target computer at the beginning of a deployment?

A-2. Yes. Simply remove the DeployRoot line from the bootstrap.ini file of each of your deployment shares, and then update your deployment shares to regenerate the boot images. Now, when a target computer is started from a boot image, a dialog will be displayed asking you to type the UNC path to the deployment share you want to use. Alternatively, you can manually create a LocationServer.xml file that MDT can use to display a drop-down list of deployment shares on the target computer. For more information on LocationServer.xml file, see the topic titled "Selecting a Local Microsoft Deployment Toolkit Server When Multiple Servers Exist" in the MDT Documentation Library, which is installed as part of MDT 2010.

Q-1. How do you pre-configure the default user settings for users who will log on to a computer on which you are deploying Windows 7 using MDT 2010?

A-1. The only officially supported method for customizing the default user profile in Windows 7 is described in KB 973289, see http://support.microsoft.com/?id=973289.

There is also a helpful post on this topic by Stephen Rose on the Springboard Series blog, see http://tinyurl.com/yc9o7wl.

If you're using roaming profiles, you can find information on page 576 of our book on how to create a default network profile for your users.

Additional Resources: Planning for deployment using MDT 2010

See Michael Niehaus' Windows and Office deployment ramblings blog for a good introduction to the new features in MDT 2010. MIchael's posts on this topic begin with this one.

For interactive guidance on how to migrate Windows XP computers to Windows 7 see the Windows XP to Windows 7 Migration Guide on Microsoft TechNet.

Disclaimer: The Windows 7 Resource Kit Unofficial Support Site makes no representations concerning the accuracy, reliability or suitability of the information contained herein. All such information is presented "as is" with no warranties of any kind. Contact us if you have questions or feedback concerning this site.   
  
   

 Internet services courtesy of MTS Communications

© 2008 by Mitch Tulloch. All site content is presented "as is" with no warranties and confers no rights.