<a href="http://technet.microsoft.com/en-us/library/bb680951(TechNet.10).aspx">URL:[url]http://technet.microsoft.com/en-us/library/bb680951[/url](TechNet.10).aspx</a>
Setup Prerequisite Checks
[Topics referencing Configuration Manager 2007 R2 are pre-release documentation and are subject to change in future releases.]
<b>Topic last updated—May 2008</b>
The Configuration Manager 2007 setup prerequisite check helps you determine what you have to do in order to prepare your environment to install or upgrade a Configuration Manager 2007 primary site, secondary site, or Configuration Manager console. The prerequisite checker notifies you of any warnings or errors encountered that would cause setup or an upgrade to fail. Tests that result in a warning do not prevent you from successfully upgrading to Configuration Manager 2007. However, it is recommended that you resolve the condition that generated the warning before continuing the setup or upgrade process. Tests that result in an error do prevent you from continuing the setup or upgrade process. You must resolve the condition that generated the error before continuing Configuration Manager 2007 Setup.
Setup will make no changes to your system until after the prerequisite check process has successfully completed. If necessary, you can temporarily leave the setup process to correct prerequisite warnings and errors after the check has completed. Once any error conditions have been resolved, you can return to, and re-run, the prerequisite check process. Until all errors have been resolved, you will not be able to proceed with setup.
Note
The Configuration Manager Setup prerequisite check rules verify that software and settings required for setup are installed. In some cases, the required software itself may require additional software updates not verified by Configuration Manager Setup. Before beginning setup, you should ensure that the computer operating system, and additional installed software components Configuration Manager Setup relies on, have been updated with all relevant software updates.
The prerequisite check rule name, severity, description and details for each Configuration Manager 2007 Setup prerequisite check rule are listed in the following table.
Depending on the type of installation or upgrade being performed by Configuration Manager Setup, you may or may not see all tests listed in the table.
<b>Prerequisite Check Rule</b>
<b>Severity</b>
<b>Rule Description</b>
<b>Rule Details</b>
Administrative rights
(Management point)
Failure
Verifies that the logged on user and site server computer accounts possess administrative rights on the management point computer.
Configuration Manager Setup requires that the logged on user and site server computer account possess administrative rights on the management point computer.
(Site system)
Verifies that the logged on user possesses administrative rights on the site system computer.
Configuration Manager Setup requires that the logged on user possess administrative rights on the site server computer.
(SQL Server)
Verifies that the logged on user and site server computer account possess administrative rights to the SQL Server computer.
Configuration Manager Setup requires that the logged on user and site server computer possess administrative rights to the SQL Server computer.
If installing the site database on a SQL Server cluster instance, the logged on user and site server machine account require administrative rights to all SQL Server cluster instance node computers
Administrative shares
Verifies that the required administrative shares are present on the site system computer.
Configuration Manager Setup requires that the Admin$ administrative share is present on the site system.
Backlogged inboxes
Warning
Verifies that the site server is processing critical inboxes in a timely fashion, and that inboxes do not contain files older than one day.
To ensure that data is not lost during the upgrade process, critical inboxes should be performing as expected and have no backlogged files waiting to be processed. If this test does not pass, this could indicate that a component has stopped, has stopped processing data, or is unable to keep up with incoming traffic.
Child Sites
(Pre-SMS 2003 SP2 direct child sites)
Verifies that the site server to be upgraded and all of its direct child sites are running SMS 2003 SP2 or later.
SMS site servers to be upgraded, and all direct child sites of Configuration Manager primary sites must be running SMS 2003 SP2 or later.
(Pre-SMS 2003 SP2 indirect child sites)
Verifies that all the sites below the direct child sites of the site to be upgraded are running SMS 2003 SP2 or later.
SMS site servers to be upgraded, and all indirect child sites of Configuration Manager primary sites should be running SMS 2003 SP2 or later.
Client activity
Verifies that all clients assigned to the site to be upgraded have recently communicated successfully with their assigned management point.
Inactive clients cannot be managed by Configuration Manager. Inactive client records should be removed from the site database before continuing the upgrade process.
Client Duplicate IDs
Verifies that the Configuration Manager 2007 site database to be upgraded does not contain duplicate client IDs.
Duplicate client IDs can cause unexpected results in collection evaluation and software distribution to clients. Duplicate client IDs should be resolved before continuing the upgrade process.
Client GUID consistency
Verifies that the Configuration Manager 2007 site database to be upgraded does not contain inconsistent client GUIDs.
Inconsistent client GUIDs can lead to SQL Server errors and should be resolved before continuing the upgrade process.
Client version
Verifies that there are no SMS 2003 Legacy Client records existing in the site database before upgrade.
Configuration Manager hierarchies do not support SMS 2003 Legacy Clients. Any existing Legacy Clients in the site to be upgraded should be upgraded to the SMS 2003 Advanced Client before continuing the upgrade process.
Distribution point package version
Verifies that all distribution points in the site have the latest version of software distribution packages.
All distribution points in the site to be upgraded should have the latest version of software distribution packages before beginning the upgrade process.
Domain membership
Verifies that the computer specified for installation is a member of a Windows domain.
Configuration Manager site server components can only be installed on computers that are members of a Windows domain.
FAT Drive on Site Server
Checks for the existence of a FAT drive on the Configuration Manager 2007 Site Server computer.
Installing Configuration Manager components on FAT formatted disk drives does not provide the recommended level of security for site server installations. It is recommended that you only install site server components on NTFS formatted disk drives.
Hardware inventory group map
Verifies that the hardware inventory definitions for the site to be upgraded have not been extended in a way that will conflict with the default inventory definitions for Configuration Manager.
Some custom hardware inventory modifications may conflict with the default hardware inventory settings provided by Configuration Manager. If there are conflicting hardware inventory settings, they should be resolved before continuing with the upgrade process.
IIS Configuration
(BITS installed)
Verifies that Background Intelligent Transfer Service (BITS) is installed in Internet Information Services (IIS).
Background Intelligent Transfer Service (BITS) is required for the management point and BITS-enabled distribution point site system roles.
(BITS enabled)
Verifies that Background Intelligent Transfer Service (BITS) is enabled in Internet Information Services (IIS).
(IIS service running)
Verifies that Internet Information Services (IIS) is running.
Internet Information Services (IIS) is required for some site system roles. If you have selected to install a site system role requiring IIS, and the IIS service is not running, this rule will fail.
(WebDAV installed)
Verifies that Web-based Distributed Authoring and Versioning (WebDAV) is installed.
Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not installed, this rule will fail.
(WebDAV enabled)
Verifies that Web-based Distributed Authoring and Versioning (WebDAV) is enabled.
Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not enabled, this rule will fail.
(WWW Service installed)
Verifies that the World Wide Web (WWW) Publishing Service is installed.
The WWW Service is a core component of IIS and is required to allow Configuration Manager clients to communicate with management points and BITS-enabled distribution points.
Management Point NLB Configuration
Verifies that the management point is not configured as part of a Network Load Balancing (NLB) cluster.
To enable Configuration Manager client approval when the default management point is configured as an NLB cluster, a Service Principal Name (SPN) must be registered in Active Directory Domain Services to enable Kerberos authentication.
Microsoft Management Console (MMC) version
Verifies that Microsoft Management Console (MMC) version 3.0 or later is installed.
Microsoft XML Core Services 6.0 (MSXML60)
Verifies that the Microsoft Core XML Services (MSXML) version 6.0 or later libraries are installed.
MSXML 6.0 or later libraries are required for Configuration Manager console and site server installations.
Minimum .NET Framework version
Verifies that the Microsoft .NET Framework version 2.0 or later is installed.
Schema extensions
Determines if the Active Directory Domain Services schema has been extended, and if extended, what version of the schema extensions were used to extend it.
Configuration Manager Active Directory schema extensions are not required, for site server installation, but are recommended to fully support the use of all Configuration Manager features.
Secure key exchange
Verifies that the site to be upgraded is configured to require secure key exchange.
By default, Configuration Manager sites require secure key exchange. It is recommended that you enable secure key exchange on sites to be upgraded before beginning the upgrade process.
Security rights
(Class Security Rights)
Verifies that any of the user names specified for Class Security Rights are less than 350 bytes long.
Class Security Rights user names must be less than 350 bytes long for a primary site upgrade to succeed.
(Instance Security Rights)
Verifies that any of the user names specified for Instance Security Rights are less than 350 bytes long.
Instance Security Rights user names must be less than 350 bytes long for a primary site upgrade to succeed.
Short file name (8.3) support
Verifies that short file name support (8.3) is enabled on the site system computer.
Configuration Manager Setup requires that short file name (8.3) support is enabled on site system computers.
Site control file processing backlog
Verifies that site control file changes are being processed in a timely fashion.
To ensure that data is not lost during the upgrade process, site control file changes should be being processed in a timely fashion. If this test does not pass, it could indicate that a component has stopped, has stopped processing data, or is unable to keep up with incoming traffic.
Site security mode
Verifies that the SMS 2003 site to be upgraded, and all of its direct child sites, is configured for advanced security.
Configuration Manager sites have only one security mode. That mode is equivalent to SMS 2003 advanced security mode. All SMS 2003 sites to be upgraded should be functioning in advanced security mode before beginning the upgrade process.
SMS 2003 Feature Packs (Inventory Tool for Custom Updates)
Verifies that the SMS 2003 Inventory Tool for Custom Updates Feature Pack is not installed.
All SMS 2003 feature packs must be uninstalled before upgrading SMS 2003 sites to Configuration Manager.
SMS 2003 Feature Packs (Inventory Tool for Dell Updates)
Verifies that the SMS 2003 Inventory Tool for Dell Updates Feature Pack is not installed.
SMS 2003 Feature Packs (SMS Inventory Tool for HP ProLiant and Integrity)
Verifies that the SMS 2003 SMS Inventory Tool for HP ProLiant and Integrity Feature Pack is not installed.
SMS 2003 Feature Packs (IBM Systems Update Tool for Microsoft SMS)
Verifies that the SMS 2003 IBM Systems Update Tool for Microsoft SMS Feature Pack is not installed.
SMS 2003 Feature Packs (Operating System Deployment)
Verifies that the SMS 2003 Operating System Deployment Feature Pack is not installed.
SMS 2003 Feature Packs (SMS Device Management)
Verifies that the SMS 2003 SMS Device Management Feature Pack is not installed.
Software distribution package hash
Verifies that the hash value for software distribution package files is not blank or MD5 which is no longer supported
Configuration Manager clients will not download and run package files that are not properly signed. If this rule does not pass, you should update distribution points that host affected package source files to create or update the package security hash before proceeding with the upgrade process.
Software updates
(KB911897)
Verifies that the software update associated with KB911897 has been installed.
You do not have to restart the computer after you apply this update.
(KB913538)
Verifies that the software update associated with KB913538 has been installed.
You must restart the computer after you apply this update.
(KB914389)
Verifies that the software update associated with KB914389 has been installed.
(KB925335)
Verifies that the software update associated with KB925335 has been installed.
(KB925903)
Verifies that the software update associated with KB925903 has been installed.
(KB932303)
Verifies that the software update associated with KB932303 has been installed.
The WMI service may stop responding on Configuration Manager site systems with the .NET 2.0 framework installed. This update should only be applied to computers experiencing a specific error and is available by contacting Microsoft Online Customer Services. More information about this update is available at:
<a href="http://go.microsoft.com/fwlink/?LinkId=93927">[url]http://go.microsoft.com/fwlink/?LinkId=93927[/url]</a>
(KB940848)
Verifies that the software update associated with KB940848 has been installed.
(KB941132)
Verifies that the software update associated with KB941132 has been installed.
SQL Server
(Database collation)
Verifies that the SQL Server database collation settings of the tempdb database and site database to be upgraded are the same.
Configuration Manager requires that the SQL Server database collation settings of the tempdb database and site database are the same for daily site database operations.
(Replication objects)
Verifies that the site database is not configured for replication and checks for replicated objects in the database.
Site databases cannot be upgraded when they are configured for replication. Before beginning the upgrade process, you should disable SQL Server replication if it is enabled.
(Security mode)
Verifies that SQL Server is configured for Windows authentication security.
It is recommended to configure the SQL Server that will host the Configuration Manager site database to operate using Windows authentication security.
(SQL Server version)
Verifies that the version of Microsoft SQL Server installed on the computer selected to host the site database meets the minimum requirement of SQL Server 2005 SP2.
Configuration Manager sites require SQL Server 2005 SP2 for site database operations to succeed.
SQL Server (Sysadmin rights)
Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions on the SQL Server instance targeted for site database installation. SOL Server sysadmin role permissions are required in order to create the site database and configure necessary database role and login permissions for Configuration Manager sites.
A SQL Server best practice is to remove the Builtin\Administrators group from the sysadmin role on installed SQL Server instances. If the Builtin\Administrators group has been removed from the sysadmin role, the user account running Configuration Manager Setup must be granted sysadmin role permissions for setup to succeed.
Unsupported client operating system version
Verifies that all of the clients assigned to the site to be upgraded meet the minimum operating system requirement of Windows 2000 Professional SP4 or later.
Configuration Manager clients are only supported on Windows 2000 SP4 or later operating systems.
Unsupported Configuration Manager console operating system
Verifies that the computer specified for Configuration Manager console installation is running at least Windows XP Professional SP2.
Configuration Manager consoles can only be installed on systems running Windows XP Professional SP2 or later.
Unsupported site server operating system version for setup
Verifies that the site server operating system meets the minimum requirement of Windows Server 2003 SP1 for site server installation.
Configuration Manager site systems can only be installed on systems running Windows Server 2003 SP1 or later.
Unsupported site server operating system version for upgrade
Verifies that the site server to be upgraded meets the minimum operating system requirement of Windows Server 2003 SP1 for site server installation.
Unsupported SMS database version
Verifies that the site database version to be upgraded is at least SMS 2003 SP2.
For the site database upgrade to succeed, the database version must be SMS 2003 SP2 or later.
WSUS client installation package version
Verifies that the client installation package version published to WSUS is correct.
This prerequisite check rule is not run during Configuration Manager 2007 SP1 Setup.
WSUS SDK on site server
Determines if the Windows Server Update Services (WSUS) administrator console is installed on the site server.
Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 or later.
The prerequisite check rule name, severity, description, and details for additional setup prerequisite checks included in Configuration Manager 2007 SP1 Setup are listed in the following table.
Prerequisite Check Rule
Severity
Rule Description
Rule Details
SMS Provider communication
Verifies that the SMS Provider computer can communicate successfully with the site database computer.
Installed version of WAIK
Verifies that the correct version of the Windows Automated Installation Kit (WAIK) is installed on the SMS Provider computer for the site.
WSUS 3.0 SP1 SDK installed on site server
Verifies that the Windows Server Update Services (WSUS) administrator console installed on the site server is at the WSUS 3.0 SP1 level.
FQDN specified for site systems
Verifies that an FQDN is specified for site systems during site upgrade to Configuration Manager 2007 SP1.
During site upgrades to Configuration Manager 2007 SP1, installed site systems are checked to ensure that an FQDN has been specified. Not specifying an FQDN for site systems in mixed mode sites might prevent cross-domain client auto approval processes. When mixed mode sites are migrated to native mode, not specifying FQDN for site systems might cause client to management point communication errors.
Windows Server 2003–based schannel hotfix
Determines if the Windows Server 2003–based schannel hotfix is installed on the site server.
Windows Remote Management (WinRM) v1.1
Verifies that Windows Remote Management (WinRM) version 1.1 or later is installed.
You do not need to restart the computer after you apply this update unless it is applied to a Windows Server 2003 R2 computer.
Microsoft Remote Differential Compression (RDC) library registered
Error
Verifies that the Microsoft Remote Differential Compression (RDC) library is registered on the computer specified for Configuration Manager site server installation.
Share Name in Package
Verifies that the <b>#</b> character has not been used in software distribution package share names.
The <b>#</b> character is not a valid character for software distribution package share names and is not supported as a virtual directory share name character by IIS 7.0 included with Windows Server 2008.
Share Name in Distribution Point
Verifies that the <b>#</b> character has not been used in software distribution point share names.
The <b>#</b> character is not a valid character for software distribution point share names and is not supported as a virtual directory share name character by IIS 7.0 included with Windows Server 2008.
<a href="http://technet.microsoft.com/en-us/library/bb694113(TechNet.10).aspx">Prerequisites for Installing Configuration Manager</a>
<a href="http://technet.microsoft.com/en-us/library/bb681060(TechNet.10).aspx">How to Start the Setup Prerequisite Checker</a>
<a href="http://technet.microsoft.com/en-us/library/bb693622(TechNet.10).aspx">Configuration Manager 2007 Upgrade Checklist</a>
![SQL優化SQL語句優化的目的[圖]](data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=)