On Windows 32-bit
operating system, use the 32-bit installer. On Windows 64-bit operating system, you can
use either the 32-bit or the 64-bit installer.
Procedure
To install the OS deployment server:
- Log on as the local Administrator (or as a user with equivalent
privileges).
- Run the installation executable file. The installation
executable is a self-extracting archive. By default, it expands itself
in a temporary folder under c:\install\. This executable
file installs Tivoli® Provisioning Manager for OS Deployment. It
also performs basic OS configuration tasks
from the answers provided, such as setting the administrator name
and password.
Note: You cannot use National
Language Version (NLV) characters.
- Follow the setup wizard instructions. Some additional information
is available to help you answer the questions of the setup wizard:
- Language selection
- Language selection is valid for both the setup wizard and Tivoli Provisioning Manager for OS Deployment.
- Custom Setup
- Click Reset if you have deselected some
components and want to select them all again.
Click Disk
Usage to check that you have enough space on your disks
to install the product.
- Database configuration
- There are three main kinds of configurations:
- If the Microsoft Access
database provided by default (with the 32-bit installer) is applied,
there is nothing specific to do. However, if the account is not a
local service, some other parameters might be necessary (such as Database
account and Gateway account).
- If the OS deployment server is
configured to point to an SQL (trusted) database, the account from
the database Gateway (dbgw) is used for authorization. You must fill
in DBGW Account and DBGW Password.
- When the server points to an SQL (untrusted) database, you must
fill in the ODBC Database account parameters Username and Password.
- Data folder
- The default location for the data folder, also known as data
directory, is c:\TPMfOS Files\. To have the data
directory on a network driver disk use the OS deployment server silent
installation command line because it allows to specify the UNC path
of the data folder.
Note: You cannot use National Language
Version (NLV) characters.
- HTTP server console settings
- The default HTTP console port is 8080. The default
HTTPS console port is 443. The port parameters proposed
by default are standard and must be changed only if required.
- DHCP Server OS Configuration
- Installing Tivoli Provisioning Manager for OS Deployment and
a DHCP server on the same computer requires some parameters. If the
installer detects that a DHCP server is running, and that changes
in the OS configuration are
necessary, the panel is displayed. Selecting Yes in this dialog
allows the installer to perform all the changes described in DHCP server configuration.
Results
When the installation process ends, you must have the following
new items on your computer:
- A new service called IBM® Tivoli OS Deployment Server:
this is the main component of Tivoli Provisioning Manager for OS Deployment, that
offers the PXE remote-boot functionality. This service is automatically
started and stopped with the operating system.
- A new service called IBM Tivoli TCP to ODBC gateway:
this service allows Tivoli Provisioning Manager for OS Deployment targets to
use an ODBC source to retrieve their OS configuration and
store inventory information in a database. This service is automatically
started and stopped when the IBM Tivoli OS Deployment Server service
is started and stopped.
- A new service called IBM Tivoli web interface extension: this
service gives access to different OS components through the web interface of the Tivoli Provisioning Manager for OS Deployment. The web interface extension is automatically
started and stopped with the operating system.
- An ODBC source (System DSN) called AutoDeploy: this source
points to the database used by Tivoli Provisioning Manager for OS Deployment to
store information about the OS deployment process, operating system
and other software images and computer inventory. This was created
only if it did not exist before the installation.
- A new group called IBM Tivoli Provisioning Manager in
your start menu, with one icon for launching the web interface of the Tivoli Provisioning Manager for OS Deployment.
What to do next
When the installation is complete, you can start the web interface of the Tivoli Provisioning Manager for OS Deployment by
logging onto http://localhost:8080, where localhost is
the hostname of the computer. After logging in, go to Server
> Server status > Installation check on the web interface. It
provides you with a summary of errors encountered during the installation
process. If no errors were encountered during installation, you
see messages indicating that No significant event found in the
xxx file in the past 30 min.
If it is the first time
you are working with a OS deployment server,
click Check PXE boot to become more familiar with the concepts
behind Tivoli Provisioning Manager for OS Deployment.