Re: SMS 2003 and Site Names
From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 10/21/04
- Next message: Kim Oppalfens: "Re: reinstallation for a crashed SMS server"
- Previous message: Bill: "Re: SMS 2003 and Site Names"
- In reply to: Bill: "Re: SMS 2003 and Site Names"
- Next in thread: Bill: "Re: SMS 2003 and Site Names"
- Reply: Bill: "Re: SMS 2003 and Site Names"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 21 Oct 2004 16:30:33 +0200
Sms 2003 sites can not report to an sms 2003 parent.
So you would have to upgrade the primary site sms 2.0 first.
The thing I don't understand is you want to migrate clients, if you
upgrade there should be no need for this. Unless you mean install the
new client version with migrating.
Step 5 won't be an option since it has the secondary sites attached, you
would orphan these sites if you did this. And as already mentionned
there is no way to reattach secondary sites without a full
reinstallation.
Kim Oppalfens
In article <1CC7F078-C341-474C-BCD1-40AAB8F348D3@microsoft.com>,
Bill@discussions.microsoft.com says...
> So, if I bring the new 2003 server into production, and then attach the
> current Primary 2.0 Site to the new 2003 site (with the Secondary 2.0 sites
> still reporting to the Primary 2.0 site), there's no way for me to upgrade
> the Secondary Sites without migrating all the clients at the same time?
> Doesn't give me a chance to test clients at the Secondary sites.
>
> I guess what I'm looking for is a step-by-step process of what I should do.
> Feel free to modify this:
>
> 1. Install SMS 2003 site on new hardware in production (after testing in
> lab, of course).
> 2. Attach current SMS 2.0 site to new SMS 2003 site (I've read somewhere
> you have to do this, but I may be wrong).
> 3. Migrate clients from Primary 2.0 site to new SMS 2003 site.
> 4. Upgrade Secondary Sites to SMS 2003.
> 5. Migrate Secondary Site clients to SMS 2003.
> 5. Uninstall SMS 2.0 Site.
>
> If this is right, I'm wondering what will happen to the Secondary Site
> clients between steps 4 and 5. Will they still be reporting to the 2.0 site?
>
> Thanks.
>
> "Kim Oppalfens" wrote:
>
> >
> > AFAIK, there is no way of attaching a secondary site to a new parent
> > without completely reinstalling the secondary site. So no this is not
> > correct.
> >
> > Kim Oppalfens
> > In article <CEB1B4DF-FD82-4581-A615-A27C98672FFC@microsoft.com>, "=?Utf-
> > 8?B?QmlsbCBHdXNodWU=?=" <Bill Gushue@discussions.microsoft.com> says...
> > > Ah, I see your point. I was confusing myself into thinking there would be
> > > side-by-side Secondary Sites also, but there is no need for that.
> > >
> > > So, I will install SMS 2003 on the new server with a new site code. Once
> > > this is installed, I will have to make the 2.0 site a child of the 2003 site,
> > > correct?
> > >
> > > Also, I want to continue to have a functional site during the migration, so
> > > if I upgrade a Secondary Site to SMS 2003, will the SMS 2.0 clients still
> > > report to the 2.0 site and function normally, or will they have to be
> > > migrated immediataly after the upgrade?
> > >
> > > Current Hierarchy:
> > >
> > > Primary 2.0 Site
> > > 4 Secondary 2.0 Sites
> > >
-- Check out the SMS Technical FAQ: http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default .mspx
- Next message: Kim Oppalfens: "Re: reinstallation for a crashed SMS server"
- Previous message: Bill: "Re: SMS 2003 and Site Names"
- In reply to: Bill: "Re: SMS 2003 and Site Names"
- Next in thread: Bill: "Re: SMS 2003 and Site Names"
- Reply: Bill: "Re: SMS 2003 and Site Names"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
