It is possible to remove auto-reboot process after silent install ??

<Configuration Product="Enterprise">

<Display Level="basic" CompletionNotice="yes" SuppressModal="no" AcceptEula="yes" />

<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> -->

<PIDKEY Value="XXXXXXXXXXXXXXXXXX" />

<USERNAME Value="XXXXXXX" />

<COMPANYNAME Value="XXXXXXXX" />

<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<SOURCELIST Value="\\XXXXXXXX\Microsoft\Office Enterprise 2007\Install" />

<!-- <DistributionPoint Location="\\server\office" /> -->

<OptionState Id="ACCESSFiles" State="Local" Children="force" /> //access
<OptionState Id="OUTLOOKFiles" State="Local" Children="force" /> //outlook
<OptionState Id="PubPrimary" State="Local" Children="force" /> //publisher
<OptionState Id="AceRepl" State="absent" Children="force" /> //access db Engine replication
<OptionState Id="CAGFiles" State="Local" Children="force" /> //Clip Organizer
<OptionState Id="MSSOAP3" State="absent" Children="force" /> //SOAP toolkit
<OptionState Id="OsaNonBoot" State="Local" Children="force" /> //new,open office docu lnks
<OptionState Id="ProofingTools_1036" State="absent" Children="force" /> //french
<OptionState Id="ProofingTools_3082" State="absent" Children="force" /> //spanish
<OptionState Id="WISPFiles" State="Local" Children="force" /> //handwriting
<OptionState Id="DocServicesFiles" State="Local" Children="force" /> //docu update util
<OptionState Id="HTMLSourceEditing" State="Local" Children="force" /> //script editor
<OptionState Id="DocumentImagingUtils" State="Local" Children="force" /> //scanning,ocr,indexing
<OptionState Id="OISFiles" State="absent" Children="force" /> //picture manager
<OptionState Id="OSESupp" State="Local" Children="force" /> //sharepoint support
<OptionState Id="QueryFiles" State="Local" Children="force" /> //msQuery
<OptionState Id="VisioPreviewerFiles" State="Local" Children="force" /> //visio viewer
<OptionState Id="XDOCSFiles" State="Local" Children="force" /> //infopath
<OptionState Id="GrooveFiles" State="Local" Children="force" /> //groove
<OptionState Id="OneNoteFiles" State="Local" Children="force" /> //onenote
<OptionState Id="RefIEBarFiles" State="absent" Children="force" /> //research explorer bar
<OptionState Id="WebDriveFiles" State="absent" Children="force" /> //hosted webs
<OptionState Id="VBAFiles" State="absent" Children="force" /> //VB for applications
<OptionState Id="OfficeDigitalSFiles" State="absent" Children="force" /> //vba certificates

<Setting Id="Reboot" Value="IfNeeded" />

<!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

It is possible to remove auto-reboot process after silent install ??

I'm trying to install Office Enterprise 2007 in my AD environment via Group Policy.

Office 2003 was manually installed before I got here, so I don't have a Group Policy to upgrade.

On some test machines, when I push Office 2007, it installs next to Office 2003, not over top, or as an upgrade. This is totally not the desired affect.

Unattending or silently installing MS Office System, has now become easier than ever.

First, you fetch yourself the version of Office that you want from Microsoft Connect. Two versions are available currently, both being Beta1 Technical-Refresh - either the ProPlus (core apps only, 441 MB) or the Enterprise (core+other+server, 1.08 GB).

Then, there are two ways to unattend your setup. Option A (use it only if you got Office12 thru SoftwareAssurance, which comes with activation stripped out). Option B is for all the others (retail/OEM/academic/etc). Both are colored differently below.


Option A:
1. Ensure you have WindowsInstaller 3.1 already installed.
2. Ensure you have an actual enterprise/corporate CD & CD-key (which wont need activation).
3. Notably, o2k7 uses setup patches (*.MSP) rather than transforms which previous versions used (*.MST). The below instructions will give you an MSP file, which is not accepted by non-corporate versions of o2k7. If you ignored point2 above, then you will end up wasting 15 minutes of your life which I'm not responsible for.
4. Now at the command prompt, type: setup.exe /admin
5. Choose the product for which you want to make a customization-patch.
6. Then go through all steps in the customization wizard (to install the reqd apps & remove junk & change default settings).
7. Be sure to have "completion notice" turned on & "suppress modals" turned off (this is to get to see errors, if any exist). Once you're done with testing, go thru the customization again to modify the MSP to disable completion notice & enable suppress modals.
8. Save the resulting patch file in the same folder as o2k7 setup files.
9. Now just execute this command (thru any method) for silent install: setup.exe /adminfile CUSTOM.MSP

NEWS-FLASH!
If you have the final Enterprise release of Office 2007, then Option A works flawlessly.
You could even drop the CUSTOM.MSP file in the "Updates" folder & setup will pick it up automatically (without any switches being used).

I was wondering if this method works for Proplus. I have put the .msp file in the updates folder and when I go to deploy it to a test machine it starts to install office but quickly comes to the ctrl-alt-del then when I log in to check it only installs the office folder. No word excel etc. jsut like image scanner and one other office tool. any thoughts on this?

if I have a .msp file in the updates folder, does that get applied when installing from the Enterpriseww.msi file via group policy?

any idea how to get rid of office 2003 during the upgrade?

I was wondering if this method works for Proplus. I have put the .msp file in the updates folder and when I go to deploy it to a test machine it starts to install office but quickly comes to the ctrl-alt-del then when I log in to check it only installs the office folder. No word excel etc. jsut like image scanner and one other office tool. any thoughts on this?

am wondering what option i need to set to make it completely silent, i still have the option window were it says install and customize.

every evaluation version form microsoft gives me the error from the image I posted . why? is this a feature?

but it's much more simple to use OCT instead of config.xml. why they do this?
also I suspect that Office 2007 standard doesn't support msp files. is this true?

So now theres OCT, MSP and XML.

Sorry to have to say this but no, this isn't "more simple" than it used to be.

To install Office 2003 silently all you had to do was use this switch:

SETUP.EXE TRANSFORMS=Unattended.MST /qb-

Now with Office 2007 we have to mess around with XML files, or is it MSP
files, or is it OCT.... next someone will be saying theres another way.

i think you don't know what oct and msp are and the difference between xml and msp files and how to create them

Someone prove to me that Microsoft are NOT trying to annoy people! Prove it!

the documentation on Microsoft XML files for office 2007 didnt explain a lot of things, they almost take for granted that you know the Properties names and all, so you really "cant" customize all in the xml way unless you are an office 2007 xml files guru...