Upgrading, Server

  • Article

If you have SCRM installed on your SMS 2003 SP2 database and are upgrading to SMS 2003 SP3, you must run an SQL script to enable SCRM tasks on the SMS database

The SCRM related triggers may generate too much data in the SMS 2003 SP2 database, even if you do not install SCRM. To prevent this problem, SCRM related triggers are disabled by default in SMS 2003 SP3.

WORKAROUND:   To make SCRM work, enable triggers by running the following SQL command:

IF OBJECT_ID ('dbo.DWTr_User_Disc_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_User_Disc_Del'), 'EXECISTRIGGERDISABLED') = 1
     ALTER TABLE User_DISC Enable TRIGGER DWTr_User_Disc_Del 

 IF OBJECT_ID ('dbo.DWTr_User_Group_DISC_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_User_Group_DISC_Del'), 'EXECISTRIGGERDISABLED') = 1
     ALTER TABLE User_Group_DISC Enable TRIGGER DWTr_User_Group_DISC_Del 

 IF OBJECT_ID ('dbo.DWTr_SoftwareInventory_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_SoftwareInventory_Del'), 'EXECISTRIGGERDISABLED') = 1
     ALTER TABLE SoftwareInventory Enable TRIGGER DWTr_SoftwareInventory_Del 

 IF OBJECT_ID ('dbo.DWTr_CollectionMembers_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_CollectionMembers_Del'), 'EXECISTRIGGERDISABLED') = 1 
     ALTER TABLE CollectionMembers Enable TRIGGER DWTr_CollectionMembers_Del 

 IF OBJECT_ID ('dbo.DWTr_PatchStatusSummary_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_PatchStatusSummary_Del'), 'EXECISTRIGGERDISABLED') = 1 
    ALTER TABLE PatchStatusSummary Enable TRIGGER DWTr_PatchStatusSummary_Del 

 IF OBJECT_ID ('dbo.DWTr_System_Disc_Del') IS NOT NULL AND 
   OBJECTPROPERTY(OBJECT_ID('dbo.DWTr_System_Disc_Del'), 'EXECISTRIGGERDISABLED') = 1
    ALTER TABLE System_DISC Enable TRIGGER DWTr_System_Disc_Del

FQDN Support on Management Points may require a change to Active Directory schema

As part of SMS 2003 SP2 and SMS 2003 SP3 releases, a minor update to the SMS schema extensions in Active Directory is required to support the use of the FQDN. If upgrading from SMS 2003 SP2 to SMS 2003 SP3 and if the schema extensions were updated when installing SMS 2003 SP2, no additional schema extension updates are necessary.

WORKAROUND:   The scenario and its solution are fully documented in the updated Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment guide available from the SMS Product Documentation Page.

Uninstall Administration Feature Pack before Upgrading to SMS 2003

You must uninstall the SMS 2.0 Administration Feature Pack before you upgrade to SMS 2003. The Administration Feature Pack is binary-incompatible and not supported by SMS 2003. Using the SMS 2.0 Administration Feature Pack tools (Transfer Site Settings, Manage Site Accounts, and Elevated Rights tool) on an SMS 2003 server computer causes undefined behavior and could potentially cause severe side effects on your SMS site server.

WORKAROUND:   None.

Server Locator Point Might Stop Functioning After Upgrading To SMS 2003 Service Pack 3

If the site system serving as your server locator point (SLP) is running Microsoft Windows Server 2003 SP1, the Local Launch permissions for the Internet Guest Account may be removed after the upgrade to SMS 2003 SP3.

WORKAROUND:   Follow the manual procedures outlined in the Site Systems Frequently Asked Questions.

Reset the COM permissions so that the Internet Guest Account (IUSR_<servername>) has Local Launch permissions, as shown in the following procedure.

To grant Local Launch permission to the Internet Guest Account

  1. On the site system, from the Start menu, click Run and type dcomcnfg.exe.

  2. In Component Services, click Console Root, then click Component Services. Next, click Computers, My Computer, DCOM Config, and then click SMS_SERVER_LOCATOR POINT. On the Action menu, click Properties.

  3. In the Launch and Activation Properties dialog box, navigate to the Security tab. In the Launch and Activation Permissions section, click Edit.

  4. In the Launch and Activation Permissions dialog box, select the check box to allow Local Activation for Internet Guest Account (IUSR_servername).

Clients Can Become Orphaned If There Is an SMS 2.0 and SMS 2003 Hierarchy in Same Domain

Clients can become orphaned if there is an SMS 2.0 and an SMS 2003 hierarchy in the same domain if all of the following conditions are present:

  • User logon scripts have been updated by an SMS 2.0 site in the same domain as the SMS hierarchy that you are upgrading to SMS 2003.

  • User logon scripts contain client installation methods for both SMS 2.0 and SMS 2003.

  • The clients are running on platforms that are not supported in SMS 2003, such as Windows 95.

Logon points are not supported in SMS 2003. Before you upgrade an SMS 2.0 site to SMS 2003, you must disable Windows Networking Logon Discovery and Windows Networking Logon Client Installation. This process takes some time because it involves replication between domain controllers designated for Windows Networking Logon Client Installation and/or Windows Networking Logon Discovery. Do not continue with the upgrade until you verify that the logon points are completely removed.

WORKAROUND:   Ensure that the user logon scripts contain no references to SMSls.bat or SMSman.exe binary files from an SMS 2.0 site.

If you continue with the upgrade before the logon points are completely removed, clients that are not supported by SMS 2003 (for example, computers running Windows 95) can be orphaned.

To remove the SMS client software from a computer that is running an unsupported Windows operating system, and that was upgraded before logon points were removed

  1. Stop all SMS client processes.

  2. Remove the systemroot\MS\SMS folder and its subfolders.

  3. Remove all SMS related registry entries.

  4. Remove all SMS related files in the systemroot\Temp folder.

  5. Log off the computer, and then log back on.

    This will begin the SMS 2003 logon script initiated client installation (if you have added a Capinst.exe command line to the logon script) that will install the Windows 95 client in an SMS 2.0 site if the computer is within the boundaries of an SMS 2.0 site. For more information, see Chapter 17, "Discovering Resources and Deploying Clients," in the Microsoft Systems Management Server 2003 Concepts, Planning, and Deployment Guide.