Majority (98%) of our machines were imaged using Norton Ghost (OS is Win2k Prof. at SP3 or higher). A MS Office 2000 Premium installation was part of these images. Depending on when the machine was last imaged, Office version is the Premium (pre-SR1 build) with or without SR1a applied separately OR the Office 2000 SR1 installation.

Moving forward we have created administrative installation points for future images and installs. However reimaging the existing machines is far to large a task (1500+ PCs).

What I'd like to do is create an update script (SMS, login or otherwise) that points the existing installations to look towards the administrative installation point (OFC2kPRM or OFC2kSR1 depending on version installed). This will allow us to automate updates/repairs/reinstalls without the need to use CDs at the client PCs.

I can easily distinguish the version installed based on the MSI the Installer looks for (data1.msi for OFC2KSR1 installs and data1prm.msi for OFC2KPRM installs with or without SR1a applied seperately).

My question is:

What registry keys need to be changed on the client PC to allow for the Office installation to automatically look at the Network Administrative Install Point without the user needing to manually browse to the location and select the appropriate MSI file?

So far I've located a few keys that seem relevant, but I'm worried about missing something:

HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts 904000001E872D116BF00006799C897ESourceList (?)
HKEY_CLASSES_ROOTInstallerProducts904000001E872D11 6BF00006799C897ESourceListMedia
HKEY_CLASSES_ROOTInstallerProducts904000001E872D11 6BF00006799C897ESourceListNet
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentV ersionInstallerUserDataS-1-5-18Products904000001E872D116BF00006799C897EInstallP ropertiesInstallSource
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentV ersionUninstall{00000409-78E1-11D2-B60F-006097C998E7}InstallSource

Anyone ever done this before? Any comments? Thanks all!