 Office 2007, Unattended Setup & Fine-tuning, its very easy & simple! |
MSFN Forums > Microsoft Software Products - Discussion & Support > Microsoft Office 97/2000/2002-XP/2003/2007   |
 Apr 14 2006, 10:22 AM Post
#1 | |
| Follow the rules please :-)  Group: Patrons Posts: 6780 Joined: 14-November 03 From: Bangalore, India Member No.: 9470   |
(updated to reflect final RTM version) Unattending or silently installing MS Office System, has now become easier than ever. There are two ways to unattend your setup: --> Option A (use it only if you got Office2007 thru SoftwareAssurance, which comes with activation stripped out). --> Option B is for all the others (retail/OEM/academic/trial/etc). Both are colored differently below. Option A: 1. Ensure you have an actual VLK (some call it enterprise/corporate) disc & product-key. 2. Notably, o2k7 uses setup patches (*.MSP) for uA, 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 point1 above, then you will end up wasting 15 minutes of your life which I'm not responsible for. 3. Now at the command prompt, type: setup.exe /admin 4. Choose the product for which you want to make a customization-patch. 5. Then go through all steps in the customization wizard (to install the reqd apps & remove junk & change default settings). 6. 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. 7. Save the resulting patch file in the same folder as o2k7 setup files. 8. Now just execute this command (thru any method) for silent install: setup.exe /adminfile CUSTOM.MSP Or if you have the Office 2007 Enterprise VLK, you could even drop the CUSTOM.MSP file in the "Updates" folder & setup will pick it up automatically (without any switches being used). For this, ensure you have WindowsInstaller 3.1 already installed. You can add in further MSP files (extracted from SP1 update EXE) as well, to have updates applied during install. *** For completely silent install, you MUST set the DisplayLevel to "none", either by MSP (accessible from step 6 above) or by xml, otherwise you'll get a confirmation dialog similar to the image shown in attachment below. (do this only AFTER testing, when you're sure it works)  
confirm.jpg ( 24.3K )
Number of downloads: 1284This post has been edited by prathapml: Nov 8 2008, 12:24 PM |
 |   |
| Apr 14 2006, 11:11 AM Post
#2 | |
| Follow the rules please :-) Group: Patrons Posts: 6780 Joined: 14-November 03 From: Bangalore, India Member No.: 9470 | Option B: 1. Go to the folder-path, "Office2007\Pro.WW" (or any ??????.WW folder for other editions such as standard/enterprise/etc) 2. Modify "config.xml", or copy it to somewhere else & modify it, using my posted code below as a sample. 3. If you modified it "in location", then setup will take up the changes automatically. 4. Otherwise, place the modified file in the same folder of setup.exe, as custom-uA.XML 5. This is the command to run setup with the customizations specified in custom-uA.XML: setup.exe /config custom-uA.XML 7. This method is also a great way to make changes to the defaults itself, so that you dont need to keep changing it upon every new time you install it. The sample XML here, makes setup fully silent, cuts down features rarely used by me, and reduces install footprint of Office 2007 Professional from 721 MB, to 303 MB (of course you can always add/remove components later); I've also removed lines that I found useless from it, you might like to keep many of the default lines & customize them. Also, be aware that the XML offers a way to chain updates & install them before or after o2k7 setup, but then you'll lose control over reboot parameters. By default, o2k7 setup wont cause an auto-reboot, so no need of "/noreboot" or "Reboot=ReallySuppress" properties. I intend this XML to be used for clean installs, with no previous version settings or profiles to be migrated. Use "start /wait" for silent installs. This file is for the main suite, you can modify it accordingly for the other component products, the options are commented with double-slashes. I obtained the OptionIds from setup.xml files, in each component folder. Here's a tested/working config.xml file, to get you started with Option B: (you need to put in your own key, and configuration-Product can be obtained from your current xml) CODE <Configuration Product="Pro"> The procedure is same for all other editions of Office 2007. The above is just a working sample, you'd need to put in an appropriate key & modify as per your needs.<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> <USERNAME Value="0wner" /> <COMPANYNAME Value="0wn Inc." /> <OptionState Id="ACCESSFiles" State="absent" Children="force" /> //access <OptionState Id="OUTLOOKFiles" State="absent" Children="force" /> //outlook <OptionState Id="PubPrimary" State="absent" 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="absent" Children="force" /> //handwriting <OptionState Id="DocServicesFiles" State="absent" Children="force" /> //docu update util <OptionState Id="HTMLSourceEditing" State="absent" Children="force" /> //script editor <OptionState Id="DocumentImagingUtils" State="absent" Children="force" /> //scanning,ocr,indexing <OptionState Id="OISFiles" State="absent" Children="force" /> //picture manager <OptionState Id="OSESupp" State="absent" Children="force" /> //sharepoint support <OptionState Id="QueryFiles" State="absent" Children="force" /> //msQuery <OptionState Id="VisioPreviewerFiles" State="absent" Children="force" /> //visio viewer <OptionState Id="XDOCSFiles" State="absent" Children="force" /> //infopath <!-- These are additionals from Enterprise RTM <OptionState Id="GrooveFiles" State="absent" Children="force" /> //groove <OptionState Id="OneNoteFiles" State="absent" 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 --> </Configuration> If you downloaded a single SETUP.EXE (500-MB?) from MSDN, then you might need to extract it to some folder, to get the installation source. CODE setup.exe /extract:D:\o2k7 This post has been edited by prathapml: Mar 25 2007, 08:04 PM |
| | |
| Apr 14 2006, 11:35 PM Post
#3 | |
| Follow the rules please :-) Group: Patrons Posts: 6780 Joined: 14-November 03 From: Bangalore, India Member No.: 9470 |
My only beef with this version (atleast in the current beta), is that there doesn't seem to be any way to disable creation of the LIS. (LIS = local installation source, its the s*** that you see in the name of an "MSOcache" folder littering any of your HDD partitions at random). If the LIS was disabled by default, the installation time could be reduced by 3 minutes approx, besides saving HDD space (because the last 3 minutes consists of copying files from CD to the LIS). Here's what I've already tried in the config.xml, but both failed: CODE <LIS CACHEACTION="REMOVECACHEONLY" /> CODE <CDCACHE Value="0" /> In both cases, setup refuses to use the XML.Yes, I know that we could write a batch file to search all drives for the "MSOcache" folder & delete it if found, but it would be even better to disable LIS, in the first place. Does anybody know how to do this in o2k7?  |
| | |
 Apr 19 2006, 07:31 AM Post
#4 | |
| Group: Members Posts: 1 Joined: 19-April 06 Member No.: 94096  |
Hello prathapml, Do you maybe know a way to tell setup that I want a customized setup and keep my previous office 2003 installation ? Your explanation on editing config.xml really worked for me ! Thank you very much ! Robert Louwen |
| | |
| Apr 19 2006, 08:20 AM Post
#5 | |
| Advanced Member  Group: Members Posts: 426 Joined: 28-January 04 From: Shimla-India Member No.: 13315 |
@prathapml Good one! This thread was really required (though I may be miles away from the new 2007 office versions). Keep it up! |
| | |
| Apr 19 2006, 01:41 PM Post
#6 | |
| Follow the rules please :-) Group: Patrons Posts: 6780 Joined: 14-November 03 From: Bangalore, India Member No.: 9470 | QUOTE (RobertLouwen @ Apr 19 2006, 07:01 PM)  Do you maybe know a way to tell setup that I want a customized setup and keep my previous office 2003 installation ? Hi Robert,I believe what you want to do, is to have access to all dialogs, you basically want to just customize the setup defaults & go ahead normally from there on. Here's how: Go to the 2nd line in my example above. You see "Display Level="none"". Change it back to "full" instead of "none". That is all. @clavicle Thanks indeed.  I just wish someone finds out how to disable the "MSOcache" facility in o2k7.....
|
| | |
| Apr 19 2006, 05:35 PM Post
#7 | |
| MSFN Addict  Group: Super Moderator Posts: 1861 Joined: 14-April 05 From: Wisconsin Member No.: 51914 OS: Windows 7 x64  |
Very excellant post prathapml, glad to see an unattended way to do this finally was lookinf for a way and you beat me to it, i'll have to try this tommorow at work
|
| | |
| May 24 2006, 09:45 AM Post
#8 | |
| Newbie Group: Members Posts: 38 Joined: 5-June 05 Member No.: 59099  |
Is there a way to install Office 2007 Beta 2 without it checking for previous versions - it wont let me install it because it says I have prevous versions installed which I dont
|
| | |
| Jun 1 2006, 01:36 AM Post
#9 | |
| Group: Members Posts: 3 Joined: 31-May 06 Member No.: 97666 |
Hi there, after I found out, that I just have to execute my OPPLUS-DE.EXE and grab the contents after unpacking from my temp dir befor cancelling the installation, I was able to alter the config.xml file the way you suggested. ;-) However, I still get a dialog window asking whether to install or to alter settings. Even with Display Level = "none". When I click install, the whole process takes place unattended as expected. When choosing to alter settings I see, that my changes in the config.xml are working. Any ideas why I still get this dialog? Regards, Chris. |
| | |
| Jun 1 2006, 04:27 AM Post
#10 | |
| Group: Members Posts: 2 Joined: 31-May 06 From: Mumbai Member No.: 97677 |
[font=Tahoma][size=2] Can we change LIS location using Config.xml? |
| | |
| Jun 2 2006, 03:08 AM Post
#11 | |
| Senior Member Group: Members Posts: 551 Joined: 4-July 04 From: Vienna, Austria Member No.: 23952 OS: none  | QUOTE However, I still get a dialog window asking whether to install or to alter settings. Even with Display Level = "none". When I click install, the whole process takes place unattended as expected. When choosing to alter settings I see, that my changes in the config.xml are working. Hi! I have the same problem. The config.xml is obviously being used but I get the same dialog window. By the way ... is there a way to tell Office in the config.xml to install ALL components, not just the default ones ? Thanks, Alex |
| | |
| Jun 2 2006, 03:20 AM Post
#12 | |
| Group: Members Posts: 3 Joined: 31-May 06 Member No.: 97666 |
I didn't find an option that automatically selects all available features. Regarding the Dialog Window: I managed to create a script that can be integrated into an unattended setup to automatically click the button. The only problem is, that if you deploy Office 2007 with SMS 2003 for instance, the script won't work, since the gui will not be visible to the user. And this is basically my problem,... I can't get it to work with SMS 2003. However, here is the script: CODE Dim objWSHShell, objExec Set objWSHShell = WScript.CreateObject("WScript.Shell") On Error Resume Next ' Wait for Uninstall ' -------------------------------------------------------------------------------- Set objExec = objWSHShell.Exec("setup.exe") WScript.Sleep 500 ' -------------------------------------------------------------------------------- waitForWindow "Microsoft Office Professional Plus 2007 (Beta)" objWSHShell.SendKeys "{ENTER}" ' <install> WScript.Sleep 500 ' Wait for the setup to finish Do While objExec.Status = 0 WScript.Sleep 500 Loop ' Quit this script WScript.Quit ' Waits until the window appears or quits after 30 seconds SUB waitForWindow( Title ) i = 0 DO bActive = objWSHShell.AppActivate( Title ) WScript.Sleep 1000 i = i + 1 LOOP UNTIL bActive = TRUE OR i > 30 WScript.Sleep 100 END SUB |
| | |
| Jun 2 2006, 09:19 AM Post
#13 | |
| Senior Member Group: Members Posts: 551 Joined: 4-July 04 From: Vienna, Austria Member No.: 23952 OS: none |
Hi ! thanks for the script. Will try it soon ! Here´s an adapted config.xml that will install EVERYTHING except Japanese font and New/open document links. CODE <Configuration Product="Pro"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <PIDKEY Value="ENTER CODE" /> <USERNAME Value="0wner" /> <COMPANYNAME Value="0wn Inc." /> <OptionState Id="ACCESSFiles" State="local" Children="force" /> //access <OptionState Id="OUTLOOKFiles" State="local" Children="force" /> //outlook <OptionState Id="EXCELFiles" State="local" Children="force" /> //excel <OptionState Id="PubPrimary" State="local" Children="force" /> //publisher <OptionState Id="PPTFiles" State="local" Children="force" /> //Powerpoint <OptionState Id="AceRepl" State="local" Children="force" /> //access db Engine replication <OptionState Id="CAGFiles" State="Local" Children="force" /> //Clip Organizer <OptionState Id="MSSOAP3" State="local" Children="force" /> //SOAP toolkit <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="local" 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="OsaNonBoot" State="absent" Children="force" /> //new,open office docu lnks </Configuration> Bye, Alex Hi again, mhh, if I start your script with this line CODE wscript "path.to\script.vbs" I get a Windows XP Setup message !! Maybe the path to the setup.exe is wrong. I have found these lines CODE Set FileSysObj = CreateObject("Scripting.FileSystemObject") ScriptPath = FileSysObj.GetFile(WScript.ScriptFullName).ParentFolder in some other script but they do not work in your script (and I am not good at vbs scripting at all)  MAybe something else is wrong too because the same thing happens if I double click on the vbs ... Thanks for your help, Alex This post has been edited by midiboy: Jun 2 2006, 09:31 AM |
| | |
| Jun 2 2006, 05:00 PM Post
#14 | |
| Senior Member Group: Members Posts: 551 Joined: 4-July 04 From: Vienna, Austria Member No.: 23952 OS: none |
Hi again, I adapted some other script I found on the net. This one works for me: CODE dim WshShell, iLoopTimeWait Set WshShell = CreateObject("WScript.Shell") iLoopTimeWait = 800 Set FileSysObj = CreateObject("Scripting.FileSystemObject") ScriptPath = FileSysObj.GetFile(WScript.ScriptFullName).ParentFolder Cmd = Chr(34) & "setup.exe" WshShell.Run Cmd Call Main() Set WshShell = Nothing WScript.quit() Sub Main() Connect2Window iLoopTimeWait, "Microsoft Office Professional Plus 2007 (Beta)" WshShell.SendKeys ("{ENTER}") End Sub Function Connect2Window(iTime, sWindowName) Do until WshShell.AppActivate (sWindowName) WScript.Sleep iTime loop End function This post has been edited by midiboy: Jun 3 2006, 05:45 AM |
| | |
| Jun 6 2006, 03:46 AM Post
#15 | |
| Group: Members Posts: 2 Joined: 31-May 06 From: Mumbai Member No.: 97677 |
Very excellant post prathapml, I recently installed Office 2007 on my machine and noticed that MSOCache folder is being created under my %HOMEDRIVE%. I went through ORK 2007 documentation and it suggestes that that location should be %PFiles%\Microsoft Office\Office 12\MSOCache. prathapml, can I specify the LIS Location in config.xml in a such way, whenever setup will start cache it will cache only under dir mentioned in config.xml. The config.xml file you have provided is very useful. However, I tried several ways to prevent Access and Visio installation using config.xml. Though I successed the same using .MSP I would like to do the same using config.xml. Can you please give me some tips on this? Thanks a lot. This post has been edited by vilasshewale: Jun 6 2006, 03:49 AM |
| | |
 Jun 6 2006, 11:11 AM Post
#16 | |
| Newbie Group: Members Posts: 13 Joined: 18-January 05 Member No.: 41270 | QUOTE (prathapml @ Apr 14 2006, 11:11 AM) Option B: 1. Go to the folder-path, "Office2007\Pro.WW" 2. Modify "config.xml", or copy it to somewhere else & modify it, using my posted code below as a sample. 3. If you modified it "in location", then setup will take up the changes automatically. 4. Otherwise, place the modified file in the same folder of setup.exe, as PRO.XML 5. This is the command to run setup with the customizations specified in PRO.XML: setup.exe /config pro.xml I guess I'm clueless - all I have is the installer executable from Microsoft - could someone post a more detailed set of instructions for slipstreaming this? I extracted the installer with winrar, found a ProWW.cab... am I supposed to extract that too? All the other cabs? What do I do with them afterward? I've made installer CDs before with nlite, etc, but I am not familiar with the process here... there seem to be quite a few steps left out as "you should just know them".... I don't. |
| | |
| Jun 7 2006, 03:28 AM Post
#17 | |
| Newbie Group: Members Posts: 43 Joined: 4-November 03 Member No.: 9028 |
i'm getting an error message: CODE Setup could not find any available products to install. Please contact your system administrator Please help Regards, Jeet |
| | |
| Jun 8 2006, 01:02 AM Post
#18 | |
| Group: Members Posts: 3 Joined: 31-May 06 Member No.: 97666 |
aelfwyne: Run the setup file with /extract:<PATH> with <PATH> being the path where you want the files to be copied to. Also you can run the setup file with /? to vie the possible parameters.
|
| | |
| Jun 10 2006, 11:29 AM Post
#19 | |
| Follow the rules please :-) Group: Patrons Posts: 6780 Joined: 14-November 03 From: Bangalore, India Member No.: 9470 |
@midiboy: No need of VBscripts, just use this command-line for fully silent install: CODE setup.exe /config pro.xml You shud execute this from your SMS scripts or thru unattended batch-files. Note that modifying the original config.xml is sub-optimal, it'd be better to specify path to a *.XML file that you've created! And to others, well, LIS configuration eludes me as of now. And yes, i did forget to mention that you need to run setup & when the first screen shows, grab the extracted files from your %temp%. And here's a link to some info that MS has now put up, for everyone to access - http://www.microsoft.com/office/preview/beta/deploy.mspx |
| | |
| Sep 15 2006, 02:17 AM Post
#20 | |
| Senior Member Group: Members Posts: 551 Joined: 4-July 04 From: Vienna, Austria Member No.: 23952 OS: none |
Hi guys, has anyone found a way to integrate the Technical refresh into the Office 2007 installation base ? If the TR is run, it expands a bunch of msp files into the temp folder. However, those msp files do not directly correspond with the installation msi files except for the ProWW.msp so I don´t know which msp I should be running against which msi. edit: Running an msiexec /p ProWW.msp /a ProWW.msi does not work at all. The process quits right at the beginning. Has anyone found a solution yet ? Thanks, Alex This post has been edited by midiboy: Sep 15 2006, 03:01 AM |
| | |
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 7th November 2009 - 11:07 AM |
All trademarks mentioned on this page are the property of their respective owners
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy