WSUS and Office Updates.

I work for a company that has over 1,000 client PC's. I got WSUS running
just fine, but I noticed an issue I'm not sure how to correct.

Some client PC's that are reporting they need Office service packs or
updates are getting a "Failed" when the scheduled install date/time occurs.
95%-98% of my failures are occurring on "Office" updates.

I have the scheduled install time to be at 3am. But since not all PC's are
on during that time, the install occurs after they boot up their PC the next
day. I'm pretty sure the Failure is occurring on those PC's because they are
probably running their Outlook right after they log on. I don't think WSUS
will update client PC's Office if an Office product is currently running.

I was wondering if there was an easier way to correct this. I don't want to
have to tell them they can't use their PC's for the first 30 minutes each day
while the updates are installed.

Any ideas?

Thanks!

Look at %WINDIR%\Windowsupdate.log for the reason why the updates are failing.
It may be that an installation source is required and not available.

Try using MS Update to install once of the required updates and see if you get
any error messages from the GUI process that will help you understand what is
happening.

On Mon, 22 May 2006 17:13:01 -0700, gettps <gettps@discussions.microsoft.com>
wrote:

>I work for a company that has over 1,000 client PC's. I got WSUS running
>just fine, but I noticed an issue I'm not sure how to correct.
>
>Some client PC's that are reporting they need Office service packs or
>updates are getting a "Failed" when the scheduled install date/time occurs.
>95%-98% of my failures are occurring on "Office" updates.
>
>I have the scheduled install time to be at 3am. But since not all PC's are
>on during that time, the install occurs after they boot up their PC the next
>day. I'm pretty sure the Failure is occurring on those PC's because they are
>probably running their Outlook right after they log on. I don't think WSUS
>will update client PC's Office if an Office product is currently running.
>
>I was wondering if there was an easier way to correct this. I don't want to
>have to tell them they can't use their PC's for the first 30 minutes each day
>while the updates are installed.
>
>Any ideas?
>
>Thanks!
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

Hi,

Some reading for you...
More information on Office Updates viaa WSUS on www.wsuswiki.com;

Office Administrative Installs
www.wsuswiki.com/OfficeAdministrativeInstalls

Office Updates and WSUS support
http://www.wsuswiki.com/OfficeAIPs

Happy Patching,
Mohammed Athif Khaleel
http://msmvps.com/athif

I've been implementing Office 2003 updates from WSUS with no problem.
Office updates have no problem running with the applications running. It
will, though, usually require a reboot.

How is office installed on the workstations? Some implementations do not
do well with office updates.

As Dave says, first please to look is in "Windows Update.log" (note the
space in the name). That should give you any errors. Then either resolve
it or do a Google on the error.

Post here with the error if you need to.......

Regards,
Hank Arnold

gettps wrote:
> I work for a company that has over 1,000 client PC's. I got WSUS running
> just fine, but I noticed an issue I'm not sure how to correct.
>
> Some client PC's that are reporting they need Office service packs or
> updates are getting a "Failed" when the scheduled install date/time occurs.
> 95%-98% of my failures are occurring on "Office" updates.
>
> I have the scheduled install time to be at 3am. But since not all PC's are
> on during that time, the install occurs after they boot up their PC the next
> day. I'm pretty sure the Failure is occurring on those PC's because they are
> probably running their Outlook right after they log on. I don't think WSUS
> will update client PC's Office if an Office product is currently running.
>
> I was wondering if there was an easier way to correct this. I don't want to
> have to tell them they can't use their PC's for the first 30 minutes each day
> while the updates are installed.
>
> Any ideas?
>
> Thanks!

This is one of the errors:
2006-05-18 08:31:33 840 368 Report REPORT EVENT:
{E97CD8BB-5C79-4F16-8582-5405FECFBEFA} 2006-05-18
08:31:28-0400 1 195 101 {BE1F4943-76F2-4195-B7E0-9C2539D8BFDC} 52 8024002d AutomaticUpdates Failure Content
Install Installation Failure: Windows failed to install the following update
with error 0x8024002d: Office XP Service Pack 3.

I install Office using a network installation source. We always install
Office with all options because the source files are not available to the
clients.

I do use a slipstreamed installation source, but that can't be the problem
because I have lots of PC's that I installed with that source that ARE
updating just fine. Plus, all of my slipstreamed installations are in Office
2003, I am only showing 1 2003 failure and 20 Office XP SP3 failures. I
never used the Office XP slipstreamed source. We upgraded to 2003 before I
ever used it.

--
Gary Thompson
Florida State Technology Office
Department of Management Services


"Hank Arnold" wrote:

> I've been implementing Office 2003 updates from WSUS with no problem.
> Office updates have no problem running with the applications running. It
> will, though, usually require a reboot.
>
> How is office installed on the workstations? Some implementations do not
> do well with office updates.
>
> As Dave says, first please to look is in "Windows Update.log" (note the
> space in the name). That should give you any errors. Then either resolve
> it or do a Google on the error.
>
> Post here with the error if you need to.......
>
> Regards,
> Hank Arnold
>
> gettps wrote:
> > I work for a company that has over 1,000 client PC's. I got WSUS running
> > just fine, but I noticed an issue I'm not sure how to correct.
> >
> > Some client PC's that are reporting they need Office service packs or
> > updates are getting a "Failed" when the scheduled install date/time occurs.
> > 95%-98% of my failures are occurring on "Office" updates.
> >
> > I have the scheduled install time to be at 3am. But since not all PC's are
> > on during that time, the install occurs after they boot up their PC the next
> > day. I'm pretty sure the Failure is occurring on those PC's because they are
> > probably running their Outlook right after they log on. I don't think WSUS
> > will update client PC's Office if an Office product is currently running.
> >
> > I was wondering if there was an easier way to correct this. I don't want to
> > have to tell them they can't use their PC's for the first 30 minutes each day
> > while the updates are installed.
> >
> > Any ideas?
> >
> > Thanks!
>

I did read up on those before I posted, but they didn't seem to apply.

Those only seem to apply when the installation source is required for
operation. I always install Office with all options fully installed because I
know the source will not be available to the customers.

--
Gary Thompson
Florida State Technology Office
Department of Management Services


"Mohammed Athif" wrote:

> Hi,
>
> Some reading for you...
> More information on Office Updates viaa WSUS on www.wsuswiki.com;
>
> Office Administrative Installs
> www.wsuswiki.com/OfficeAdministrativeInstalls
>
> Office Updates and WSUS support
> http://www.wsuswiki.com/OfficeAIPs
>
> Happy Patching,
> Mohammed Athif Khaleel
> http://msmvps.com/athif
>
>

"gettps" <gettps@discussions.microsoft.com> wrote in message
news:C19FFA02-24CD-45D4-97C5-9FE118374D1A@microsoft.com...
>I did read up on those before I posted, but they didn't seem to apply.
>
> Those only seem to apply when the installation source is required for
> operation. I always install Office with all options fully installed
> because I
> know the source will not be available to the customers.


Even with ALL options installed, the installation source is still required.
In fact, the Office 2003 installation /creates/ a Local Installation Source
on every desktop it is install to, so unless you removed the LIS, it should
still be there.

If you installed from a network Administrative Installation Point, then you
need to refer to the links that Athif directed you to:

Office Administrative Installs
www.wsuswiki.com/OfficeAdministrativeInstalls

Office Updates and WSUS support
http://www.wsuswiki.com/OfficeAIPs

I'm curious why you think that the source will not be available to the
customers.

Are these not /licensed/ installations of Office? If so, why would you NOT
make the installation source available to every desktop system, either via
the LIS, or a network AIP?

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....


> Gary Thompson
> Florida State Technology Office
> Department of Management Services
>
>
> "Mohammed Athif" wrote:
>
>> Hi,
>>
>> Some reading for you...
>> More information on Office Updates viaa WSUS on www.wsuswiki.com;
>>
>> Office Administrative Installs
>> www.wsuswiki.com/OfficeAdministrativeInstalls
>>
>> Office Updates and WSUS support
>> http://www.wsuswiki.com/OfficeAIPs
>>
>> Happy Patching,
>> Mohammed Athif Khaleel
>> http://msmvps.com/athif
>>
>>

"Lawrence Garvin (MVP)" wrote:

> Even with ALL options installed, the installation source is still required.
> In fact, the Office 2003 installation /creates/ a Local Installation Source
> on every desktop it is install to, so unless you removed the LIS, it should
> still be there.

I didn't know about the LIS. That could be why I only have 1 2003 failure
and 20 2002 errors.

> If you installed from a network Administrative Installation Point, then you
> need to refer to the links that Athif directed you to:
>
> Office Administrative Installs
> www.wsuswiki.com/OfficeAdministrativeInstalls
>
> Office Updates and WSUS support
> http://www.wsuswiki.com/OfficeAIPs
>
> I'm curious why you think that the source will not be available to the
> customers.

If Office XP has an LIS then it must have either been deleted or corrupted
on those failed machines.
> Are these not /licensed/ installations of Office? If so, why would you NOT
> make the installation source available to every desktop system, either via
> the LIS, or a network AIP?

The AIP will not be available because not everyone we support gets
everything. We have an EA for the basic office package and windows but not
for other programs like Project, Visio... etc. We cannot legally provide
those sources to everyone.

> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, eveything else is at
> http://wsusinfo.onsitechsolutions.com
> ....
>
>
> > Gary Thompson
> > Florida State Technology Office
> > Department of Management Services
> >
> >
> > "Mohammed Athif" wrote:
> >
> >> Hi,
> >>
> >> Some reading for you...
> >> More information on Office Updates viaa WSUS on www.wsuswiki.com;
> >>
> >> Office Administrative Installs
> >> www.wsuswiki.com/OfficeAdministrativeInstalls
> >>
> >> Office Updates and WSUS support
> >> http://www.wsuswiki.com/OfficeAIPs
> >>
> >> Happy Patching,
> >> Mohammed Athif Khaleel
> >> http://msmvps.com/athif
> >>
> >>
>
>
>

"gettps" <gettps@discussions.microsoft.com> wrote in message
news:634D34E8-9B7D-482D-A4BA-AE7384754B04@microsoft.com...

> I didn't know about the LIS. That could be why I only have 1 2003 failure
> and 20 2002 errors.

Quite likely accounts for the minimal number of errors on the Office 2003
systems.

> If Office XP has an LIS then it must have either been deleted or corrupted
> on those failed machines.

Office XP does not have an LIS. That was a feature new to Office 2003. It
has been my experience based on several dozens of installations of Office XP
service packs, that Office XP will /always/ require the installation media
when applying service packs. It may or may not require the media for
installing updates.

I would recommend putting a copy of the media on a network share, and
directing the clients to that share when prompted for the location of the
media.

> The AIP will not be available because not everyone we support gets
> everything. We have an EA for the basic office package and windows but
> not
> for other programs like Project, Visio... etc. We cannot legally provide
> those sources to everyone.

Hmmm... sounds like maybe some investigation into deployment technologies
and share permissions would be appropriate.

Now.. an EA for the "basic office package". Something doesn't fit there for
me. As I recall, the /only/ edition available on an Enterprise Agreement is
Office 2003 Professional Enterprise Edition, which includes everything
except Project and Visio.

Project and Visio are separate installation images, anyway, and the way to
deal with them is via NTFS restricted file shares.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....

> "Lawrence Garvin (MVP)" wrote:
>
>> Even with ALL options installed, the installation source is still
>> required.
>> In fact, the Office 2003 installation /creates/ a Local Installation
>> Source
>> on every desktop it is install to, so unless you removed the LIS, it
>> should
>> still be there.
>
>
>> If you installed from a network Administrative Installation Point, then
>> you
>> need to refer to the links that Athif directed you to:
>>
>> Office Administrative Installs
>> www.wsuswiki.com/OfficeAdministrativeInstalls
>>
>> Office Updates and WSUS support
>> http://www.wsuswiki.com/OfficeAIPs
>>
>> I'm curious why you think that the source will not be available to the
>> customers.
>
>> Are these not /licensed/ installations of Office? If so, why would you
>> NOT
>> make the installation source available to every desktop system, either
>> via
>> the LIS, or a network AIP?
>
> The AIP will not be available because not everyone we support gets
> everything. We have an EA for the basic office package and windows but
> not
> for other programs like Project, Visio... etc. We cannot legally provide
> those sources to everyone.
>
>> --
>> Lawrence Garvin, M.S., MVP-Software Distribution
>> Everything you need for WSUS is at
>> http://technet2.microsoft.com/window...s/default.mspx
>> And, eveything else is at
>> http://wsusinfo.onsitechsolutions.com
>> ....
>>
>>
>> > Gary Thompson
>> > Florida State Technology Office
>> > Department of Management Services
>> >
>> >
>> > "Mohammed Athif" wrote:
>> >
>> >> Hi,
>> >>
>> >> Some reading for you...
>> >> More information on Office Updates viaa WSUS on www.wsuswiki.com;
>> >>
>> >> Office Administrative Installs
>> >> www.wsuswiki.com/OfficeAdministrativeInstalls
>> >>
>> >> Office Updates and WSUS support
>> >> http://www.wsuswiki.com/OfficeAIPs
>> >>
>> >> Happy Patching,
>> >> Mohammed Athif Khaleel
>> >> http://msmvps.com/athif
>> >>
>> >>
>>
>>
>>