Outbound from Groove Manager to Groove Relay. SOAP over port 9080 Used by Groove Data Bridge to receive XML calls from external applications. Port 9080/TCP: Inbound on Groove Data Bridge to receive requests from external applications. HTTP over port 8010 Supports Groove Relay administrative Web pages. Port 8010/TCP: Inbound on Groove Relay. MS-SQL Tabular Data Stream (TDS) encapsulated in TCP Used by Groove Manager front-end IIS server to contact back-end SQL server. Port 1433/TCP (typically): Inbound on SQL database server. Outbound from Groove Manager IIS server to SQL server. Lightweight Directory Access Protocol (LDAP) Used by Groove Manager to integrate with optional LDAP-based directory server. Port 389/TCP (typically): Inbound on LDAP directory server. Outbound from Groove Manager IIS server to LDAP directory server. Local Area Network Device Presence Protocol (LAN DPP) Used by Groove clients on a LAN subnet. Supports Groove device presence detection, enabling clients on a LAN to find each Port 1211/UDP: Inbound on Groove clients. Outbound from Groove clients to Groove client. Wide Area Network Device Presence Protocol (WAN DPP) Used by Groove clients and servers to WAN device presence detection. Groove application-layer protocol over SSTP. Rendezvous Protocol (RVP) Used by Groove clients to support user presence information. Groove application-layer protocol over SSTP. IM protocol Used by Groove clients to support instant messaging. Groove protocol over SSTP. Workspace protocol Used by Groove clients to support data synchronization. Groove protocol over SSTP. Simple Mail Transfer Protocol (SMTP) Used by a Microsoft virtual SMTP server and called by Port 25/TCP: Inbound on mail host.
Inter- net * * Perimeter Network rn8 167.10.159.18 SSTP – 443/TCP Groove Relay SSTP communications Inter- net * * Perimeter Network rn8 167.10.159.18 HTTP – 80/TCP Groove Relay HTTP encapsulated SSTP communications Inter- net * * Perimeter Network rn9 167.10.159.19 SSTP – 2492/TCP Groove Relay SSTP communications Inter- net * * Perimeter Network rn9 167.10.159.19 SSTP – 443/TCP Groove Relay SSTP communications Inter- net * * Perimeter Network rn9 167.10.159.19 HTTP – 80/TCP Groove Relay HTTP encapsulated SSTP communications Perimeter Network to Public Internet Source Zone Host IP Destination Zone Host IP Protocol port Purpose Perimeter Network mn8 167.10.159.18 Internet * * SSTP – 2492/TCP Groove Relay SSTP communications Perimeter Network mn9 167.10.159.19 Internet * * SSTP – 2492/TCP Groove Relay SSTP communications
Perimeter Network to Perimeter Network Source Zone Host IP Zone Host IP Protocol port Purpose HTTP – Groove Relay HTTP/SOAP HTTP – Groove HTTP/SOAP mail E-mail SMTP Private Intranet to Perimeter Network Source Zone Host IP Destination Zone Host IP Protocol port Purpose Intranet * * Perimeter Network mn10 167.10.159.20 HTTP – 80/TCP Groove Manager HTTP/SOAP communications Intranet * * Perimeter Network mn10 167.10.159.20 RDP-TCP – 3389/TCP Microsoft Remote Desktop communications Intranet * * Perimeter Network rn8 167.10.159.18 SSTP – 2492/TCP Groove Relay SSTP communications Intranet * * Perimeter Network rn8 167.10.159.18 SSTP – 443/TCP Groove Relay SSTP communications Intranet * * Perimeter Network rn8 167.10.159.18 HTTP – 80/TCP Groove Relay HTTP encapsulated 25/TCP
Groove Relay Capacity Installing Office Groove Server 2007 Relay at your site ensures relay availability to your Groove users and places all relay management within the control of your server administrators. If you decide to secure and manage dedicated relays, plan on supporting no more than 18,000 Groove users on a single relay server. However, actual limitations on relay capacity may vary and you should monitor Groove client and relay performance to determine when additional server hardware or software may be necessary. If your organization supports a global network of users, to maximize the performance of your relay equipment, try to locate your relay servers in close proximity to your main communities of users. The increased network "hop" count necessary to support data transmissions from Groove clients to distant relays degrades network performance. The following specifications are on an average deployment in a mid-sized company and can provide a reference point for planning a Groove Relay deployment. Hardware/Software Projected Load for Community of 36,000 Groove Users Dual 64-bit processors, 2.4 GHz, 8 GB RAM Multiple disk controllers (one dedicated controller for the relay’s data volume and zero-to-one additional controller for operating system volumes) Multiple NICs, and write-caching hardware RAID 450-GB RAID disk array for relay data Windows Server 2003 x64 12,000 users provisioned to a Groove Relay server and online 30,000 connected Groove devices Maximum bandwidth of 8 MB/concurrent user/day The above describes an organization with a community of 36,000 Groove users. In this scenario, all 36,000 users are provisioned to the relay server with the assumption that no more than 33% of the provisioned users will be online at any time. About 12,000 provisioned users are online and connected concurrently. The 30,000 connected devices include the devices of users provisioned to this relay server and online, as well as the devices of other collaborating users provisioned to other Relays. Note that the of online Groove users to devices connected to the relay server varies depending on usage patterns. Typically clients provisioned to other relays connect to a Groove Relay server in order to enqueue data for clients that are provisioned to that relay. The connected devices for non-provisioned users consume some relay resources, although substantially fewer resources than for a provisioned and online user. Therefore,