"Freaky" <> wrote in message
news:OUK$...
> Hi there,
>
> we have some weird issues. We're running WSUS 3.2.7600.226 and are
> seeing some weird things.
>
> All workstations here are English Windows XP. They were all installed
> with the same procedure (RIS) and all have identical hardware. Some
> software is pushed through AD GPO's. The only thing that is installed
> manually is Microsoft Dynamic CRM 4.0 with update 3.
>
> The issue is the following, according to WSUS all machines have Office
> 2007 SP2 installed and KB951748 would also be installed according to WSUS.
>
> Apparently the Office service packs are only partially in many cases.
> Whilst office nicely reports in it's version that it has SP2,
> microsoftupdate frequently shows SP2 and in some cases shows SP1 (after
> this is installed it will show SP2... which is weird because afaik SP2
> is cumulative and should contain all SP1 updates).
>
> These service pack installs are usually done in 5 seconds or so, which
> probably means it's just a small part of the service pack that isn't
> properly installed or detected.
>
> The KB951748 shows up on all computers in microsoftupdate whilst
> according to WSUS it is already installed on all computers.
>
> Anyone else seen this behaviour and/or know a solution?
I'm not exactly sure what the question is. :-/
Nor what KB951748 has to do with Office 2007 or office updates in general.
KB951748 is a 16 month old DNS client update that should have been installed
eons ago, and is probably rolled up into every current service pack (except
XP SP3 which predates KB951748).
As for the question of what MU displays as Needed -- it's not unlikely that
SP2 has dependencies that are not installed, and thus SP1 would be presented
because SP2 is *notInstallable* at that moment.
> It would be nice if I could actually trust WSUS.
I'm curious as to why a minor difference in what is detected by WSUS and
WU/MU would challenge your trust levels in WSUS. Unless you've configured
your WSUS server to be an absolute clone of Microsoft Update, it's pefectly
normal that there would be discrepancies:
1. There are updates on MU you cannot get on WSUS.
2. There are updates on MU you may have chosen not to synchronize to WSUS.
3. There may be updates on MU that you've declined on WSUS.
> Can anyone clarify whether or not the detect process between WSUS
> and microsoft update differs?
The detection process, as performed by the Windows Update Agent, is
identical between WSUS, WU, MU, and AU. What differs in those three sources
is the *catalog*.
> Next to that most are missing KB973923 (Microsoft Visual C++ 2005
> Service Pack 1 Redistributable Package update).
This update has very selective applicability. It's been the subject of much
discussion between the content people and myself over this selective
applicability, as well as the product categoryies chosen for distribution.
However, aside from the standard applicability that the Visual C++ 2005
runtimes have to be installed to begin with, very few applications actually
use the VS2005 C++ runtimes.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog:
http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:
http://www.microsoft.com/wsus
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin
Linear Mode
