Inplace Upgrade os SMS2.0 to 2003

I have been tasked with upgrading our current SMS2.0 installation to SMS2003,
and would like people’s advice on the way to go and any pitfalls / problems
people may have found when upgrading.

Currently our SMS 2.0 Installation consists of a Central Site Server and one
Primary Child Site Server; both of these servers are in different locations
and are connected by a WAN link. Both servers have the following roles,
Client Access Point, Component Server, Distribution Point, Site Server and
SQL Server. On the Central Site server there are roughly 700+ clients, a
mixture of Windows 95, 98, NT4.0, 2000 Server & Pro, XP and 2003 Server. On
the Primary Child Site there are roughly 170+ clients; again a mixture of
Windows 95, 98, NT4.0, 2000 Server & Pro, XP and 2003 Server. Also there are
around 90 packages and 40 Advertisements . In the central site there is also
another server that is being used as a SMS Distribution Point.

I recently ran the Deployment Readiness Wizard on both the Central Site and
Primary Site server and when reviewing the log it has discovered some issues,
for example.

Several machines have unsupported Operating Systems; this I think is due to
the installed client not reporting the OS back to the SMS database.

It has detected a lot of inactive clients, presumable I can remove these and
let SMS 2003 rediscover.

I also have quite a few clients reporting Duplicate Client Id’s.

One of the Distribution Points has out-of-date packages

A lot of the problems, especially the unsupported O/S, seem to be where the
Client software hasn’t reported back the correct information.

My main questions on the upgrade are:

Site Boundaries – Are these retained or do I have to write down all of the
existing site boundaries? Can overlapping Site boundaries be used?, I have
some clients that are at each site that sit on the same IP subnet.

Servers – What order do I need to upgrade?, Central Site first or Child Site?

Clients – How do I go about upgrading all the Windows 2000 or above clients
to the Advance Client, will this be done automatically when SMS is upgraded?
Do I need to upgrade the clients before I perform the Upgrade of the Servers?

Packages/Advertisements – Are these retained or upgraded?

Is there any other advice you can give

Many Thanks




.

Relevant Pages

  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... you should definately read the SMS documention throughly to make ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Create an upgrade schedule for all 50 secondaries ...
    (microsoft.public.sms.admin)
  • RE: NT clients after 2K3 server upgrade
    ... it seems that the NT clients cannot find ... The following article describes how to install a WINS server on Win2k3 ... I would like give you the detailed upgrade ... 5.Use the Windows Server 2003 Active Directory wizard to turn on the Active ...
    (microsoft.public.windows.server.migration)
  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... Upgrading from SMS 2.0 to SMS 2003 ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Create an upgrade schedule for all 50 secondaries ...
    (microsoft.public.sms.admin)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... the distribution points so I know which ones need updating? ... >> Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)