SP 2 is coming (the rumor mill says this month). This article will give you a head start on your planning.
Prior to an upgrade from either the RTM or SP1 code, there are a couple of hotfixes that must be manually applied. These hotfixes help prevent the scenario that occurred all too often in the upgrade from the RTM to SP1 code. What happened in that upgrade was that logon points were sometimes updated to SP1 by a different site that was upgrading, but a local site's CAPs might not be updated yet. So, when a client tried the logon point, it would start updated versions of bootstraps and Clicore.exe, but the CAP files remained at RTM code. This essentially stopped the SMS client functions on the client, forcing a reinstallation, update of the CAPs, and another reinstallation.
There are two required hotfixes for both RTM and SP1 sites. The first hotfix is for logon points so that clients can properly determine whether the logon point has been updated to SP2. This is only required when the logon points are shared with multiple SMS sites. In this case, one site may be updated prior to others, causing clients to become unstable
If you have SMS sites running the RTM version (Build 1239) of Systems Management Server (SMS) 2.0, you must apply hotfix updates to all of those sites before upgrading them to SMS 2.0 Service Pack 2 (SP2). The following Microsoft Knowledge Base articles will help you to apply the updates:
- Q251070 SMS: Copylog.tcf Does Not Reflect Site Which Site Last Updated the Logon Point Q252718 SMS: CCM Avoids Installation Attempts on SP2 Clients
If you have SMS sites running SMS 2.0 SP1 (Build 1380), you must apply hotfix updates to all of those sites before upgrading them to SMS 2.0 SP2. The following Microsoft Knowledge Base articles will help you to apply the updates:
These Knowledge Base articles are located at the Microsoft Product Support Services Web site:
Note: The update install files, which are addressed in these articles, are located in the SMSQFE directory on the SMS 2.0 SP2 CD.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: