Office 2000 full-file patches requesting original installation med

[JPenske]

We are constantly having problems pushing out "full file" updates to our end
users. Our policy does not allow us to put the Office installation files on
the hard drive of our PCs, and we have been unsuccessful at pointing them to
the server during the update process to obtain the appropriate MSI when
installing an office update. We have over 10,000 computers, and every time
we push the latest office update, it breaks Excel and/or Word. I need a way
to successfully push these updates without requiring access to the original
installation media. An administrative installation point is out of the
question because we have many remote sites that would have too slow of a
connection to the server. Any suggestions are welcome, I'm pulling my hair
out here!

 

[Eric A.]

Hello JPenske,

Office 2000 is a bear when it comes to needing source. As you are no doubt
aware there was no MSOcache with office 2000 so it is pretty common for it to
ask for source alot.


You have two options.

#1. Put a copy (the same copy that was used during the initial install) on a
network share and recache the clients machines to the network source using
the following command "msiexec /i (full path to share and data1.msi)
REINSTALL=ALL REINSTALLMODE=VOMUS /qn" If the data1.msi is the same exact one
used during the intial install then all future requests for source would
direct office to look there.

#2 Try installing the filehashpatch. There is a patch that MS released to
address this issue. After installing this patch Office 2000 will ask for
source much less. I can't gurentee that it will never ask for source as I
imagine there are still some patches (maybe service packs) that will still
require source. Since your issue is with just a few patches give this a try
though.

http://support.microsoft.com/default.aspx?kbid=835220


If #2 doesn't work (it very well might) and #1 doesnt work because it thinks
it is not the right source, then let me know and I will tell you what you
will need to do.

 

[JPenske]

Eric,

I recently implemented the file hash and it has resolved the issue with
about 40% of the machines. Do you have any other recommendations?

Thanks for the help!

Jason

 

[Eric A.]

Unfortunatly if the file hash patch did not resolve Office 2000 asking for
source the only way to fix it for that machine is to provide the source. The
reason why this is a bummer is because it is pretty common for people to try
to use their original discs and they find that 2000 is not satisfied with
that source and says it isnt the right source.

The most common reason for this is because people will create an AIP (Admin
Install Point) with a .mst or will update they aip and then the original
source is in fact a modified aip which if they remove it will never be
available again.

The best surefire method for solving your problem is to remove all of the
office 2000 installations, create an AIP from scratch, Update it to sp3, and
redeploy.

I just re-read your email and see that a AIPs are out of the question, and
your policy prevents putting source on the local machines. That puts you in a
really tough spot with Office 2000.

Since Office 2000 doesnt create a LIS, if the file hash patch doesn't work,
you can't use an AIP, your options are pretty much limited to sending
everyone a removable disc... removing office and reinstalling with that disc
(so the source is the orginal), or upgrading.

I wish I had a better solution for you, but not being able to put the source
anywhere for the installs to reference is a bad deal.

For Office 2007, MS has gotten to the point where they have in fact force
the MSOcache to exist on the drive. Customers dont even have the ability to
install without it.

 

[JPenske]

Thank you for all the help and suggestions! You've proved what I've been
telling them all along!