SMS 2003 Side-by-side upgrade

Posted on 2004-08-06
Medium Priority
Last Modified: 2012-08-13
We are currently trying to perform a side by side upgrade of our SMS 2.0 site server to SMS 2003.

We currently only have 1 SMS 2.0 Site with about 500 users and would like to basically start over by installing a new SMS 2003 site on new hardware with a different site code and a fresh database. I beleive this is called a Side-by-Side upgrade.

My first question is, to migrate clients over to the new site and and un-install the SMS 2.0 client, all we would need to do is to roll out the Advanced client from our new SMS 2003 site correct? Does the action of rolling out the advanced client cleanly uninstall the old one? The least amount of administrative work would be favorable.

Once we have the majority of the clients assigned to the new site with the advanced client installed, what is the procedure to go about taking off the Logon Point Role for our DC's since SMS 2003 no longer supports Logon Points?  Does it happen automatically when we insert the original SMS 2.0 CD and do a Primary Site un-install?

Looking for advice from someone who's done this before, but any expertise is much appreciated.
Question by:Fthao

Author Comment

ID: 11735174
opps, I may have posted this in the wrong spot. If any moderators are reading this, would it be possible to move this to the Microsoft Network Solutions area? Just didn't want to post 2 of the same questions.

Accepted Solution

jdfulton earned 1500 total points
ID: 11736107
All SMS 2.0 clients will upgrade to the SMS 2003 Legacy Client on their next CCIM cycle after the client access point is updated with SMS 2003 binaries. You can use the cliupgrade tool to prevent SMS 2.0 clients from upgrading and allow staging of upgrades in addition to direct upgrade to the SMS 2003 Advanced Client.

You should be ok.  You know how bad SMS 2.0 was on the client side.  2003 seems to be much better for installs.  Also the Advanced client is only good for 2000 or above machines.

On the logon point issue and the above.  As long as you fix all the problems found with the Deployment Readiness wizard you should be fine.


Expert Comment

ID: 12770768
Would love to help you, please supply the following info:

What is the OS on the client side: mainly XP? W2K? Win98 ? NT 4?
How many subnets do you have in your network, which SMS 2.0 is aware of?
Do you have Active Directory in place?

You have several options.

For sure, you could the discovery process on the new server anytime you want to discover all the resources. Disovery is harmless beside bandwidth utilization. If you have AD in place and all your machines are Win2k or better, then you task is very easy. Extend the AD Schema hen you install SMS 2003 and configure AD System Discovery to run. When you have the majority of your clients in the "All Systems" Collection, you could simply push gradually or all at onve the new client.

When you enable pushing the client:
Win2k/XP/W2k3 will get the Advanced Client
Win98 and NT4 Sp6a will get the "Legacy Client" which is very similar to the SMS 2 Client.
(I have seen the legacy client installation happen successfully on NT4 SP5 machines if WMI and IE 5 were installed though it is only supported on SP6a, FYI)

SMS Transition Site Build:
You will need to come with new Site Code(s) and if you have several subnets, then you could incremently add your IP subnets one by one and  sweep your clients on stages. In case of trouble with some clients. You could email and I could send you a package that you could push on the SMS 2.0 side that uninstalls the client, in case of trouble. In any case, SMS 2.0 Clients automatically uninstall themselves after 24 hours of NOT locating and communicating with their CAP. So you could on a weekend uninstall SMS 2.0 and have the clients up so that they by Sunday uninstall themselves.

If you are on AD, then just make sure that your subnet are in AD Sites and Services MMC, then SMS 2003, upon extending the schema, will be able to read your AD Sites and even OUs.

Another option would be to push the client to the Advanced Clients and have them served by the transition client. If you have a large number of Windows 95, you will need a holding SMS 2.0 Site to support them.

For more info in detail please see:

Truly yours,


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
In the video, one can understand the process of resizing images in single or bulk. Kernel Bulk Image Resizer is an easy to use tool for resizing large number of images. One can add and resize multiple images with this tool in single go. The video sh…

597 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question