Test and validate the Groove Server installation

Groove Server 2010

Applies to: Groove Server 2010

Topic Last Modified: 2010-10-26

This article describes how to test the Groove Server installation before promoting it for production. Testing involves evaluating the overall functionality and production readiness of the onsite server system to ensure that it is suitable for hosting the expected user community.

In this article:

Install and setup the Groove Server system as described in, Deployment for Groove Server 2010

The following procedure presents recommended system pre-test measures.

To pretest the Groove Server system
  • Address the requirements in Before you begin.

  • If you have prepared an Active Directory forest for integrations with Groove Server Manager, verify Active Directory contact with Groove Server Manager by checking the Windows Event Viewer on the Manager server.

  • Test Groove Server Manager functionality.

  • Verify server activity by opening to your Groove Server Manager administrative Web site, selecting Groove Server Manager from the navigation pane, clicking the Reports tab, and checking the Server Log.

  • Test Groove Server Relay functionality.

  • Test Groove Server Manager to Groove Server Relay SOAP communications for each relay server.

  • Test SharePoint Workspace client to Groove Server Manager communications from public Internet and private intranet zones on port 80/TCP and 443/TCP.

  • Test SharePoint Workspace client to Groove Server Relay communications from public Internet and private intranet zones on all ports: 80/TCP, 443/TCP, and 2492/TCP.

  • Test Relay-to-Relay communications on port 2492/TCP between each onsite relay and from each onsite relay to any relay on the public Internet.

  • Test for correct DNS name resolution for all servers from public Internet and private intranet zones.

  • Test administrative access to Groove Server Manager (80/TCP or 443/TCP) and to Groove Server Relay administrative Web site (port 8010/TCP).

  • Test automatic account configuration, if it is implemented.

  • Test system penetration (for all servers and perimeter networks).

  • Test intrusion detection system (for all perimeter network).