Registering Relay servers with Groove Server Manager
Applies to: Groove Server 2010
Topic Last Modified: 2010-02-22
This article describes how to register a Groove Server Relay system with Groove Server Manager to enable communications between the two servers. This article also describes how to configure registered Relay server provisioning settings to manage client message load. Once a Relay server is registered with a Manager server, it can be assigned to management domain members to provide services that enable the efficient transmission of SharePoint Workspace client messages in a range of environments.
These procedures require that Groove Server Relay is installed as described in Install and configure Groove Server 2010 Relay and that Groove Server Manager is installed as described in Install and configure Groove Server 2010 Manager.
In this topic:
Groove Server Relay systems must be registered with Groove Server Manager to enable communications between the two servers. After registration with the Manager server, the Relay server can be assigned to management domain members to provide important SharePoint Workspace client communication services. Groove Server Manager communicates with Groove Server Relay via SOAP, and public key infrastructure is used to authenticate between servers. Therefore, an exchange of public keys is required to help support secure communications. Registering a Relay server with a Manager server achieves this exchange in two main steps: updating the Windows registry on the Relay server with the Groove Server Manager registry file and uploading the Relay server ID file to the Manager server.To register a Relay server with Groove Server Manager
Create a directory of SharePoint Workspace users for Groove Server Manager, as described in Create a SharePoint Workspace user directory for Groove Server Manager.
Log on to your Groove Server Manager administrative Web site, expand Relay Pools, and select a Relay pool from the navigation pane.
Note For convenience, depending on your setup, you can log on to Groove Server Manager from the Groove Server Relay computer.
Download the Groove Server Manager public key as follows:
Click Download Manager’s Public Key in the toolbar to download the Groove Server Manager certificate together with its public key and identifying information which are stored in the file, Groove_Manager_Public_Key.reg.
From the File Download dialog box, click OK, click Save, select a location for saving the file (on the local device if you are performing this procedure from Groove Server Relay), click the Save button, and then click Close.
Copy the .reg file onto the Relay server that will be registered.
From the Relay server, double-click the Groove_Manager_Public_Key.reg file to update the Windows registry on the Relay server.
Note To ensure correct downloading and processing of the Manager public key file, save the file, copy it to the Relay server, and then double-click the file to update the Relay registry. Do not try to run the Groove_Manager_Public_Key.reg file from a browser on the Relay server.
Locate and copy the Relay ID file (serverID.xml). The Relay ID file is defined by the Groove Server Relay administrator during installation and configuration of the supporting server, and usually resides in the Groove Server Relay installation directory. Copy the Relay ID file to a safe location on disk.
Click Add Relay Server from the Relay pool page on Groove Server Manager and, from the Select serverID.xml File text box, browse to the Relay ID file. This file contains two certificates: a SOAP certificate which is used by Groove Server Manager to authenticate the Relay server, and an SSTP certificate which will be used by SharePoint Workspace clients provisioned to this server.
Select Allow members to be provisioned to this relay if you want this Relay server to be available for provisioning. For information about related provisioning settings, see Changing Relay provisioning settings.
Click OK to upload the Groove Server Relay ID file to Groove Server Manager. The Groove Server Relay name appears in the list of servers for the selected Relay pool.
The following procedure describes how to configure Relay server provisioning settings to manage the capacity and message queues of registered Relay servers. This process helps minimize service interruption from overloaded systems and message backlog.
For more information about Groove Server Relay operation, databases, and message queues, see Operations for Groove Server 2010 Relay.
For information about how to register a Relay server with Groove Server Manager, see Register a Relay server with Groove Server Manager.To configure Relay server provisioning settings to manage load
From the Groove Server Manager administrative Web site, expand Relay Pools, and select a Relay pool from the navigation pane.
Click the Relay server for which you want to change provisioning settings.
Change the settings as needed, using the following table for guidance:
Provisioning Setting Description
Allow members to be provisioned to this relay
Specifies whether the Relay server should be available to support SharePoint Workspace communications for management domain members who are serviced by this Relay Pool. When this option is selected, you can configure the maximum and nominal user provisioning levels that are used in Relay load balancing, as described later in this table.
Maximum Provisioning Level – This level
Specifies the maximum number of SharePoint Workspace users that the Relay server can support. When the server reaches this maximum limit, new users that are assigned to this Relay server will be unable to contact it, although the Relay server will continue to function and service existing users.
Default: 25000 users
Nominal Provisioning Level - This level
Specifies the typical or average number of SharePoint Workspace users that the Relay server can support. A green indicator reflects this state. When the indicator changes to yellow, the Relay is reaching capacity and you should take action to add another Relay server to the pool.
Default: 20000 users
Lets you enable quotas that help regulate Relay server queues for Groove workspace messages.
Default: Cleared (disabled)
When the quotas option is selected, you can specify in the Quota (megabytes) field, a maximum number of megabytes that can be stored in queues for each managed user account on Relay servers. When the quota is reached, messages are temporarily stored on the sending device until the queue frees again (as clients contact the Relay server to collect their messages) or the messages can be delivered via direct peer-to-peer connection.
Default: 100 megabytes.
Lets you enable automatic purging of Relay message queues. When this option is enabled, you can specify message life times that determine when the messages should be purged from Relay queues.
Default: Selected (enabled)
Identity Message Lifetime (days): Specifies the number of days that identity messages can remain in a Relay queue before they are deleted. Identity messages consist of Groove instant messages and Groove workspace invitations. Because identity-targeted queues cannot be recovered after deletion (unlike device messages), the default holding time for these messages is longer than for device messages.
Device Message Lifetime (days): Specifies the number of days that device messages can remain in a Relay queue before they are deleted. Device messages consist of Groove workspace information.