Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: RobM <robM@xxxxxxxx>
- Date: Mon, 11 Dec 2006 13:59:53 +0000
For the upgrade path check this out:
Upgrading from SMS 2.0 to SMS 2003
http://www.microsoft.com/smserver/techinfo/upgrade.mspx
A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL
replication is configured on the site database in Systems Management
Server 2003
http://support.microsoft.com/kb/886629
SMS 2003: Preparing for Migration/Installation
http://www.myitforum.com/articles/8/view.asp?id=6657
On Mon, 11 Dec 2006 11:05:13 +0000, RobM <robM@xxxxxxxx> wrote:
my ten cents worth ... see inline-
On 11 Dec 2006 02:09:53 -0800, "patnerd"
<padraig.denihan@xxxxxxxxxxxxxx> wrote:
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)
I'd go for side-by-side, clean slate and more control. untainted
database. I would not connect the sms 2.0 site to the new environment,
keep it pristine. you could perform an in-place upgrade but i like
everything new and shiny :>
Build new site server hardware
Install SMS 2003 on that giving it a brand new site name
Create an upgrade schedule for all 50 secondaries
Start with 1st secondary,
Push the sms2003 adv client to the clients at the secondary site
Deinstall the sms 2.0 secondary, configure the OS to support the new
sms2003 secondary site then perform an install from the new sms2003
pri\central.
Setup the secondaries boundaries and configure the site settings
Clients at the secondary site should auto-assign to the secondary once
everything is configured correctly. If they do not then there are some
tools you can use to remotely assign them but auto-assignment should
work and if it doesn't should be investigated rather than worked
around. But if it's a live production rollout and you must keep the
clients in-communication with a site then the tools can be used as an
emergency work-around for assignments.
Repeat for the other 49 secondaries
Alternatively you could perform discovery of clients at the
pri\central and perform a push of the client after rather than before
your upgrade.
others in the group can elaborate, expand and\or correct the above.
Questions:
- If we do it this way - what about the existing 2.0 Primary site -
what happens to that?
if you've upgraded it to sms2003 and pushed secondaries out from it
then you can't do anything except retain it due to the relationship a
secondary has with it's primary.
- as you upgrade Secondaries, do those sites 're-home' automatically to
be direct children of the new SMS 2003 Primary site?
nope. a secondary site is intimately linked with it's pri and this
association will not change. to get these secondaries to connect to
the new pri you would have to deinstall them and perform the install
from the new pri
- 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
nope. you would have to push the software out to the new clients.
sms2003 adv client does not perform a maintenance check as does 2.0 so
to upgrade clients you have to manually deal with the client upgrade.
same applies to modified mofs you have to send a job down to them to
mofcomp the new mof.
- 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?
not really, the secondaries are hard coded to the 2.0 primary so this
option wouldn't work
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.
hope this helps.
-
Rob - Windows Management User Group
www.wmug.co.uk
Rob - Windows Management User Group
www.wmug.co.uk
.
- Follow-Ups:
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: patnerd
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- References:
- Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: patnerd
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: RobM
- Need guidance on SMS 2.0 to 2003 Upgrade approach
- Prev by Date: Re: SMS collection query help please
- Next by Date: Re: SMS collection query help please
- Previous by thread: Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- Next by thread: Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- Index(es):
Relevant Pages
|
