View Single Post
  #8  
Old June 22nd, 2005, 12:03 PM
Jason Lu [MSFT]
external usenet poster
 
Posts: n/a
Default

Hi John,

I understand your concerns. From the previous test, I am suspecting some domain related IDs registered in the Registry do not match the
new network. Normally, it is hard to locate the exact keys for repairing. I suggest you use Windows Installer command line to reinstall
Office 2000. In this way, you do not need to reinstall Office on each client. Instead, you can simply push a script out to all the clients.

According to my research, the following command may fix this issue. You can first test it on one client experiencing this issue.

msiexec /i Admin Path\Data1.msi Reinstall=All ReinstallMode=vomus

where Admin Path is the path to your administrative installation point.

In case it does not help, we can use two Windows Installer commands to first uninstall Office and then reinstall it.

msiexec /x {Product Code of the Office SKU}

You can find the Product Code in Office registry keys and it is the same for all Office installations with the same Office suite.

Admin Path\setup /i data1.msi /qb+

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.