Description of the Groove Manager Server 2007 hotfix package (Ems.msp, Emsmui-en-us.msp): October 28, 2008

This article describes the Microsoft Office Groove Manager Server 2007 issues that are fixed in the Groove Manager Server 2007 hotfix package that is dated October 28, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix packages.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issues that this hotfix package fixes

This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• You configure a directory integration server over secure Lightweight Directory Access Protocol (LDAP) port 636 in Groove Manager Server 2007. However, the connection over this port fails.
• If the total characters of the user logon name and the domain name is less than 7 characters, you receive the following error message when auto-activation is enabled in Groove Manager Server 2007:
  Groove could not find account information on the local machine.

Note To resolve the auto-activation problem, Groove Manager must resynchronize with Active Directory after you install this hotfix.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The English version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

64-bit hotfix package

Download informationMicrosoft Windows Installer .msp file informationEms.msp informationEmsmui-en-us.msp information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: