Home > ConfigMgr 2007 > In-Place Upgrade of SMS 2003 to SCCM 2007 SP2

In-Place Upgrade of SMS 2003 to SCCM 2007 SP2

When it comes time to migrate your SMS 2003 environment (short of ripping and replacing the current SMS environment) there are two methods recommended by Microsoft for upgrading to SMS 2003 to SCCM 2007 (In-place upgrade and Side-by-side upgrade). This post will talk about the in-place upgrade and the steps you will need to use and know in order to have a successful migration. In this environment I am running SMS 2003 with SP2 and SQL 2005 sp2 on Windows 2003 Standard SP2.

NOTE: SQL 2000 is not supported with SCCM 2007 and must be upgraded to SQL 2005 SP2

Before you begin:

1. If you have made any changes to any of the default groups (initial collection membership rules) will need to make a note of these as it will be over written.

2. If you have made changes to your SMS_def.mof file you will need to back the file up before you perform the upgrade to SCCM as the setup will overwrite them.

3. If you are using SQL replication you will need to disable SQL replication prior to the upgrade

4. Backup your SMS database using the SQL Server Studio before the upgrade. I like to remove the default destination and create my own.

Prerequisite Checker

5. Run the prerequisite checker from the SCCM 2007 Media. In this example I made sure to have none of the pre-requisites installed so that you can see what is needed.

Schema Extensions: 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.

Software Updates KB932303: Configuration Manager out of band service point requires Windows Server 2003-based schannel hotfix. The schannel hotfix is available for download at: http://support.microsoft.com/kb/942841/en-us.

WSUS SDK on site Server: Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 SP1 or later. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see http://go.microsoft.com/fwlink/?LinkID=79477.

Windows Server 2003-based schannel hotfix: Configuration Manager out of band service point requires Windows Server 2003-based schannel hotfix. The schannel hotfix is available for download at: http://support.microsoft.com/kb/942841/en-us.

Windows Remote Management (WinRM) v1.1: WinRM v1.1 is required to run the out of band console and must be installed before primary site or Configuration Manager console installations or upgrades. WinRM 1.1 is available for download at: http://support.microsoft.com/kb/KB936059.

MMC Updates for Configuration Manager: This software update addresses several MMC errors that may occur when running the Configuration Manager console. This update should be applied if any of the following occur: Configuration Manager console stops responding when the host computer is low on available memory, context menu errors on console home pages, or inconsistent display after drag-and-drop operations do not succeed. More information about this update is available at: http://go.microsoft.com/fwlink/?LinkId=98349.

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.

FQDN Specified for site systems: It is recommended to specify a Fully Qualified Domain Name (FQDN) for site systems in mixed mode Configuration Manager sites. It is required to specify an FQDN for site systems in native mode sites to allow clients to authenticate with site systems.

 

Once you have fixed all your prerequisites you will see the following:

Testing the Site Database

6. Test the site database for the upgrade. Browse to the smssetup\bin\i386 folder from your SCCM media. Run the command below (where SMS_LAB) is your database name.

The following wizard will appear. Click on “Begin TestDBUpgrade”.

The wizard will disappear and it will appear as if nothing is happening. Wait a few minutes and you will see the following message appear

7. You can now proceed with running the setup.exe from the SCCM media.

Upgrading SMS to SCCM

8. Walk through the wizard the click begin.

9. Monitor the installation of the components. This will take a few minutes.

10. The in-place upgrade is complete. You will need to update all systems reporting into SCCM with the new client version.

11. At this point the upgrade is completed. Click next to either view the log file or launch Configuration Manager.

Categories: ConfigMgr 2007
  1. January 4, 2011 at 10:43 am

    Sweet post.

  2. November 16, 2011 at 12:59 am

    nice post

  3. Andy
    February 2, 2012 at 9:22 am

    Tom,
    We have cleaned up all the warnings. We opted not to do the in-place upgrade.

    In your post, you mention to use an existing client installation method to upgrade the Client to the SCCM 2007. Since we have our new server in place, could we use the SCCM 2007 Client Push versus the Client package? What would you recommend? We have tried both ways in our testing.

    Thank you for your documentation. It has certainly helped with our process.
    Andy

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: