Re: Upgrade SMS 2.0 to SMS 2003 to new hardware without losing old data
- From: "Torsten [MVP]" <torsten.meringer@xxxxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 20:16:36 +0100
Hi Baludinger,
see inline ...
"Baludinger" <Baludinger@xxxxxx> schrieb im Newsbeitrag
news:1162292361.377015.158780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I have an urgent need to migrate my SMS 2.0 SP5 Servers (1 primary, 2
secondary) with about 2.000 clients (all XP SP1) to SMS 2003 SP2 on new
HW and new OS. I also need a way to keep all my queries, packages,
collections, advertisements etc.. What would be the best way to do so?
There's no definite answer without knowing your environment exactly.
My thought was the following:
1. Upgrade central SMS 2.0 Server to SMS 2003.
That would work.
Extend AD schema.
Why don't you extend the schema before installing SMS 2003?
Add
boundaries of secondary sites to central site.
Why? Just keep them as they are. SMS 2.0 secondary site can be attached to
SMS 2003 site.
Start new Discovery.
Why? Your clients are already in the SMS database when you upgrade your
site.
Distribute Advanced Client to all Clients. At the same time or using a
phased upgrade of clients by using the clientupgrade /disable switch?
It depends. You could even send out an advertisement for upgrading the
clients. Or client push installation. Or whatever fits best in your
environment.
What happens when you send the /enable switch? Is the legacy client
installed automatically? I only need the advanced client!
I am not 100% sure about this without reading the docs again. But I *think*
that clients, that could be upgraded to the advanced client, do not
automatically upgrade themselves to the legacy client. But that's documented
in the .html file of the service pack 2.
2. Installing SMS 2003 on new HW with new OS and make it a child of
central site. Queries, packages etc. are then replicated to new primary
2003 site.
I think you want to upgrade your siteserver? So (see above) you have already
a SMS 2003 site.
3. Remove boundaries from central site and create same boundaries on
primary server. Clients will be assigned to primary site. How long does
this take?
They will not be automatically assigned to another site if they are advanced
clients!
4. Install secondary servers on new HW with new OS. Configure them (MP,
DP etc.) and make them a child of primary server.
Secondaries could also be upgraded in theory.
5. Turn off central server. Will then the primary server become a
central server automatically or do you have to configure this?
A site will become a central site if the parent primary site is removed.
I also know about the other way to make the new SMS 2003 server on new
HW and OS a central server and make the old 2.0 central server a child
of the new one. But I do not have a possibility to keep all my data, do
I?
If a new site will be above an existing site you will only have your clients
replicated up.
Is there a way to export 2.0 data into 2003 central server?
Could be done with scripting, but IMHO there's nothing out that's ready to
go. Maybe it's even better to start from scratch. That can't be solved via
newsgroup.
Your help is very much appreciated as it is an urgent need!
Exact planning takes time.
Thanks in advance for your help.
Baludinger
As you've got a german email address you could also use microsoft.public.de
for posting your question ;o)
Torsten
Microsoft MVP - SMS
.
- Next by Date: Re: Upgrade SMS 2.0 to SMS 2003 to new hardware without losing old data
- Next by thread: Re: Upgrade SMS 2.0 to SMS 2003 to new hardware without losing old data
- Index(es):
Relevant Pages
|
Loading
