Software Deployment

Haven't done Office 2007 yet and am surprised these settings aren't in the OCT...

Had a quick look - it seems the keys you are interested in are:

HKCU\Software\Microsoft\Office\12.0\Common\UpdateReliabilityData: 0x00000000
HKCU\Software\Microsoft\Office\12.0\Common\QMEnable: 0x00000000
HKCU\Software\Microsoft\Office\12.0\Common\General\ShownOptIn: 0x00000001
HKCU\Software\Microsoft\Office\12.0\Common\Internet\UseOnlineContent: 0x00000001

Set the values depending on what settings you want.. but the above should turn them all off and suppress the dialog. As with most MS products though - it may not be this simple ;-)

Hope it helps...

Regards,
Rob.

Thanks Rob! I actually did just finally find them, they're buried in the security settings of the OCT. I haven't tested it since I made those changes though, I'll be doing that shortly. If that doesn't do what I want I'll attack the reg keys. Thanks!

You could also load the office 2007 admx files into ur GP.

Hi
Could you let me know where that setting is in the OCT please?

Many Thanks
Jimmy

So I have a few questions that maybe someone might have experienced.

Our corp environment is based on a layered Office suite. We are not migrating our Office base (yet) to Office Pro 2007 but we do provide component of 2007 when needed.

My problem lies in this scenario, I create the individual .msp's for Access, PPT, Word, Excel. Reading the Deployment Guide, it states to place them inside individual folders at the root of the network share and call them on my command line. That is done. What I have a problem with is that in a scenario where a user requires both Excel and Word 2007, the setup.exe /admin can only be used during the initial install. What do I do after this to script further component installs on the same machine?

Looking forward to some guidance...I've racked my brain long enough.

Once you install any office 2007 product, you need to modify your installation if you want to add one or more product. In my case, everything was installed except for Access. You need to create an .xml file (I don't know how to create them.... I only found the information on several website).

Access .xml file :

<Configuration Product="ProPlus">
<Display Level="Basic" CompletionNotice="Yes" SuppressModal="No" NoCancel="yes" AcceptEula="yes" />
<Logging Type="verbose" Path="%Windir%\Temp" Template="Access_2007_ML_Microsoft.log" />
<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />
<AddLanguage Id="match" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ACCESSFiles" State="Local" Children="force" />
</Configuration>

Configuration Product="ProPlus" determine which office version you have (you can find that in the office .msi)

Display Level can be set to None if you don't want desktop interaction, also put CompletionNotice to No

OptionState ID determine which product to install/remove. You can find the ID name inside the product .msi (with ORCA) (ex. Excel should be EXCELFiles (I don't remember if it's case sensitive though)).
State="Local" = Install
State="absent" = Remove

Installation command line:
setup.exe /modify ProPlus /config %INST%\Access_Install.xml

I hope that will help you

Darkfang! You da man.

Works like a charm.

I created the specific .xml files for each components needed. But I have one last challenge.

Knowing that I built my first install (Excel) using setup.exe /adminfile %inst%\excel.msp. What should I do since this may not be needed by a user who might need Access only since we're using setup.exe /modify which it's looking for a prior installation to exist on the box.

I'm not sure how to design that solution. Not every user will get Excel and then whatever component they really requested.

Make sense?

I guess you will have to create a .msp file for Access for the initial install.

But i'm wondering if its possible the generate an "empty" .msp file who doesn't install any product and create an .xml file for each product using setup.exe /modify.

What you think ?

I think it makes sense to create the individual .msp's and break them into two groups: 1st time installs and subsequent installs. That way no matter what the request is, they exist moving forward.

One other question, duing the initial .msp installs I see the Office Professional splash screen for like 3 second and then it disappears. Setup.exe continues to install silently but not sure why this happens when .msp is clearly marked as "none" in the display level.

Thoughts?

I tried installing office 2007 using msp file, and worked fine.
to create msp file follow the steps
->go to RUN, browse to the setup.exe (ex C:\office2007\setup.exe)
-> now type /admin against the setup.exe (c:\office2007\setup.exe /admin) in Run
-> It opens customization wizard, give ur options and click on save as under file menu and save in your local drive(C:\office2007\settings.msp)

now run the setup with msp file

ex C:\office2007\setup.exe /adminfile settings.msp (as msp is in same path, if you save in diff path give the path to msp file)

For uninstalling

use msiexec.exe /X {product ID} /qb


but after uninstalling my system is restarting automatically with out even asking for my choice


can any one please tell me how to suppress reboot after uninstall

If you include the switch to turn on verbose logging in your command line, the resulting log file will contain the information you need.