|
....................................................Windows 7 Resource
Kit
Unofficial Support Site
Win7 Reskit
> Part 2: Deployment > Chapter
12: Deploying with Microsoft Deployment Toolkit
Frequently Asked Questions: LTI deployment
using MDT 2010
Q-8. How do prevent users from
opening a WinPE command prompt during LTI install using MDT 2010?
A-8. MDT 2010 allows you to press F8
during the install process in order to open a WinPE command prompt
if this is needed. You might want to disable this functionality
however in a production deployment environment to prevent end-users
from accidentally interrupting installation.
To disable F8 keypress functionality
for MDT, use Notepad to open the unattend_pe_x86.xml and
unattend_pe_x64.xml files in the templates directory of your MDT
2010 installation and replace "/Bootstrap" with "/BootstrapNoSF8".
Q-7. How can I back up my Microsoft
Deployment Toolkit infrastructure?
A-7. Backups are important to ensure
business continuity. If you're using MDT 2010 to deploy Windows across
your organization, you should regularly back up your MDT infrastructure.
To accomplish this, do the following:
- Back up all your deployment shares.
- If you are using the MDT database,
back up the SQL Server or SQL Server Express database used by MDT.
Q-6. In a multi-site environment
where deployment shares are replicated, should I also replicate the MDT
database?
A-6. MDT 2010 supports the use of DFS
for replicating deployment shares between sites. But what about
replication the MDT database, which is typically either an SQL
Server Express database or a full SQL Server database, between
sites? Is this possible? And is it recommended?
Because the SQL query traffic for an
MDT deployment is typically very small, replicating the SQL Server
database between sites is not necessary. Instead, you should
maintain a single instance of the MDT database at corporate
headquarters and simply replicate the deployment share content out
to your branch office sites.
If you want a more robust multi-site
deployment platform however, consider using MDT 2010 together with
System Center Configuration Manager 2007 R2 which provides
additional capabilities not found in MDT alone.
Q-5. How can I suppress the Network
Location Wizard from being displayed when I use LTI to deploy Windows 7?
A-5. When you use MDT 2010 to deploy
Windows 7 to a target computer and automatically join the target
computer to the domain, the Network Location Wizard may be displayed
when the user first logs on to the computer. (Note that the Network
Location Wizard is not displayed if the target computer is
deployed into a workgroup however.) This wizard provides the user
with a choice between setting the default network location as either
Home, Work, or Public.If configuring the NetworkLocation setting in
your answer file does not allow you to prepopulate the network
location and thus prevent this wizard from being displayed, try
adding the following Run Command Line step at the start of the State
Restore group in your task sequence:
reg add
HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff
Adding this task sequence step will
create the following registry key on the target system:
HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff
The presence of this registry key on
the target computer will disable the Network Location Wizard for all
users on the computer.
Q-4. How can I configure a static
IP address using MDT 2010?
A-4. Add the following lines to your
CustomSettings.ini file and customize the address information in them as
required:
OSDAdapterCount=1
OSDAdapter0EnableDHCP=FALSE
OSDAdapter0IPAddressList=192.168.0.40
OSDAdapter0SubnetMask=255.255.255.0
OSDAdapter0Gateways=192.168.0.1
OSDAdapter0DNSSuffix=contoso.com
Q-3. How can I add desktop icons
such as Computer or Network to a target computer's desktop during
deployment?
A-3. Using Control Panel a user can add
desktop icons such as Computer or Network to the desktop of her
computer. But how do you add such icons to a target computer's desktop
during deployment using MDT 2010? To do this, simply add a task sequence
step to your task sequence that runs a reg import command imports the
following registry entries (.reg) file which you can name icons.reg if
you like:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\NewStartPanel]
"{59031a47-3f72-44a7-89c5-5595fe6b30ee}"=dword:00000000
"{20D04FE0-3AEA-1069-A2D8-08002B30309D}"=dword:00000000
"{208D2C60-3AEA-1069-A2D7-08002B30309D}"=dword:00000000
"{871C5380-42A0-1069-A2EA-08002B30309D}"=dword:00000000
The four icons specified in the .reg file
above are respectively as follows: User Account, Computer, Network, and
Internet Explorer. If you don't want all of these to appear on the
user's desktop, just remove the lines you don't need from the .reg file.
Q-2. I'm trying to deploy Windows
using MDT 2010 using LTI but the task sequence page of the wizard is
blank. Why?
A-2. Several things could cause this,
including:
- You have a USB flash drive plugged
into your technician computer and the flash drive has MDT files on
it.
- You have CD or DVD media in the
CD/DVD drive of your technician computer and the media has MDT files
on it.
- You have mis-specified the
DeployRoot variable in your bootstrap.ini file.
Q-1. You have several task sequences
created in your deployment share and they are visible in the Deployment
Workbench. However, when you boot a target computer using a LTI boot
image and walk through the pages of the Windows Deployment Wizard, the
Select A Task Sequence To Execute On This Computer wizard page has no
task sequences displayed on it. What could be wrong?
A-1. Possible reasons for this happening are
as follows:
- The value of DeployRoot is incorrect
or cannot be found on the network.
- You are booting the target computer
using an LTI boot image of one architecture (e.g. x86) while your
task sequences are configured for deploying Windows of a different
architecture (e.g. x64).
- You have DVD or USB media with MDT
deployment files on it inserted into the target computer.
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.
|
