Manualshelf

Release Notes

ManualsBrandsDell ManualsActive System ManagerOpenManage Deployment Toolkit Version 5.0.2
123456
2) In grub config section, change /dev/sda5 to /dev/sda6
3) If installer reports any missing packages, delete the packages from autoinst.xml.
Instrumentation Issues
The "/opt/dell/srvadmin" directory in the DTK ISO image should be writable. It enables the
instrumentation services to work properly.
Installation Prerequisites
Before extracting Deployment Toolkit components, ensure that you have:
•
The DTK ISO image available at support.dell.com.
•
A workstation that has
•
512 MB RAM
•
A writable CD drive and CD-writing software (optional)
•
Network access
•
A minimum BIOS version is recommended on some of the platforms for all the DTK options to
work properly. In general, it is a good practice to use the latest ("n") version of BIOS firmware or
the "n-1" version that is available on "support.dell.com."
Installation Procedure
For complete installation and deployment instructions, see the "Dell OpenManage Deployment
Toolkit User's Guide."
Installation and Configuration Notes
•
The sample scripts are provided as examples for customers who want to develop their own
deployment process. Some customers may find that the scripts work well in their environment,
while some customers may need to develop their own scripts entirely from scratch. Customers
deploying multiple systems to provide unique information for each server when appropriate. For
example, system host names, IP addresses, and BIOS asset tags need to be unique for each
system. Modify the shell scripts and configuration files to reflect the unique information for each
system being deployed. Many options are available to optimize this process.
•
Because of security reasons, the "ssh" and "scp" services are not available in DTK. The mount
command is available in the DTK CD.
Upgrading From Previous Versions
When upgrading from a previous release of the DTK, ensure that you create environment for the
new DTK version separately from the previous version of DTK. This step is necessary because the
environments and requirements for the new DTK versions are completely different.