FullFile patches still require source?

[Brian Vanover]

So I'm trying to deploy the numerous patches required for
MS04-028.

I'm determining that no matter what I do, the fullfile
patches still require access to the original source. This
will not work for us, as some of the sources have changed
since they were originally deployed (moved to a different
directory, etc).. I've tried this with Visio 2002, 2003,
project 2002, 2003, etc. I've tried every variation of a
command to try and get this to not require the original
source.

I thought the point of the fullfile patches was they
didn't require the original source?

Specifically, I've tried using the ohotfix.exe method
detailed at http://support.microsoft.com/?kbid=885885.
Using the full silent option, it just starts, then quits.
If I just run the exe, that's when I get the prompt for
the source.

Any ideas?

 

[Bob Buckland ?:-\)]

Hi Brian,

You didn't mention the method you used to deploy Office.
The fullfile patches may still require the original source
when there is a detection that either the original Office
installation may be damaged or if the MS Installer cache
has been altered, for example.

If you deployed from an Office Admin point then updating
the Admin point and then recaching the clients would be the
basic method but you may want to review the information here
on alternate methods:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

MS Installer based software expects to have access to the original
or alternate location of the original installation source files.

=======
So I'm trying to deploy the numerous patches required for
MS04-028.

I'm determining that no matter what I do, the fullfile
patches still require access to the original source. This
will not work for us, as some of the sources have changed
since they were originally deployed (moved to a different
directory, etc).. I've tried this with Visio 2002, 2003,
project 2002, 2003, etc. I've tried every variation of a
command to try and get this to not require the original
source.

I thought the point of the fullfile patches was they
didn't require the original source?

Specifically, I've tried using the ohotfix.exe method
detailed at http://support.microsoft.com/?kbid=885885.
Using the full silent option, it just starts, then quits.
If I just run the exe, that's when I get the prompt for
the source.

Any ideas? >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Brian Vanover]

Our method was the 'shotgun' method.

Some people installed it from cd, some from an admin
share, some from a share that just had the cd copied to
it, etc.

I've since created new 'clean' shares for everything, but
have no way to 'fix' all the broken installs that point to
a no longer existing share.

I thought I could use a regedit type fix, that would check
for certain reg keys to determine what was installed on a
machine, but I cannot determine how MSFT converts their
product numbers into actual reg keys (some reverse-polish
notation, but not always.??)
argh.

Has anyone come up with a decent deployment method for
deploying patches for this nasty ms04-028 bug?
Apparently, We can't use SUS for the office portions, and
we don't use SMS.

-----Original Message-----
Hi Brian,

You didn't mention the method you used to deploy Office.
The fullfile patches may still require the original source
when there is a detection that either the original Office
installation may be damaged or if the MS Installer cache
has been altered, for example.

If you deployed from an Office Admin point then updating
the Admin point and then recaching the clients would be the
basic method but you may want to review the information here
on alternate methods:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.h
tm

MS Installer based software expects to have access to the original
or alternate location of the original installation source files.

=======
<<"Brian Vanover" <[email protected]> wrote in

message news:[email protected]...

 

[Poly]

Hey did you ever figure out how to do this?
I am in a similar situation.

Is there a command line for (msiexec) or something as
such that can point the update to a network location that
contatains the source files. To force it to look at a
new location as the old location in the registry may no
longer exist?

 

[Poly]

"MS Installer based software expects to have access to
the original or alternate location of the original
installation source files."


How do you point the installer to an alternate location
without being prompted????

This should solve lots of posts!!!

Poly

 

[Bob Buckland ?:-\)]

Hi Poly,

Let us know if the information in this article helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;267362&FR=1

=====

"MS Installer based software expects to have access to
the original or alternate location of the original
installation source files."


How do you point the installer to an alternate location
without being prompted????

This should solve lots of posts!!!

Poly >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx