/build/static/layout/Breadcrumb_cap_w.png

Microsoft Office 2007

Version: 12

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 33.2k  |  Created: 10/05/2006

Average Rating: 0
Office 2007 has 1 inventory records, 38 Questions, 3 Blogs and 19 links. Please help add to this by sharing more!

Deployment Tips (43)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 5 ratings
Most Commonly Reported Deployment Method
Repackaged (to a legacy setup.exe)
207
Command Line
After you create the .msp file you can deploy the setup out like this:

"setup.exe" /adminfile "office.msp"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • JTMan33
  • 04/12/2007  
  • Show Comments   ( 0 )

143
Note

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, .
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

141
Command Line
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 08/16/2008  
  • Show Comments   ( 0 )

139
Command Line
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 08/16/2008  
  • Show Comments   ( 0 )

135
Note

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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • WillDunn
  • 03/14/2007  
  • Show Comments   ( 0 )

131
Note
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • germo001
  • 12/06/2006  
  • Show Comments   ( 0 )

130
Note
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"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

127
Note
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,"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Scotte
  • 08/24/2007  
  • Show Comments   ( 0 )

126
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • jameson
  • 04/19/2007  
  • Show Comments   ( 0 )

125
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • neil.cole
  • 02/18/2008  
  • Show Comments   ( 0 )

123
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

123
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 01/10/2008  
  • Show Comments   ( 0 )

122
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • adamind
  • 09/28/2007  
  • Show Comments   ( 0 )

122
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

122
Note
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:"<absolute_path_of_your_Office_installation_source>\Updates"


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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • netjustin
  • 03/21/2008  
  • Show Comments   ( 0 )

121
Note
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).
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • bkelly
  • 11/27/2006  
  • Show Comments   ( 0 )

121
Note
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Netviz
  • 10/29/2007  
  • Show Comments   ( 0 )

121
Terminal Services
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 07/07/2008  
  • Show Comments   ( 0 )

120
Note
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".
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • aquateen
  • 09/04/2007  
  • Show Comments   ( 0 )

120
Terminal Services
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)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 01/18/2008  
  • Show Comments   ( 0 )

119
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

119
Note
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 05/24/2007  
  • Show Comments   ( 0 )

118
Note
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • scarneiro
  • 06/12/2007  
  • Show Comments   ( 0 )

118
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

117
Note

In addition to the MSDN distributing a retail copy (see above OCT error), Action Pack subscribers are also receiving a retail copy.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Drac346
  • 10/03/2007  
  • Show Comments   ( 0 )

117
Terminal Services
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 01/18/2008  
  • Show Comments   ( 0 )

116
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 02/15/2008  
  • Show Comments   ( 0 )

6
Command Line
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • spoirier
  • 05/09/2007  
  • Show Comments   ( 0 )

5
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

4
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

3
Note
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."
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 04/01/2009  
  • Show Comments   ( 0 )

3
Note
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."
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • nzdude
  • 04/01/2009  
  • Show Comments   ( 0 )

2
Note
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
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • clearbyte
  • 10/17/2008  
  • Show Comments   ( 0 )

2
Note
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.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • tstaub
  • 05/13/2010  
  • Show Comments   ( 0 )

1
Note
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)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • clearbyte
  • 01/05/2010  
  • Show Comments   ( 0 )

0
Note

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!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • mbruner
  • 01/07/2009  
  • Show Comments   ( 0 )

0
Command Line
For 2007MicrosoftOfficeSuiteServicePack2(SP2) I used the following...

Full Command Line: setup.exe /adminfile OFFICE2007.MSP
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Istone
  • 08/31/2011  
  • Show Comments   ( 0 )

0
Note
Most of the registry entry changes listed here can be modified in the GUI of the Office Customization Tool.

First, make sure you have the latest version of the OCT by going here:
http://www.microsoft.com/download/en/details.aspx?amp;DisplayLang=en&id=22666
Download the file and follow the instructions here:
http://support.microsoft.com/kb/929767
(in short, unpack it to an empty folder and copy the \Admin folder over the existing \Admin folder from your Office source media)
This will add the "Disable Opt-in Wizard on first run" option and will fix an RSS feed option.


Type setup /admin to start the OCT.


Navigate to: Features > Modify user settings

To prevent the Privacy / Customer Experience Improvement Program pop-up:

Microsoft Office 2007 System > Privacy > Trust Center

Disable Opt-in Wizard on first run = Enabled

And to optionally disable the services the pop-up asks about:

Enable Customer Experience Improvement Program = Disabled
Automatically receive small updates to improve reliability = Disabled


To prevent the Windows Desktop Search installation prompt:

Microsoft Office Outlook 2007 > Tools | Options... > Preferences > Search Options:

Prevent installation prompts when Windows Desktop Search component is not present = Enabled
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • DeQuosaek
  • 01/19/2012  
  • Show Comments   ( 0 )

0
Note
For my Office Pro Plus 2007 Deployment as a silent install, I create an MSP file. Steps I use are as follows:
1) First I extract the contents of my Office 2007.iso into a folder.
2) Start a command prompt in that folder (shift + right click select "Open Command Window Here")
3) Type "Setup.Exe /admin" without the quotes and that will open up the Office Customization Tool (OCT)
4) Create a new Setup customization file for the following products "Microsoft Office Professional Plus 2007"
5) Go through the OCT and once done, save your MSP.
6) To save from having to use a special command line, place your MSP file that you created with OCT in the updates folder in the Office 2007 folder of all contents.
7) If you use KACE then go into the folder with the installation files and highlight them all and place them into a zip folder.
8) Log into your K2000 machine, go to post-installation tasks,
8.1) Add a New Application
8.2) Name your application ex: APP: Office 2007 Pro Plus
8.3) Upload your zip file
8.4) under your command line place: setup.exe
8.5) add any notes you want
8.6) Save
9) Now you can use that as necessary to customize your setup for Office 2007

If you don't use KACE, you can still use the customized file by using the setup folder contents and using the setup.exe in the same manner as you would above.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

0
Note


Be sure you download the latest OTC
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • jaybee96
  • 12/20/2012  
  • Show Comments   ( 0 )

-1
Command Line

"setup.exe" /adminfile "Standard_Desktop.msp"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Istone
  • 06/30/2011  
  • Show Comments   ( 0 )

-2
Command Line
For version 12.0.6425.10000 I used the following msiexec.exe command

msiexec.exe /x {90120000-0011-0000-0000-0000000FF1CE} /quiet /qn /norestart
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • gharouff
  • 07/28/2010  
  • Show Comments   ( 0 )

-15
Command Line
For Microsoft Office Enterprise 2007 12.0.6425.1000 I used the following...

Full Command Line: setup.exe /adminfile office2007.msp
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • tstaub
  • 05/13/2010  
  • Show Comments   ( 0 )

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Office 2007

Version

12

Questions & Answers (38)

Questions & Answers related to Microsoft Office 2007

3
ANSWERS
Trying to Remove Office products smoothly with "Remove-PreviousOfficeInstalls" Powershell script
By: bowenz 5 years ago 2.6k views
Edenauto commented 5 years ago
4
ANSWERS
Script to Modify Office 2007 Pro install - uninstall everything but Access
By: Janet 7 years ago 1.4k views
Janet answered 7 years ago
1
ANSWERS
Uninstall Office 2007 and Install Office 2013
By: Janet 7 years ago 2.8k views
Janet commented 7 years ago
2
ANSWERS
Force office 365 pro plus (2013 version) click to run to perform an upgrade in script
By: KHaught 8 years ago 1.7k views
KHaught commented 8 years ago
2
ANSWERS
Unable to opened WORD 2007 documents without first saving to hard drive when accessing from a link off of web page.
By: elemence 9 years ago 1.7k views
caropoulin answered 9 years ago
2
ANSWERS
Uninstall for office 2010 and 2007 not Visio or project
By: wayn3597 9 years ago 3.5k views
Womain answered 7 years ago
0
ANSWERS
Changes in VBA from 2003 to 2013
By: ur00361883 9 years ago 2.7k views
anonymous_9363 commented 9 years ago
2
ANSWERS
Can we create a custom installer msi package of MS Office 2007 or later?
By: nima.msi 10 years ago 5k views
EdT answered 10 years ago
1
ANSWERS
application does not install through sccm 2007
By: swap20june 10 years ago 1.9k views
EdT answered 10 years ago
1
ANSWERS
Change what excel version opens when client clicks on a hyperlink in excel (2003/2007 dual versions installed)
By: lewcianci 10 years ago 3.1k views
lewcianci commented 10 years ago
0
ANSWERS
Office 2007 / Clipart - Word2007 - Clip art Collection adding?
By: anonymous_94669 11 years ago 4.2k views
1
ANSWERED
Just looking to push a single file out over the network - Word 2007 Normal.dotm
By: anonymous_94669 11 years ago 4.4k views
0
ANSWERS
SCCM Office 2010 Deployment did not remove Office 2007 from add/remove programs
By: sonik777 11 years ago 4.5k views
1
ANSWERED
Trouble with K1000 Software inventory and Office 2007-2010
By: trainee 11 years ago 2.4k views
1
ANSWERS
Deploying MS Office 2007 to Windows XP
By: jaja789 11 years ago 2.7k views
2
ANSWERED
How to Update Office File Format from 2007 to 2010
By: samzeeco 11 years ago 2.9k views
1
ANSWERS
Unable to uninstall the Microsoft Office Outlook 2007 Junk email filter 32-bit edition.
By: ashu270291 11 years ago 3.5k views
1
ANSWERS
How can I Input the Volume Licence details in to the Assets (Licences) on Kace???
By: auxchipmunk 11 years ago 2.6k views
3
ANSWERS
Microsoft Office 2007 Silent Install using Microsoft Deployment Toolkit
By: nvr8981 11 years ago 12.5k views
1
ANSWERED
How to uninstall MS Office 2007 via K1000
By: manpang 12 years ago 6k views
More Questions

Blogs (3)

Blog posts related to Microsoft Office 2007

blog
Office 2007 APP-V let the games begin
By: sparky86 11 years ago 6.7k views
blog
KACE: Issues distributing office 2007 Pro and Standard
By: ohiosoundguy 12 years ago 5.9k views
blog
Add a New menu on Mouse right for workbook Navigation
By: ashish koul 12 years ago 6.2k views

Reviews (0)

Reviews related to Microsoft Office 2007

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ