We are running into a problem deploying Office 2007 (Suite and VISIO and Project components) using SCCM R2 in that, despite querying for an existing version, there are times when the product is deployed to a computer with one or more of the components, and, although the install is set for silent, we get the "Change your installation (Add or Remove Features or Repair or Remove) of..." popup, which, since the install is done in the System context, no user ever sees, so...it times out.

What I would like to do, is to somehow set the behavior to install or upgrade or repair (do nothing), depending on if there is NO component, older or lesser component, or exact same component. But, don't see a way to tell the install to do this. Would setting the install to Repair, also install? Any ideas on how to do this--main thing is, that it must NOT stop the install.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Have you considered making a collection with machines which DO NOT have any of the Office 2007 components installed?
Answered 05/26/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
We are running SCCM R2, and, have started using Task Sequences to install applications, and, using Collection Variables to determine to install or not, but...every once in a while, things don't work as planned...<G>

What I found...even though we used the OCT to configure an MSP for a totally silent install with no UI, when doing an install over an already-installed product, it comes up with the Add/Remove/Repair UI screen, and, since that's in the System Context, nobody sees it, and, the install times out. I found that if you configure the config.xml to also do a silent install, then, put that in the same (root) folder of the Office product as setup.exe, then run setup.exe /config config.xml, it seems to figure out to do a repair, rather than an install. Now, the documentation states that a full UNC path to config.xml must be used, not relative, so, still have to test to ensure that this works with SCCM TS', but, if it does, this may be the trick.

If this is indeed the fix, it needs to be amplified a bit by Microsoft, as...this is NOT made crystal in the documentation.

Answered 05/26/2009 by: gmouse
Orange Senior Belt

Please log in to comment