Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: RobM <robM@xxxxxxxx>
- Date: Tue, 12 Dec 2006 14:49:50 +0000
Hi, ask away and remember either path either in-place or side-by-side
works. I prefer side-by-side and totally detatched environments as i
don't like SMS2.0 data entering an SMS2003 server but sometimes the
route you take means you do have to attach 2.0 to 2003 systems such as
carrying the data from the old environment in to the new for continued
reporting and trending of the historical data from the one
environment. It depends on how you want to approach the migration is
all, neither approach is more right or wrong than the other. Both
provide disavantages and benefits.
Also, you should definately read the SMS documention throughly to make
sure you understand all the new roles and what they depend on, and
what has changed between 2.0 and 2003.
http://www.microsoft.com/smserver/techinfo/productdoc/default.mspx#EEH
i cannot stress this enough, etch out a design plan for an upgrade and
a side-by-side. take in to account the options both routes provide,
and the admin hassle. put together a list of wants, i want to retain
data, i want a fresh environment, i want to do as little as possible
etc. scope out the new roles and features sms2003 provides and work
those in to your plan. understand local\remote roaming model,
publishing to the A/D and why its needed and what its used for. Also
document each of the processes and determine the steps needed say for
preparing the secondary for sms2003 so you can repeat these steps in a
controlled and documented fashion.
from 10 cents of advise to 20 heh
RTM ;-)
if you want to bounce ideas about with me then visit my website and
take this thread there :>
see below
On 11 Dec 2006 08:43:20 -0800, "patnerd"
<padraig.denihan@xxxxxxxxxxxxxx> wrote:
Rob,
Appreciate your input very much. Can I follow-up with questions in-line
in your replies below please?
Thanks,
Padraig.
RobM wrote:
For the upgrade path check this out:(PD - What do we have to do to 'configure the OS to support the new
Upgrading from SMS 2.0 to SMS 2003
http://www.microsoft.com/smserver/techinfo/upgrade.mspx
A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL
replication is configured on the site database in Systems Management
Server 2003
http://support.microsoft.com/kb/886629
SMS 2003: Preparing for Migration/Installation
http://www.myitforum.com/articles/8/view.asp?id=6657
On Mon, 11 Dec 2006 11:05:13 +0000, RobM <robM@xxxxxxxx> wrote:
my ten cents worth ... see inline
On 11 Dec 2006 02:09:53 -0800, "patnerd"
<padraig.denihan@xxxxxxxxxxxxxx> wrote:
Hi all,
We are belatedly upgrading from SMS 2.0 to SMS 2003. We have one
Primary site and 50+ Secondary Sites spread across the country with
varying WAN links 256Kb up to 1Mb. What we really want to do is replace
the Primary Site Server hardware as it is old and under spec. We also
want to upgrade all the sites to SMS 2003. We mostly want to keep the
hierarchy intact but allow the option of recreating or consolidating
secondary sites as some of them are throwing errors under SMS 2.0 . All
the clients are XP. All the servers are W2K3. Domain is AD W2K3 Native.
I have not found the docs to be crystal clear on an approach we can
take to this. My assumed way to go ("side-by-side" upgrade?):
- Build new site server hardware
- Install SMS 2003 on that giving it a brand new site name
- Make the existing Primary a child of this new Primary
- Upgrade secondary sites OR consolidate (by re-homing clients via Site
boundaries and pushing out client s/ware)
I'd go for side-by-side, clean slate and more control. untainted
database. I would not connect the sms 2.0 site to the new environment,
keep it pristine. you could perform an in-place upgrade but i like
everything new and shiny :>
Build new site server hardware
Install SMS 2003 on that giving it a brand new site name
Create an upgrade schedule for all 50 secondaries
Start with 1st secondary,
Push the sms2003 adv client to the clients at the secondary site
Deinstall the sms 2.0 secondary, configure the OS to support the new
sms2003 secondary site
SMS2003 secondayr site?)
then perform an install from the new sms2003
the preparation guide will advise on how to configure your OS\system
in readiness for sms2003 to be installed. See the following link:
http://www.microsoft.com/technet/prodtechnol/sms/smssp2/supconfig/0bdafa4a-71b3-4ed6-94bb-42a9f3986951.mspx?mfr=true
pri\central.
Setup the secondaries boundaries (PD - presumably to be the same as the orifgianl SM 2.0 boundaries - the IPs have not changed) and configure the site settings
same boundaries but consider falling back on AD Sites instead of
subnets as this allows you to manage a sites subnets from one place,
the active directory rather than on the site server itself.
See
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/cpdg/plan4kv9.mspx?mfr=true
section Evaluating Active Directory Site Membership
Clients at the secondary site should auto-assign to the secondary once
everything is configured correctly. (PD - would the 2003 site code be the same as the original 2.0 one? )
If you are performing an upgrade then it'll use the current sitecode,
if its a new site server choose a new sitecode. advanced clients
assign to a primary by design, not a secondary but they will use the
secondaries proxy management point and DP. RTM this in the sms
documentation for more info.
If they do not then there are some
tools you can use to remotely assign them (PD - waht are the tools, could you point s at them?)
lots of tools to choose from, here's a link to one:
http://blogcastrepository.com/blogs/brian_tucker/archive/2005/02/07/55.aspx
but auto-assignment should
work and if it doesn't should be investigated rather than worked
around. But if it's a live production rollout and you must keep the
clients in-communication with a site then the tools can be used as an
emergency work-around for assignments.
Repeat for the other 49 secondaries
Alternatively you could perform discovery of clients at the
pri\central and perform a push of the client after rather than before
your upgrade.
others in the group can elaborate, expand and\or correct the above.
Questions:
- If we do it this way - what about the existing 2.0 Primary site -
what happens to that?
if you perform side-by-side then once all clients have migrated to new
environment, archive\backup the 2.0 environment and either leave it
switched on for reporting puproses or turn the light out ;-)
(PD - Here I meant if we had linked it as a child of the new 2003if you've upgraded it to sms2003 and pushed secondaries out from it
then you can't do anything except retain it due to the relationship a
secondary has with it's primary.
primary. I presume in your recommended setup above, the original 2.0
primary eventually ends up empty? Will it function as normal during the
migration, i.e. we will have 2 parallel hierarchies?)
Yes, two environments. you'll be able to migrate clients according to
a plan, on a site-by-site basis or by breaking the sites clients down
and migrating in batches. once all clients have migrated off the 2.0
environment, see aboves comment about what to do with it.
(PD - is that what you are recommending, i.e. de-install 2.0 and
- as you upgrade Secondaries, do those sites 're-home' automatically to
be direct children of the new SMS 2003 Primary site?
nope. a secondary site is intimately linked with it's pri and this
association will not change. to get these secondaries to connect to
the new pri you would have to deinstall them and perform the install
from the new pri
re-install as 2003 on every Secondary site server?)
if you upgrade from the central downwards then you can upgrade the 2.0
secondaries to 2003. if you do perform an upgrade then the sms2.0
client can communicate with a 2003 site and will upgrade to the
sms2003 legacy client which allows you to then upgrade to the advanced
client. if you do side-by-side then yes deinstall the 2.0 secondary
then tell the sms2003 primary to install a secondary. secondaries have
one owner for their entire lifecycle, the primary they are associated
with during installation time. there is no way to make a secondary
point at a new primary without reinstalling.
(PD - sorry I dont know what these mof's refer to?)
- as you upgrade Secondaries (not consolidating), do clients
automatically upgrade to Advanced Client s/w or do you have to do
Client Push/Software Distribution as you go
nope. you would have to push the software out to the new clients.
sms2003 adv client does not perform a maintenance check as does 2.0 so
to upgrade clients you have to manually deal with the client upgrade.
same applies to modified mofs you have to send a job down to them to
mofcomp the new mof.
If you haven't modified your site MOF then this is a subject you can
RTM later on. If you have a modified MOF then google how to manage
implementing the MOF on your sms2003 advanced clients.
(PD - I mean something like 1) backup the 2.0 site DB, 2) replace the
- is there a way to just replace the Central/Primary site hardware,
i.e. effectively 'swap out' the old SMS 2.0 server and leave everything
beneath it intact. Then I assume we could just do in-place upgrades
across the board?
not really, the secondaries are hard coded to the 2.0 primary so this
option wouldn't work
hardware, 3) restore the 2.0 site DB, 4) proceed with an in-place
upgrade. Are you saying that for us to get a new server in as the 'top
of the tree', we have to go down the route you describe, i.e.
unistall/reinstall on all the 2.0 secondaries?)
nope, you can put the current central site on to the new hardware then
perform an upgrade. you need to pen and paper both processes to see
which one suits both your environment, you and your needs.
--
We have tried to build a test bed to dry run the upgrade effort but we
are more confused than before. As you can see, we'd appreciate some
guidance!
Thanks in advance
Padraig.
hope this helps.
-
Rob - Windows Management User Group
www.wmug.co.uk
Rob - Windows Management User Group
www.wmug.co.uk
Rob - Windows Management User Group
www.wmug.co.uk
.
- References:
- Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: patnerd
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: RobM
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: RobM
- Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- From: patnerd
- Need guidance on SMS 2.0 to 2003 Upgrade approach
- Prev by Date: Creating a collection based on program not installed.
- Next by Date: Re: Obsolete entries and Collection Direct Membership
- Previous by thread: Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
- Next by thread: Re: (probably stupid) question.... : Vista vs. SMS 2.0 ?
- Index(es):
Relevant Pages
|
