What does 'Not Installed' actually mean?

I've recently set up WSUS and it's all working OK apart from a couple of
updates related to Microsoft Office. There are two updates: one is Office
2007 SP2 and the other is Office Compatibility Pack SP2.

I have some PCs that have been showing one or the other of these updates as
'Needed' for several days. It's the only update these PCs need. Running a
report shows the Approval as 'Install' and the Status as 'Not Installed'.
I'm not clear what 'Not Installed' means -- does it come before 'Downloaded'
or afterwards?

Also, does anyone have any idea why these two updates should be so reluctant
to install themselves?

--
Michael

"Michael M Mason" <> wrote in message
news:%23oJO6%...
> I've recently set up WSUS and it's all working OK apart from a couple of
> updates related to Microsoft Office. There are two updates: one is Office
> 2007 SP2 and the other is Office Compatibility Pack SP2.
>
> I have some PCs that have been showing one or the other of these updates
> as 'Needed' for several days. It's the only update these PCs need.
> Running a report shows the Approval as 'Install' and the Status as 'Not
> Installed'. I'm not clear what 'Not Installed' means -- does it come
> before 'Downloaded' or afterwards?

It means exactly what it says. The update is Not (yet) Installed.

Why it's not installed is a sub-status that's available if you click on the
"Not Installed" hyperlink in the report, which will bring up a status dialog
and give you the rest of the information.

> Also, does anyone have any idea why these two updates should be so
> reluctant to install themselves?

The most common reason an Office Update won't install from WSUS is because
Office has been installed in Per-User mode.

However, have you confirmed that the update(s) have downloaded the content
to the WSUS Server? If the content is not successfully downloaded, the
clients will not be able to download (or install) either.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "Michael M Mason" <> wrote in message
> news:%23oJO6%...
>> I've recently set up WSUS and it's all working OK apart from a couple of
>> updates related to Microsoft Office. There are two updates: one is
>> Office 2007 SP2 and the other is Office Compatibility Pack SP2.
>
> The most common reason an Office Update won't install from WSUS is because
> Office has been installed in Per-User mode.

What does 'Per-User mode' mean?


> However, have you confirmed that the update(s) have downloaded the content
> to the WSUS Server? If the content is not successfully downloaded, the
> clients will not be able to download (or install) either.

The content is downloaded OK, and Office updates have been working fine up
until now.

I've had a look at the WindowsUpdate.log file on the recalcitrant machines.
I've included the details from one machine that I rebooted, and it looks to
me like the PC knows where the WSUS server is (http://ron is correct for my
LAN). However, it's contacting something called a Regulation Server at
microsoft.com, and being told that 'BCE161EA-FAF8-475F-8D56-67170B418C77 is
"PerUpdate" regulated and can NOT download.'

I have no idea what that means.


QUOTE FROM LOGFILE:

2009-06-22 16:00:39:546 1152 784 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: +0100) ===========
2009-06-22 16:00:39:609 1152 784 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-06-22 16:00:39:609 1152 784 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-06-22 16:00:39:546 1152 784 Service *************
2009-06-22 16:00:39:609 1152 784 Service ** START ** Service: Service
startup
2009-06-22 16:00:39:609 1152 784 Service *********
2009-06-22 16:00:39:609 1152 784 Agent * WU client version 7.2.6001.788
2009-06-22 16:00:39:609 1152 784 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-06-22 16:00:39:609 1152 784 Agent * Access type: No proxy
2009-06-22 16:00:39:609 1152 784 Agent * Network state: Connected
2009-06-22 16:01:27:452 1152 784 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-06-22 16:01:27:452 1152 784 Agent *********** Agent: Initializing
global settings cache ***********
2009-06-22 16:01:27:452 1152 784 Agent * WSUS server: http://ron
2009-06-22 16:01:27:452 1152 784 Agent * WSUS status server: http://ron
2009-06-22 16:01:27:452 1152 784 Agent * Target group: Customer Services
2009-06-22 16:01:27:452 1152 784 Agent * Windows Update access disabled:
No
2009-06-22 16:01:28:068 1152 784 Agent * Found 1 persisted download calls
to restore
2009-06-22 16:01:28:170 1152 784 DnldMgr Download manager restoring 1
downloads
2009-06-22 16:01:29:350 1152 784 Agent * Successfully loaded 1 persisted
download calls.
2009-06-22 16:01:29:436 1152 784 AU ########### AU: Initializing Automatic
Updates ###########
2009-06-22 16:01:29:436 1152 784 AU # WSUS server: http://ron
2009-06-22 16:01:29:436 1152 784 AU # Detection frequency: 22
2009-06-22 16:01:29:436 1152 784 AU # Target group: Customer Services
2009-06-22 16:01:29:453 1152 784 AU # Approval type: Scheduled (Policy)
2009-06-22 16:01:29:453 1152 784 AU # Scheduled install day/time: Every
day at 3:00
2009-06-22 16:01:29:453 1152 784 AU # Auto-install minor updates: Yes
(Policy)
2009-06-22 16:01:29:487 1152 784 AU # Reconnecting download for 1 updates
2009-06-22 16:01:29:487 1152 784 AU # Reconnected 1 pending download calls
2009-06-22 16:01:29:487 1152 784 AU Setting AU scheduled install time to
2009-06-23 02:00:00
2009-06-22 16:01:29:504 1152 784 AU AU setting pending client directive to
'Download Progress'
2009-06-22 16:01:29:504 1152 784 AU AU finished delayed initialization
2009-06-22 16:01:29:880 1152 784 Report *********** Report: Initializing
static reporting data ***********
2009-06-22 16:01:29:880 1152 784 Report * OS Version = 5.1.2600.3.0.65792
2009-06-22 16:01:29:914 1152 784 Report * Computer Brand = Dell Inc.
2009-06-22 16:01:29:914 1152 784 Report * Computer Model = Vostro 200
2009-06-22 16:01:29:914 1152 784 Report * Bios Revision = 1.0.10
2009-06-22 16:01:29:914 1152 784 Report * Bios Name = Phoenix - AwardBIOS
v6.00PG
2009-06-22 16:01:29:914 1152 784 Report * Bios Release Date =
2007-12-15T00:00:00
2009-06-22 16:01:29:914 1152 784 Report * Locale ID = 2057
2009-06-22 16:01:29:914 1152 1b4 DnldMgr *********** DnldMgr: Regulation
Refresh [Svc: {7971F918-A847-4430-9279-4A52D1EFE18D}] ***********
2009-06-22 16:01:29:914 1152 1b4 DnldMgr Contacting regulation server for 1
updates.
2009-06-22 16:01:29:914 1152 1b4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\wuredir.cab:
2009-06-22 16:01:29:983 1152 1b4 Misc Microsoft signed: Yes
2009-06-22 16:01:29:983 1152 1b4 DnldMgr Regulation server path:
http://update.microsoft.com/v6/Updat...egulation.asmx.
2009-06-22 16:01:30:393 1152 1b4 DnldMgr Per-Update:
bce161ea-faf8-475f-8d56-67170b418c77 at rate 0
2009-06-22 16:01:30:393 1152 1b4 DnldMgr * Regulation call complete.
0x00000000
2009-06-22 16:01:30:393 1152 1b4 DnldMgr *********** DnldMgr: New download
job [UpdateId = {BCE161EA-FAF8-475F-8D56-67170B418C77}.102] ***********
2009-06-22 16:01:30:393 1152 1b4 DnldMgr Regulation:
{7971F918-A847-4430-9279-4A52D1EFE18D} - Update
BCE161EA-FAF8-475F-8D56-67170B418C77 is "PerUpdate" regulated and can NOT
download. Sequence 2178 vs AcceptRate 0.
2009-06-22 16:01:30:393 1152 1b4 DnldMgr * Update is not allowed to
download due to regulation.
2009-06-22 16:01:30:393 1152 1b4 DnldMgr Regulation:
{7971F918-A847-4430-9279-4A52D1EFE18D} - Update
BCE161EA-FAF8-475F-8D56-67170B418C77 is "PerUpdate" regulated and can NOT
download. Sequence 2178 vs AcceptRate 0.
2009-06-22 16:01:30:393 1152 1bc AU AU checked download status and it
changed: Downloading is paused
2009-06-22 16:01:45:389 1152 784 AU No pending client directive

--
Michael

"Michael M Mason" <> wrote in message
news:%...
> "Lawrence Garvin [MVP]" <> wrote in message
> news:...
>> However, have you confirmed that the update(s) have downloaded the
>> content to the WSUS Server? If the content is not successfully
>> downloaded, the clients will not be able to download (or install) either.
>
> The content is downloaded OK, and Office updates have been working fine up
> until now.

Some further information. I tried pointing one of the recalcitrant PCs at
Microsoft Update, and it cheerfully downloaded and installed the problematic
Office update.

I notice that both of the updates I'm having trouble with were released on
June 9th. This just happens to be a day or two before I rolled out WSUS to
all our workstations after trying it out for a couple of months on a few
machines. Is it possible that the PCs that I'm having trouble with had
already found the Office updates but been unable to download them (June 9th
being Update Tuesday) and after they got switched to WSUS they've been
confused about where the update is supposed to be coming from?

--
Michael

"Michael M Mason" <> wrote in message
news:%...
>
> "Lawrence Garvin [MVP]" <> wrote in message
> news:...
>> "Michael M Mason" <> wrote in message
>> news:%23oJO6%...
>>> I've recently set up WSUS and it's all working OK apart from a couple of
>>> updates related to Microsoft Office. There are two updates: one is
>>> Office 2007 SP2 and the other is Office Compatibility Pack SP2.
>>
>> The most common reason an Office Update won't install from WSUS is
>> because Office has been installed in Per-User mode.
>
> What does 'Per-User mode' mean?

Office can be installed for the specific user performing the installation,
or can be installed for the machine (for ALL users).

> However, it's contacting something called a Regulation Server at
> microsoft.com, and being told that 'BCE161EA-FAF8-475F-8D56-67170B418C77
> is "PerUpdate" regulated and can NOT download.'

This is evidence that the machine may have been attempting to download (and
install) updates from AU when the policy was applied to reassign it to the
WSUS Server. The 'regulated downloads' are what's in the BITS queue for
download from AU. Generally this can be resolved by flushing the BITS queue,
and rerunning a detection:

BITSADMIN /RESET /ALLUSERS

WUAUCLT /RESETAUTHORIZATION /DETECTNOW


> 2009-06-22 16:01:28:068 1152 784 Agent * Found 1 persisted download
> calls to restore
> 2009-06-22 16:01:28:170 1152 784 DnldMgr Download manager restoring 1
> downloads
> 2009-06-22 16:01:29:350 1152 784 Agent * Successfully loaded 1 persisted
> download calls.

This is it.... likely a left-over download from before the machine was
assigned to the WSUS Server.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Michael M Mason" <> wrote in message
news:%...
> "Michael M Mason" <> wrote in message
> news:%...
>> "Lawrence Garvin [MVP]" <> wrote in message
>> news:...
>>> However, have you confirmed that the update(s) have downloaded the
>>> content to the WSUS Server? If the content is not successfully
>>> downloaded, the clients will not be able to download (or install)
>>> either.
>>
>> The content is downloaded OK, and Office updates have been working fine
>> up until now.
>
> Some further information. I tried pointing one of the recalcitrant PCs at
> Microsoft Update, and it cheerfully downloaded and installed the
> problematic Office update.

Not unexpected at all. Essentially you allowed it to complete an event
already in progress when you assigned it to use the WSUS Server.

> I notice that both of the updates I'm having trouble with were released on
> June 9th. This just happens to be a day or two before I rolled out WSUS
> to all our workstations after trying it out for a couple of months on a
> few machines.

<VBG>... the timing fits too. The machines grabbed the update availability
from AU before you rolled out the WSUS policy, but the downloads (perhaps
because of bandwidth availability, the size of the update package, or the
power status of the client machine) did not complete prior to the WSUS
policy being enforced.


> Is it possible that the PCs that I'm having trouble with had already found
> the Office updates but been unable to download them (June 9th being Update
> Tuesday) and after they got switched to WSUS they've been confused about
> where the update is supposed to be coming from?

:-)


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "Michael M Mason" <> wrote in message
> news:%...
>> I notice that both of the updates I'm having trouble with were released
>> on June 9th. This just happens to be a day or two before I rolled out
>> WSUS to all our workstations after trying it out for a couple of months
>> on a few machines.
>
> <VBG>... the timing fits too. The machines grabbed the update availability
> from AU before you rolled out the WSUS policy, but the downloads (perhaps
> because of bandwidth availability, the size of the update package, or the
> power status of the client machine) did not complete prior to the WSUS
> policy being enforced.

Many thanks for your patient explanations: it all makes sense now!

--
Michael