Solved

SMS 2003 Side-by-side upgrade

Posted on 2004-08-06
3
401 Views
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.
0
Comment
Question by:Fthao
3 Comments
 
LVL 1

Author Comment

by:Fthao
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.
0
 
LVL 6

Accepted Solution

by:
jdfulton earned 500 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.


0
 

Expert Comment

by:netguru6
ID: 12770768
Hello,
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:
http://www.microsoft.com/resources/documentation/sms/2003/all/cpdg/en-us/plan0smv.mspx

Truly yours,
Nguru

SMS/RIS/ADS/AD/Exchange/SOE
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…

805 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