Re: 2.0 to 2003 Migration Questions
From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 08/31/04
- Next message: Allan Tee: "Re: MP.MSI exited with return code: 1603"
- Previous message: Kim Oppalfens: "Re: SMS 2003 Scan Tools Question"
- In reply to: Jacob: "Re: 2.0 to 2003 Migration Questions"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 31 Aug 2004 23:44:53 +0200
Inline
In article <263249DA-4C64-4D1C-880D-59E5583D655A@microsoft.com>,
Jacob@discussions.microsoft.com says...
> Thanks for your reply..
Your more than welcome.
> So instead of making the new site a child site of the old Central as is the
> scenarios I stated; just install 2003 on the new server and make the old
> central site a child of the new central site.
Yups.
>
> Should the old central site be upgraded to 2003 or left at 2.0? The plan is
> to get rid of the old servers...
Upgrading prior to attaching to the new central site is not necessary.
Make sure you export querries; sms_def.mof; maybe even packages &
collections since this data is not replicated up.
>
> As the other child sites are upgraded, could they be set to report to the
> new central site? I guess you could report all child sites to the new central
> site and get rid of the old central site prior to upgrade, correct?
As long as they are all primary sites this should be possible yes.
>
> "Kim Oppalfens" wrote:
>
> > In article <C517C72E-1715-4160-9AAC-3197D2943BC3@microsoft.com>,
> > Jacob@discussions.microsoft.com says...
> > > Currently, my company is in the planning phase of upgrading our SMS 2.0 SP5
> > > infrastructure to SMS 2003.
> > >
> > > One of the issues we have is our Central site resides on two servers and we
> > > want the central site to reside on one server. There currently are no clients
> > > on the central site. SMS is on one server and the database and sms provider
> > > is on another server. The Central site will have new hardware. Since you
> > > cannot move the database and provider back to the server, we are wondering if
> > > the following is possible�.
> > >
> >
> > The only solution I see is installing an sms 2003 server, and make your
> > current central site a child site of this new site, all data will then
> > replicate to the new parent. and you can then restructure your current
> > child sites to point to the new Central site I guess.
> >
> > Making a certain site a central site does nothing to the database of the
> > old central site. So your scenario will not work or I misunderstood what
> > you are planning to do.
> >
> > Kim Oppalfens
> > > Question:
> > > If we install SMS 2.0 SP5 as a new child primary of the current central
> > > site, then change it to be the central site, will the database from the old
> > > Central site move to the new server?
> > > To remove the old central site, can we just point the rest of the child
> > > primary sites to the new central site and remove the old Central Site?
> > >
> > > Would it be better to upgrade the existing Central site first to 2003? Then
> > > add the new server as a 2003 child primary, after the install, make the new
> > > server the Central site? To remove the old servers, point the rest of the
> > > child primary sites to the new server? Should we upgrade the rest of the
> > > child Primary sites to 2003 prior to connecting to the new Central site?
> > >
-- Check out the SMS Technical FAQ: http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default .mspx
- Next message: Allan Tee: "Re: MP.MSI exited with return code: 1603"
- Previous message: Kim Oppalfens: "Re: SMS 2003 Scan Tools Question"
- In reply to: Jacob: "Re: 2.0 to 2003 Migration Questions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
