Need guidance on SMS 2.0 to 2003 Upgrade approach



Hi all,

We are belatedly upgrading from SMS 2.0 to SMS 2003. We have one
Primary site and 50+ Secondary Sites spread across the country with
varying WAN links 256Kb up to 1Mb. What we really want to do is replace
the Primary Site Server hardware as it is old and under spec. We also
want to upgrade all the sites to SMS 2003. We mostly want to keep the
hierarchy intact but allow the option of recreating or consolidating
secondary sites as some of them are throwing errors under SMS 2.0 . All
the clients are XP. All the servers are W2K3. Domain is AD W2K3 Native.
I have not found the docs to be crystal clear on an approach we can
take to this. My assumed way to go ("side-by-side" upgrade?):

- Build new site server hardware
- Install SMS 2003 on that giving it a brand new site name
- Make the existing Primary a child of this new Primary
- Upgrade secondary sites OR consolidate (by re-homing clients via Site
boundaries and pushing out client s/ware)

Questions:

- If we do it this way - what about the existing 2.0 Primary site -
what happens to that?
- as you upgrade Secondaries, do those sites 're-home' automatically to
be direct children of the new SMS 2003 Primary site?
- as you upgrade Secondaries (not consolidating), do clients
automatically upgrade to Advanced Client s/w or do you have to do
Client Push/Software Distribution as you go
- is there a way to just replace the Central/Primary site hardware,
i.e. effectively 'swap out' the old SMS 2.0 server and leave everything
beneath it intact. Then I assume we could just do in-place upgrades
across the board?

We have tried to build a test bed to dry run the upgrade effort but we
are more confused than before. As you can see, we'd appreciate some
guidance!

Thanks in advance
Padraig.

.



Relevant Pages

  • Re: Upgrade Questons
    ... I think I would upgrade SQL first, but I guess that is just my personal ... preference because I know more about sms than about sql. ... > resources which would now include the resources from the secondary sites. ... clients cannot be assigned to secondary sites anyway. ...
    (microsoft.public.sms.setup)
  • Re: Upgrade Questons
    ... So just to confirm when should I upgrade to sql 2000 sp3. ... upgraded my sms 2.0 primary site to sms 2003 (configuring using standard ... so anyway we have a sms 2.0 primary site with 2 secondary sites hanging off ...
    (microsoft.public.sms.setup)
  • Re: Moving SMS Primary site to new hardware
    ... a good start would be to install the recovery expert website. ... First my SMS ... hierarchy consists of a SMS Primary site with a number of SMS Secondary sites. ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 and Site Names
    ... Sms 2003 sites can not report to an sms 2003 parent. ... So you would have to upgrade the primary site sms 2.0 first. ... Step 5 won't be an option since it has the secondary sites attached, ... > the Secondary Sites without migrating all the clients at the same time? ...
    (microsoft.public.sms.setup)
  • Re: Primary vs Secondary
    ... I personally would tend to go with a primary site unless I have a good ... Check out the SMS Technical FAQ: ... Aside from the sql and server license. ... Advanced Clients cannot be assigned to Secondary Sites. ...
    (microsoft.public.sms.admin)