7 Appendix B: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Office Groove Server 2007

  • Microsoft Groove Server 2010

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.2.3.2:  The Office Groove Server 2007 and Groove Server 2010 products provide a Manager component and a Relay component. The Manager component implements the management server functions of the protocol specified in this document, and is the client for the protocol. The Relay component implements the relay server functions of the protocol specified in this document, and is the server for the protocol

<2> Section 2.2.3.6.1:  Office Groove Server 2007 and Groove Server 2010 do not test for positive values for the relay defaults for device lifetime, device target quota size, identity lifetime, and identity target quota size. These servers ignore invalid values and do not return a SOAP fault.

<3> Section 2.2.3.6.1:  On Office Groove Server 2007 and Groove Server 2010 enabling the quota can stop messages from being sent to offline users for any size message.

<4> Section 2.2.3.8.1:  Office Groove Server 2007 and Groove Server 2010 do not test for invalid values and treat all nonzero values as 1.

<5> Section 3.2.3:  The Office Groove Server 2007 Manager and Groove Server 2010 Manager generate a registry file containing its certificate (1) and identity information to support interoperability. The registry file uses the following template:

 REGEDIT4
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\Groove\Groove Relay\Parameters\ManagementServers\[[- hostname -]]/gms.dll]
 "GUID"="[[- management server GUID -]]"
 "Organization"="[[- management server organization name -]]"
 "ServerURL"="http://[[- hostname -]]/gms.dll"
 "Certificate"=hex:[[- certificate in hex -]]

[[- hostname -]]: The host name for the management server.

[[-management server GUID -]]: The unique ID that identifies this management server.

[[- management server organization name -]]: the organization name for the management server.

[[- certificate in hex -]]: The management server certificate (1) in HEX format

<6> Section 3.2.5.6.1:  Office Groove Server 2007 and Groove Server 2010 relay servers purge messages for the specified user or users under most conditions. Under some conditions, the server processes the message without fault but does not purge messages. For example, if the server has received a new message targeted to the user within a minute preceding receiving the userPurge message, the server does not purge the messages for the user.

<7> Section 5.1.6:  In the Office Groove Server 2007 and Groove Server 2010 implementations, the requirement for a secure exchange mechanism for the certificate (1) is done through the Management Server web administration user interface. The server administrator is responsible for downloading the client's certificate (1)and uploading the relay's server identification XML file (which contains the relay server's SOAP certificate (1)). The administrator uses the Management Server HTTPS web interface to ensure that the correct management interface is being used.