Installation considerations – Lenovo ThinkVantage ImageUltra Builder Version 5.0 User Manual

Page 63

Advertising
background image

Installation considerations

Consider the following information when installing the ImageUltra Builder
program.

The ImageUltra server installs Cloudscape V10.0, a relational database program
that is written entirely in Java

and is supported on any certified Java Virtual

Machine (JVM). Running Cloudscape requires a certified JVM and at least 4MB of
available memory.

The repository can be installed on the following computers:

v

ImageUltra Builder server

v

ImageUltra Builder console

v

Shared disk of another computer (where the server or console program is
installed)

v

The computer intended to be used as both the console and server computer.

Notes:

1.

Additional storage is required for repositories. Make sure that you have enough
storage for future growth.

2.

The repository must be accessible to the ImageUltra console, the source
computer for import operations, and any target computer that will have a
Smart Image deployed over the network.

v

When building driver modules, use only certified Microsoft WHQL device
drivers. Device drivers must have an INF file extension to install correctly.
Building modules with unsigned device drivers might cause Windows to display
information messages during installation, thereby preventing an image from
installing in an unattended manner.

v

Research compatibility between operating systems and versions of Symantec
Norton Ghost, Symantec DeployCenter, and Microsoft ImageX before you begin
creating Portable-Sysprep Images or Hardware-Specific Images.

v

If you intend to use stand-alone Distribution Media or Network Deployment Media,
the ImageUltra Builder program can create CDs, DVDs, USB Keys, and USB
hard disk drives (hard disk drives).

v

One repository is sufficient for most environments, you can create additional
repositories using the New Repository Wizard. Before creating multiple
repositories, it is a good idea to develop a repository strategy. Consider the
following:
– When you create a new repository, make sure you assign it a unique ID that

has not been used for any other repository in your company. If you have
duplicate IDs, and import modules from a source computer that has a Smart
Image that was deployed from a different repository, there is a chance that
modules can get overwritten.

– All modules defined in a map must be in the same repository as the map.
– The driver map and base map used for deployment must be in the same

repository.

v

Consider using a separate server to back up your module repository.

v

It is possible to create an image that contains modules that collide, or fail to
interact correctly.
For example, an image that contains two antivirus program modules might not
install correctly. As a result, the image might not work. One way to prevent the

Chapter 4. Installing the ImageUltra Builder program

49

Advertising