Re: Inplace Upgrade os SMS2.0 to 2003


I'll comment inline.
In article <E469A059-F39E-42D4-8F7E-9EA4B68DEEEE@xxxxxxxxxxxxx>,
>
> 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.

That could be the case, or you might have machines running windows 95
which are not supported.
>
> It has detected a lot of inactive clients, presumable I can remove these and
> let SMS 2003 rediscover.
Yups.
>
> I also have quite a few clients reporting Duplicate Client Id�s.
You can better clean these up as well.
>
> One of the Distribution Points has out-of-date packages
Easiest solution would be to remove the distribution point and reinstall
it once the sms 2003 site is up. This will come with a pretty high
network load since all packages need to be copied over again.

Cleanest solution would be to solve the distribution point issue before
upgrading.

I am not quite sure which one to advise, guess it depends on the speed
of the network and the number & size of the 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.
>
Site boundaries should be retained after the upgrade. To be sure you
could install the sms2.0 admin feature pack and export the
siteboundaries using the siteboun tool.

Two different sms2003 sites cannot have overlapping boundaries.

> Servers � What order do I need to upgrade?, Central Site first or Child Site?
Top to bottom, in other words central first, followed by child sites,
grandchild sites,....
>
> 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?

This depends on whether you plan to upgrade to sms 2003 rtm or sp1.
In rtm clients will be upgraded to legacy clients, and you should
upgrade them yourself to advanced clients.

In SP1 clients no longer upgrade automatically and you can upgrade them
directly to SP1 advanced clients using client push, software
distribution, manual or login script based installation, or GPO
deployment.

>
> Packages/Advertisements � Are these retained or upgraded?
Packages & advertisements should be retained.
>
> Is there any other advice you can give
Make sure you have a decent sms backup just in case, and test your
procedure in a lab environment.
>
> Many Thanks
>

--
Kim Oppalfens
MVP SMS
Computacenter Belgium
.

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)