Re: Move SMS 2003 to another server
- From: "Steve Thompson" <stevethompson@xxxxxxxxxxxxx>
- Date: Wed, 8 Nov 2006 13:58:16 -0500
"Matt Hendrickson" <MattHendrickson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:D4323363-4B38-40D2-9686-F017771EBA2E@xxxxxxxxxxxxxxxx
There are two ways you can go with a new install; since you have a number
of
clients already assigned, it may make sense to install SMS with the same
site code as defined before.
Are there any negatives to reinstalling SMS with the existing site code?
We
are in a similar situation at my company (thousands of existing clients,
new
SMS central server with new server name) and I talked to an MS rep who
recommended changing the site code to avoid issues. I'd like to avoid
changing the site code, if possible.
If you have extended Active Directory with the SMS extensions it will work
fine keeping the same site code (I've done it). I've seen some issues with
re-installing SMS, using the same site code, with clients not obtaining a
valid certificate in a non-extended AD environment. Perhaps that's why your
MS contact recommended the change...
As I mentioned in another recent posting, one of the advantages of changing
the site code, it's easy to tell that you are assimilating the clients into
the new environment. There are other techniques you can use to determine the
health of SMS clients, however all require a little more expertise.
Steve
.
- References:
- Re: Move SMS 2003 to another server
- From: Steve Thompson
- Re: Move SMS 2003 to another server
- From: Lisa@
- Re: Move SMS 2003 to another server
- From: Steve Thompson
- Re: Move SMS 2003 to another server
- From: Matt Hendrickson
- Re: Move SMS 2003 to another server
- Prev by Date: Re: Move SMS 2003 to another server
- Next by Date: Failed to get a SQL Server connection
- Previous by thread: Re: Move SMS 2003 to another server
- Next by thread: Re: Move SMS 2003 to another server
- Index(es):
Relevant Pages
|
Loading