User's Manual

136 Known Issues and Frequently Asked Questions
• On PowerEdge 1950 and 2950 systems with internal USB, you can
configure BIOS settings for internal USB Port only if the
User
Accessible/external
(UA) USB ports are set to All Ports On . If the UA USB
ports are not set to
All Ports On and you try to configure BIOS setting for
the internal USB port using SYSCFG, the configuration will appear to be
successful but the changes will not take effect after the next reboot. If you
set the UA USB port from
All Ports On to All Ports Off or Only Back
Ports On
, the USB port will be automatically Set to Off during the next
reboot.
Windows PE Installation Issues
• If virtual flash is enabled and does not contain a valid image (for example,
if the virtual flash contains a corrupt or random image), you may not be
able to install Windows Server 2003 locally or remotely. To fix this issue,
install a valid image on virtual flash or disable virtual flash if it will not be
used during the installation procedure.
Frequently Asked Questions
The following questions are organized by DTK utility or other function.
General Deployment Questions
Q: While running SYSCFG.EXE on a Windows PE image, the
SYSCFG.EXE tool silently fails.
A: Ensure that you have built your Windows PE image with the /WMI option.
See "Running Deployment Scripts Using DTK and Microsoft Windows PE."
Q: When I use the sample DTK scripts to deploy multiple systems, do I need
to edit the configuration files to reflect unique information (such as unique
system names, IP address, and BIOS asset tags) for each system?
A: The sample scripts are provided as examples for users who want to develop
their own deployment process. You may find that the scripts work perfectly in
your environment, or you may need to develop your own scripts entirely from
scratch. If you are deploying multiple systems, for example, you will need to
provide unique information for each system when appropriate. To perform
this task, you will need to modify each .ini (or other configuration script) file
to reflect the unique information for each system you are deploying (such as