Partager via


Summary of Office 2007 Service Pack 2 changes for Groove

Hi all!

You may have noticed that it's been pretty quiet here lately. That's because we've been busy preparing for the recent releases of Microsoft Office 2007 SP2 and Microsoft Office servers 2007 SP2.

These service packs fix the following problems:

Server installation and configuration:

  • Groove Manager Server 2007 cannot use SQL Server 2008 as a database. (See KB 968770)
  • Groove 2007 Manager cannot create an AD integration server connection in Directory Integration Properties dialog when using a Single Label Domain
  • Other Groove Manager installation issues

Activation:

  • Groove client auto-activation fails if the Active Directory domain name and the NetBIOS domain do not match.
  • Groove client auto-activation fails if the user logon name and the domain name combined contain fewer than seven characters. You receive the following error message: "Groove could not find account information on the local machine."
  • Account configuration fails when the Groove client uses an IPv6 address.
  • If a new Groove domain client is provisioned with an invalid certificate, the client displays an error message, but the Relay does not log the failed registration attempt.

Client operations:

  • Groove 2007 may crash because of a resource limitation after you create or join lots of file sharing workspaces. The exact number of file sharing workspaces varies by system, but is usually between 50 and 55. This problem was discussed in this post Note that as part of this fix, there is now a hard limit of 64 File Sharing workspaces. (See KB 968769).
  • The Groove Forms tool incorrectly interprets spaces for digit grouping in currency values for some locales.

Server operations:

  • On Windows Server 2008, when Windows Firewall uses complex rules, Groove Relay may incorrectly detect that ports are blocked and fail to start.
  • In some circumstances, large instant messages that became corrupt cannot be recovered by Groove Relay, and the instant message is never delivered.
  • In some circumstances, the Groove Relay silently stops accepting SSTP connections and SSL connections. This intermittently causes remote users to be unable to connect to the Groove Relay server. This failure is not logged. When you shut down the relay to attempt to recover from this situation, the relay eventually hangs.
  • Various problems with sending debugging information to Microsoft.

Also, be aware of this change: KB 968768 -- SP2 adds .cnt and .hpj to blocked file formats in Groove 2007 and Groove 2007 Manager.

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    Good question. From the bug description, it doesn't look like they would be, but I've sent off some queries to make sure that we checked. I'll let you know.