SMS 2003 Deployment Readiness Wizard Overview

  • Article

This document supplements the Deployment Readiness Wizard (DRW) for Systems Management Server (SMS). The DRW helps you determine what you have to do to prepare your existing SMS site hierarchy for an upgrade to SMS 2003, SMS 2003 Service Pack 1 (SP1) or SMS 2003 Service Pack 2 (SP2). If you are upgrading from SMS 2.0 to SMS 2003, run the version of DRW that is included on the SMS 2003 CD. If you are upgrading from SMS 2.0 or SMS 2003 to SMS 2003 SP1, run the version of DRW that is included on the SMS 2003 SP1 CD. If you are upgrading from SMS 2003 or SMS 2003 SP1 to SMS 2003 SP2, run the version of DRW that is included on the SMS 2003 SP2 CD.

The DRW runs predesigned tests and it notifies you of any warnings and errors that it encounters that would cause the upgrade to fail. Tests that result in a warning do not prevent you from successfully upgrading your SMS site. However, it is recommended that you resolve the condition that generated the warning before you upgrade the SMS site. Tests that result in an error do prevent you from upgrading the SMS site. You must resolve the condition that generated the error before you can upgrade the SMS site. This document describes the steps you can take to resolve a warning or error so you can upgrade successfully.

Deployment Readiness Wizard Tests

The following table lists the tests that DRW runs, the type of failure that the test generates, and information about the test and how to resolve the warning or error. Note that some tests are only run when you are upgrading from SMS 2.0 to SMS 2003. These are identified in the Test Name column of each table with the text SMS 2003 specific test. Some tests are only ** run when you are upgrading from SMS 2.0 or SMS 2003 to SMS 2003 SP1. These are identified in the Test Name column of each table with the text SMS 2003 SP1 specific test. Some tests are only run when you are upgrading from SMS 2003 RTM or SMS 2003 SP1 to SMS 2003 SP2. These are identified in the Test Name column of each table with the text SMS 2003 SP2 specific test.

Test name

Information

Failure type

Alpha processor clients

Verifies that no alpha-based client operating systems exist in the SMS site.

For this test to pass, you must enable and collect hardware inventory because that contains the operating system data. This test issues a warning if there is no operating system data in the database for a client assigned to the site, or if the operating system indicates an alpha processor. If the processor field in the report is blank, the test interprets that there is no operating system data and issues a warning. If you do have clients running on an alpha-based processor, you must uninstall the SMS client from each client in your hierarchy that is running on an alpha-based computer for the test to pass. SMS 2003 does not support alpha-based client operating systems.

For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide.

Warning

IPX site boundaries

Verifies that there are no IPX site boundaries configured.

For this test to pass, remove any site boundaries defined as IPX addresses within the site where you are running DRW. SMS 2003 does not support IPX site boundaries.

Warning

Non-TCP/IP clients

Verifies that all clients use TCP/IP.

For this test to pass, you must configure TCP/IP addresses for all computers that will be SMS 2003 clients. SMS 2003 clients require TCP/IP.

Warning

NetWare server site systems

Verifies that there are no site system servers running Novell NetWare.

For this test to pass you must remove NetWare from existing computers so that they can support SMS 2003. Alternatively, you can remove the SMS site system role from the NetWare servers. It is recommended that you identify one or more servers running a Windows operating system to assume the role currently being played by the NetWare servers. NetWare is unsupported for SMS 2003 site servers and site server roles.

Error

Secure client configuration

SMS 2003 specific test

Identifies those computers in the SMS site that are running Windows 2000 or later that have the SMS 2.0 client installed.

When you upgrade the site, SMS 2003 installs the Legacy Client on these computers. However, the recommended client for computers running Windows 2000 or later is the Advanced Client. The Legacy Client runs and is supported on Windows 2000 or later, but it is intended solely to assist with the migration to the preferred Advanced Client on these platforms. You should upgrade these computers to the Advanced Client as soon as possible.

You can use the web report and query Computers recommended for Advanced Client upgrade to easily identify these computers and deploy the Advanced Client to them. Note that when you upgrade to SMS 2003 SP1, Microsoft no longer supports the Legacy Client on computers running the Windows 2000 or later operating system.

Warning

Secure client configuration for SMS 2.0 client

SMS 2003 SP1 specific test

Identifies those computers in the SMS site that are running Windows 2000 or later that have the SMS 2.0 client installed.

When you upgrade the site, SMS 2003 will not install the Legacy Client on these computers. The recommended client for computers running Windows 2000 or later is the Advanced Client. You should upgrade these computers to the Advanced Client as soon as possible.

You can use the web report and query Computers recommended for Advanced Client upgrade to easily identify these computers and deploy the Advanced Client to them. Note that when you upgrade to SMS 2003 SP1, Microsoft no longer supports the Legacy Client on computers running the Windows 2000 or later operating system.

Warning

Secure client configuration for SMS 2003 Legacy Client

SMS 2003 SP1 specific test

Identifies those computers in the SMS site that are running Windows 2000 SP2 or later that have the SMS 2003 Legacy Client installed, and those clients for which no hardware inventory has been reported.

SMS 2003 SP1 does not support the Legacy Client on computers running Windows 2000 or later. When you upgrade your SMS site from SMS 2.0 or SMS 2003 to SMS 2003 SP1, Legacy Clients on computers running Windows 2000 or later are not automatically upgraded to SMS 2003 SP1 Advanced Client.

You can upgrade to or replace these SMS 2003 Legacy Clients with the SMS 2003 SP1 Advanced Client before you upgrade the site to SMS 2003 SP1 by ensuring that a management point is available and then using software distribution. SMS 2003 SP1 Advanced Clients are compatible with SMS 2003 sites.

Warning

Pre-Windows 2000 SP2 site systems

SMS 2003 specific test

Verifies that all site systems are running Windows 2000 SP2 or later. SMS 2003 site systems require Windows 2000 SP2 or later. For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

For this test to pass you must upgrade the site systems running operating systems earlier than Windows 2000 SP2 to Windows 2000 SP2 or later. If you know that the site systems are running Windows 2000 SP2 or later, you can ignore the warning message. DRW runs under the logged-in user account. This test connects to the registry on every site system of the site being tested in order to read the operating system version. If there are site systems in different domains, it is possible that no single account has rights to all of them. This prevents the test from passing because there could be some site systems that cannot be contacted.

This test generates a warning message if the site system is earlier than Windows 2000 SP2, or if the site system cannot be contacted. A site system running an operating system that is earlier than Windows 2000 SP2 site system does not prevent upgrade or cause upgrade to fail. However, Site Component Manager cannot upgrade those site systems to SMS 2003 after the upgrade is completed until they are running Windows 2000 SP2 or later.

If your site systems are not currently running Windows 2000, you must purchase Windows 2000 and upgrade the site systems’ operating systems before you can upgrade to SMS 2003.

If your site systems are currently running a version of Windows 2000 earlier than SP2, you can get information about downloading Windows 2000 service packs at https://www.microsoft.com/windows2000/downloads/servicepacks

Warning

Pre-Windows 2000 SP3 site systems

SMS 2003 SP1 specific test

Verifies that all site systems are running Windows 2000 SP3 or later. SMS 2003 SP1 site systems require Windows 2000 SP3 or later. Site Component Manager will not be able to upgrade the CAP if it is installed on a computer running a pre-Windows 2000 SP2 operating system. For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

For this test to pass you must upgrade the site systems running operating systems earlier than Windows 2000 SP3 to Windows 2000 SP3 or later. If you know that the site systems are running Windows 2000 SP3 or later, you can ignore the warning message. DRW runs under the logged-in user account. This test connects to the registry on every site system of the site being tested in order to read the operating system version. If there are site systems in different domains, it is possible that no single account has rights to all of them. This prevents the test from passing because there could be some site systems that cannot be contacted.

This test generates a warning message if the SMS 2003 SP1 site system is earlier than Windows 2000 SP3, or if the site system cannot be contacted. A site system running an operating system that is earlier than Windows 2000 SP3 does not prevent upgrade or cause upgrade to fail. However, Site Component Manager cannot upgrade those site systems to SMS 2003 after the upgrade is completed until they are running Windows 2000 SP2 or later. Although SMS 2003 SP1 does not support site systems running an operating system earlier than Windows 2000 SP3, the upgrade of a site system fails only if that site system is running an operating system earlier than Windows 2000 SP2.

If your site systems are currently running a version of Windows 2000 earlier than SP3, you can get information about downloading Windows 2000 service packs at https://www.microsoft.com/windows2000/downloads/servicepacks.

Warning

Unsupported client operating systems

SMS 2003 specific test

Verifies that none of the clients assigned to the site are running an unsupported operating system. Unsupported client operating systems include: Windows 3.1, Windows for Workgroups 3.11, Windows NT 3.51, Windows NT 4.0 without SP6, Windows 95, Windows Millennium Edition, Windows XP Home Edition, or any operating system with Internet Explorer 4 or earlier.

For this test to pass, you can do one of the following:

Uninstall the SMS 2.0 client from those computers running operating systems unsupported by SMS 2003 and remove those client records from the SMS site database.

Upgrade the operating systems of the computers running unsupported operating systems to operating systems supported by SMS 2003. For more information about which client operating systems are supported by SMS 2003, see the “Getting Started” section in the Systems Management Server 2003 Concepts, Planning and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Alternatively, if you ignore this warning, and upgrade to SMS 2003, the computers running SMS 2.0 will either uninstall, or if they are also assigned to an SMS 2.0 site that will not be upgraded to SMS 2003, they will stop being assigned to the current site and remain assigned to the SMS 2.0 site. For more information, see Chapter 6 “Understanding Interoperability with SMS 2.0” and Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment available at https://www.microsoft.com/smserver/techinfo/productdoc.

  

Unsupported client operating systems for SMS 2003

SMS 2003 SP1 specific test

Verifies that none of the clients assigned to the site are running an unsupported operating system. Unsupported client operating systems include: Windows 3.1, Windows for Workgroups 3.11, Windows NT 3.51, Windows NT 4.0 without SP6, Windows 95, Windows Millennium Edition, Windows XP Home Edition, or any operating system with Internet Explorer 4 or earlier.

For this test to pass, you can do one of the following:

Uninstall the SMS 2.0 client from those computers running operating systems unsupported by SMS 2003 and remove those client records from the SMS site database.

Upgrade the operating systems of the computers running unsupported operating systems to operating systems supported by SMS 2003. For more information about which client operating systems are supported by SMS 2003, see the “Getting Started” section in the Systems Management Server 2003 Concepts, Planning and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Alternatively, if you ignore this warning, and upgrade to SMS 2003, the computers running SMS 2.0 will either uninstall, or if they are also assigned to an SMS 2.0 site that will not be upgraded to SMS 2003, they will stop being assigned to the current site and remain assigned to the SMS 2.0 site. For more information, see Chapter 6 “Understanding Interoperability with SMS 2.0” and Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment available at https://www.microsoft.com/smserver/techinfo/productdoc.

Warning

Unsupported client operating systems for SMS 2003 service pack1

SMS 2003 SP1 specific test

Verifies that none of the clients assigned to the site are running an unsupported operating system. Unsupported client operating systems include: Windows 3.1, Windows for Workgroups 3.11, Windows NT 3.51, Windows NT 4.0 without SP6, Windows 95, Windows Millennium Edition, Windows XP Home Edition, Windows 2000 SP1 or earlier, or any operating system with Internet Explorer 4 or earlier.

For this test to pass, you can do one of the following:

Uninstall the SMS 2.0 client from those computers running operating systems unsupported by SMS 2003 and remove those client records from the SMS site database.

Upgrade the operating systems of the computers running unsupported operating systems to operating systems supported by SMS 2003. For more information about which client operating systems are supported by SMS 2003, see the “Getting Started” section in the Systems Management Server 2003 Concepts, Planning and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Note: This test queries client data collected by hardware inventory. If hardware inventory is not enabled, the test reports clients that have not reported hardware inventory in addition to computers running unsupported operating systems. To verify the results of this test, verify that hardware inventory is collected from all clients.

If this test reports a client that has already been upgraded to a supported operating system, and for which hardware inventory has been collected, the discovery and hardware inventory data might not have synchronized yet. Verify that the discovery and hardware inventory data are current.

Alternatively, if you ignore this warning, and upgrade to SMS 2003 SP1, the computers running SMS 2.0 will either uninstall, or if they are also assigned to an SMS 2.0 site that will not be upgraded to SMS 2003, they will stop being assigned to the current site and remain assigned to the SMS 2.0 site.

For more information, see Chapter 6 “Understanding Interoperability with SMS 2.0” and Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment available at https://www.microsoft.com/smserver/techinfo/productdoc.

Warning

Unsupported client operating systems for SMS 2003 Service Pack 2

SMS 2003 SP2 specific test

Verifies that none of the clients assigned to the site are running an unsupported operating system for SMS 2003 Service Pack 2. Unsupported client operating systems include: Windows 3.1, Windows for Workgroups 3.11, Windows NT 3.51, Windows NT 4.0 without SP6, Windows 95, Windows Millennium Edition, Windows XP Home Edition, Windows 2000 SP3 or earlier, Windows XP with no service pack or any operating system with Internet Explorer 5 or earlier.

For this test to pass, you can do one of the following:

Uninstall the SMS client from those computers running operating systems unsupported by SMS 2003 SP2 and remove those client records from the SMS site database. 

Upgrade the operating systems of the computers running unsupported operating systems to operating systems supported by SMS 2003 SP2.

Alternatively, if you ignore this warning, and upgrade to SMS 2003 SP2, the computers running unsupported operating systems will not install the SMS 2003 SP2 client. These clients will have reduced SMS functionality while in this state, and should be upgraded to a supported operating system, and then upgraded to SMS 2003 SP2, to receive full SMS client functionality.

Warning

Windows 98 FE Clients without Internet Explorer 5

Verifies that all of the clients running Windows 98, First Edition that are assigned to the site have Internet Explorer 5 or later installed. The test does this by checking the hardware and software inventory records for the client. For this test to succeed, you must enable and collect hardware and software inventory.

For this test to pass, you can do one of the following:

Uninstall the SMS 2.0 client from those computers running Windows 98 first edition without Internet Explorer 5 and remove those client records from the SMS site database.

Upgrade the version of Internet Explorer installed on the computers.

Warning

FAT drive on site server

Verifies that a FAT drive does not exist on the site server.

For this test to pass, you must convert the FAT drive to an NTFS drive. A FAT drive on the Site Server might pose a security risk. This is because compressed copies of the SMS packages might be stored on the FAT drive. For this test to pass, you must convert the FAT drive to an NTFS drive. If you cannot do this, then after upgrading to SMS 2003, you should update all packages on the FAT drive and verify that the compressed copies are moved to an NTFS drive.

Warning

Indirect child sites earlier than SMS 2.0 SP4

Verifies that all sites below the child sites of the site being tested are running SMS 2.0 SP4 or later.

For this test to pass, verify that all sites below the child sites of the site being tested are running SMS 2.0 SP4 or later. You can obtain the latest SMS service pack from the SMS Downloads Web site www.microsoft.com/smserver/downloads. The most current service pack available is SMS 2.0 SP5.

For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Warning

Pre-SMS 2.0 SP4 sites

Verifies that the site server being tested and all its child sites are running a version of SMS 2.0 SP4 or later.

For this test to pass, verify that the site server being tested and all its child sites are running SMS 2.0 SP4 or later. You can obtain the latest SMS service pack from the SMS Downloads Web site www.microsoft.com/smserver/downloads. The most current service pack available is SMS 2.0 SP5.

For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Error

SMS 1.2 Clients

Verifies that there are no SMS 1.2 clients installed in the site.

For this test to succeed, you upgrade the SMS 1.2 site and its clients to SMS 2.0. Alternatively, you can detach the SMS 1.2 site from the SMS hierarchy, and remove the SMS 1.2 client records from the SMS site database. SMS 2003 supports a client upgrade path from SMS 2.0 SP4 or later only.

Warning

Collation of temp database and SMS database should be the same

Verifies that the collation of the temporary database and the SMS site database are the same.

Microsoft SQL Server 2000 supports objects having different collations.

For this test to pass, you must change the collation of SQL Server to match that of the SMS site database. If the instance of SQL Server that is being used by the SMS site database is not being used by another application, run the Rebuild Master utility (Rebuildm.exe) to change the collation order of SQL Server to match that of the SMS site database. If this is not possible because of other applications that use this instance of SQL Server, then use another instance of SQL Server with the same collation as the SMS site database. Backup the SMS site database, restore it to the other instance of SQL Server, then do an SMS site reset to point it to the new instance of SQL Server. Review the SQL Server documentation for more information.

Error

Site database SQL Server version less than 7.0 SP3

Verifies that the version of SQL Server used for the SMS site database is SQL Server 7.0 SP3 or later.

SMS 2003 supports SQL Server 7.0 SP3 or later. Additionally, SMS 2003 requires SQL Server 2000 with SP3 for Advanced Security.

For this test to pass, you must upgrade to SQL Server 7.0 SP3 or later. For more information about SMS site system requirements, see the “Getting Started” chapter in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide available at https://www.microsoft.com/smserver/techinfo/productdoc.

Error

Backlogged inboxes

Verifies that the site server is processing critical inboxes in a timely fashion and does not have any files older than one day. Review the test results for more information.

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. The test results indicate which inboxes have old data that has not been processed.

For this test to pass, diagnose and correct the problem that is keeping the files from being processed. The SMS component with the problem is listed in the report. Check the component’s status messages for errors and warnings. The component may have fallen behind in processing files due to a temporary condition and will catch up on its own. Or the site server may need hardware upgrades to handle the load.

Warning

Client GUID consistency

Verifies that no clients have inconsistent GUIDs in the SMS database.

This scenario can occur, for example, if a client had its GUID set in the MachineIDGroupXRef table but not in the System_DISC table, a new DDR is received for the client, and Discovery Data Manager tries to update the GUID in the MachineIDGroupXRef table. The GUID cannot be updated, and a SQL error results

For this test to pass, all client GUIDs must be consistent.

To correct this situation, run the following SQL Query:

delete sys

from System_DISC sys

join MachineIdGroupXRef xref on sys.ItemKey=xref.MachineID

where IsNULL(SMS_Unique_Identifier0,'') != IsNULL(GUID,'')

Error

Distribution point has latest versions of packages

Verifies that all distribution points in the site have the latest version of software distribution packages. Review the test results for more information.

For this test to pass, all distribution points must have the latest version of software distribution packages. You can determine which distribution points do not have the latest version of packages through the SMS Administrator console as follows:

Navigate to System Status\Package Status. Select each package under Package Status. In the right pane, the distribution points that do not have the latest version of packages are those where the values displayed in the Targeted and Installed columns are not equal. Right-click the distribution point and choose Show Messages to troubleshoot the problem. Also check error and warning status messages for the components involved with distributing packages, including SMS_SCHEDULER, SMS_LAN_SENDER, and SMS_DISTRIBUTION_MANAGER.

Warning

Duplicate client IDs

Verifies that the site does not have any duplicate client IDs in its database. For each GUID, the test looks for different current and old machine names. They are the only fields that determine whether it is listed the first time. Other fields determine if more instances of the different current/old machine name are listed. If any other field (domain name, site code, old domain name) is different, each instance is listed in the DRW report.

For this test to pass, delete any duplicate client IDs from the SMS site database retaining the current ID. The scope of this test is all clients assigned to any site in the SMS site database. Duplicate client IDs can cause various problems including client inventories that are not valid and problems with software distribution.

Warning

Event to trap translator

Verifies that the SNMP Event to Trap Translator client agent is not enabled on the site.

For this test to pass, you must disable this client agent. Note that this feature is supported as part of Windows 2000 and later operating systems.

Error

Hardware Inventory Group Map

Verifies that the inventory definitions for the SMS 2.0 site have not been extended in a way that conflicts with the updated inventory definitions for SMS 2003, and that there are no incorrect NOIDMIF definitions that were created by SMS 2003 Beta 1, duplicate GroupMap table name entries, or GroupMap entries with missing tables.

For extended inventory definitions, the conflict occurs when the Group Name in a custom MIF or extended MOF matches the Group Name of an inventory group used in SMS 2003 but the Class Name of the inventory group does not match. If the conflict comes from a custom MIF then you should change the Class Name you use. This is true for an extended MOF also. However, in this case you might want to verify if the SMS 2003 MOF has been extended in the same way (to collect the same class) and if so, you should use the SMS extension and not your own. Both solutions may require you to change collections or queries that use the old class name. If you take no action, after the upgrade has been completed, the collections and queries that have been affected by this conflict will have an asterisk prefixed to their names. These collections and queries will not be evaluated and should be updated. Removing the asterisk from the name may be enough to allow the collections and queries to be reevaluated without error, but if not then they should be deleted and recreated. Data previously collected under the old conflicting names is not deleted, but it is no longer accessible through SMS. Instead the affected inventory DATA and HISTORY tables will have the term, OLD, appended to the table name. You can delete these tables.

For incorrect SMS 2003 Beta 1 NOIDMIFS and duplicate GroupMap table name entries, you might have to correct the collections as indicated above.

For GroupMap entries with missing tables, the upgrade process will delete the entries. Review the test results for more information.

Warning

Inactive Clients

Verifies that all the clients assigned to the site are communicating successfully with the site’s client access points (CAPs). The test does this by verifying that hardware inventory. software inventory, a discovery record, or at least one status message from the client has appeared in the SMS site database within the last 30 days. If clients are not communicating with the site server, they might not be upgraded successfully.

For this test to pass, determine why the client has not communicated with the CAPs by examining the event logs and SMS logs on the client. Then correct the problem. It could also be that the client has been removed from the site or reimaged, in which case you can delete the client from the SMS site database.

Warning

Logon Client Installation Disabled

Verifies that SMS 2.0 Logon Client Installation has been disabled.

For this test to pass, you must disable Windows Networking Logon Client Installation. SMS 2003 does not support logon points because SMS 2003 does not support Windows Networking Logon Discovery or Windows Networking Logon Client Installation.

Error

Logon Discovery Disabled

Verifies that SMS 2.0 Logon Discovery has been disabled.

For this test to pass, you must disable Windows Networking Logon Discovery. Because SMS 2003 does not support logon points, logon discovery is not included as a discovery method in SMS 2003.

Error

Logon points installed in Hierarchy

Verifies that no logon points are currently installed in the hierarchy. The test checks whether the SQL table sysResList contains any RoleName = 'SMS Logon Server'. It will contain such a rolename if logon installation or logon discovery is enabled for any site in the SMS site database.

For the test to succeed, you must disable all logon points.

Ensure that your logon scripts no longer call SMSls.bat. Instead, invoke Capinst.exe with optional command-line switches in your logon scripts. For more information about the optional command line switches see Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment available at https://www.microsoft.com/smserver/techinfo/productdoc.

Error

Packages SQL constraint

Verifies that there are no duplicate package IDs.

For this test to pass, you must apply the hotfix for Knowledge Base article Q819665. This will delete all duplicate packages except the first instance, and it will apply a primary key constraint to the SMSPackages SQL table so no more duplicate packages can occur.

Error

Multi-site assigned clients

Verifies that no clients are assigned to more than one SMS site.

For this test to pass, verify that all clients report to one site only. Multisite assignment is unsupported in SMS 2003. During upgrade, a new Legacy Client removes all sites except the one that initiated client upgrade from its membership list if the client is within the boundaries of multiple sites. A Legacy Client automatically uninstalls if all site boundaries are removed, or if it moves out of the boundaries of its assigned site, unless travel mode is enabled.

Warning

SMSExec is running

Verifies that SMS Executive is running on site systems such as the SMS site server and the CAPs.

For this test to pass, the SMS Executive service must be installed and running on the SMS site server, and on the site’s CAPs. This test checks the HKLM\Software\Microsoft\SMS\Components\SMS_Site_Component_Manager\Component Servers registry key on the site server. This key has an entry for each site system computer, and each entry has a Components\SMS_Executive sub-key that includes a State variable. This test checks the value of the State variable. If State=3, it means the SMS Executive service is running and the test will pass.

This test might list a server that is no longer used as having failed the test. This can occur if the Site Component Manager is unable to remove the server from the registry.

When you use the SMS Administrator console to remove a site system, SMS removes it from the site control file. The fact that the site system is in the registry but not in the site control file is what triggers Site Component Manager to uninstall the site system. The State variable for that site system is set to 5, indicating that the component is in the process of being uninstalled. Site Component Manager typically updates this value at least every hour.

After Site Component Manager succeeds in uninstalling the site system, it deletes it from the registry. If Site Component Manager is unsuccessful, it retries the uninstallation every hour for one week. After this period of time, Site Component Manager times out and deletes the site system from the registry.

However, if Site Component Manager does not have rights to remove the registry key or one of its subkeys, you will see entries similar to the following in Sitecomp.log every time Site Component Manager starts:

  • Parsed the master site control file, serial number xxx.

  • Could not read server xxx from the registry.

  • Deleting server xxx from the registry.

  • Could not delete server xxx from the registry.

In this case, DRW will continue to list the site system as having failed the test. For this test to pass, manually delete the site system’s registry key from the HKLM\Software\Microsoft\SMS\Components\SMS_Site_Component_Manager\Component Servers registry key. Then run DRW again to verify the test now passes, or, if the test fails, that it no longer lists that site system as having failed the test.

  

SMSExec Service crashes

Verifies that no SMS Executive service crashes have happened on the site server within the last 30 days.

This warning does not prevent you from upgrading the site. Nevertheless, SMS Executive service crashes are indicative of problems with site systems. It is recommended that SMS Executive service crashes should be investigated and resolved before continuing with the upgrade. Review the test results for more information.

Warning

Site control file processing backlog

Verifies that site control file changes are being processed in a timely fashion. This test checks whether the query "select count(*) from SiteControl where SiteCode = 'xxx' “ (where xxx is the site code DRW is run against) returns a number less than 4.

For the test to succeed, the site control file must not have more than four pending changes. Review the test results for additional information. Check for error and warning status messages from SMS_HIERARCHY_MANAGER and SMS_SITE_CONTROL_MANAGER.

Error

Software Distribution: Uninstall registry key usage

Verifies that no SMS 2.0 programs use the Remove software when it is no longer advertised option, which uses the Uninstall registry key.

For this test to pass, you must disable this option on SMS 2.0 programs. SMS 2003 does not support removing software when it is no longer advertised (by means of the Uninstall registry key). Review the test results for additional information.

Warning

Software metering site systems

Verifies that there are no software metering site systems configured in the SMS hierarchy.

For the test to succeed, you must clear Use this site system as a software metering server in the Properties dialog box for all site systems listed by this test. Upgrade will automatically perform all other required actions to remove SMS 2.0 software metering. Although it is not necessary to remove all traces of SMS 2.0 software metering, you might also:

Delete the account SWMAccount, but only if no other SMS 2.0 sites are using it.

Delete the SMS 2.0 c:\swmtr and c:\sms\licmtr folders.

In Control Panel, open Data Sources (ODBC) in Administrative Tools, navigate to the System DSN tab, and remove the LicAdmin and License Server Local DSN entries.

Delete the SMS 2.0 license metering database on the SMS site database server.

Delete the following registry entries:

HKLM\SYSTEM\ControlSet001\Services\LICENSE_METERING

HKLM\SYSTEM\ControlSet001\Services\LICSVR_SERVICE

HKLM\SYSTEM\ControlSet002\Services\LICENSE_METERING

HKLM\SYSTEM\ControlSet002\Services\LICSVR_SERVICE

Previous versions of software metering are not supported by SMS 2003. For more information about removing legacy software metering, see Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment available at https://www.microsoft.com/smserver/techinfo/productdoc.

Error