December, 2010

Recently we received a number of emails with questions about what is co-authoring, which products support it, and what can possibly cause it not to work auto-magically.

In technical terms:

Co-authoring functionality simplifies collaboration by enabling multiple users to work productively on the same document without intruding on one another’s work or locking one-another out.

In plain English:

Co-authoring is simultaneous editing. Two or more people are working on different parts of a document.  While one person works on his section of the document, another person can work on hers, without either interrupting their work.  Imagine if you were in the same room as the committee of five working on the Declaration of Independence with pen, ink and parchment.  Alas they only had one pen to use, so their dilemma was not locking each other out of a file/document, rather they had to wait their turn to share the pen and ink.

When a document is being edited by multiple people, a windows pop up will alert you like the image below:

Microsoft Office 2010 offers co-authoring functionality for Microsoft PowerPoint 2010, Microsoft Word 2010, and Microsoft OneNote 2010 documents on SharePoint Server 2010.  New co-authoring functionality is also supported in Excel Web App and OneNote Web App.  The co-authoring functionality requires SharePoint Foundation 2010, or a Windows Live SkyDrive account. 

Within each application co-authoring applies in a specific way.  In Word only the paragraph the person is working on is locked.  In PowerPoint the particular slide and in Excel the particular cell is locked.

Co-Authoring is the default behavior for Word 2010 accessing SharePoint 2010 servers, however there are a few things that could prevent co-authoring from occurring:

·         All co-authors need to be using Office 14

·         Currently in Word, the only document type available for co-authoring is .docx

·         It is also possible your document could have non-coauthoring compatible features such as IRM/DRM, Macros, Encryption, Document marked as Final, etc. 

·         Documents stored in a SharePoint document library that have the required check-out turned on will also prevent co-authoring

Co-Authoring is a great way to eliminate the previous methods of sending out a document for multiple reviews, and then trying to compile the “final revision”.    If you have not already tried it out, grab a collegue and open a file together to see how it works. 

Enjoy!

For more details:  Co-Authoring Overview (SharePoint 2010)

The Microsoft Office 2010 Upload Center enables you to monitor files that you’re uploading to a server. In particular, the Microsoft Office Upload Center uses a feature known as Efficient File Transfer (EFT) to help reduce bandwidth usage between SharePoint 2010 and Office 2010 applications. After a file is fully uploaded to the SharePoint 2010 site, a local copy of the file is kept in the Microsoft Office Upload Center (in the Office Document Cache), where it is broken into smaller units for editing. This breakdown of the file also takes place to the file that is uploaded on the SharePoint site. When you make changes to the local copy of the file, EFT sends only the changes to the SharePoint site. As a result, files open more quickly and you can start using the file before the download is complete.

You can access the Microsoft Office Upload Center by either clicking the Microsoft Office Upload Center icon in the notification area or by opening it from the Start menu (Start\Microsoft Office\Microsoft Office 2010\Tools \Microsoft Office 2010 Upload Center).

The Microsoft Office Upload Center lists all files that have been cached.  Users can monitor the status of files that are in the process of being uploaded. Users can also manage cache settings to determine how long cached files are retained and to delete all cached files, if necessary.

Removing the Microsoft Office Upload Center icon from the desktop

When you install Office 2010, the Microsoft Office Upload Center installs automatically. If you wish, you can remove the icon from  the desktop:

1. In the Taskbar or System Tray, right-click the Office 2010 Upload Center icon.
2. Select Settings.
3. Under Display Options, clear the check box for Display icon in notification area, and then click OK. The icon will no longer display in the Taskbar or System Tray.

For more information about how to use the Microsoft Office Upload Center, see Microsoft Office 2010 Upload Center.

On Tuesday, December 14, we released an update (KB2412171) for Microsoft Outlook 2007. We have discovered several issues with the update and want to inform you about problems you might encounter and what corrective steps we recommend. As of December 16, this Outlook 2007 update has been removed from Microsoft Update.

This Outlook 2007 update was distributed via Microsoft Update. Many of you receive updates automatically and if you installed the update between Tuesday, December 14, and Thursday, December 16, it is likely that you are affected.

Please read the Microsoft Outlook Product Team's blog post for the details on the issues identified and the corrective steps to take.

We've had questions about whether the Office Customization Tool can be used to install a Key Management Service (KMS) key for a volume licensed version of Visio 2010 Standard. The short answer is yes. Here are the details:

The Enter another product key option in the Licensing and user interface section of the OCT is intended for entering a Multiple Activation Key (MAK) key. You can also use the Enter another product key option (shown below) to enter a KMS key for volume license versions of Microsoft Visio Standard 2010 or Microsoft Visio Professional 2010. Visio 2010 is preinstalled with the Microsoft Visio Premium 2010 KMS client key by default. This enables all the Microsoft Visio Premium 2010 features. However, if you have a license agreement for either Microsoft Visio Standard 2010 or Microsoft Visio Professional 2010, you must install the appropriate KMS client key. The features that are available depend on the key that you install.

For more information, see Deploy Visio 2010 in Deploy volume activation of Office 2010, and the Office Deployment team blog, Volume License editions of Visio 2010 install Premium edition by default.

The following table shows the KMS client keys for Visio 2010 editions. If you have a license agreement for Microsoft Visio Standard 2010 or Microsoft Visio Professional 2010, you can enter the appropriate KMS client key in the OCT when you perform an initial installation of Visio.

To create a Setup customization .msp file to install the Visio KMS key with the OCT: 

1. Run the OCT from the network installation point (the shared network location that contains the Visio Standard 2010 or Visio Professional 2010 source files).
2. From the root of the network installation point, run the setup.exe /admin command line to start the OCT. For example:
   \\server\share\Office2010\Visio2010Pro\x86\setup.exe /admin
3. Select the Visio product (Visio Professional 2010 32-bit in this example) that you want to configure, and then click OK.
4. In the left pane, click Licensing and user interface.
5. In the right pane, select Enter another product key (shown below), and enter the appropriate Visio KMS license key without spaces in the Product key text box. For example, for Visio Professional 2010, enter: 7MCW8VRQVKG677TPDJCMQ8TCP
   
    
   
6. Click Save on the File menu, and then save the Setup customization .msp file in the Updates folder at the root of the network installation point for Visio (x86 folder in this example).

When you run Setup.exe from the network installation point, Setup looks in the Updates folder for Setup customization .msp file for the product that you are installing.

To learn about the Office Activation Technologies, see Volume activation overview for Office 2010.

For information about how to use the OCT to customize Setup, see Customize Setup before installing Office 2010. This video demonstrates how to use the OCT: Office 2010 client: Office Customization Tool walkthrough (http://go.microsoft.com/fwlink/?LinkId=203127).

Licensed customers can now download the Office Multilanguage Pack (MLP) and Proofing Tools from the Microsoft Volume Licensing Service Center.   There are 2 Office 2010 MLP downloads: CD and DVD.  If you want the Multilanguage Pack and/or Proofing Tools, choose the DVD download.  The CD download only includes the individual single language packs for each of the languages and does not include the Multilanguage Pack or Proofing Tools. 

Need some guidance on what packs to pick and how to deploy them?  See the following topics:

• Plan for multilanguage deployment of Office 2010
• Companion proofing languages for Office 2010
• Mixed language versions of Office 2010
• Customize language setup and settings for Office 2010

Enjoy!

We've seen several recent reports of customers hitting the following errors when using OMPM to scan Access databases:

• Database too large, not copying. Access properties skipped.
• Not logging Access properties for database.

One of our Microsoft consultants, Sebastien Roche, discovered a workaround to fix this issue:

Modify the OMPM configuration file (offscan.ini) as follows:

Set MaxCopyFileSize=300            ;or a size larger than your largest database

If you set this parameter large enough, you may still receive a "timeout error." In that case, you have to modify the values of the parameters RetryCount & RetryInterval as follows:

[Network]

RetryCount=15                ;set this to the number of retries per file you would like before moving on

RetryInterval=1500        ;set this to the number of milliseconds to wait between retries.

The downside to this workaround is that OMPM scan performance is slow.

We've had a couple people report recently that they are trying to use OCCI but the Inspect VBA Project option never shows up in the Developer ribbon. When installed correctly, OCCI will add the following buttons to the Developer ribbon, like this:

If you have installed OCCI but it's not showing up in the Developer ribbon, OCCI might be disabled or installed incorrectly. Here are a few things to try:

• Check to see if the Microsoft Office 2010 Code Compatibility Inspector folder exists under c:\Program Files or c:\Program Files (x86). It it does not, OCCI did not get installed properly.
• Verify that you installed OCCI as an administrator and that you have the Microsoft .NET Framework 3.5 installed.

You can also verify that OCCI was installed correctly by checking the following locations.

On the splash screen when the application is launched:

In the Options dialog box for the application (OCCI is listed in File => Options =>Add-ins): 

If you installed OCCI but it's not showing up in the Add-ins list, it's possible that the add-in was disabled. For example, the add-in may have been disabled if you clicked Yes after seeing the following message: "Word experienced a serious problem with the 'Word 2010 Code Compatibility Inspector' add-in. If you have seen this message multiple times, you should disable this add-in and check to see if an update is available. Do you want to disable this add-in?"

Disabled add-ins are hidden by default but you can view them by selecting Disabled Items in the Manage drop-down menu shown below. For instructions on re-enabling add-ins, see How to: Re-enable an Add-in That Has Been Disabled on MSDN.

Still having trouble? Let us know in the Comments section!

The OCT is the main client customization tool for Office 2010 (and Office 2007). This tool is part of the Setup program and is included only in volume license versions of Office, such as Office 2010 Professional Plus.

You use the OCT to configure settings in these areas:

• Setup
  • Install location and organization name
  • Additional network sources
  • Licensing and user interface
  • Remove previous installations
  • Add installations and run programs
  • Office security settings (sets initial defaults only; users can change the settings)
  • Modify Setup properties
• Features:
  • Modify user settings (sets initial default settings that users can modify later)
  • Set feature installation states (specifies how Office applications are installed or not installed on users' computers)
• Additional content:
  • Add files
  • Remove files
  • Add registry entries
  • Remove registry entries
  • Configure shortcuts
• Outlook:
  • Outlook profile
  • Add accounts
  • Export settings
  • Specify Send\Receive groups

Versions

In Office 2010, there are two architecture-specific versions of the OCT, one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. The OCT files are located in the Admin folder under the x86 (32-bit) and x64 (64-bit) folders, respectively. See Architecture-specific versions of the Office Customization Tool for more information.

How to run the OCT

From the root of the network installation point (location that contains the Office 2010 source files), run the following command line to start the OCT: \\server\share\setup.exe /admin

where \\server\share is the network share containing the Office 2010 source files

In the Select Product dialog box, select a single product (such as Microsoft Office 2010 Professional Plus) that you want to customize, and then click OK.

Note:

To run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder, for example: \\server\share\Office14\x86\setup.exe /admin

To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder, for example: \\server\share\Office14\x64\setup.exe /admin

The following screen shot shows the OCT user interface:

Updates folder

When you use the OCT to configure an initial installation of Office 2010 (or Office 2007), you save your customizations in a Setup customization .msp file and you place the file in the Updates folder on the network installation point. The preceding screen shot shows the Updates folder. When you install Office, Setup looks for a Setup customization file in the Updates folder and applies the customizations you specified. The Updates folder can only be used to deploy software updates during an initial installation of Office 2010.

As an alternative to the Updates folder, you can place the Setup customization .msp files in a network share, and then you can use the Setup command-line option /adminfile to specify the fully-qualified path of the location of the .msp file. For example, type:

setup.exe /adminfile \\server\share\mychanges\custom.msp

Note:

If you use a folder other than the Updates folder for your customization files, you can specify the folder's location in the Config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. The Config.xml file is located in the core product folder (core_product_folder_name.WW folder, for example, ProPlus.WW for Microsoft Office Professional Plus 2010) for the Office 2010 product that you install. The preceding screen shot shows the ProPlus.WW folder.

What if I need to install more than one Office 2010 product? You can place only one Setup customization .msp file per product in the Updates folder.

What about software updates? If there are Office 2010 product updates (service packs or hotfixes) that you want to install with the initial installation, you can place the update (.msp) files in the Updates folder. In this case, Setup will apply the Setup customization .msp file with the initial installation, and the software updates are installed after the installation completes. Note that you can use the Updates folder for product updates only during initial installations. You cannot use the Updates folder to deploy product updates after the initial installation of Office.

Note:

If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file for each Office 2010 product that you are installing in the Updates folder for an initial installation. You must deploy the rest of the customization .msp files for a product after the Office installation is completed. Only one Setup customization file per product in the Updates folder is supported. If you are deploying multiple Office 2010 products, such as Microsoft Office Professional Plus 2010 and Microsoft Visio Professional 2010, you can include one customization .msp file for Office Professional Plus 2010 and one customization .msp file for Visio Professional 2010 in the Updates folder. The customization .msp files that you place in the Updates folder will be deployed first. Therefore, they must include any Setup customizations that cannot be changed after the installation, for example, the installation location.

If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete.

How do I deploy product updates using the Updates folder? First you need to extract the .msp patches from the Microsoft Self-Extractor file (product update .exe). You will find instructions for this in the Updates folder and Deploying software updates with an initial Office 2010 installation sections of Distribute product updates for Office 2010.

Running the OCT after initial deployment

You can also use a Setup customization .msp file to change an existing Office 2010 installation. Because a Setup customization file is an expanded form of a Windows Installer .msp file, you apply the customization file to the user's computer exactly as you would a software update (this applies only to maintenance Setup customization .msp files). The user's existing Office installation is updated with the customizations that you make.

For example, if you change the installation states of some features to Not Available and apply the resulting customization file to an existing installation of Office, those features are removed from the user's computer.

Note that some options in the OCT are applicable only to a new installation of Office. These options are identified in the OCT and in the OCT Help. For example, you can use the Default installation path option (in the Install location and organization name section) to specify the folder where Office is to be installed on the user's computer. However, if a customization file is applied to an existing installation, the Default installation path option is ignored (you must uninstall and reinstall Office to change the installation location).

To apply a maintenance Setup customization .msp file after an initial installation of Office, you can use one of the following methods (these methods apply only to maintenance Setup customization .msp files, where Office 2010 is already deployed to the computer and you are applying additional Setup customization .msp files):

• Users can double-click the .msp file.

• Users can run Msiexec.exe at the command prompt and use one of the following command-line options to apply the .msp files:
  msiexec.exe /p \\server\share\custom.msp
  msiexec /update \\server\share\Patch1.msp
  
  where:
  \\server\share indicates the path of the shared folder that contains the .msp files
  /p installs the .msp
  /update installs the .msp
  
  For information about Windows Installer, see the following resources on the MSDN Web site:

  • Standard Installer Command-Line Options (http://go.microsoft.com/fwlink/?LinkId=111106)
  • Command-Line Options (http://go.microsoft.com/fwlink/?LinkId=111127)

  • What's New in Windows Installer (http://go.microsoft.com/fwlink/?LinkId=111108)
    

• Users can also use Microsoft System Center Configuration Manager 2007 to deploy the .msp files.
  

Importing .msp files

New to Office 2010 OCT is the Import feature. The OCT supports importing Setup customization .msp files as follows:

• 32-bit Setup customization .msp files can be imported into 64-bit OCT and can then be used to customize 64-bit Office products.
• 64-bit Setup customization .msp files can be imported to 32-bit OCT and can then be used to customize 32-bit Office products.

Note:

You can import Setup customization .msp files for equivalent cross-architecture products only. You can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Office Professional Plus 2010 .msp file; doing so is prevented and an error message is displayed.

You cannot import 2007 Office system Setup customization .msp files into the Office 2010 OCT.

For more information, see the following resources:

• Importing Office Customization Tool .msp customization files

• Import an Office 2010 Setup customization file

• Deploy multiple Setup customization files

• Office Customization Tool in Office 2010

• Customize setup for Office 2010

• Setup command-line options for Office 2010

• Video: Office 2010 client: Office Customization Tool import feature (http://go.microsoft.com/fwlink/?LinkId=203128)

• Video: Office 2010 client: Office Customization Tool walkthrough (http://go.microsoft.com/fwlink/?LinkId=203127)
  

Config.xml file

When do I use the Config.xml file? You can also use the Config.xml file to make changes to your Office installation. You can customize most of the same options that you can with the Office Customization Tool, including a few additional ones that are not available in the OCT.

The Config.xml file is not installed or cached on users' computers and it is used only when you run Setup. Administrators can edit the Config.xml file to customize the installation. By default, the Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder; for example, ProPlus.WW) directs Setup to install that product. For example, the Config.xml file in the ProPlus.WW folder installs Microsoft Office Professional Plus 2010. The following screen shot shows the ProPlus.WW folder and Config.xml.

Using the Config.xml file is the recommended method for performing the following installation tasks:

• Instructing Setup to copy the local installation source to the user's computer without installing Office

• Specifying the path of the network installation point

• Selecting which product or language to install

• Changing where Setup looks for Setup customization files and updates

• Making last-minute or one-off customizations that do not warrant running the OCT to create a new customization file

For more information about Config.xml, see:

• Config.xml file in Office 2010

• Precache the local installation source for Office 2010

• Customize language setup and settings for Office 2010

Enforcing user settings

If you need to enforce user or computer settings instead of setting only initial defaults with the OCT, you must use Group Policy.

Group Policy is used to configure the Office 2010 policy settings that are contained in Administrative Templates. The operating system enforces those policy settings. In an Active Directory environment, administrators can apply policy settings to groups of users and computers in a site, domain, or OU to which a Group Policy object is linked.

For more information, see the following resources:

• Enforce settings by using Group Policy in Office 2010
  
• Group Policy overview for Office 2010
  
• Planning for Group Policy in Office 2010