Office XP SP3 requires .msi File and Preventing issue with WSUS

Hi all,

Hopefully this is an easy fix.

I'm running WSUS 3 to update all my WinXP PCs running various versions of
Office.

One PC is requiring the Office XP SP3 update and is failing. When I go to
this PC to manually install this update it asks for the path to beret.msi
file which I'm assuming it wants the Office XP CD. It appears to have 2
default paths: a path for the original XP CD and a path for the network
location of Office XP SP2.

I guess it comes down to I don't want to have to put this CD in for every
PC. I want WSUS to be 'hands off' and just install all the updates. Is
there a way that I can bypass this check for the CD? If not (and much less
preferred) is there a way to change the path it looks for on each PC (such
as via registry) for the CD and copy it to the network? This is less
preferred because it will inevitably be different for each version of
Office.

Thanks,
Mike

Mike,

Basically the registry holds the default location. So, editing the registry to
point to the network resource should resolve the issue:

Example Only:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\ Registration

Key Name: SmartSourceDir
Key Type: STRING
Value: Source Path (Example: E:\)

--
Newbie Coder
(It's just a name)


"Mike" <mike008usNO-> wrote in message
news:%...
> Hi all,
>
> Hopefully this is an easy fix.
>
> I'm running WSUS 3 to update all my WinXP PCs running various versions of
> Office.
>
> One PC is requiring the Office XP SP3 update and is failing. When I go to
> this PC to manually install this update it asks for the path to beret.msi
> file which I'm assuming it wants the Office XP CD. It appears to have 2
> default paths: a path for the original XP CD and a path for the network
> location of Office XP SP2.
>
> I guess it comes down to I don't want to have to put this CD in for every
> PC. I want WSUS to be 'hands off' and just install all the updates. Is
> there a way that I can bypass this check for the CD? If not (and much less
> preferred) is there a way to change the path it looks for on each PC (such
> as via registry) for the CD and copy it to the network? This is less
> preferred because it will inevitably be different for each version of
> Office.
>
> Thanks,
> Mike
>
>

"Mike" <mike008usNO-> wrote in message
news:%...
| Hi all,
|
| Hopefully this is an easy fix.
|
| I'm running WSUS 3 to update all my WinXP PCs running various versions of
| Office.
|
| One PC is requiring the Office XP SP3 update and is failing. When I go to
| this PC to manually install this update it asks for the path to beret.msi
| file which I'm assuming it wants the Office XP CD. It appears to have 2
| default paths: a path for the original XP CD and a path for the network
| location of Office XP SP2.
|
| I guess it comes down to I don't want to have to put this CD in for every
| PC. I want WSUS to be 'hands off' and just install all the updates. Is
| there a way that I can bypass this check for the CD? If not (and much less
| preferred) is there a way to change the path it looks for on each PC (such
| as via registry) for the CD and copy it to the network? This is less
| preferred because it will inevitably be different for each version of
| Office.
|
| Thanks,
| Mike
|
|

Perhaps try the WSUS Newsgroup
http://www.microsoft.com/technet/com...pdate_services

news://msnews.microsoft.com/microsof...pdate_services
(OE client)

xposted for convenience
--
====================================
TaurArian [MS-MVP] 2005-2008 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Defending your machine: http://defendingyourmachine2.blogspot.com/
http://taurarian.mvps.org/index.htm

Emails will not be acknowledged - please post to the newsgroup so all may benefit.

Hi Taurian,

Please note the groups I copied. If I'm correct, I had originally done what
you suggested.

Thanks,
Mike


"TaurArian [MS-MVP]" <> wrote in message
news:%2321%...
>
> "Mike" <mike008usNO-> wrote in message
> news:%...
> | Hi all,
> |
> | Hopefully this is an easy fix.
> |
> | I'm running WSUS 3 to update all my WinXP PCs running various versions
> of
> | Office.
> |
> | One PC is requiring the Office XP SP3 update and is failing. When I go
> to
> | this PC to manually install this update it asks for the path to
> beret.msi
> | file which I'm assuming it wants the Office XP CD. It appears to have
> 2
> | default paths: a path for the original XP CD and a path for the network
> | location of Office XP SP2.
> |
> | I guess it comes down to I don't want to have to put this CD in for
> every
> | PC. I want WSUS to be 'hands off' and just install all the updates. Is
> | there a way that I can bypass this check for the CD? If not (and much
> less
> | preferred) is there a way to change the path it looks for on each PC
> (such
> | as via registry) for the CD and copy it to the network? This is less
> | preferred because it will inevitably be different for each version of
> | Office.
> |
> | Thanks,
> | Mike
> |
> |
>
> Perhaps try the WSUS Newsgroup
> http://www.microsoft.com/technet/com...pdate_services
>
> news://msnews.microsoft.com/microsof...pdate_services
> (OE client)
>
> xposted for convenience
> --
> ====================================
> TaurArian [MS-MVP] 2005-2008 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Defending your machine: http://defendingyourmachine2.blogspot.com/
> http://taurarian.mvps.org/index.htm
>
> Emails will not be acknowledged - please post to the newsgroup so all may
> benefit.
>
>

Thanks Newbie.

This however means distributing this to all clients and will I have to do
this again when I get to the next version of Office patches?

Does anyone have a way to completely bypass this?

Thanks,
Mike

"Newbie Coder" <> wrote in message
news:%...
> Mike,
>
> Basically the registry holds the default location. So, editing the
> registry to
> point to the network resource should resolve the issue:
>
> Example Only:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\ Registration
>
> Key Name: SmartSourceDir
> Key Type: STRING
> Value: Source Path (Example: E:\)
>
> --
> Newbie Coder
> (It's just a name)
>
>
> "Mike" <mike008usNO-> wrote in message
> news:%...
>> Hi all,
>>
>> Hopefully this is an easy fix.
>>
>> I'm running WSUS 3 to update all my WinXP PCs running various versions of
>> Office.
>>
>> One PC is requiring the Office XP SP3 update and is failing. When I go to
>> this PC to manually install this update it asks for the path to beret.msi
>> file which I'm assuming it wants the Office XP CD. It appears to have 2
>> default paths: a path for the original XP CD and a path for the network
>> location of Office XP SP2.
>>
>> I guess it comes down to I don't want to have to put this CD in for every
>> PC. I want WSUS to be 'hands off' and just install all the updates. Is
>> there a way that I can bypass this check for the CD? If not (and much
>> less
>> preferred) is there a way to change the path it looks for on each PC
>> (such
>> as via registry) for the CD and copy it to the network? This is less
>> preferred because it will inevitably be different for each version of
>> Office.
>>
>> Thanks,
>> Mike
>>
>>
>
>

Yep, you posted to :microsoft.public.officeupdate (Office Update),
microsoft.public.windowsupdate (Windows Update)
I didn't realise you had also made a separate post to:
microsoft.public.windows.server.update_services (WSUS)

Hope you resolve your problem.

"Mike" wrote:

> Hi Taurian,
>
> Please note the groups I copied. If I'm correct, I had originally done what
> you suggested.
>
> Thanks,
> Mike
>
>
> "TaurArian [MS-MVP]" <> wrote in message
> news:%2321%...
> >
> > "Mike" <mike008usNO-> wrote in message
> > news:%...
> > | Hi all,
> > |
> > | Hopefully this is an easy fix.
> > |
> > | I'm running WSUS 3 to update all my WinXP PCs running various versions
> > of
> > | Office.
> > |
> > | One PC is requiring the Office XP SP3 update and is failing. When I go
> > to
> > | this PC to manually install this update it asks for the path to
> > beret.msi
> > | file which I'm assuming it wants the Office XP CD. It appears to have
> > 2
> > | default paths: a path for the original XP CD and a path for the network
> > | location of Office XP SP2.
> > |
> > | I guess it comes down to I don't want to have to put this CD in for
> > every
> > | PC. I want WSUS to be 'hands off' and just install all the updates. Is
> > | there a way that I can bypass this check for the CD? If not (and much
> > less
> > | preferred) is there a way to change the path it looks for on each PC
> > (such
> > | as via registry) for the CD and copy it to the network? This is less
> > | preferred because it will inevitably be different for each version of
> > | Office.
> > |
> > | Thanks,
> > | Mike
> > |
> > |
> >
> > Perhaps try the WSUS Newsgroup
> > http://www.microsoft.com/technet/com...pdate_services
> >
> > news://msnews.microsoft.com/microsof...pdate_services
> > (OE client)
> >
> > xposted for convenience
> > --
> > ====================================
> > TaurArian [MS-MVP] 2005-2008 - Australia
> > ====================================
> > How to make a good post: http://www.dts-l.org/goodpost.htm
> > Defending your machine: http://defendingyourmachine2.blogspot.com/
> > http://taurarian.mvps.org/index.htm
> >
> > Emails will not be acknowledged - please post to the newsgroup so all may
> > benefit.
> >
> >
>
>
>

"TaurArian [MS-MVP]" <> wrote in message
news:%2321%...
>
> "Mike" <mike008usNO-> wrote in message
> news:%...
> |
> | I guess it comes down to I don't want to have to put this CD in for
> every
> | PC. I want WSUS to be 'hands off' and just install all the updates.

This is a limitation of Office XP, not WSUS.

> | Is there a way that I can bypass this check for the CD?

No.

> | If not (and much less
> | preferred) is there a way to change the path it looks for on each PC
> (such
> | as via registry) for the CD and copy it to the network?

You could edit the registry on each PC, but, shucks, as long as you're there
editing the registry, why not just stick the CD in, update the computer, and
be done with it.


> | This is less
> | preferred because it will inevitably be different for each version of
> | Office.

Not if it's a NETWORK location specified by UNC pathname (which would be the
recommended methodology in this situation).

--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
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