Especially such a major Microsoft product with all its tie ins to the OS & other apps. I cannot possibly imagine that if you kick off a repair with the app open, you actually expect it to stay open with docs still open. i can't distribute this in the network, users need to save their documents if opened. I'm trying to script a silent repair for office 2007 but the problem is that the pc got rebooted (cold boot) at the end of the repair.

it's when bmc triggers the repair that the script is needed. Since english is not my primary language, is this explanation understandable?Įdit: i forgot to say, if the repair is triggered by the windows installer, there is no need for the script. So i had to script it so that when bmc launches the repair, in fact it is launching a script i've done that put the correct value for the sourcelist reg key, msocache. The problem is that the msi file is located at the root of this directory and the cab file is located in a sub-folder. When office installs, it write the correct value to the registry for its sourcelist, which is somewhere in msocache.īut when bmc triggers a repair, it changes the value of that registry key for the source of its own channel, which is somewhere in program files. (sorry could not help myself).īmc can't handle the installation of office 2007 because the way to install has changed (thanks microsoft). Our distribution software is bmc, i think some of you know that b***s***.

Repair microsoft office 2007