Users Guide

9
Known issues and frequently asked questions
This section describes known issues with the Deployment Toolkit (DTK) utilities and scripts, including answers to some frequently
asked questions.
Known issues
The following issues are organized by DTK utility or other function.
General issues
• Virtual disk creation and/or deletion takes a long time on Microsoft Windows PE.
RAIDCFG issues
• Due to a rounding limitation for RAID 0, RAID 1, and RAID 5, when creating a virtual disk, RAIDCFG can accept a disk size that is 1
MB greater than the maximum allowable virtual disk size limit. However, RAIDCFG creates the maximum virtual disk size and
does not display an error. If you want to use the maximum allowable virtual disk size, it is recommended that you do not provide
the size in the CLI and let RAIDCFG calculate the size for the RAID type.
Windows PE installation issues
• If virtual ash is enabled and does not contain a valid image (for example, if the virtual ash contains a corrupt or random image),
you may not be able to install Windows Server 2008 locally or remotely. To x this issue, install a valid image on virtual ash or
disable virtual ash if it is not used during the installation procedure.
Embedded Linux installation issues
• If internal SD card is present in the server, you may not be able to install the operating system using default partition. To x this,
remove the SD card from the server.
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. For more details, see Running The Deployment Scripts.
Q: When I use the sample DTK scripts to deploy multiple systems, do I edit the conguration les to reect 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. The scripts may work
perfectly in your environment. If not, you may need to develop your own scripts entirely from scratch. If you are deploying multiple
systems, for example, provide unique information for each system when appropriate. To perform this task, modify each .ini (or other
conguration script) le to reect the unique information for each system you are deploying (such as the remote access controller
(RAC) IP addresses and BIOS asset tags). There are many options available to optimize this process and it is suggested that you
conduct an Internet search for available tools.
61