Topic last updated—November 2007
The Setup Prerequisite Checker is started automatically during Configuration Manager 2007 Setup and is used to verify that required installation prerequisites have been installed before beginning the setup process. You can also use the stand-alone version of the Setup Prerequisite Checker on site systems as a planning tool before beginning Configuration Manager 2007 Setup to ensure successful installation or upgrade processes.
The Setup Prerequisite Checker can be started automatically during Configuration Manager 2007 Setup or directly from the autorun splash screen (splash.hta) located in the root of the installation media. For more information about starting the Setup Prerequisite Checker, see How to Start the Setup Prerequisite Checker.
Using the Setup Prerequisite Checker
The Setup Prerequisite Checker can be used to verify that required setup prerequisites are installed using the following options:
- Primary site. This option is used to
verify that setup prerequisites are installed for new Configuration
Manager 2007 primary site installations. This option requires the
Microsoft SQL Server name, and the instance name if using a
named instance of SQL Server, that will be used to host the
site database. If a management point site system role will be
installed during Setup, a computer name for the computer that will
host the management point site system role can be entered to verify
- Secondary site. This option is used to
verify that setup prerequisites are installed for new secondary
- Configuration Manager console. This
option is used to verify that setup prerequisites are installed for
new Configuration Manager console installations.
If Systems Management Server (SMS) 2003 or Configuration Manager 2007 components are already installed, the Setup Prerequisite Checker can be used with the following options to verify that all required Setup prerequisites are installed before beginning the upgrade process:
- Upgrade. This option is used to verify
that setup prerequisites are installed for upgrading primary sites,
secondary sites, and SMS 2003 Administrator Consoles or
Configuration Manager consoles.
- All secondary sites. This option is
used to verify that upgrade prerequisites are installed on all
secondary sites attached to a primary site being upgraded.
Important When using the All secondary sites option and a failure is encountered when checking a secondary site for required prerequisites, all sites evaluated after the failed site will have a failed value stored in their registry and will be unable to upgrade successfully. If this happens, you can either remediate the failures for the sites that failed the prerequisite checking process and re-run the prerequisite checker to properly set all the registry keys or run the prerequisite checker locally on all secondary sites.