Re: Inplace Upgrade os SMS2.0 to 2003
- From: Kim Oppalfens <kim@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Sep 2005 14:07:06 +0200
You could run an md5 hash on the original sources, and compare that with
the folders on the dp. But there is no automated way of comparing
folders using sms that I know of.
Kim
In article <AAFFA199-6B5F-4D24-951E-E0F65C2CA501@xxxxxxxxxxxxx>,
Paul@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> Kim,
> On the Package issue, is there a way of comparing the packages installed on
> the distribution points so I know which ones need updating?
> Thanks
> Paul
>
> "Kim Oppalfens" wrote:
>
> >
> > 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.
--
Kim Oppalfens
MVP SMS
Computacenter Belgium
.
- References:
- Inplace Upgrade os SMS2.0 to 2003
- From: Paul
- Re: Inplace Upgrade os SMS2.0 to 2003
- From: Kim Oppalfens
- Re: Inplace Upgrade os SMS2.0 to 2003
- From: Paul
- Inplace Upgrade os SMS2.0 to 2003
- Prev by Date: Re: Inplace Upgrade os SMS2.0 to 2003
- Next by Date: Advanced client installation problem
- Previous by thread: Re: Inplace Upgrade os SMS2.0 to 2003
- Next by thread: SMS 2003 Advanced Client and On Command CCM Client
- Index(es):
Relevant Pages
|
