Re: Moving Server Options
- From: "Three Toed Sloth" <ThreeToedSloth@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 8 May 2005 17:58:03 -0700
Thankyou for your response.
I'm assuming that there are no other options for moving the site?
I understand that option 1 is the preferred method - it may not be feasible
in this instance.
In terms of option 2, AD has been extended so it isn't all bad news!
Regards,
Marc
"Stan White [MS]" wrote:
> We usually recommend option 1, and we've seen it succeed countless times.
>
> Option 2 can have issues, not only with data loss but the clients won't
> re-assign to a new site code without forcing them to the new site.
> Even if the site code is the same, the clients will not trust the MP and
> Site server particularly if they were on the same machine.
> (If you have AD extended it gets easier because the public keys are
> published in AD so the client can trust the site and MP)
> If AD is not extended you'll need to force the clients to the new 'machine'
> either by a push from the 'new' site server or clearing the public key
> information from the client so it trusts the new site.
>
> --
> --
> Stan [MSFT]
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> --
>
> "Three Toed Sloth" <ThreeToedSloth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:FF9AE9F6-D820-4BC4-A63F-3F2C82127B3A@xxxxxxxxxxxxxxxx
> >I have installed SMS2003 and had it running for 9 months. Management has
> > found it to their liking and have purchased a shiny new to server to move
> > it
> > to - the old one being close to the end of its life. I have read a number
> > of
> > posts about this scenario have seem to have two options.
> >
> > 1. Use the recovery expert as per the Backup Recovery and Maintenance
> > guide.
> > This requires that the new server take the name of the old server which
> > means
> > I can't do the sms move until I have finished with everything else on the
> > old
> > server and my sms site server will ALWAYS have the same name no matter how
> > often it gets replaced.
> >
> > 2. Print out reports of historical data I want to keep, remove the site
> > from
> > the domain and then install a new primary site on the new server. If I use
> > the current site code 'maybe' my clients will report in to the new server
> > otherwise I have to manipulate all the clients.
> >
> > Is this an accurate summary of my options? I'm trying to get an
> > understanding of what my options are so we can decide which way to go.
> >
> > Regards,
> >
> > Marc
>
>
>
.
- Follow-Ups:
- Re: Moving Server Options
- From: Stan White [MS]
- Re: Moving Server Options
- References:
- Re: Moving Server Options
- From: Stan White [MS]
- Re: Moving Server Options
- Prev by Date: Re: The remote server returned an error: (500) Internal Server Err
- Next by Date: Re: Advertisement status not updating
- Previous by thread: Re: Moving Server Options
- Next by thread: Re: Moving Server Options
- Index(es):
Relevant Pages
|
