Installing a Configuration Manager console
The Configuration Manager console
is installed on the primary site server during setup, but you can
also install a child Configuration Manager console
on any remote computer that can connect to the primary server. For
example, you might install a secondary console on your own workstation.
Secondary consoles also require planning for prerequisites and other
considerations.
Verifying the success of the installation
Although you might often use the console to refer to the
following sources of information long after installing a Configuration Manager 2007
site, status messages and codes, log files, and state messages can
all point out a problem that might arise during installation.
Installing the IBM Deployment Pack on the site server
The IBM Deployment Pack installs
components into the site infrastructure and into the console. Interface
components are joined to the Admin console. Packages, programs, collections,
drivers, and reports are located within the site infrastructure, but
are not necessarily on the site server itself.
Installing the IBM Deployment Pack on a secondary console
You must install the IBM Deployment Pack for Microsoft System Center
Configuration Manager 2007, v1.0 on any secondary
site consoles where you intend to use the IBM Deployment Pack.
Performing post-setup configuration tasks
Several configuration tasks require careful planning. Although
some configuration tasks apply more to other features, you must configure Configuration Manager for the
Operating System Deployment feature.
Distributing Configuration Manager and deployment pack components
You must distribute the image packages and other packages
to distribution points before you can actively use any of the task
sequences that you create to deploy operating system images and packages
on IBM® servers.