This following is a model process for deploying Groove to a large number of users (approximately 10,000) and employing Groove Networks-hosted management and relay services. These processes assume that the necessary SharePoint servers are already opera-tional in the enterprise.
The flow chart below presents an overview of deployment activities in an environment of onsite Groove servers. Each activity in the chart is discussed in more detail in the sections that follow:
Groove Enterprise Planning and Deployment General Server Deployment Guidelines 69
• Optimize Network Infrastructure
• Assemble Production Support for Groove Operations
• Define Groove Management Domains
• Prepare Groove Virtual Office Software for Distribution
Groove Enterprise Planning and Deployment General Server Deployment Guidelines 70
• Conduct User Deployment Pilot
• Evaluate User Fulfillment Optimize Network Infrastructure
This activity involves making the recommended network changes necessary to optimize Groove's communications and minimize impact on other network operations.
Tasks
• Modify or enhance the enterprise DMZ firewall / proxy configuration(s) to optimize support for Groove protocols.
• Enhance Intranet / Internet WAN links as needed (including additional bandwidth and routing modifications).
Result
Performing the above tasks results in a network infrastructure that has been optimized and is ready to support the expected Groove user community.
Assemble Production Support for Groove Operations
This activity involves establishing the enterprise's internal ability to manage the Groove software, user IDs and provide first line (escalated) support to end users.
Tasks
• Establish onsite operations staff for administering the Groove management domain(s).
• Plan for and add Groove user support to existing first line support with provisions for escalation to Groove support.
• Train in-house personnel responsible for operating and supporting Groove, via the following Groove Education course options:
• Course on administering hosted Groove management servers
• Course on supporting Groove
• Define Groove escalation process and identify named support contact(s)
• Decide on and purchase the appropriate Groove support contract.
Result
Performing the above tasks results in a trained staff ready to operate, manage and support the Groove users in the enterprise.
Define Groove Management Domains
This activity involves creating one or more Groove domains for the enterprise on the Man-agement Server(s). The domain(s) must be configured specifically to manage Groove in compliance with the enterprise's business requirements and policies.
Tasks
Groove Enterprise Planning and Deployment General Server Deployment Guidelines 71
• Execute an appropriate hosted services contract with Groove Networks. The hosted services Groove domain is provisioned by Groove Networks, who creates the required management domains, defines administrator roles, loads license
package(s) for seats purchased, and registers hosted relay servers with management domains.
• Create logon accounts for domain administrators and assign access control role.
• Configure domain settings.
• Create domain groups.
• Set managed user identity and device policies for domain groups.
• Assign License Package(s) to domain groups.
• Configure Groove relay services for domain groups.
Result
Performing the above tasks results in the creation of one or more Groove domains. Each domain is configured and ready to manage. Licenses are loaded. Groove devices and iden-tities are configured and ready to manage.
Prepare Groove Virtual Office Software for Distribution
This activity involves preparing the Groove virtual office software for large-scale distribu-tion and installadistribu-tion on all users' PCs.
Tasks
• Discuss options and features (such as silent installation) available in the Groove Enterprise Installer with your Groove Networks representative.
For information about the Groove Enterprise Installer, see the Groove Software Deployment Administrator’s Guide.
• Choose a Groove Virtual Office software distribution option, such as one of the following:
• Acquire Groove Enterprise Installer from Groove Networks if desired.
• Download from the Groove Networks Web site
• Install from CD
• Internally host from onsite server (self download/install, pulled-to-desktop)
• Package for silent install via software distribution system (pushed-to-desktop)
• Consider managed PC issues, including the following:
• User/group Windows file system permissions
Note that the Groove Enterprise Installer Service provides component installation on behalf of users whose file system permissions prevent them from otherwise installing or upgrading for themselves
• Windows group membership
• Installation directory paths (for system, program, and user data) and related permission modifications
• Engineer and test each package /delivery method needed to reach all users' PCs.
Groove Enterprise Planning and Deployment General Server Deployment Guidelines 72
Result
Performing the above tasks results in a customized package for delivering, installing, and supporting Groove software on end user PCs.
Conduct User Deployment Pilot
This activity involves testing the entire user fulfillment processes and supporting systems with a small number of users (less than 100). The goal is to identify any problems that may exist and correct them prior to the large-scale deployment and placing Groove in a production setting.
Tasks
• Test user fulfillment for less than 100 users.
Pilot users should be selected on the basis of their ability to exercise the various unique deployment and operations issues expected, taking into account PC platform, software distribution method, VPN, and network location.
• Identify and correct any problem areas discovered in fulfillment or operations.
Result
Performing the above tasks results in a validated and production ready user fulfillment process suitable for supporting the entire deployment and long-term Groove operations.
Evaluate User Fulfillment
This activity involves the production rollout of Groove software to the enterprise. It enables each user to use Groove software with their assigned managed identity. Users are typically fulfilled in groups based on their community affiliations.
Tasks
• Execute the communications plan that sets user expectations for the Groove