Software Deployment

Why not go completely mad and add the verbose logging argument to your command line?

The obvious question is, why does a repair need to be scripted? Why not simply let it repair if it needs repairing?

ok here's why!

our distribution software is bmc, i think some of you know that b***s***. (sorry could not help myself).

bmc can't handle the installation of office 2007 because the way to install has changed (thanks microsoft).

when office installs, it write the correct value to the registry for its sourcelist, which is somewhere in msocache.

but 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.

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. don't tell me to relocate it, i can't. (told you bmc was BS didn't i?)

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. then the script triggers the repair. but the repair does a reboot.

since english is not my primary language, is this explanation understandable?

thanks a lot VBScab!

edit: i forgot to say, if the repair is triggered by the windows installer, there is no need for the script. it's when bmc triggers the repair that the script is needed.

thanks!

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. i can't distribute this in the network, users need to save their documents if opened.
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. Especially such a major Microsoft product with all its tie ins to the OS & other apps. Are we not being a little ambitious here, or have I misunderstood your statement? Have you ever tried to change the piston rings in a car engine while it is still running?

ORIGINAL: kiptek

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. i can't distribute this in the network, users need to save their documents if opened.
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. Especially such a major Microsoft product with all its tie ins to the OS & other apps. Are we not being a little ambitious here, or have I misunderstood your statement? Have you ever tried to change the piston rings in a car engine while it is still running?



check my latest post ;-)

every sunday morning, bmc checks all the packages it has installed on a workstation and it decides that a repair is needed. the trigger for a repair from bmc could be different from the triggers we know with windows installer.

bmc is very tricky and poorly designed, and gives me headaches.

i need to suppress the reboot because i need to think of every thing that could happen.

think about a user who goes home friday and forget to save some document not office related. sunday, bmc decides to repair office, so the pc reboots. then monday, the user comes to work to find its doc gone.

i need to make sure all possibilities like that won't happened because if it does, who do you think will be blamed? bmc or me? ;-)

thanks!

Aha! Good ol' marimba!

So if you had to deploy a patch that needed a reboot, what? There is the hand off between looking out for users during business hours, & coddling them because they are too lazy to save their work on Friday evening before going home for the weekend. This is not a reasonable expectation on their part.

Also if Marimba is kicking off Office repairs every w/end, this speaks to a much larger problem. I though it had a provision for a "dump & run" type app that did not place that much overhead on maintaining the app. After all, once on the machine, WI does a pretty good job of that.

i need to know how to suppress the reboot after a repair.

is it doable?

thanks!

got it!

To configure a silent repair of a 2007 Office system product that requires no user interaction, you must modify the Config.xml file for the product and set the Display element's Level attribute to "none" (Display Level="none"), and then save the Config.xml file as SilentRepairConfig.xml, as shown in the following procedure.

http://technet.microsoft.com/en-us/library/cc982159.aspx#BKMK_RepairInstall

I found this : http://itninja.com/question/quick-sus-question/problem9&mpage=1&key=&#36169

[Quote]
I was able to suppress a restart by adding the property SETUP_REBOOT=Never in the MSP.
[/Quote]

But since Office is already installed, I think you can't use .msp anymore.

going back to what Ian asked: what does the verbose log say? What commandline is it running? What are the values of the REBOOT property throughout?

ORIGINAL: kiptek

Aha! Good ol' marimba!

So if you had to deploy a patch that needed a reboot, what? There is the hand off between looking out for users during business hours, & coddling them because they are too lazy to save their work on Friday evening before going home for the weekend. This is not a reasonable expectation on their part.

Also if Marimba is kicking off Office repairs every w/end, this speaks to a much larger problem. I though it had a provision for a "dump & run" type app that did not place that much overhead on maintaining the app. After all, once on the machine, WI does a pretty good job of that.



marimba has the patch manager that allows me to display a message to users asking them to reboot. no problem there.

this office 2007 channel in marimba is special and required some special actions.

anyway tomorrow i will test my latest findings, i think all will be as i wish it to be.

thanks!

FWIW, the change to the installation methodology which comes with Office 2007 is the biggest driver for moving my current client from GP deployment to SCCM. Has anyone seen anything from MS where they explain what drove the change? I'd *love* to see it...

ORIGINAL: kardock

got it!

To configure a silent repair of a 2007 Office system product that requires no user interaction, you must modify the Config.xml file for the product and set the Display element's Level attribute to "none" (Display Level="none"), and then save the Config.xml file as SilentRepairConfig.xml, as shown in the following procedure.

http://technet.microsoft.com/en-us/library/cc982159.aspx#BKMK_RepairInstall



problem solved. no more reboot!