- Message Boards
- Package KB
- Software KB
- Free Videos
- MSI Errors
- Tools
- Tech Home Pages
- Reviews
- Downloads
- Articles
- FAQs
- Tips & Tricks
- Services
- News
- Newsletter
Search AppDeploy
Office 2007 12.x
| Company: | Microsoft |
| Setup Type: | Native Windows Installer setup (MSI) |
| Package Difficulty Rating: |
[ Rate It or View Ratings ]
|
| Most Commonly Reported Method: | Windows Installer (with Custom Transform) |
| Record Created On: | 10/5/2006 |
| Number of Views: | 147,476 |
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.
Software Knowledge Base
Software Knowledge BaseFull Name: Microsoft Save as PDF or XPS Add-in สำหรับโปรแกรม Microsoft Office 2007
Version: 12.0.4518.1019
Publisher: Microsoft Corporation
Help: http://www.microsoft.com/support
Uninstall String: MsiExec.exe /X{90120000-00B2-041E-0000-0000000FF1CE}
More Info URL: http://www.microsoft.com/support
Categories: Desktop
Threat: Fairly Safe
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.
| After you create the .msp file you can deploy the setup out like this: "setup.exe" /adminfile "office.msp" | ||||
| Above Entry Provided on 4/12/2007 by JTMan33 | Rate It | Rating 181 | ||
| You can also specify the product to be installed by using the /config switch: setup.exe /adminfile custom.msp /config ProPlus.WW\config.xml You don't have to modify the config.xml but there are some options that you can uncomment. | ||||
| Above Entry Provided on 5/9/2007 by spoirier | Rate It | Rating 0 | ||
| Silent uninstall information: http://technet.microsoft.com/en-us/library/cc178956.aspx /uninstall [ProductID] Runs Setup to remove the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify. Example \\server\share\Office12\setup.exe /uninstall Enterprise where Office12 is the root of the network installation point, and Enterprise is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office12\Enterprise.WW\setup.xml), where Enterprise.WW is the location of the Microsoft Office Enterprise 2007 installation files. You can customize the /uninstall option by using it with /config and a modified Config.xml file. This is essential if you want to run a “silent†uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use. To run a silent uninstall: Using a text editor, edit the following element attributes in the \\server\share\Office12 Enterprise.WW\SilentUninstallConfig.xml file: <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> </Configuration>At the command line, use the following syntax: \\server\share\Office 12\setup.exe /uninstall Enterprise /config \\server\share\Office 12\Enterprise.WW\SilentUninstallConfig.xml | ||||
| Above Entry Provided on 8/16/2008 by nzdude | Rate It | Rating 133 | ||
| For Microsoft Office Enterprise 2007 12.0.6425.1000 I used the following... Full Command Line: setup.exe /adminfile office2007.msp | ||||
| Above Entry Provided on 5/13/2010 by tstaub | Rate It | Rating -3 | ||
| For version 12.0.6425.10000 I used the following msiexec.exe command msiexec.exe /x {90120000-0011-0000-0000-0000000FF1CE} /quiet /qn /norestart | ||||
| Above Entry Provided on 7/28/2010 by gharouff | Rate It | Rating 0 | ||
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.
| The successor of the famous Office Resource Kit Tools (ORK) to customize the Office installation is now called Office Customization Tool (OCT) and is included within the original setup so you don't need to download anything. To start the Office Customization Tool (OCT) type setup.exe /admin. At the end of the process, the OCT saves your choices in a MSP file, rather than the transform (MST) produced by the Custom Installation Wizard. Like a transform, the customization file results in uniform default configuration of the product for all users. Unlike a transform, however, which you had to specify explicitly on the command line or in the Setup.ini file, you can allow Setup to apply the customization file automatically by storing it in the Updates folder at the root of the network installation point. During the installation, Setup finds and applies all the MSP files in the Updates folder - both customization files and Software Updates - that match that product. You can specify an alternate location for MSP files in Config.xml, or you can point to a particular customization file by using the /adminfile command-line option. For detailed information about using the OCT, see this article at Microsoft. | ||||
| Above Entry Provided on 10/8/2006 by rpfenninger | Rate It | Rating 137 | ||
| If you deployed a previous version of Office in a large organization, you probably ran Setup.exe from your source media with the /a command-line option to extract compressed installation files and to create an administrative installation point on the network. The administrative installation point served as the initial source for users installing the product, and the ongoing source for maintenance operations such as install on demand and repair. In the 2007 Office release, there is no /a option. Instead, creating a network installation point is as simple as dreagging and dropping installation files from the source media to the server. All installation files remain compressed and unchanged on the network source. When you install Office on users' computers, Setup copies the installation files from the network to a local installation source on the client computer and completes the installation from there. The local source - not the network - becomes the primary source for maintenance operations. | ||||
| Above Entry Provided on 10/8/2006 by rpfenninger | Rate It | Rating 120 | ||
| Retail 2007 Office products do not support the /admin switch (that provides the new Office Customization Tool (formerly Custom Installation Wizard)) as it does not include the files that make up the needed "Admin" folder. The message shown when it is unavailable reads, Setup Error: "Files necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product." It should be noted that the edition of Office 2007 that is provided via MSDN is retail. Only volume license/enterprise editions will have the ability to use the Office Customization Tool (OCT). | ||||
| Above Entry Provided on 11/27/2006 by bkelly | Rate It | Rating 120 | ||
| I have found it better to first uninstall Office 2003 before installing Office 2007 when Office 2003 has been deployed through GPO. I noticed that even though Office 2003 is gone its shortcuts remain and when clicking on the shortcut it will try to reinstall that Office program from the GPO source. Very annoying so uninstall Office 2003 first. By the way does anyone know how two turn off those two questions that the user gets prompted with when they first run an Office 2007 program. I think one is on privacy options and the other is on sign up for Microsoft Update. | ||||
| Above Entry Provided on 12/2/2006 by anthonymel | Rate It | Rating 121 | ||
| To remove privacy option popup, set the following values in the registry: [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\User Settings\Product code] "Count"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General] "Authorized"=dword:00009904 "ShownOptIn"=dword:00000001 | ||||
| Above Entry Provided on 12/6/2006 by germo001 | Rate It | Rating 130 | ||
| The registry entries work great to get rid of the Privacy Options when the application is first opened, but to get rid of the option to go to Office Updates at the end of the install, you must go into the msp file, go to the Modify Setup properties section, and add a property named HIDEUPDATEUI with the value set to True. | ||||
| Above Entry Provided on 3/14/2007 by WillDunn | Rate It | Rating 132 | ||
| Office 07-My quick summary, Microsoft really wants you to install Windows Desktop Search. It takes up extra resources. Here is how to disable the Warning notification about Windows Desktop not being installed or up to date please contact your system administrator. Thanks for the extra helpdesk support call Microsoft. Anyway here is how to disable it. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\General Create string value PONT_STRING value of 60 Each value correlates to a message box. I just know 60 is for that darn WDS notification. Also thanks to the others for helping to disable the WDS download. | ||||
| Above Entry Provided on 4/19/2007 by jameson | Rate It | Rating 125 | ||
| This is the message you get when you first run Outlook 2007 if you're not going to install Windows Desktop Search. [Windows Desktop Search is not currently installed or not up to date. Outlook will not be able to provide fast search results when using the new Instant Search functionality unless this Windows component is installed. Please contact your system administrator.] To get rid of the message permanently, when you check the "Do not show this message again" tickbox and click OK, the following key gets set: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\General PONT_STRING" (reg_sz),"60" More information about PONT_STRING and how it is used is found here: http://support.microsoft.com/kb/831398 | ||||
| Above Entry Provided on 5/24/2007 by nzdude | Rate It | Rating 119 | ||
| If you want to uninstall Office 2007: 1: Run setup.exe /uninstall. 2: You need to edit the config.xml file in the product folder you wish to uninstall. 3: Make sure the package folder is different from the one you use to install. The Updates folder should NOT have the .msp file you used to install Office. The folder should be empty | ||||
| Above Entry Provided on 6/12/2007 by scarneiro | Rate It | Rating 117 | ||
| The (free) downloadable Microsoft book "Deployment for the Office 2007 release" currently (as of 13th June 2007) has the wrong package codes in the section "run setup from the local installation source". I've logged a ticket with Microsoft to get this fixed, but basically, the codes should be {9012000-nnnn-...} instead of {94012000-nnnn-...} The information is also wrong here: http://technet2.microsoft.com/Office/en-us/library/7897ccea-d9e2-4cdf-bb63-53090da8fd0d1033.mspx NOTE: Microsoft fixed this in late 2007, but if you had previously downloaded the book or printed out the documentation, you might want to check. | ||||
| Above Entry Provided on 1/10/2008 by nzdude | Rate It | Rating 122 | ||
| So i'll share a little of what I've learned with Office 2007 - Not sure if this is documented anywhere but here goes... The registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings] Works just like Active Setup, that meaning each subkey is applied to a current user hive(in the same location) if it does not exist. Each subkey should have a "Count"=dword:00000001 and "Order"=dword:00000001 (I've also seen an 8 value here) The following two examples change(or add) the location for shared templates and hide the "Instant Search" Bar at the top of the Outlook window(which lets users download Windows Desktop Search). These examples use the Create registry key... You can also use the CreateFile which i'll show below to copy a file to a users profile. --> Delete(Current user Registry) is also available but I haven't use it, looks like the setup is the same as Create. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\AllUsersTemplates] "Count"=dword:00000001 "Order"=dword:00000008 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\AllUsersTemplates\Create\Software\Microsoft\Office\12.0\Common\General] "SharedTemplates"=hex(2):-fill in your own Binary Value- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\RemoveInstantSearchBar] "Count"=dword:00000001 "Order"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\RemoveInstantSearchBar\Create\Software\Microsoft\Office\12.0\Outlook\Search] "DisableDownloadSearchPrompt"=dword:00000001 <<<<< CreateFile >>>>>>> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\FileCopy1] "Count"=dword:00000001 "Order"=dword:00000008 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\FileCopy1\CreateFile\FileCopy1.potx] "TargetFile"="[AppDataFolder]\\Microsoft\\Templates\\FileCopy1.potx" "SourceFile"="C:\\Documents and Settings\\All Users\\Templates\\FileCopy1.potx" | ||||
| Above Entry Provided on 6/14/2007 by gmorgan618 | Rate It | Rating 127 | ||
| There's also a bug in the Common Feed List group policy. The "Synchronize Outlook RSS Feeds with Common Feed List" setting is not set correctly in the Office Customization Tool and in the Group Policy templates http://support.microsoft.com/kb/932126 Also, even if you enable that, Outlook still prompts and asks the user if they'd like to use the Common Feed List which will override the GPO setting temporarily (until they close reopen Outlook. In order to prevent the prompt from coming up, a value of 48 needs to be appended to HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\General\PONT_STRING. So, for instance, I already had 60 in there to prevent the desktop search box, so my value is now "60,48," | ||||
| Above Entry Provided on 8/24/2007 by Scotte | Rate It | Rating 125 | ||
| I've tried every reg setting I could find on the web in the OCT; however, only one successfully worked one time. That setting was actually listed on Microsoft's site. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General ShownOptIn (Value) 00000001 Every other time I've I tried to launch the install with any reg settings in the OCT it gets messed up. What happens is the install completes but it does not put any shortcuts in the system anywhere. If I attempt to run any of the office 2007 programs from the program files folder I get "Word does not have enough memory". | ||||
| Above Entry Provided on 9/4/2007 by aquateen | Rate It | Rating 118 | ||
| In addition to notes listed above, here are specific registry keys that can be used to stop the Opt-In Wizard appearing for all users. It uses the HKLM to HKCU mechanism built in to Office 2007 (the best explanation I found was here) which means each time an Office 2007 application is started, the registry entries specified here are pulled from the HKLM entry and put into HKCU hence taking affect for all users regardles of if they have logged into the PC previously or not. ---- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn] "Count"=dword:00000001 "Order"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn\Create\Software\Microsoft\Office\12.0\Common\General] "ShownOptInFix"="Applied" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn\Create\Software\Microsoft\Office\12.0\Common\General] "ShownOptIn"=dword:00000001 ---- You can cut and paste the above into a .reg file and either import it into the 'Add registry entries' section of the OCT (which is probably the neatest solution) or run otherwise after install. | ||||
| Above Entry Provided on 9/28/2007 by adamind | Rate It | Rating 121 | ||
| In addition to the MSDN distributing a retail copy (see above OCT error), Action Pack subscribers are also receiving a retail copy. | ||||
| Above Entry Provided on 10/3/2007 by Drac346 | Rate It | Rating 117 | ||
| Easiest and quickest way to uninstall a product is to amend the a Config.xml file as follows: <Configuration Product="Product Name"> <Display Level="none"/> <Setting Id="SETUP_REBOOT" Value="NEVER"/> </Configuration> This will uninstall the product and stop the machine from restarting. This will need to be called using the setup.exe /config ...\config.xml /uninstall "Product Name" command | ||||
| Above Entry Provided on 10/29/2007 by Netviz | Rate It | Rating 119 | ||
| http://support.microsoft.com/kb/940289/en-us Description of Office Compatibility Pack Service Pack 1 Just like Visio Viewer 2007, the Office Compatibility Pack 2007 SP1 is just a Service Pack which is almost as big as the original. You need to install the Compat Pack, then SP1. Hopefully Microsoft will reissue this as a standalone pre-patched installation. | ||||
| Above Entry Provided on 2/15/2008 by nzdude | Rate It | Rating 116 | ||
| If you have a MSDN or retail version of Office 2007 and want to run the Office Customisation Wizard, download the "2007 Office system Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool version 2.0" from http://www.microsoft.com/downloads/details.aspx?FamilyID=92d8519a-e143-4aee-8f7a-e4bbaeba13e7&DisplayLang=en. Extract the files and the copy the complete Admin directory into the network installation folder. The OCT can the be started using the setup.exe /admin as documented elsewhere. The Completed msp needs to be saved in the Updates folder. | ||||
| Above Entry Provided on 2/18/2008 by neil.cole | Rate It | Rating 121 | ||
| I just finished a Premier support call with Microsoft and some of what we discussed may be useful to you if you are planning an Office 2007 deployment. Issue 1 I performed a standalone install of Outlook 2007: when trying to install the full Office 2007 Pro (from an existing 2003 Office Pro environment) I received a prompt asking me to to choose which action I wished to take (update Outlook or install Office 2007 Pro). Fix: if you control your installation options using a .msp, ensure the Office 2007 pro .msp file you created is located in the updates folder and you set the view in that .msp to basic or none. This keeps the nstall silent and avoid being prompted. You can do this other ways, but placing it in the updates folder saves you a step having to declare setup /adminfile %pathtoyour.msp%. As I already had already installed Outlook 2007 I deselected in in my .msp. Issue 2 Upon removing Outlook 2007 and then attempted to re-install Outlook and/or any other Office 2007 application I received a "duplicatedefinition" error. Fix: replace your source files with a fresh copy (disc or from MSDN). Microsoft does not have a definitive way to determine which .xml file may have produced the corruption issue so they recommend you replace all the installation files. Issue 3 Hotfixes do not apply when placed in the updates folder. Fix: In my case, read the documentation. You must extract (hotfixname.exe /extract) a hotfix and place the .msp in the updates folder. As with any other .msp placed in that folder, it is automatically at install. Issue 4 I cannot suppress the privacy notice in Office. Fix: use the latest templates, ensure you install office 2007 sp1, and then office-kb941275-fullfile-x86-glb.exe --in that order. If you install the roll-up (kb941275) first sp1 will not load correctly. I mention this since I had a pre-release of KB941275 which did not require office sp1 to be installed, so I had to rip it out, apply sp1, and then apply the final release of 941275. Issue 5 After updating to Outlook 2007 and/or Office Pro 2007 (without MS Access 2007 installed) your SharePoint edit in datasheet feature crashes I.E. Fix: install MS Access 2007 runtime or remove and then re-apply the Windows SharePoint Services Support built into the Office 2007 products. In regards to the SharePoint services, this can get bugged compeling you to remove and then re-add. Hope you find this moderately helpful. | ||||
| Above Entry Provided on 3/19/2008 by ManiacMarine | Rate It | Rating 121 | ||
| Issue: You get a message a dialog box is in use when you lauch Outlook 2007 but you cannot force the box to the foreground. Fix: None from Microsoft at this time. Workaround: modify your registry with the content shown below. Please note if Outlook is already open, you must force Outlook.exe to close, add the registry information, and the start Outlook. [HKEY_CURRENT_USER\Software\Microsoft\Office\Common\UserInfo] "Company"="whatever your company is named" "UserName"="user" "UserInitials"="user" I added this to my .mst using the office customization tool --add registry entries section but a reghack, manual entry, or command line addition would work as well. | ||||
| Above Entry Provided on 3/20/2008 by ManiacMarine | Rate It | Rating 118 | ||
| To include SP1 in your Office 2007 installations, including AD deployment and any other installations, use the following steps: 1. Download the SP1 installation package, available at the following site at the time of writing: http://www.microsoft.com/downloads/details.aspx?FamilyId=9EC51594-992C-4165-A997-25DA01F388F5&displaylang=en 2. Navigate to the SP1 installer you've downloaded, and from the command line extract its contents to the Updates folder in your Office 2007 installation location. The command syntax for me was as below, where the Office source folder should be inserted to the /extract switch: office2007sp1-kb936982-fullfile-en-us.exe /extact:" Make sure you have write access to the destination folder first. Once you've extracted the MAINWWsp1.msp and other MSP files into Updates, your subsequent Office 2007 installations will automatically launch the SP1 update with no further input from the user. | ||||
| Above Entry Provided on 3/21/2008 by netjustin | Rate It | Rating 122 | ||
| If you set the key "HKCU\Software\Microsoft\Office\12.0\Common\Internet\DisableCustomerSubmittedDownload" to 1 the online templates won't work and Word will show an error message and quits with an error even if you allow the online templates. Solutions: 1. Set the key back to 0 or 2. download and run office-kb956506-fullfile-x86-glb.exe which solves the problem | ||||
| Above Entry Provided on 10/17/2008 by clearbyte | Rate It | Rating 2 | ||
| The OCT has the ability to save the default file type also which isn't mentioned anywhere here. It is kind of hard to find. But, if you look under Modify User Settings > Microsoft Word 2007 > Word Options > Save > Save files in this format you will see the setting for Word. You can find the others using this example. Enjoy! | ||||
| Above Entry Provided on 1/7/2009 by mbruner | Rate It | Rating 0 | ||
| We have a corporate policy that only templates that conform to our style guide can be used. In the default Office installation, the File > New dialog box is different and you have access to quite a few Office Online templates. For corporates, this isn't good. I unticked all the template-related items in the OCT, but the templates were still showing. A Microsoft MVP has stated in an online forum that you can choose not to install standard templates in Access and Publisher, but you can not stop the installation in Word 2007. I found http://support.microsoft.com/kb/953474, which says to create this key to force Office to use the old-style File > New dialog box. [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Common\Internet] DisableTemplatesOnTheWeb=1 This is a setting exposed in Office12.adm, so you can set it that way, and it works (as long as you have KB953474 installed), but then you see a whole heap of different templates that make it difficult for corporate users to find our company's templates (eg: Equity Report, New Blog Post, and Median Resume). People have struggled with getting rid of these, including some suggestions to delete HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Components\8F622368F04F7B849AÂ7B2021EE668F21 The solution is simple.. turns out you only need to set [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General] MyTemplatesOnly = 1 (DWORD) It appears that with this key enabled, you don't need to even set DisableTemplatesOnTheWeb=1, but I'm setting both. Here's an adm I created: CLASS USER CATEGORY !!YOURCOMPANYNAMEHEREHeader CATEGORY !!OptInHeader CATEGORY !!OptInContent POLICY !!PolicyMyTemplatesOnly KEYNAME "Software\Policies\Microsoft\Office\12.0\Common\General" EXPLAIN !!ExplainMyTemplatesOnly VALUENAME "MyTemplatesOnly" VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 END POLICY END CATEGORY END CATEGORY END CATEGORY [strings] YOURCOMPANYNAMEHEREHeader=YOURCOMPANYNAMEHERE Custom Policies OptInHeader=Microsoft Office 2007 OptInContent=My Templates Only PolicyMyTemplatesOnly="Do not show installable and online templates within File New dialog box" ExplainMyTemplatesOnly="Please see http://support.microsoft.com/kb/953474\n\nThis setting, when enabled, will set the\n\nHKCU\Software\Policies\Microsoft\Office\12.0\Common\General\MyTemplatesOnly\n\nregistry value to 1.\n\nThis will ensure that Office 2007 Office doesn't show Office Online and installable templates." | ||||
| Above Entry Provided on 4/1/2009 by nzdude | Rate It | Rating 1 | ||
| Using WinZip for Faster and More Reliable Office 2007 Installations For the highest rate of successful upgrades and installations of Office 2007, several sources (like LANDesk's "Best Known Methods for Deploying Office 2007") promote copying the folders/files needed for the installation to the target machine, and then having the installation execute locally. While I found this definitely results in a higher rate of success (as opposed to having the installation stream from a network share), I also found copying the Office 2007 installation folders/files takes (on our network) a minimum of 30 minutes, and often much longer. With the number of files involved, the packet overhead is great. If machines are running the upgrade/installation concurrently, there is a great amount of network traffic, the copying process is even longer, and the slowness is compounded. To minimize this issue, I created a scripted solution that leverages WinZip. I created a .zip file of the Office 2007 installation directory, and my script copies that single .zip file to the local machine instead of the individual folders/files. This drastically reduces packet overhead and network traffic, and greatly shortens the overall installation time. On average on our network, the .zip file copies to the target machine in 5 minutes or less. Many scripting methods can be used; the key to this approach is using WinZip command line options to extract the .zip file without user interaction. A batch file could have a section that looks like this: cd "C:\Program Files\[WinZip Program Folder]" winzip32.exe -e "C:\[download folder]\Office_2007.zip" "C:\[target folder for extract]\" Once the installation folder has been extracted from the .zip file, the command line options for Office 2007 per Microsoft and as documented in further detail by others here at AppDeploy can be used to execute the installation. | ||||
| Above Entry Provided on 7/14/2009 by craig16229 | Rate It | Rating 5 | ||
| Well I put a few of these tips together and have come up with the following ADM. The "create" keys are genius! and defiantly need to be documented more. Below is ADM template to: 1) remove stupid opt in wizard (even though the MS adms should have done that, as it IS an option) 2) Remove stupid Windows Desktop Search prompting and 3) remove stupid RSS feed prompting. Ownage. So here we go. Its not glamorous at ALL, no comments just dirty to get the job done. also F microsoft for naming something PONT_string. Comeon! I spent at least an hour because of POiNT_string! ---------------Begin code snippet-------------------- CLASS MACHINE CATEGORY "Disable Office 2007 Opt in for Reals" POLICY "Count" KEYNAME "SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn" PART "Count" NUMERIC VALUENAME "Count" END PART END POLICY POLICY "Order" KEYNAME "SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn" PART "Order" NUMERIC VALUENAME "Order" END PART END POLICY POLICY "ShownOptInFix" KEYNAME "SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn\Create\Software\Microsoft\Office\12.0\Common\General" PART "ShownOptInFix" EDITTEXT DEFAULT "Applied" VALUENAME "ShownOptInFix" END PART END POLICY POLICY "ShownOptIn" KEYNAME "SOFTWARE\Microsoft\Office\12.0\User Settings\ShownOptIn\Create\Software\Microsoft\Office\12.0\Common\General" PART "ShownOptIn" NUMERIC VALUENAME "ShownOptIn" END PART END POLICY END CATEGORY CATEGORY "Disable Windows Desktop Search prompting in outlook" KEYNAME "SOFTWARE\Microsoft\Office\12.0\User Settings\Outlook_Core\Create\Software\Microsoft\Office\12.0\Outlook\Options\General" POLICY "Disable Windows Desktop Search in office" VALUENAME "PONT_STRING" VALUEON "60,48," VALUEOFF DELETE PART "Disable Windows Desktop Search" TEXT END PART END POLICY END CATEGORY ------------------------END code snippet------------------ The result is that when a domain user logs in, everything is all setup for them and they get no prompts. yay. | ||||
| Above Entry Provided on 11/18/2009 by deploypimpin | Rate It | Rating 2 | ||
| Proofing Tool kit 2007 can sometimes really be a pain to install. The installation fails in silent mode and in the log file you see something like: "Unable to locate a suitable resource file which contains resources that match the current user's Locale" To solve the problem, add the following Reg key Key: HKLM\SOFTWARE\Microsoft\Office\12.0\Common\LanguageResources Value Name: PreferredSetupLanguage Type: DWORD Data: 1033 (decimal) | ||||
| Above Entry Provided on 1/5/2010 by clearbyte | Rate It | Rating 0 | ||
| to create a custom install of Office 2007, you run the Office setup with the option /admin run: setup.exe /admin This will create a custom admin file. Place this admin file in the "updates" sub directory. For the Dell KACE K1000 Appliance, you then zip up all the Office install files including all sub directories and associate the Zip file to the Office 2007 item listed in Software Inventory. | ||||
| Above Entry Provided on 5/13/2010 by tstaub | Rate It | Rating 1 | ||
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.
| Considerations when installing Outlook 2007 in a Terminal Services environment. http://technet2.microsoft.com/Office/en-us/library/7e816caa-7c1c-4d78-ac28-693aa4ea58d81033.mspx Microsoft recommend that Office 2007 be installed either while sitting at the server or by using ILO, as opposed to over RDP. | ||||
| Above Entry Provided on 1/18/2008 by nzdude | Rate It | Rating 116 | ||
| We came across an issue when we installed Outlook 2007 onto our Terminal Server when using the Symantec Enterprise Vault add-in. (This might affect other Outlook add-ins, too). We would get the following error message the first time each sessions when we tried to open a vaulted message: "Microsoft Office Outlook cannot provide form scripting support." The fix was to force the VBScript component of Outlook 2007 to be installed. The following is from Microsoft Knowledge Base article 302003: To enable VB Script support for Outlook forms when running Outlook 2007 on a Terminal Server computer, do the following: 1. Install Outlook 2007 as a standalone application or as part of a 2007 Office suite. 2. Determine the globally unique identifier (GUID) for the product that you just installed. If you installed Outlook, use that product GUID. If you installed Office Enterprise 2007, use that product GUID. For more information about how to determine the GUID of the product that you installed, click the following article number to view the article in the Microsoft Knowledge Base: 928516 Description of the numbering scheme for product code GUIDs in 2007 Office suites and programs. 3. After you have the product GUID, run the following command line: msiexec /i <Product Code GUID of [SKUName]WW.msi> ADDLOCAL=OutlookVBScript /qb Note In this command, <Product Code GUID of [SKUName]WW.msi> is a placeholder for your product GUID. For example, if you have Office Enterprise 2007 installed, your product GUID would be the following: {90120000-0030-0000-0000-0000000FF1CE} Therefore, the command line should appear as follows: msiexec /i {90120000-0030-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb In our case, because we installed Outlook as a standalone application, we ran the following: CHANGE LOGON /DISABLE CHANGE USER /INSTALL msiexec /i {90120000-001A-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb CHANGE USER /EXECUTE CHANGE LOGON /ENABLE (we found it easier to find the GUID by locating Outlook.WW. It was in the C:\MSOCache\All Users\{90120000-001A-0000-0000-0000000FF1CE}-C folder, therefore our guid was 90120000-001A-0000-0000-0000000FF1CE) | ||||
| Above Entry Provided on 1/18/2008 by nzdude | Rate It | Rating 119 | ||
| Removing the default user name for Terminal Services Office 2007 installations http://technet.microsoft.com/en-us/library/cc179072.aspx Removing the default user name Any user name that is provided during setup is written to the registry key HKCU\Software\Microsoft\Office\Common\UserInfo. Terminal Services mirrors this registry key to HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ TerminalServer\Install\Software\Microsoft\Office\Common\ UserInfo. Any new users then receive the defaults from the HKLM UserInfo key in their own user profile. Because a user name already exists, any new Terminal Services users will not be prompted to input their own names, and instead they get the default user name of the administrator. To resolve this issue for new users in a current Terminal Services deployment, the administrator on the computer running Terminal Services should remove values from the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\ Office\Common\UserInfo. To resolve the issue for all users in a new Terminal Services deployment, the administrator on the computer running Terminal Services should perform one of the following tasks: * During installation, select Customize, and then clear the user name and initial values. * Use a config.xml file that has the user name and initials set to empty values. * After installation, remove the values from the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\ Common\UserInfo. | ||||
| Above Entry Provided on 7/7/2008 by nzdude | Rate It | Rating 120 | ||
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
| Office 2007 Setup Properties Setup command-line options for the 2007 Office system Office Customization Tool in the 2007 Office system | ||||
| Above Entry Provided on 11/27/2006 by bkelly | Rate It | Rating 5 | ||
| How to prevent the "Welcome to the 2007 Microsoft Office system" dialog box from opening when a 2007 Office suite is started for the first time http://support.microsoft.com/kb/929767 INTRODUCTION This step-by-step article describes how to change the registry so that the Welcome to the 2007 Microsoft Office system dialog box does not open when a 2007 Microsoft Office suite is started for the first time. MORE INFORMATION Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Click Start, type Regedit, in the Start Search box, and then click regedit in the Programs list. 2. Expand the following subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General 3. Right-click General, point to New, and then click Dword (32-bit) Value. 4. Type ShownOptIn, and then press ENTER to name the new entry. 5. Right-click ShownOptIn, and then click Modify. 6. In the Value data box, type 00000001, and then click OK. 7. Close Registry Editor. Alternatively, you can use a policy setting in the following subkey to make this change: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Common\General For more information about how to use policies with 2007 Office suites, click the following article number to view the article in the Microsoft Knowledge Base: 924617 (http://support.microsoft.com/kb/924617/) How administrators can use Office policy templates together with the Group Policy settings of Windows Note If this policy setting is later removed, the Welcome to the 2007 Microsoft Office system dialog box opens the next time that the 2007 Microsoft Office suites are started. ****************************** We created a custom policy for this: CLASS USER CATEGORY !!Header CATEGORY !!OptInHeader CATEGORY !!OptInContent POLICY !!PolicyOptIn KEYNAME "Software\Policies\Microsoft\Office\12.0\Common\General" EXPLAIN !!ExplainOptIn VALUENAME "ShownOptIn" VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 END POLICY END CATEGORY END CATEGORY END CATEGORY [strings] Header= "Custom Policies" OptInHeader="Microsoft Office 2007" OptInContent="Welcome screen" PolicyOptIn="Disable 'Welcome to the 2007 Microsoft Office system' screen" ExplainOptIn="Please see http://support.microsoft.com/kb/929767\n\nThis setting, when enabled, will disable the 'Welcome to the 2007 Microsoft Office system' on the first-run of Office 2007.\n\nEnabling this setting will set the following key:\n\n[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General]\n"ShownOptIn"=dword:00000001 " | ||||
| Above Entry Provided on 5/17/2007 by nzdude | Rate It | Rating 118 | ||
| I got burnt by these errors in the .adm and/or .opa files, so I thought I'd post them here: http://support.microsoft.com/kb/935734/en-us The "Prevent users from adding PSTs to Outlook profiles and/or prevent using Sharing-Exclusive PSTs" setting is configured incorrectly in the Office Customization Tool and in the Group Policy templates http://support.microsoft.com/kb/935733/en-us Cached Exchange Mode is enabled in Outlook 2007 even though you set the "Do not use Cached Exchange Mode for all new Outlook profiles" setting in the Office Customization Tool http://support.microsoft.com/kb/936979/en-us The "Make Outlook the default program for E-mail, Contacts, and Calendar" setting is disabled in Outlook 2007 Also, this article was useful to disable the DRM UI: http://technet2.microsoft.com/Office/en-us/library/b2869a87-5f86-4c7d-ac5f-808db138b2131033.mspx?mfr=true | ||||
| Above Entry Provided on 5/21/2007 by nzdude | Rate It | Rating 118 | ||
| Quite a good description on enterprise deployment can be found on technet: http://technet2.microsoft.com/Office/en-us/library/4dfe1831-8683-4856-8c0f-70c4c58f8a5e1033.mspx | ||||
| Above Entry Provided on 11/8/2007 by mdwbb | Rate It | Rating 117 | ||
| Service Pack 1 has been released. Microsoft won't be releasing CDs with SP1 integrated, but you can deploy SP1 at the same time as the initial install by using the \Updates folder. It's important to note the following about \Updates folder: The \Updates folder can only be used for deploying software patches during an initial installation of 2007 Office release. If there is a combination of customization and product update patches, only one customization patch is applied during the deployment phase, and the rest are applied after the installation is completed. The customization patch must be deployed first to ensure that modifications such as product key and quiet mode settings are applied. You cannot use the \Updates folder to deploy product updates after the initial installation of Office. http://technet2.microsoft.com/Office/en-us/library/2ce70869-aa75-4a73-9c9b-8b74001f1c3c1033.mspx | ||||
| Above Entry Provided on 1/11/2008 by nzdude | Rate It | Rating 118 | ||
| Best Known Method for Deploying Office 2007 with LANDesk Management Suite | ||||
| Above Entry Provided on 9/13/2008 by rhyous | Rate It | Rating 0 | ||
| Prescriptive guidance for sequencing 2007 Office programs in Microsoft SoftGrid http://support.microsoft.com/kb/939796 | ||||
| Above Entry Provided on 12/18/2008 by Ludo | Rate It | Rating 0 | ||
| Office 2007 SP2 download links: http://support.microsoft.com/kb/968170 | ||||
| Above Entry Provided on 5/4/2009 by nzdude | Rate It | Rating 1 | ||
| Symantec's guide to create a MS Office 2007 AIP: http://www.symantec.com/connect/articles/office-2007-silent-installation-lessons-learned | ||||
| Above Entry Provided on 6/14/2010 by Rheuvel | Rate It | Rating 0 | ||
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
