Groove Software Deployment

Groove Software Deployment

Version 3.1

Administrator’s Guide

Groove Software Deployment Copyright i

Copyright

Copyright © 2001-2005, Groove Networks, Inc. All rights reserved.

You may not reproduce or distribute any part of this document in any form or by any means, without the written permission of Groove Networks, Inc., nor may you use it to create derivative works.

Groove Networks, Groove, the interlocking circles design, Groove Virtual Office, and groove.net are registered trademarks of Groove Networks, Inc. Other product or company names may be the trademarks of their respective owners.

Use of Groove Networks, Inc. software is subject to the terms of a license agreement and applicable export and import restrictions. Restricted rights for U.S. government users.

This product includes software used under license from third parties, including those par-ties identified by the following notices. Copyright © 1995 - 2001 International Business Machines Corporation and others. All rights reserved. VcardParser.cpp © Copyright Apple Computer, Inc., AT&T Corp., International Business Machines Corporation and Siemens Rolm Communications Inc. Outside In® ActiveX Control © 2002 IntraNet Solu-tions Chicago, Inc. All rights reserved. This software is based in part on the work of the Independent JPEG Group. ACME Labs Freeware Copyright © 2000 by Jef Poskanzer <[email protected]>. All rights reserved.

Table of Contents

Copyright i

Table of Contents ii

Overview 1Groove Clients and Servers 1A Process for Deployment 2Setting up Groove Servers and EI Software 4

Verifying Management Domains and Policies 5

Identifying Target Groove Users and Devices 5

Customizing the Installation 5

Assembling Device Registry Keys and Other Registry Updates 5

Setting Up Centralized Distribution Software (optional) 6

Packaging Distribution for an Internal Web Site (optional) 6

Running the Enterprise Installer 6

Distributing Managed Identities 7

Activating Groove in a Managed Environment 7

Assumptions 7The Groove Software Deployment Guide 8

Preparing for Deployment 9Requirements 9Hardware 9

Software 10

Expertise 12

Planning 12User and Device Management 12

Component Update Management 13

Groove Data and User Account Backup 14

Client Account Backup 14Managed Account Backup 14Groove Space Backup 15Password Reset and Data Recovery 15

Client Auditing 15

Installing Groove with Enterprise Installer 17Enterprise Installer Basics 18QuickStart 19

Groove Software Deployment Table of Contents ii

Before You Begin 20Getting Help 20

Prerequisites 20

Running the Groove Enterprise Installer 21Customizing Groove Installation Using MSI Transforms 22Customizing Groove Installation from the Command Line 25Command Line Format 25

Command Line with Setup.exe 26Command Line with Setup.exe and Transform 26Command Line with MSIExec.exe 27Command Line with MSIExec.exe and Transform 27Command Line Options 28

Specifying Unattended Installation 28Changing Groove Installation Directory Paths 28 Changing Groove Installation Options 29 Setting Device Management and Registry Updates via MSI Transforms 29 Checking Windows Installer Log Files 31Activating Groove 31Updating Groove 32Controlling Groove Updates 32

Controlling the Groove Installer Service 33

Uninstalling the Groove Enterprise Installer 33

Centralized Deployment with the Enterprise Installer 34Before You Begin 34Active Directory GPO Installations 35SMS Installations 36SMS Packages 36

Creating SMS Advertisements 37

Activating Groove After a Centralized Installation 37

Website Deployment 38

Installing Groove Components 39Requirements 39Hardware 39

Software 40

Installing Groove Components on a Server 40Enabling Manual Client Upgrades from Groove Components 41MIME Types in IIS version 6.0 41

Troubleshooting 43Installation Problems 43Groove User Activation Problems 44 Run Time Problems 46

Common Administrative Tasks 48Logging into Client Devices as Administrator 48Installing Groove in Unattended Mode 48

Groove Software Deployment Table of Contents iii

Changing the Groove Installation Directory 48Centrally Deploying Device Registry Files 49Making a Device Managed Without Losing Previous Data 49Converting an Unmanaged Identity to a Managed Identity 49Centrally Executing .GRV Files 49Final Restarting of Client Devices 50Updating and Overinstalling Groove 50

Glossary 51

Appendix A. Registry Changes for Mail/Messaging Integration 54For Lotus Notes R5 54For Microsoft Outlook 2000 (or later, including XP) 54

For MSN Messenger 55

Appendix B. Managed Install Permissions 56

Appendix C. Controlling Local Virus Scanning and Filtering 59

End User License Agreement 62

Index 78

Groove Software Deployment Table of Contents iv

Overview

How an enterprise chooses to install and configure the Groove® Virtual Office (formerly Groove Workspace) software at a site, depends on the organization’s size, resources, secu-rity policies, and IT practices. IT administrators may choose to standardize Groove deployment with a single organization-wide installation package, or choose to create cus-tom installations that target specific departments. The installation may be conducted from a centralized deployment server running a software management service, or it may be sta-tioned on an internal server available to device users for download. For small deploy-ments, administrators may choose to run a standard installation on each desk top.

Whatever the approach, the Groove Enterprise Installer can help facilitate the process. The Enterprise Installer is a Microsoft Installer-based application that allows administrators to customize Groove software installations for their users via .msi files and transforms (.mst files). Using a Groove Virtual Office.msi file and a centralized software distribution sys-tem such as Microsoft Active Directory®, administrators can centrally deploy Groove software throughout an enterprise.

This guide provides baseline procedures for incorporating the Enterprise Installer into a total managed deployment process that meets the requirements of many organizations. It also provides advice about alternative deployment methods.

This overview introduces the following topics:

• Groove Clients and Servers

• A Process for Deployment

• Assumptions

• The Groove Software Deployment Guide

Groove Clients and Servers

A Groove deployment in an enterprise involves management, relay, and Groove compo-nent services hosted by onsite servers or Groove Networks, in addition to the Groove cli-ent device pool. Each of these resources plays a specific role in enabling smooth collaboration within an enterprise and with key contacts outside of it:

• Management services enable administrators to provision Groove clients with Groove licenses, relay servers, and usage policies via one or more management domains. These services also report Groove usage statistics.

Groove Software Deployment Overview 1

• Relay services support wide-area network contact information for Groove users, virtual peer-to-peer communications, including disconnected operation, navigation across firewalls, and economical message transfer.

• Groove Component services provide a central repository of Groove components and tools, available for download onto client devices as determined by device policies.

• Groove provides instant messaging, collaboration tools, and peer-to-peer communication.

LDAP or other database servers and Groove integration servers can be added to further automate Groove administration.

Once company IT planners have determined that a managed Groove deployment is desir-able, an overall process can be established by addressing a few basic questions. The answers will determine what components to include in the process, as suggested in the fol-lowing table:

A Process for Deployment

If the answer to all of the above questions is No, Groove is best installed manually on indi-vidual devices and does not require onsite or Groove-hosted management or relay servers.

If the answer to any of the above questions is Yes, a model procedure (illustrated in Figure

Question If Yes, Suggested Solution is:

Is unattended installation necessary? Use the Groove Enterprise Installer to conduct the deployment without requiring end-user input.

Should Groove installation parameters be standardized?

Use the Groove Enterprise installer to customize Groove installation paths and options, and to ensure standard installation settings throughout an enterprise or department.

Is the user-base large enough to merit centralized Groove deployment?

Use the Enterprise Installer with a centralized distribution system, such as Active Directory to conduct an automated, customized organization-wide installation.

Do security practices involve locked-down desktops (users without administrative access to their PCs)?

Use the Enterprise Installer in conjunction with a centralized distribution system, such as Active Directory, to allow Administrative access to client devices, avoiding the need for administrative login to each device in order to install successfully.

Is device management required to support corporate network and security practices?

Use Groove management and relay servers, along with the Enterprise Installer, to assemble Groove devices into a management domain.

Is Groove user management required to support corporate network and security practices?

Use Groove management and relay servers to assemble Groove users into a management domain.


1) would involve all or most of the following tasks:

• Setting up Groove Servers and EI Software

• Verifying Management Domains and Policies

• Identifying Target Groove Users and Devices

• Customizing the Installation

• Assembling Device Registry Keys and Other Registry Updates

• Setting Up Centralized Distribution Software (optional)

Or, Packaging Distribution for an Internal Web Site (optional)

• Running the Enterprise Installer

• Distributing Managed Identities.

• Activating Groove in a Managed Environment


Figure 1. Groove Deployment

The following sections describe each of the main tasks in more detail:

Setting up Groove Servers and EI Software

Verify that you have administrative access to Groove management and relay servers,


either onsite at your company, or through Groove Networks-hosted services. Also make sure you have access to the Groove Enterprise Installer application on CD or on a corpo-rate server.

Verifying Management Domains and Policies

In a managed Groove environment, where Groove devices and users are subject to central-ized usage policies, administrators should already have defined management domains with associated Groove licenses and usage policies. Any managed relay servers should also be registered with these domains. Groove licenses give domain members access to Groove components and tools. Groove usage policies control the Groove activities of user devices and identities that are management domain members. Device and identity policies, such as component downloads to managed devices and publishing of managed identity contact information, help secure the collaboration environment within each management domain. Managed relay servers host Groove relay services (such as offline user support) for management domains. Confirming that domains have been fully defined helps assure a successful Groove deployment.

Identifying Target Groove Users and Devices

Once Groove management services are set up in an organization and user PCs have been installed on the network, administrators can use the Groove Enterprise Installer, along with a software distribution system, such as Active Directory, to install Groove on user devices throughout an organization. Because this process typically involves registering devices and users in a Groove management domain, administrators should have a list of device names and user identity information on hand before beginning a Groove installa-tion.

Customizing the Installation

The MSI-based Enterprise Installer lets administrators customize the Groove installation to suit corporate requirements. Customization parameters, including installation directo-ries and options, and instructions for integrating Lotus Notes® or Microsoft Outlook® with Groove, can be specified in the installation command line or via Microsoft Installer Transform files.

For instructions on customizing the installation, see the “Installing Groove with Enterprise Installer” section of this guide.

Assembling Device Registry Keys and Other Registry Updates

If centralized security and other policies are to control Groove devices, these devices must be registered with a Groove management domain. Administrators can use the Enterprise Installer with MSI transform files, to systematically install domain registry keys and other registry updates, onto Groove client devices. Registry keys (available from the Groove management server) register devices in Groove management domains.

For instructions on distributing device registry keys and other Windows registry updates via EI and MSI transform files, see the “Installing Groove with Enterprise Installer” sec-tion of this guide.


Setting Up Centralized Distribution Software (optional)

Groove’s Enterprise Installer allows administrators to create a Windows Installer package for Groove Virtual Office.msi, distributed from Microsoft Active Directory General Pol-icy Objects (GPOs). This customized, centralized installation of Groove onto individual client devices, ensures a standardized installation among managed clients throughout an organization. Microsoft SMS, IBM® Tivoli, or Marimba® central deployment systems are also supported.

For more information about incorporating the Groove Enterprise Installer into a central-ized distribution package, see the “Centralized Deployment with the Enterprise Installer” section of this guide.

Packaging Distribution for an Internal Web Site (optional)

Deploying Groove from an internal Web site is a form of product install repackaging that offers another alternative for centralized installation. If a Web server (such as IIS) is installed onsite, a link to the Web-packaged Enterprise Installer can be set up from which users can install and upgrade Groove. This is most easily accomplished by using InstallShield® Package for the Web, available from its Web site.

For more information about incorporating the Groove Enterprise Installer into a central-ized distribution package, see the “Centralized Deployment with the Enterprise Installer” section of this guide.

Running the Enterprise Installer

The Enterprise Installer is a specialized version of the Groove Virtual Office (formerly Groove Workspace) application, designed for deployment in an organization. This Microsoft Installer-based application can be run from CD or a specific network location. Typically, when repeat installations are expected and when the installation has been cus-tomized, (usually via MSI transforms), the Installer runs from a network location. When a large enterprise-wide deployment is planned, the Enterprise Installer is best run from a centralized deployment system, such as Active Directory, SMS, Tivoli, or Marimba.

In an enterprise environment involving onsite management and relay servers, a central deployment server, and numerous client devices, some preparation is necessary. Once management and relay servers are installed and client devices are physically connected the network, management domains must be defined on the management server and populated with Groove licenses and user identity information. Groove device and identity policies should be optimized for each domain and managed relay servers must be assigned to the domain. In addition, domain registry keys and identity activation keys must be assembled for distribution to target devices and users, making them subject to domain management.

Once these network and install configuration tasks are accomplished and the centralized deployment service has been set up appropriately, the Enterprise Installer is ready to run, installing Groove software on designated client devices.

For detailed instructions on running the Groove Enterprise Installer, see the “Installing Groove with Enterprise Installer” section of this guide.


Distributing Managed Identities

Managed Groove user identities are pre-defined on Groove management servers by administrators, then distributed to users via email. The email contains a Groove activation key with the required identity information and instructions for activating Groove. Once Groove is installed on client devices and users receive the email containing their managed identity information, Groove can be activated.

Activating Groove in a Managed Environment

Activating Groove Virtual Office (formerly Groove Workspace) in a managed environ-ment implies an ongoing relationship with a management domain rather than the simple receipt of Groove licenses. The domain, not only enables license access, but directs domain members to managed relay servers and applies usage policies to their Groove activities.

Unmanaged Groove users install Groove and create their identities immediately or shortly after installing Groove on their devices, then activate Groove to receive licenses. In a man-aged environment, administrators typically use a Groove management server to distribute domain registry keys to devices and managed Groove identities to users. Upon receipt of administrative emails that contain their managed identities, users activate Groove, imme-diately assuming domain membership. with access to domain licenses and specified relay servers. At that point, registered client devices and domain member users become subject to device and user policies governing password creation, component downloads, and other practices.

As an alternative to individual manual activation of Groove, the Enterprise Management Server (EMS) Groove Identity Auto-Activation feature can automatically activate man-aged user accounts without requiring users to enter an activation key. For this method, the management server relies on managed users’ Microsoft Windows domain logins to authenticate users defined in its database. See the Groove Enterprise Management Server Administrator’s Guide for more information about Auto Activation.

Assumptions

The information in this guide assumes that the following measures have already been taken to prepare a site for Groove deployment:

• Enterprise Installer CD is on hand. The Groove Virtual Office software is contained in this application.

• Client devices meet the requirements for the current version of Groove Virtual Office.

• For a centralized distribution, a software deployment system (such as Active Directory) is installed and operational.

• For an internal Web site distribution, the Web site is set up.

• An onsite Enterprise Management Server is installed and configured at your site, as described in the Groove Enterprise Management Server Administrator’s Guide. Or, Groove Hosted Management Services is setup with management domains defined as described in the Groove Management Server Domain Administrator’s Guide.


• An Enterprise Relay Server is installed and configured at your site, as described in the Groove Enterprise Relay Server Administrator’s Guide. Or, Groove Hosted Relay Services is operational at the site.

The Groove Software Deployment Guide

This Groove Software Deployment Guide provides guidelines for deploying Groove in an enterprise. The Guide includes the following sections:

• Overview - Describes the interaction between Groove clients and the Groove servers that support them in an enterprise.

• Requirements - Lists software, hardware, and expertise required for Groove deployment in an enterprise.

• Running the Enterprise Installer - Provides instructions for running the Groove Enterprise Installer to deploy Groove in an enterprise.

• Centralized Deployment with the Enterprise Installer - Describes basic considerations that you need to address when defining packages and notifications (advertisements) for centralized Groove deployment, in conjunction with the Enterprise Installer. Information can be used as a model for setting up other centralized distribution software.

• Web Site Deployment - Describes how to package Groove deployment for implementing on an internal Web site.

• Installing Groove Components - Provides instructions for using the Groove Components application to download Groove components from an onsite server.

• Common Administrative Tasks - Provides guidelines for conducting common administrative tasks.

• Troubleshooting - Lists common problems related to Groove usage in an enterprise and suggests ways to address them.

• Glossary - Describes terms used in this guide.

• Appendices - Provide supplementary information.

20050330


Preparing for Deployment

This section summarizes the equipment and software necessary to support an efficient company-wide deployment of the Groove Virtual Office (formerly Groove Workspace) application in a managed environment. It also discusses important management issues that you should dress prior to deployment, such as what limits you should set (if any) on local device downloads in order to control Groove component updates.

Topics are as follows:

• Requirements

• Planning

Requirements

The Enterprise Installer runs on a variety of Windows-based devices, including client PCs, file servers (such as Windows Server 2000), deployment servers, and Web site servers (such as Microsoft IIS). Client device requirements for running the Enterprise Installer are identical to those for running Groove. Server requirements generally correspond to those for Windows Server software, IIS, and whatever centralized deployment system you are using.

The following sections describe the minimum or recommended hardware, software, and expertise you need to deploy Groove software in most enterprise environments:

• Hardware requirements

• Software requirements

• Expertise

For additional, product-specific information, check the following Microsoft Web sites:

• Microsoft Windows Installer -

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4B6140F9-2D36-4977-8FA1-6F8A0F5DCA8F

• Microsoft Active Directory -

http://www.microsoft.com/windows2000/technologies/directory/ad/default.asp

Hardware

The following table lists overall client and server hardware requirements for an enterprise-

Groove Software Deployment Preparing for Deployment 9

wide deployment of Groove, as of this publication.

Software

The following table lists Groove client and server software requirements, as of this publi-

System Components Specifications

Groove Client Devices • Intel® Pentium® II processor, 400 MHz or higher.

• 256 MB RAM for Groove® software minimum, 512 MB RAM for Groove software recommended

256 MB RAM for synchronizing a Groove Mobile Workspace with a Microsoft® SharePointTM site.

• 100 MB free disk space, with additional space required for your data.

• Display resolution 800 x 600, 15-bit (32,768) color minimum.

• Sound card, speakers, and microphone required to use voice features.

• Internet Connection:

> 56 kbps dialup connection minimum.

> LAN (Local Area Network) with Internet access, DSL, or cable modem preferred.

See http://docs.groove.net/htmldocs/readme/sysreq.html for the latest client specifications.

Management and Relay Servers

For a managed deployment, you need:

• At least one Groove Enterprise Management Server and accompanying SQL server, installed and configured as described in the Groove Management Server Administrator’s Guide.

Or, a subscription to Groove Hosted Management Services.

• At least one Enterprise Relay Server, installed onsite as described in the Groove Relay Server Administrator’s Guide.

Or, a subscription to Groove Hosted Relay Services.

Note: A hybrid option may consist of a combination of onsite management servers and Groove Networks-hosted relay services.

Centralized Deployment Server (optional)

For a centralized Groove deployment: a server running a centralized software distribution application, such as:

• Microsoft® Active Directory®, Microsoft® Systems Management Server (SMS), IBM® Tivoli, or Marimba® Software Distribution.

Component Server (optional)

For onsite Groove component update services: Windows Server 2000 (or later) running the latest version of Groove Components, as described in “Installing Groove Components”.

Web Site Server For an internal Web site-based deployment, you need:

• Web server, such as Microsoft Information Services (IIS) server


cation.

System Component Specifications

Client Software

See http://docs.groove.net/htmldocs/readme/sysreq.html for the latest client specifications.

Groove installer and application

• Latest version of Groove Enterprise Installer (version 3.0 or later) to install the corresponding version of Groove® Workspace

• Microsoft® Windows® Installer 2.0 (or later) - InstMSIW.exe is provided with EI

• isscript.msi - This file is provided with EI and automatically installed by entering setup.exe to run EI

Operating System One of the following:

• Microsoft Windows NT® 4.0 (with Service Pack 5 or later)

• icrosoft Windows 2000

• Microsoft Windows XP

NOTE: Although Groove also runs on Windows NT 4.0 (with Service Pack 5 or later), the MSI-based Enterprise Installer requires Windows 2000 or XP.

Browser • Microsoft Internet Explorer (IE) 6.0 or later

Integration • To use Groove/Lotus Notes integration features: Lotus Notes® 5.0 or later required.

• To use Groove/Outlook integration features, one of the following versions of Microsoft Outlook®:

> Outlook 2000, 2002, or 2003

• To use Groove/Office integration features, one of the following versions of Microsoft Office®:

> Office 97

> Office XP

> Office 2000 or 2003

Server and Client Software

Server software • Groove Enterprise Management Server or Hosted Management Services, installed and configured as described in the Groove Management Server Administrator’s Guide

• Groove Enterprise Relay Server or Hosted Relay Services, installed and configured as described in the Groove Relay Server Administrator’s Guide

• Central distribution system, such as Microsoft Active Directory, SMS, Tivoli, or Marimba, optional

• Groove Components application (if onsite Groove Components server is used)

Groove client software • Groove Enterprise Installer

• Windows Core Software Development Kit (SDK) and Installer SDK (if using Orca to edit MSI Transform files)


Expertise

Deploying Groove in an enterprise requires the following expertise:

• Familiarity with Windows and Windows Server configuration.

• Knowledge of your organization’s software deployment procedures and associated security policies.

• Working knowledge of Microsoft Windows Installer, Transforms (.mst files), and Orca (or other transform editor).

• Working knowledge of Active Directory Group Policy Objects (GPOs) for centralized MSI deployments.

• Working knowledge of SMS or other centralized software distribution systems, if used.

• Working knowledge of Web site packaging, if used.

Planning

Planning your Groove deployment before conducting the software installation, will help ensure initial success and predictable, reliable operation of your managed Groove environ-ment over the long term. This section addresses decisions best made at the outset, includ-ing:

• User and Device Management

• Component Update Management

• Groove Data and User Account Backup

• Password Reset and Data Recovery

• Client Auditing

User and Device Management

In order to effectively manage Groove in an enterprise environment, you need methodolo-gies for regulating Groove component updates on client devices, backing up user accounts and data, and recovering Groove user data when a password is forgotten or a user leaves the company. Groove management servers provide configurable policies that help you define and implement these and other methodologies for all managed users devices. To utilize these capabilities, you must ensure that Groove client devices are registered with a Groove management domain, as defined on a Groove-hosted or your company-hosted onsite management server.

The easiest way to register devices in a Groove management domain is to plan ahead and make devices managed during Groove installation, instead of waiting until collaboration is underway and security or data integrity problems arise mid-project. Devices must be man-aged in order to respond to component installation, data recovery, and other domain poli-cies essential to comprehensive Groove management. Both Groove and the Enterprise Installer allow you to make devices ‘managed’ by copying a device registration key from the management server to the directory from which you are conducting the installation. If you are installing from a central deployment server, such as MSI, a batch file can run the registry files to update client device registries. For information about registering Groove devices with a management server at Groove installation time, see “Setting Device Man-


agement and Registry Updates via MSI Transforms” in the Running the Enterprise Installer section of this guide.

Administrators define managed users for Groove domains and groups early in the installa-tion process, using the Groove management server (sometimes along with a corporate directory server) to specify user identity information, assign users to a management domain, and distribute Groove activation keys to them. Users must be management domain members in order to fall under policies controlling Groove account backup and other activities. The Groove Management Server Domain Administrator’s Guide provides detailed information about managing users.

Be aware that, once Groove is installed on client devices and users receive administrative email containing their managed Groove identities and activation keys, they must log on r activation step is necessary for both silent and manual Groove installations.

Component Update Management

Essential to managing any client deployment is the ability to control local software com-ponent installations on client devices. Some components may require testing in accor-dance with standard company deployment practices before installation on client machines. Others you may need to prohibit entirely, depending on their version or source.

Groove automatically notifies users when new Groove components are available, whether components are minor tool updates or components that support major Groove software release updates. Groove maintenance release updates tend to occur frequently (sometimes every few weeks), while major release updates usually occur at considerably longer inter-vals. In unmanaged environments, users need only accept the notification and new soft-ware will automatically be installed on the user devices from the Groove Networks Web site, under the auspices of the Groove Installer Service.

In a managed environment, IT practices usually employ a combination of network security devices and software permission settings to control end user device use. These practices may or may not affect Groove component installation capabilities the way you want them to. The Groove management server and enterprise installer offer features that allow you to set necessary restrictions while allowing specific automatic updates as appropriate.

At the highest level, Groove management servers allow management domain administra-tors to set component installation policies for managed devices. These policies govern which Groove components can or cannot be installed on managed devices, if any. Be sure that a domain administrator has configured management servers in accordance with stan-dard company practice before conducting a Groove deployment. In this way, you can arrange for Groove component updates throughout your organization as safely and effi-ciently as possible. For detailed information about managing Groove component updates, see the “Managing Devices” section of the Groove Management Server Domain Adminis-trator’s Guide.

Once device policies are defined on the management server, the Enterprise Installer allows you to set the Installer Service for automatic operation (as in unmanaged Groove). For more information about the Installer Service, see “Controlling the Groove Installer Ser-vice” in the Running the Enterprise Installer section of this guide.


For tighter control over Groove component updates, you can consider installing the Groove Components application on a server at your site, providing that your site already includes an Enterprise Management Server. Then, you can set a management server device policy to direct users to the specified server for Groove component downloads. See the “Installing Groove Components” section of this guide for more information about Groove Components.

Groove Data and User Account Backup

Groove software, supported by a management server, provides several mechanisms for backing up Groove data, as described these sections:

• Client Account Backup

• Managed Account Backup

• Groove Space Backup

Client Account Backup

Another important aspect of Groove management, as with any knowledge-based end-user software, is having a process in place for backing up critical information. Groove Virtual Office (formerly Groove Workspace) provides an account backup capability that end-users can run whenever they choose. In case of account loss, disk failure or other prob-lems, users can then access their backed-up account so it can be restored. User accounts consist of user identity information, domain management settings, and the list of Groove workspaces associated with that account, all of which are saved during Groove account backup.

Managed Account Backup

The Groove management server puts account backup functionality in the hands of admin-istrators, via a configurable device policy that schedules automatic account backups for all users in a management domain. Make sure that this policy is enabled for your manage-ment domains. Once this policy is in place for a domain, managed users benefit from the domain’s automatic account backups.

Backing up Groove accounts does not include Groove workspace data (which users can fetch, either from another computer on which they have the same account, or from other members of their Groove workspaces). However, locating Groove in specific directories slated for periodic backup is not recommended; backing up many extensive data directo-ries involved in a large-scale installation can noticeably tax system resources. Using the Groove managent server and account backup capabilities, is the recommended method of backing up Groove information. User data files can be easily retrieved from fellow Groove space members or other user devices.

Note that you cannot download expired accounts (those which have not been backed up within the past 60 days). However, all restoration functionality remains in case you still want to restore the account as is on the client. For information about how to restore an expired account, contact Groove Customer Support.

For detailed information about setting a device policy to schedule account backups, see the “Managing Users” section in the Groove Management Server Domain Administrator’s


Guide.

Groove Space Backup

If you want to backup Groove workspace data to a central location, you can consider uti-lizing the Enterprise Backup Service which runs in conjunction with the Groove Enter-prise Integration Server, an optional system designed to help integrate Groove with other corporate applications. The backup service can be configured to automatically make backup copies of a company’s Groove spaces. Several bots (pieces of automated agent code) support this service, allowing it to run seamlessly in the background of Groove operations. The Backup Service periodically backs up all spaces under its control into Groove Space Archive (.gsa) files. These .gsa files are deposited into a corporate file sys-tem.

For more information about Groove Backup and Integration services see the Groove Enterprise Backup Service Administrator’s Guide and Groove Enterprise Integration Server Administrator’s Guide.

Password Reset and Data Recovery

Another factor to consider during Groove deployment planning is Groove user password reset and data recovery. Being prepared in the event of a sudden employee departure, machine loss or damage, or simply a forgotten password requires taking some preliminary steps prior to installing software. In an unmanaged environment, if a user leaves the com-pany or forgets a password, no one can access that user’s Groove spaces unless they know the user’s password. The management server’s Password Reset and Data Recovery fea-tures enable you to reset a user’s password and restore data on managed devices in a domain, providing that you have set device policies to allow administrative access to cli-ent accounts.

Groove Data Recovery requires three conditions to be met:

• The first step toward setting up Groove Data Recovery is to make sure that user devices targeted for Groove deployment be managed, as described above in “User and Device Management”.

• One of two data recovery policy options must be enabled for your management domains. Decide whether administrators need the ability to restore passwords, or whether they only need access to user data and set the policies accordingly. If neither policy is enabled, you cannot recover lost data or passwords on client devices.

For detailed instructions about resetting passwords, recovering data, and setting associated device policies, see the Groove Management Server Domain Administrator’s Guide.

Client Auditing

Large enterprise environments sometimes require close monitoring of user software usage practices and trends. To address this requirement, the Groove Enterprise Management Server, as of version 3.0, supports an optional Groove client auditing feature that allows administrators to audit Groove activities on client devices. The audit function runs on a Groove audit server installed at your site, in conjunction with an Enterprise Management


Server and supporting SQL server. See the Groove Enterprise Management Server Administrator’s Guide for information about Groove client auditing.


Installing Groove with Enterprise Installer

The Groove Enterprise Installer (EI) is a packaged offering of the Groove Virtual Office (formerly Groove Workspace) software, designed to facilitate managed deployment in an organization. This enterprise version of Groove is based on Microsoft® Windows® Installer, so you can use .msi files and transforms to customize the installation and Active Directory to conduct the installation.

Typically, you install this enterprise version of Groove Virtual Office onto client PCs via Microsoft Active Directory® Group Policy Objects (GPOs). You can also use other cen-tralized software distribution systems, such as Microsoft® Systems Management Server (SMS), IBM®Tivoli, or Marimba. For individual deployments, you can run the Enterprise Installer directly on a client device.

The Enterprise Installer allows you to do the following:

• Install the Groove application silently (quiet or unattended mode) on client devices.

• Customize and standarize Groove installation directory paths and options.

• Brand the Groove Virtual Office installation to prevent non-administrative users from over-installing with a non-enterprise version of Groove.

• Enable/disable Lotus Notes® and Microsoft Outlook® integration.

• Deploy management domain registry keys to Groove client devices (required for setting device policies on Groove management servers).

• Deploy other Windows registry settings files to Groove client devices.

• Prevent end-users from over-installing a managed version of the Groove software with an unmanaged version.

• Use the Groove Installer Service to upgrade Groove components automatically.

• Automatically install Groove Help and file viewers (for use with the Groove Files tool) on Groove clients.

This document describes how to configure the Enterprise Installer and use it to deploy Groove software on client devices in your organization.

After reviewing the information in “Preparing for Deployment” and “Enterprise Installer Basics”, you can use the “QuickStart” procedure as a trial run or to quickly enable a small number of individual Groove users and devices in your enterprise. For a full company-wide deployment, use the recommended method, which involves the following steps:

Groove Software Deployment Installing Groove with Enterprise Installer 17

• Preparation Before You Begin

• Running the Groove Enterprise Installer

• Customizing Groove Installation Using MSI Transforms

• Customizing Groove Installation from the Command Line

• Setting Device Management and Registry Updates via MSI Transforms

• Checking Windows Installer Log Files

• Activating Groove

For information about upgrading Groove and uninstalling the Enterprise Installer, see the last sections:

• Updating Groove

• Uninstalling the Groove Enterprise Installer

Enterprise Installer Basics

The Groove Enterprise Installer is a special version of the Groove Virtual Office (formerly Groove Workspace) application, based on Microsoft MSI. As with typical Windows installations, you can specify installation paths and Windows Installer options from the user interface (UI) during product installation, from an MSI command line, or via an MSI transform (.mst) file.

For information about using Microsoft Windows Installer, see the information accompa-nying the software or visit http://support.microsoft.com/default.aspx?scid=http://sup-port.microsoft.com:80/support/kb/articles/Q257/7/18.ASP&NoWebContent=1.

The Enterprise Installer consists of the following directories and files:

• GrooveMSI directory - Contains the Enterprise Installer setup.exe, Groove Virtual Office.msi, and other application files.

• GrooveClientInstall.pdf - Printable Groove Software Deployment Administrator’s Guide.

The Enterprise Installer runs in silent, or quiet, mode for unattended operation, or UI mode which requests user input for installation directories and options. Unattended operation is most applicable to a centralized distribution scenario because the installation runs auto-matically using default or customized Groove installation settings. UI mode operation is most useful for pre-testing an installation.

When running in unattended mode, the Enterprise Installer relies on default installation paths and options, or paths and options specified in an MSI transform file (or command line), instead of on user input and system defaults.

During installation, the Enterprise Installer brands Groove Virtual Office as an enterprise installation, preventing end-users from over-installing with an non-enterprise version of Groove (via www.groove.net, for example). It also sets client device read/write permis-sions on directories where Groove program and data directories will reside, necessary for Groove product operation. In a secure enterprise environment, these directories are typi-cally locked down.


To ease the task of keeping Groove up-to-date in a locked-down-desktop environment, the Enterprise Installer offers the option of running the Groove Installer Service automati-cally. This service runs with LocalSystem privileges on behalf of end-users who do not have administrative rights to their PCs, enabling Groove component additions or updates to occur, as determined by managed device component policies. This feature helps admin-istrators manage the distribution and installation of Groove components to users in a secured desktop environment, and ensure that all users are running the same managed ver-sion of Groove with the latest components.

If you want to include Windows registry updates in the installation process, you can define the registry changes in an MSI transform (.mst) file and include the transform in the MSI installation command line (or central deployment package). For example, domain registry keys, available from a Groove management server, allow you to manage Groove devices and define Groove component installation and other policies that help maintain a secure environment for collaboration. Other registry settings allow you to enable virus scanning on client devices. MSI transforms let you deploy these registry updates as part of an orga-nization-wide Groove installation.

Deploying Groove software via the Enterprise Installer automatically loads Groove Help and file viewers onto client devices, so that clients need not perform this task manually. File viewers support the Groove Files tool.

For information about running the Enterprise Installer from a centralized deployment application, see “Centralized Deployment with the Enterprise Installer” in this guide.

For information about running the Enterprise Installer from a Web site, see “Website Deployment” in this guide.

QuickStart

This section presents a simple application of the Enterprise Installer to deploy Groove software on client devices, employing only the most basic installation functionality. Because it can be completed quickly, with little preparation, it is a convenient way to con-duct a baseline test. The QuickStart assumes the following:

• You are running the Enterprise Installer in UI mode.

• Your Groove management server is configured as desired with user identities defined and provisioned in the appropriate management domain.

• You accept the default installation directory paths and options, and are not using MSI transforms.

• You are not updating the Windows registry on client devices.


• You are running the installation directly on a individual client devices (without a centralized software distribution system).

Before You Begin

Familiarize yourself with Help resources and check the required tasks in the Prerequisites list before beginning the deployment.

Getting Help

A printable version of the Groove Software Deployment Administrator’s Guide, Groove-ClientInstall.pdf, is available from the root directory of the Enterprise Installer CD.

To get Help running Groove, users can do any of the following:

• Select a topic from the Groove Help menu.

• Click the F1 key from anywhere in Groove to see context sensitive Help.

• Access the Groove User’s Guide at http://www.groove.net/support/usersguide.html at the Groove Networks Web site.

To get help running Groove’s management or other supporting servers:

• Click the Help button or link from the product user interface.

• Refer to the Administrator’s Guide provided with the product.

Prerequisites

Before setting up the Groove deployment, do the following:

• Read the release notes in the readmeEI.htm file that accompanies the Enterprise Installer CD. This file contains important late-breaking information about Groove installation and directory assignments.

• Read “Preparing for Deployment” and “Enterprise Installer Basics” earlier in this guide.

• Assemble any client registry updates that may be necessary. For example:

• To manage client devices, you will need to update client devices with management server registry keys.

QuickStart to Groove Deployment

1. Identify devices where the Groove application will be installed.

2. Log in to a client device as Administrator and insert the Enterprise Installer CD in the device drive (or access the setup directory from a network location).

3. Click setup.exe and complete the setup process, accepting all defaults.

4. Activate Groove. See “Activating Groove”, later in this section, for information about activating Groove.


• To configure Groove virus filtering on managed devices, you will need to update the windows registry values on those devices, as described in “Appendix C. Controlling Local Virus Scanning and Filtering”.

• If you intend to use MSI transforms to set installation directory paths and options, or to update the Windows registry on client devices, create an .mst file accordingly. See “Customizing Groove Installation Using MSI Transforms” and “Setting Device Management and Registry Updates via MSI Transforms” for information about using MSI transforms to install Groove software.

• Assemble a list of client devices where Groove is to be installed.

• If you are running the Enterprise Installer locally on each device, login to each device as Administrator (or comparable power user). If a centralized deployment application is to run the installation, make sure that it is set to Run as Administrator.

• If you intend to manage Groove usage and security policies, make sure that your management domain administrator has defined device and/or user policies for each domain defined on the management server, as described in the Installation and Getting Started sections of the Groove Management Server Domain Administrator’s Guide.

• To manage client devices via centralized security policies, get the management server registry key necessary to register devices in a management domain. See the Groove Management Server Domain Administrator’s Guide for information about management server registry keys.

• To manage Groove users via centralized usage polices, make sure that user identity information has been entered on an Enterprise Management Server or Groove Hosted Management Server. See the Groove Management Server Domain Administrator’s Guide for information about user administration from a management server.

• If using a management server, make sure that at least one onsite Enterprise Relay Server or Groove Hosted Relay Server is assigned to your management domain(s). See a management or relay server administrator or the Groove Enterprise Relay Server Administrator’s Guide for information about onsite relay servers.

• To enable Groove client auditing, make sure you have set Groove device auditing policies on the management server accordingly.

Running the Groove Enterprise Installer

Once you have configured the Enterprise Installer, you are ready to install Groove soft-ware on the intended client devices. You can run the installation program from a CD, a specified drive, or a central distribution system (such as Active Directory or SMS).

Note: The Enterprise Installer automatically sets the necessary read/write permissions that enable intended clients to use Groove. In most enterprises, end users do not have write permissions to the Windows directories where Groove program, user data, and system data files reside by default. Groove clients have must have write access to some of these files (as summarized in “Appendix B. Managed Install Permissions”). Do NOT reset these permissions after the installation is complete.


To use the Enterprise Installer to deploy the Groove application, follow these steps:

1. Make sure that the your management domain administrator has set up the necessary Groove licences, usage policies, and any relay servers for each domain defined on the management server, as described in the Groove Enterprise Management Server Administrator’s Guide.

2. Start the installation as shown in the following table, depending on your setup:

3. Include any Windows Registry setting files (including domain registry keys for devices) in a transform, as described in “Setting Device Management and Registry Updates via MSI Transforms”.

4. To customize the installation via an MSI transform (the recommended method of customization), create a Groove .mst file with the appropriate installation paths and options. See “Customizing Groove Installation Using MSI Transforms” for information about creating Groove MSI transforms.

5. Go to the Groove installation/distribution directory and click setup.exe or MSIExec.exe. Or, open a command line and enter setup or MSIExec, followed by any command line options (and/or MSI transform file that you have created), if necessary. See “Customizing Groove Installation from the Command Line” for information about customizing Groove installations using command line options, including the difference between using setup.exe or MSIExec.exe.

6. After the installation is complete, check the MSI*.log file to verify that the installation was successful, as described in “Checking Windows Installer Log Files” later in this section.

Customizing Groove Installation Using MSI Transforms

To customize enterprise installations of Groove, you can create MSI Transform (.mst) files that can be specified in an EI installation command line or central deployment pack-

To Run EI as follows: Do the Following:

On a client device: 1 Log into the device as Administrator.

2 Insert the Enterprise Installer CD in the device drive.

From a network drive, 1. Insert the Enterprise Installer CD in the drive of a network-accessible deployment server.

2 Copy the contents of the GrooveMSI directory to a network-accessible directory, such as x:\DistributionDirectory.

3 Log into the client device as Administrator.

From a software deployment system

• Set up the package and client notification (or advertisement).

• Make sure the Enterprise Installer files (including setup.exe and Groove Virtual Office.msi) are located in the desired distribution point.

• See “Centralized Deployment with the Enterprise Installer” for more information about centralized deployment.


age. The Groove Enterprise Installer provides a set of Groove-specific properties for use in transforms. Microsoft Orca, a free MSI file editor (provided with the Windows 2000, XP or later SDK) lets you create and edit transforms, or you can use another MSI trans-form editor.

The table below lists Groove transform properties (also definable from the installation command line, as described below in “Customizing Groove Installation from the Com-mand Line”):.

Groove MSI Transform Property

Value Groove Default Installation Path

INSTALLDIR Location of Groove installation directory, where the Groove application and related files reside.

C:\Program Files\Groove Networks\Groove

GROOVEUSERDATADIR Location of Groove user and device account files and related files.

C:\Documents and Settings\<username>\Application Data\Local Settings\Groove Networks\Groove\

For Windows NT:

C:\WINNT\Profiles\[username]\Application Data\Local Settings\Groove Networks\Groove

GROOVESYSTEMDATADIR

Location of Groove system-level data, typically shared by all users of the device.

C:\Documents and Settings\All Users\Application Data\Groove Networks\Groove

For Windows NT:

Program Files\Groove Networks\Groove\Data\System

GROOVE_ ADD_TO_DESKTOP

0 = Do not add to desktop.

1 = Add to desktop.

Default: 1

Specifies whether to add a Groove shortcut to client device desktops.

GROOVE_ ADD_TO_STARTUP

0 = Do not add to Startup menu.

1= Add to Startup menu.

Default: 1

Specifies whether to add a Groove shortcut to the client device Start menu. Set the value to “True” to add a shortcut to the Start menu.

GROOVE_OUTLOOK_INTEGRATION

0 = Do not integrate with Outlook.

1 = Integrate with Outlook.

Default: 1

Specifies whether to install Groove/Microsoft Outlook integration (allowing users to send Outllook mail and calendar entries to a specified Groove space).

For information about associated Windows Registry updates see “Appendix A. Registry Changes for Mail/Messaging Integration” in this guide.


The table below shows the Groove transform ServiceInstall option:

GROOVE_NOTES_INTEGRATION

0 = Do not integrate with Notes.

1 = Integrate with Notes.

Default: 1

Specifies whether to install Groove/Lotus Notes integration (allowing users to send Notes mail and other records to a Groove space).

For information about associated Windows Registry updates see “Appendix A. Registry Changes for Mail/Messaging Integration” in this guide.

MSI Transform ServiceInstall

Name StartType Description

NewServiceInstall1 GrooveInstallerService

2 = Sets the Groove Installer Service to start Automatically.

3 = Sets the Groove Installer Service to start Manually.

4 = Sets the Groove Installer Service to Disabled.

Default: 3

Instructs the Enterprise Installer to set the Groove Installer Service, included with Groove Virtual Office, to run automatically, manually, or not at all. This Windows Service runs with LocalSystem privileges on client devices when end-users do not have administrative rights to their PCs, enabling component additions and updates (as specified by device management policies). Omitting this flag accepts the default setting of Manual start for the service.

See “Updating Groove” later in this section for more information about the Installer Service.

Groove MSI Transform Property

Value Groove Default Installation Path


Customizing Groove Installation from the Command Line

You can specify Groove installation directory paths and most options that are definable in a Windows transform file from the Windows command line, by entering Setup or MSIexec, followed by valid command line arguments and/or MSI transform files.

Valid command line property arguments for a Groove installation are:

• INSTALLDIR

• GROOVEUSERDATADIR

• GROOVESYSTEMDATADIR

• GROOVE_ADD_TO_DESKTOP

• GROOVE_ADD_TO_STARTUP

See “Customizing Groove Installation Using MSI Transforms” above for descriptions of these options, which you can also specify via an MSI transform file.

The following sections describe:

• Command Line Format

• Command Line Options

Command Line Format

You can use Setup or MSIexec in a Groove installation command line, depending on your requirements. If you are using Active Directory GPOs to centrally deploy Groove,

NewServiceInstall2 GrooveAuditService

2 = Sets the Groove Audit Service to start Automatically.

3 = Sets the Groove Audit Service to start Manually.

4 = Sets the Groove Audit Service to Disabled.

Default: 3

Instructs the Enterprise Installer to set the Groove Audit Service, included with Groove Virtual Office, to run automatically, manually, or not at all. This Windows Service runs with LocalSystem privileges on client devices when end-users do not have administrative rights to their PCs, enabling Groove client auditing (as specified by device management policies). Omitting this flag accepts the default setting of Manual start for the service.

See the Groove Enterprise Management Server Administrator’s Guide for more information about the Audit Service.

MSI Transform ServiceInstall

Name StartType Description


you must use MSIExec.exe to run Groove Virtual Office.msi; setup.exe is not a valid entry.

The following sections describe the differences between command line usages:

• Command Line with Setup.exe

• Command Line with Setup.exe and Transform

• Command Line with MSIExec.exe

• Command Line with MSIExec.exe and Transform

Command Line with Setup.exe

The following example shows a setup.exe command line specifying a full compliment of Groove installation directories and options:

C:\Setup\GrooveMSI>setup /w /S /V”/qn INSTALLDIR=D:\GROOVEINSTALL GROOVEUSERDATADIR=D:\GROOVEUSER GROOVESYSTEMDATADIR=D:\GROOVESYSTEM GROOVE_ADD_TO_DESKTOP=1 GROOVE_ADD_TO_STARTUP=1”

where values are as shown in the following table below (see the MSI documentation for a complete list of UI options):

Command Line with Setup.exe and Transform

For example:C:\Setup\GrooveMSI>setup.exe /w /S /V”/qn TRANSFORMS=GVO-[domainname].mst /lv

Value Definition

setup setup.exe

/S Full silent installation. Prevents initial setup pop-up window from querying for confirmation.

/V”...” Apply following parameters. (Quotation marks needed for multiple arguments.)

/w Force setup.exe to wait until installation is complete before exiting.

/qn Quiet installation - no UI.

Note: To specify quiet installation and an installation-complete pop-up window, use /qn+.

INSTALLDIR Groove installation directory where Groove application files reside

GROOVEUSERDATADIR Groove user and device account files and related files.

GROOVESTEMDATADIR Groove system-level data, typically shared by all users of the device.

GROOVE_ADD_TO_DESKTOP=1

Add Groove shortcut to user desktops.

GROOVE_ADD_TO_STARTUP=1

Add Groove shortcut to startup folder.


c:\GrooveMSI.log”

where values are as shown in the following table:

Command Line with MSIExec.exe

If you are assured of the following, you can use msiexec /I “Groove Virtual Office.msi” in the command line (instead of setup.exe):

• The latest Windows Installer 2.0 file (instmsiw.exe) or the latest update with Windows Service Pack (SP) 4 is already installed on the device. This file is available with Windows XP SP1 and Windows 2000 SP4. You can also update existing an Windows Installer file using the Enterprise Installer setup.exe.

• The latest InstallShield Script engine (isscript.msi) is already installed on the device. This file is available with the Enterprise Installer and with the InstallShield software. The Enterprise Installer provides these files, which are included in the installation from setup.exe.

For example:C:\Setup\GrooveMSI>msiexec /I "Groove Virtual Office.msi" /qn INSTALL-

DIR=D:\GROOVEINSTALL GROOVEUSERDATADIR=D:\GROOVEUSER GROOVESYSTEMDATA-DIR=D:\GROOVESYSTEM GROOVE_ADD_TO_DESKTOP=1 GROOVE_ADD_TO_STARTUP=1

where msiexec=MSIExec.exe and remaining values are as shown in the table for setup.exe in “Command Line with Setup.exe”, above.

Command Line with MSIExec.exe and Transform

If you are assured of the following, you can use msiexec -I Groove Virtual Office.msi in the command line (instead of setup.exe):

• The latest Windows Installer 2.0 file (instmsiw.exe) or the latest update with Windows Service Pack (SP) 4 is already installed on the device. This file is

Value* Definition

GVO-[domainname].mst Name of your transform, such as:

GVO-GrooveInst.mst

/S Full silent installation. Prevents initial setup pop-up window from querying for confirmation.

/V”...” Apply following parameters. (Quotation marks needed for multiple arguments.)

/w Force setup.exe to wait until installation is complete before exiting.

/qn Quiet installation - no UI.

Note: To specify quiet installation and an installation-complete pop-up window, use /qn+.

/lv c:\GrooveMSI.log Writes the MSI log for the Groove installation to c:\.

*Note spacing and quotes in sample command line.


available with Windows XP SP1 and Windows 2000 SP4. You can also update existing an Windows Installer file using the Enterprise Installer setup.exe.

• The latest InstallShield Script engine (isscript.msi) is already installed on the device. This file is available with the Enterprise Installer and with the InstallShield software. The Enterprise Installer provides these files, which are included in the installation from setup.exe.

For example:C:\Setup\GrooveMSI>msiexec /I “Groove Virtual Office.msi” /qn+ TRANS-

FORMS=GrooveInst.mst

where values are as shown in the following table:

Command Line Options

The following sections show sample command lines for specific Groove installation options:

• Specifying Unattended Installation

• Changing Groove Installation Directory Paths

• Changing Groove Installation Options

Specifying Unattended Installation

To specify a silent installation, use setup or msiexec in a command line, followed with by the qn argument. If using the setup command, be sure to include /S in the command line, as well as /qn, for a complete silent installation.

For example, using setup.exe:C:\Setup\GrooveMSI>setup /S /V/qn

Using msiexec:msiexec:C:\Setup\GrooveMSI>msiexec /I "Groove Virtual Office.msi" /qn

where values are as shown in “Command Line Format”.

Changing Groove Installation Directory Paths

To change the installation directory paths for Groove program, user account, and system data files on client devices, you can specify the installation directory values in the GrooveMSI command line (if you are not using an MSI transform for instance).

For example, using setup.exe:C:\Setup\GrooveMSI>setup /S /V/qn+ "Groove Virtual Office.msi" INSTALL-

DIR=D:\GROOVEINSTALL GROOVESYSTEMDATADIR=D:\GROOVESYSTEM GROOVEUSERDATA-DIR=D:\GROOVEUSER

Value Definition

msiexec MSIExec.exe

/I Install the following file.

/qn+ Quiet installation - no UI. Setup completed pop-up window upon successful installation.


Using msiexec:C:\Setup\GrooveMSI>msiexec /I "Groove Virtual Office.msi" /qn+ INSTALL-

DIR=D:\GROOVEINSTALL GROOVESYSTEMDATADIR=D:\GROOVESYSTEM GROOVEUSERDATA-DIR=D:\GROOVEUSER


Changing Groove Installation Options

To specify Groove installation options, you can use MSI arguments in the command line to specify your preferences (if you are not using an MSI transform for instance).

For example, using setup.exe:C:\setup.exe\GrooveMSI>setup /S /V/qn+ GROOVE_ADD_TO_DESKTOP=1

Using msiexec:C:\Setup\GrooveMSI>msiexec /I "Groove Virtual Office.msi" /qn+

GROOVE_ADD_TO_DESKTOP=1


Setting Device Management and Registry Updates via MSI Transforms

Managing Groove devices involves updating the Windows registry settings on those devices with a .reg file provided by the Groove management server. You can distribute this device registry file, and any other registry updates (such as those needed to enable virus scanning), to target devices via an MSI transform file. You then specify the trans-form file in the Groove Enterprise Installer command line (or central deployment pack-age).

For information about accessing domain registry keys, see the Groove Management Server Domain Administrator’s Guide.

The procedure below shows how to create a transform that updates devices with the Groove management server registry key. You can use this procedure as a model for creat-ing transforms for registry updates.

To create and use an MSI transform file for installing a management server domain regis-try key to client devices, follow these steps:

1. Start Microsoft Orca (a free MSI file editor provided with the Windows 2000, XP, or later software developer’s kit) or another MSI file editor. The steps and tables below apply specifically to Orca but are adaptable to other editors.

2. Create a Registry table as follows (in Orca):

a. If you have an existing transform (.msi) file that you want to use as a template, open it in the editor (you can right-click it and select Open with Orca).

b. Choose New Transform from the Transform menu.

c. Select Add Table from the Tables menu. The Add Tables drop-down menu appears with a list of tables.

d. Select Registry from the tables list.

3. Create a row to define the Certificate Name/Value pair as follows (in Orca):


a. Select Add Row from the Tables menu. The Add Row window appears with a table of names and values.

b. From the Add Row window, fill in the fields in the Value column for the Certificate Name/Value pair, as described in the table below. Then click OK.

4. Create another row for each of the remaining Name-Value pairs by repeating the previous step for each pair and filling in the Name and Value fields as described in the table below. Click OK to complete each row definition.

Name Column Value Column

Registry RegistryEntryName[n] where n = numbers 1 to 5 for each named row, such as:

DeviceReg1

Root Root number for HKEY_LOCAL_MACHINE

For example, type the following:

2

Key Type the following:

SOFTWARE\Groove Networks, Inc.\Groove\ManagementDomain

Name Type the following:

Certificate

Value Domain certificate value with “#x” as prefix and all spaces removed.

For example, the following:

#x3245673567899976668988687782

Component Type the following:

GrooveRegistryKeys


Name Each of the following names:

• Name

• GUID

• Group

• ServerURL


5. Save the registry changes in a .mst (transform) file (for example, registryadd.mst).

6. Reference the .mst file as a tranform in the Groove Enterprise Installer command line or package. The following is a sample command line:

C:\Setup\GrooveMSI>msiexec /I “Groove Virtual Office.msi” TRANSFORMS=regis-tryadd.mst

Checking Windows Installer Log Files

You can enable installation from the command line using the MSI logging mechanism, or by setting a registry key, as follows:

• To set up logging from an MSI command line, enter the following:

C:\setup\MSIExec.exe /I “Groove Virtual Office.msi” /lv* C:\GrooveMSI.log

• To set up installation logging (in an MSIxxx.log file) by editing the Windows registry, start regedit, go to HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer

and set the String value “Logging” = “voicewarmup”

See the MSI documentation for information about arguments for controlling the level (lv) of debugging.

Once you have enabled logging, the Installer software creates an MSI .log file in the Temp directory of the local device. The .log file records whether the installation was successful and logs any error codes returned, especially useful for unattended installation when the Enterprise Installer does not display status or error pop-ups.

Once you have verified the installation, users can activate Groove Virtual Office with their new managed identities (generated by management domain administrators), as described next in “Activating Groove”.

Activating Groove

Once Groove is successfully installed on client devices, users can activate Groove. If users are unmanaged, they start up Groove and create identities for themselves, following the Groove activation instructions.

Value Values for each of the following:

• Name value, domain name, such as:

XDomain

• GUID value, domain GUID such as:

crxe449wt9unjedwizjsff43uqghndjqbiiggza

• Group value, domain Group such as:

sff43uqghndjqbiiggzacrxe449wt9unjedwizj

• ServerURL value, such as:

htttp://empgms.internalgroove.net/gms.dll



In a managed user environment, the following steps are necessary to activate Groove:

1. From the Groove management server Web interface, a management domain administrator should distribute email containing the activation keys for managed Groove identities to all users that you want to include in a management domain.

2. End users can log into their devices.

3. Upon receipt of the activation email, users can activate their managed identities by starting up the newly installed Groove application and entering the activation key when prompted. If Groove is already running, users can click the Help menu and select Activate Product to access the prompt for the Activation Key. For more information about managed identities and activation keys, see the Groove Management Server Domain Administrator’s Guide.

To further automate the Groove installation, you can use the management server’s Auto-Activation capability. In this scenario, auto-activation registry setting automatically acti-vates Groove for managed users, based on users’ Windows domain login. For information about auto-activation, consult your management server administrator or the Groove Enter-prise Management Server Administrator’s Guide.

Once users activate their managed identities, they become managed members of a Groove management domain, gaining access to domain licenses and any managed relay servers. They also become subject centralized management policies governing identity publication and other usage issues. Similarly, any managed devices, registered in a Groove manage-ment domain become subject to device policies governing password creation, component downloads and other aspects of secure collaboration.

Note: If at some point you need to migrate large numbers of Groove users from one machine to another (for a hardware upgrade, for example), a Groove migration utility can expedite the process of relocating user workspace data. For information about obtaining this utility, contact Groove Support.

Updating Groove

You can update Groove with the latest components via the Enterprise Installer the same way as you use it to install Groove software, using MSI Transforms to control the updates. Note the upgrade process applies only to Groove version 2.5j or later.

Two transform properties affect Groove component updates, as described in the following sections:

• Controlling Groove Updates

• Controlling the Groove Installer Service

Controlling Groove Updates

You can update or upgrade Groove on all your client devices by using the Enterprise Installer and a centralized distribution application, such as MSI (or SMS). Or, you can run updates or upgrades directly on individual Groove client devices. You use the same type of transform (.mst) file, or command line, to run an update (from 2.x to 2.y, for example) or upgrade (from 2.0 to 3.0, for example) as you do to conduct a complete new installa-tion, minus the customizatioin property arguments, for which the update uses the original


installation settings.

The following is a sample command line for a quiet upgrade:C:\setup.exe\GrooveMSI>MSIExec /I "Groove Virtual Office.msi" /qn

where Groove Virtual Office.msi contains the latest version of Groove.

Controlling the Groove Installer Service

Groove utilizes the Groove Installer Service to allow LocalSystem privileges on a device when end-users lack administrative rights to their PCs, enabling Groove component updates, as specified by your device management policies.

The Installer Service is a Windows Service that is always installed with Groove Virtual Office (formerly Groove Workspace, as of version 2.5), using a default setting of manual startup. Specifying the NewServiceInstall property in an MSI transform file lets you set the Installer Service to start automatically. If you do not define a transform file with the NewServiceInstall property, the service relies on manual operation, allowing you to deter-mine when Groove component updates take place.

Groove Networks recommends that you run the Groove Installer Service only if you are using device policies to control the components that can be installed on managed client devices, as described in Groove Management Server Domain Administrator’s Guide. The objective is to adjust Groove component policies to comply with your organization’s oper-ating system security policies. For example, a set of device policies might limit updates to components signed by Groove Networks. Or, policies might allow minor Groove version upgrades only, denying installations of major version upgrades; if subsequently, compo-nents from a major release are subsequently necessary, device policies must be changed accordingly.

The Groove Installer Service can be invoked via various Groove events, including Groove space invitations, adding a tool, and component injection. Proper device policies, defined on the Groove management server, allow you to control what the Installer Service can install. See the Groove Management Server Domain Administrator’s Guide for informa-tion about setting component policies for devices registered with a Groove management domain.

Uninstalling the Groove Enterprise Installer

You can uninstall the Groove application from client devices using the Windows Add/Remove Programs control panel option.

If you deployed Groove using Active Directory, you can remove the MSI-based installa-tion from the domain controller and the application from the client device. For informa-tion about removing an MSI installation, visit http://www.microsoft.com/downloads/details.aspx?familyid=CEBBACD8-C094-4255-B702-DE3BB768148F&displaylang=en.


Centralized Deployment with the Enterprise Installer

The recommended way to deploy Groove software on client devices in an enterprise is to create a Groove deployment package, using a central software distribution application, such as Microsoft Active Directory Group Policy Objects (GPOs), along with the Groove Enterprise Installer. Microsoft Software Management Server (SMS), IBM Tivoli, and Marimba are other supported deployment methods.

The Windows Installer-based Groove Enterprise Installer enables customized, unattended (quiet or silent) installation of Groove, making it especially suitable for the central deploy-ment which enables simultaneous installations on multiple client devices. The Enterprise Installer sets the correct permissions needed to access the Groove program, user data, and system data directories. This capability is especially useful when attempting a centralized deployment in managed domain environments where users do not have the necessary read/write permissions to access the default directories for Groove program and data files to install applications.

Note: If Active Directory, SMS, or another centralized deployment application changes the read/write permissions set by the Enterprise Installer, you may need to manu-ally reset these permissions. See “Appendix B. Managed Install Permissions” for a summary of default directory locations and required permissions for Groove files.

For more information about the Enterprise Installer and creating associated MSI Trans-forms, see “Installing Groove with Enterprise Installer” in this guide.

The following sections provides guidelines for centralized Groove deployment via Active Directory or SMS:

• Before You Begin

• Active Directory GPO Installations

• SMS Installations

• Activating Groove After a Centralized Installation

Before You Begin

Before creating deployment packages and advertisements, do the following:

Groove Software Deployment Centralized Deployment with the Enterprise Installer 34

• Read the release notes in the readmeEI.htm file that accompanies the Enterprise Installer CD.

Note: The readmeEI.htm file includes important late-breaking information about Groove installation and directory paths in multi-user deployments.

• Make sure you have a working knowledge of the Groove Enterprise Installer as well as Active Directory and Group Policy Objects (GPOs), or other centralized software distribution system.

• Familiarize yourself with the material discussed in “Installing Groove with Enterprise Installer” in this guide.

• Customize the Groove installation directory paths and Notes or Outlook integration options, as necessary, by creating an MSI transform file. Locate this file in a network-accessible distribution point.

• Consider installing Windows Scripting Host (WSH) version 5.5 (or later) on every machine. Groove installation automatically installs Scripting Host but requires an administrative reboot to complete the installation. Pre-installing Scripting Host avoids the need for the administrative reboot after Groove is installed. Note that the WSH files must be installed as Administrator and the PC must be logged in as Administrator upon reboot.

• Make sure that any non-GPO-based distribution software) is set to Run as Administrator (or comparable power user).

• If your enterprise does not grant Administrator (or comparable power user) privileges to end users, and you want to allow end users to change setup options in UI mode during installation, use the Group Policy Editor and turn on Enable User Control.

Active Directory GPO Installations

To create Groove deployment packages for MSI, you can use Microsoft Active Directory Group Object Properties (GPOs) and any MSI transforms you created for Groove. To run multiple deployments, you can create multiple transforms and/or GPOs. Generally, the same rules apply to Groove MSI deployments via GPO as to Microsoft Office deploy-ments.

For more information about creating MSI packages, see the Microsoft Web site, http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/arti-cles/Q257/7/18.ASP&NoWebContent=1.

When using Active Directory GPOs and MSI transforms to deploy Groove, keep in mind the following guidelines and recommendations:

• Specify Groove Virtual Office.msi (not setup.exe) when defining Active Directory GPOs.

• If you plan to install Groove for all users (multiple logins) on a computer, make sure to deploy the Groove MSI package to computers (not users) in the GPO. When the Groove MSI is deployed to users, the Groove installation will be available only to the user that initiated the install (with the exception of Groove File Sharing


(GFS) which is integrated with Windows Explorer and therefore will appear to all users, even when a single user install is intended).

• If using MSI transforms, make sure to apply the Groove transform (.mst file) to the GPO Modifications tab.

• When deploying the Groove MSI from a GPO in an organizational unit (OU) where legacy Install Shield Groove versions have been deployed, create the Groove package as Published, not as Assigned. If you require the Groove MSI package to be deployed as Assigned in this type of environment, create a separate OU for the Groove MSI deployment.

SMS Installations

The following sections provide guidelines for using SMS with the Groove Enterprise Installer (Groove Virtual Office.msi) to centrally Groove in an enterprise:

• SMS Packages

• Creating SMS Advertisements

SMS Packages

The table below shows fields that apply to Groove Virtual Office.msi packages in SMS. If you are using another central deployment system, use this information as a reference. As you fill in the SMS Program Properties and related fields for the Enterprise Installer, note the Enterprise Installer settings recommendations listed here:

SMS Program Properties Fields Values for Enterprise Installer

General

Command line: Setup.exe /S/ /V/qn

OR

Groove Virtual Office.msi

See “Installing Groove with Enterprise Installer” in this guide for more information about the Enterprise Installer command line.

Start in: <directory path of setup.exe or Groove Virtual Office.msi>

If you did not already specify this path in the source file field of the package definition.

Run: Normal

This value has no effect when the Enterprise Installer is in silent mode.

After running: SMS restarts computer.

This setting ensures that settings are registered correctly. See “Final Restarting of Client Devices” in the Common Administrative Tasks section of this guide, for more information about restarting.


Creating SMS Advertisements

Create an SMS advertisement to suit your installation schedule. To minimize the burden on system resources during normal operating hours, schedule the advertisement to run the installation at night or during another period of low network demand.

If you created SMS advertisements for separate deployments to different departments in your organization, and you defined them as separate programs in a package, you can then direct a notification or an advertisement to different sets of target clients.

Once you have created installation packages and advertisements, the deployment service conducts the installation as scheduled.

Activating Groove After a Centralized Installation

When the installation is complete, end users can login to their devices and activate Groove, as described in “Activating Groove” in the Running the Groove Enterprise Installer section of this guide.

Requirements

Estimated disk space: 85 MB

Estimated run time: 4 minutes

This setting is a rough estimate only, as it depends on the number of devices running the advertisement and the amount of network traffic at your site.

Environment

Run mode: Run with administrative rights.

The Groove installer requires administrative access to client devices.

Advanced All Advanced fields are optional.

SMS Program Properties Fields Values for Enterprise Installer


Groove Software Deployment Website Deployment 38

Website Deployment

If your organization has a Web site, you can build a Web package with the Enterprise Installer and locate it on your Web site, allowing centralized deployment from the site. Or, you may want to create an internal Web site from which to centrally deploy Groove to onsite users. Client devices must have access to the site.

You can build Web packages with the Enterprise Installer using utilities such as WinZip or InstallShield’s Package For the Web.

To create an internal Web site, go to the ‘Package For the Web’ page of the InstallShield Web site (www.InstallShield.com/pftw). The PTFW application is free to InstallShield customers. The application prompts you for basic install information in order to create the site. Requested information includes the following:

• Location of Enterprise Installer files

• Installation mode - silent (unattended) or attended

• Installation configuration parameters

• Registry setting updates

Once you supply the necessary information, the application generates an .exe file that you can post on your Web server, put on a file server, or send via email for users to run, down-load, and execute. The .exe file is self-extracting and does not require any additional soft-ware to be installed on client devices.

PFTW allows you the option of digitally signing your package, password protecting it, or enforcing other security policies.

Note that Web site packaging is only one example of Groove install repackaging. For information about other types of repackaging, see your Groove Networks representative.

Installing Groove Components

Groove Components is an optional application that lets you deploy and manage Groove components from a Web or file server located onsite at your enterprise. This application requires an Enterprise Management Server installed at your site. To acquire this applica-tion, contact your Groove Support representative.

The following sections provide supporting information and instructions for installing Groove Components:

• Requirements

• Installing Groove Components on a Server

• Enabling Manual Client Upgrades from Groove Components

• MIME Types in IIS version 6.0

For information about setting device policies to regulate Groove component downloads and for a list of Groove component packages and version numbers, see the Groove Man-agement Server Domain Administrator’s Guide.

Requirements

The following sections list the hardware and software required to install the Groove Com-ponents application, for use with Groove client and management server installations.

Hardware

You need the following hardware to support an onsite host for Groove Components:

System Components Specifications

Processor Intel® Pentium® III processor, 1 GHz or higher

Memory 1 GB RAM

IIS data volume (optional) 10 GB for optional Internet Information Services (IIS)

Management server Enterprise Management Server installed as described in the Groove Management Server Administrator’s Guide.

Groove Software Deployment Installing Groove Components 39

Software

You need the following software to support an onsite host for Groove Components:

Installing Groove Components on a Server

To install Groove Components on a server, follow these steps:

1. Decide where to locate component files: on a dedicated HTTP Web server or a UNC file server.

2. Make sure the server meets the “Requirements” listed above and that it will be a dedicated Groove Components server.

3. If you are installing Groove Components on a dedicated HTTP server, do the following:

a. Create a directory (such as comproot) in c:\Inetpub directory on the server.

b. Copy all the files from the top directory of the Groove Components CD to the component server root directory (c:\Inetpub\comproot, for example).

c. Create an HTTP Web site on the component server and configure its root as defined above (c:\Inetpub\comproot, for example). Or, if you are familiar with Host Headers, you can set up a virtual Web site that points to the directory where you copied the Groove Components application (such as d:\GrooveComponents).

d. If the HTTP Web site is hosted on a Windows 2003 server with IIS 6.0, configure Groove component MIME types as described below in “MIME Types in IIS version 6.0”.

e. Configure the HTTP component server as follows:

• Set access permissions for the entire component server Web site to be readable anonymously.

• Set the HTTP server to operate on the standard TCP port 80.

• Disable SSL.

f. Register the Groove HTTP component server name as a publicly resolvable Domain Name Service (DNS) name.

4. If you are installing Groove Components on a dedicated UNC server, do the following:

a. Create a directory (such as comproot) on the server’s data volume.

System Component Specifications

Groove Components server • Groove Components for latest Groove Workspace version

• Microsoft® Windows® 2000 Server or Advanced Server, with Service Pack 2 (or later), or Windows Server 2003

Optional IIS server • For Windows 2000 Server - IIS version 5.0 with Service Pack 2 (or later) for

• For Windows Server 2003 - IIS version 6.0

If using a file server: Any compatible UNC file server (such as Windows 2003 Server or Windows 2000 Server).


b. Copy all files from the top directory of the Groove Components CD into the component server root directory (x:\comproot, for example).

c. Create a UNC share for the directory (comproot) on the component server.

d. Set access permissions for the entire UNC shared component server to be accessible by everyone with no authentication prompts.

e. Ensure that the component server UNC share host is registered in the Windows domain and publicly resolvable.

5. Go to the management server and set the management domain Device Policy that controls where Groove users (clients) can install components from as follows:

• If you installed Groove Components on a Web server, set the client Device Policy Install components from option to HTTP server, and enter the address of a specific HTTP server.

• If you installed Groove Components on a file server, set the client Device policy to UNC server, and enter the full path name of the component directory on a specific Universal Network Connection.

See the Groove Management Server Domain Administrator’s Guide for more information about setting this client Device Policy on the management server.

6. If you want to allow automatic component upgrades from Groove Components, from the management server, set the management domain device policy to allow automatic component upgrades.

Enabling Manual Client Upgrades from Groove Components

With an onsite server hosting Groove Components, you can create a Web site page that allows users to manually upgrade Groove, which requires the UpgradeGroove.GRV com-ponent. The page might contain hyper links such as the following:

For a Web site server:

HTTP:\\<servername>\Groove\Components\Injectables\UpgradeGroove.GRV

For a UNC file server:

\\<servername>\InstallDirectory\Groove\Components\Injectables\UpgradeGroove.GRV

MIME Types in IIS version 6.0

If installing Groove Components onto Windows 2003 with IIS 6.0, additional MIME types must be defined in addition to the default MIME types. These specific MIME types allow the various file types in the Component Server to download properly.

To add the necessary MIME types on a Windows 2003 Server-based Groove Components server, follow these steps:

1. For the component server Web site, open the server properties and from the HTTP Headers tab, select MIME Types.


2. Add the following MIME Types (in addition to the default global MIME Types already predefined by the IIS 6.0 server):

Extension MIME Type

cer application/octet-stream

.config text/xml

.cst text/xml

.gcd application/vnd.groove-componentdownload

.ghf application/vnd.groove-help

.grp text/xml

.grv application/vnd.groove-injector

.gsa application/vnd.groove-groove-space-archive

.gsl text/xml

.gws text/xm

.lic ext/plain

.log text/plain

.msp application/octet-stream

osd text/xml

.pdb application/octet-stream

.rbd text/xml

.tlb application/octet-stream

.tpl text/xm

.tst text/xml

.vcg application/vnd.groove-vcard

.wsdl text/xml

.xsd text/xm


Troubleshooting

This section describes how to resolve problems you may encounter while managing your domain. Problem descriptions are grouped into the following categories:

• Installation Problems

• Groove User Activation Problems

• Run Time Problems

Installation Problems

This section discusses problems that may arise during Groove installation in an enterprise.

Problem

The Groove virtual office software is not fully installed on a user device (the user cannot see or cannot activate Groove).

Solution

The client device probably requires a reboot, typically at the Administrator level. The installation requires the following non-Groove components to be installed and operational on the PC at the versions specified:

• Microsoft Windows Script version 5.5 (or later)

• vbscript.dll version 5.5.0.6330

• jscript.dll version 5.5.0.6330

• Microsoft C Runtime Library version 6.0 (or later)

• msvcrt.dll version 6.0.8797.0

In the event that these files are not present on a client device, the Groove installer will install/upgrade the following:

• Microsoft Windows Script version 5.6

• Microsoft C Runtime Library 6.0

When the Groove installer must install any of the above components, a client system reboot as Administrator is usually necessary. Reboot the client device as Administrator (or you can instruct the user to reboot first and, if that fails, try again with an Administrator login).

Groove Software Deployment Troubleshooting 43

Groove User Activation Problems

This section discusses Groove user activation problems and possible solutions.

Problem

Users are unable to activate the Groove virtual office software after an enterprise installa-tion.

Solution

Consider the following causes and responses:

• First, check your proxy and firewall configurations to make sure that they allow communications between Groove clients and management servers. HTTP port 80 must be open on the management server to support Groove-management server communications.

• Check a user's computer for the presence a corrupt proxy configuration file that may remain from an old Netscape installation or a valid but unused proxy configuration in Netscape that is not currently functional in your network. Groove may still try to use such a file and fail. Remove the damaged or unused file and instruct the user to retry the activation.

• If an outage occurred on the Internet causing a communications break between the management server you use and Groove clients, clients will not be able to contact the management server to download Groove licenses and policies, and will not succeed in activating Groove (management domain identities). Instruct users to retry the installation once the problem has been corrected.

• If a user device is located far from the management server, requiring multiple routing hops to reach the management server, a traffic bottle-neck may be impeding communications, causing the request contact the management server to time-out. Instruct the user to retry the installation later, preferably during a time of low traffic.

Problem

A user device displays a message indicating that it cannot access the management server.

Solution

If the user is managed, but tries to activate a Groove license ordered via E-commerce (or if they are unmanaged and try to activate a managed Groove license), their device is contact-ing the wrong management server and activation will fail. Enter the correct activation server name in the Activate Products window on the Groove client, as described in the fol-lowing table:

License Type Activation (management) Server

For groove.net E-commerce licenses

Enter activate.groove.net


Problem

When a user tries to start up Groove, a message appears stating that the product activation key is revoked.

Solution

An administrator has revoked the product package containing this license key from the domain on the management server. Re-instate the product package to the domain or instruct the user to stop using it. Issue a different product key from management server, if appropriate.

Problem

A user tries to activate an upgrade from one Groove version to another and fails.

Solution

The user probably tried the upgrade without having activated the previous version of that software. For example, a user tried to activate a Professional Edition upgrade without hav-ing activated Standard Edition first. In upgrades, the license activates only the subset of features in the higher-level edition. If those features depend on features in the lower-level edition, the newly activated features will either be unavailable or will not function. For example the Professional Edition's features depend on the Standard Edition user interface. An upgrade license activates the Professional features, but the user interface is not avail-able for the user to take advantage of those features.

Provide the user with the activation key for the previous Groove version, in addition to the key for the upgrade. If the user is a managed domain member, Groove licenses for that domain are available on the management server.

If an upgrade continues to fail, contact Groove Networks Customer Support.

Problem

A user tries to use a managed activation key and fails.

Solution

Try the following:

For Groove Networks-hosted management services domains

Enter gms.groove.net

For licenses from other management servers

See your management server administrator to get the required management server URL.

License Type Activation (management) Server


• First, check whether the user is trying to re-use the same activation key. If so, send them another activation key, as activation keys cannot be re-used.

• Check that the version of Groove for which the key is intended is installed and present on the users machine. If not, install the correct Groove version for the key or send the key that corresponds with the resident Groove version to the user. Then instruct the user to retry the activation.

• Check with the management domain administrator to make sure that the key has not been deleted from the domain since it was sent to the user. If the key has been deleted, request that another key be sent to the user, corresponding with the Groove version installed on the user’s device.

Problem

A managed user encounters access problems while trying to activate the Groove virtual office software.

Solution

Check the permissions that control read/write access to the Groove System Data stores that reside in the Windows Program Files directory. Normally, the Enterprise Installer sets these permissions on client devices as necessary. However, centralized deployment soft-ware, such as an Active Directory GPO or SMS, may reverse these settings. If this occurs, manually reset them.

Run Time Problems

This section discusses end-user problems that can arise while running a new installation of Groove.

Problem

Groove Forms, Groove-SharePoint Team Services integration, and Groove WebServices features do not operate properly.

Solution

Groove Forms, SharePoint integration, and Web Services require the following applica-tion for proper functioning:

Microsoft XML Parser (MSXML) version 3.0 SP2 (or later)

Because the Groove Installation does not itself require this application, the Groove installer does not detect or install MSXML V3.0. Install this Microsoft application on the client device, and reboot Groove, if the client requires Groove Forms, SharePoint integra-tion, or Web Services.

Problem


A user cannot properly view Visio objects from Groove and subsequently, or, once able to view Visio objects from Groove, cannot properly view them from the Microsoft Visio application.

Solution

The Groove Installer does not automatically install or update the Microsoft Visio viewer, required to view Visio objects from Groove. Trying to view a Visio object in Groove with-out the viewer prompts users to install the viewer from the Microsoft Web site. Once this is accomplished, Visio objects should appear correctly in Groove, however, objects in the Visio application display incorrectly because the viewer, instead of the native Visio appli-cation, is used. This incompatibility is unavoidable due to current Visio behavior and functionality. See www.microsoft.com for more information about the Visio viewer.

Problem

A user cannot access unmanaged data after restarting or activating Groove.

Solution

This condition typically results when a device running Groove becomes managed and the device policy for the management domain with which the device is registered allows man-aged identities only, preventing access to unmanaged data. Reversing the device policy for the domain or group of which the client is a member should permit re-access to unman-aged data. To avoid this problem in the future, be sure to warn users before registering devices in a domain (or installing Groove on newly registered devices), to backup existing unmanaged accounts so that they can restore them on another unmanaged device (and be re-invited to their spaces) if they wish.


Common Administrative Tasks

This section provides basic information about accomplishing common administrative tasks involved in an enterprise-wide Groove deployment. These tasks include:

• Logging into Client Devices as Administrator

• Installing Groove in Unattended Mode

• Changing the Groove Installation Directory

• Centrally Deploying Device Registry Files

• Making a Device Managed Without Losing Previous Data

• Converting an Unmanaged Identity to a Managed Identity

• Centrally Executing .GRV Files

• Final Restarting of Client Devices

• Updating and Overinstalling Groove

Logging into Client Devices as Administrator

Typically, you do not need to log into client devices as Administrator in order to install Groove via Active Directory, SMS, or other centralized distribution system. Active Direc-tory (and SMS) handle all the permissions required to install Groove and sets the appropri-ate permissions on the System Data directories. However, if you run the Enterprise Installer to install Groove directly on individual client devices, you must log in to each device as Administrator (or comparable power user).

Installing Groove in Unattended Mode

You can install Groove in unattended (quiet or silent) mode Groove will be installed on user computers via a central distribution system such as Active Directory or SMS. You can specify quiet installation in an MSI transform file or a command line, as described in “Installing Groove with Enterprise Installer” in this guides.

Note that the Active Directory or SMS package must be run as an Administrator so that Groove is installed correctly.

Changing the Groove Installation Directory

You can change Groove installation directories via an MSI transform file or a command line as described in “Customizing Groove Installation Using MSI Transforms” or “Cus-

Groove Software Deployment Common Administrative Tasks 48

tomizing Groove Installation from the Command Line” earlier in this guide.

Centrally Deploying Device Registry Files

You can deploy the registry key (contained in a .reg file) using an MSI transform, as described in “Setting Device Management and Registry Updates via MSI Transforms” earlier in this guide.

For detailed information about managing devices, refer to the Groove Management Server Administrator's Guide.

Making a Device Managed Without Losing Previous Data

You can make a device managed without risking loss of previous unmanaged Groove accounts by taking proper precautions. Loss of unmanaged account data is likely if you register a user device in a management domain with a device policy that allows only man-aged identities because the device immediately becomes managed upon Groove activation or reboot; at that point, device users can no longer access any unmanaged identity or account data on that device. To avoid this condition, before registering devices in a domain (or installing Groove on newly registered devices), do one of the following:

• Warn users to backup existing unmanaged accounts so that they can restore them on another unmanaged device (and be re-invited to their spaces) if they wish.

• Check that the device policy that allows only managed identities has not been inadvertently enabled on the management server domain where that device is registered.

Converting an Unmanaged Identity to a Managed Identity

You can convert a Groove user’s unmanaged identity to a managed identity by first send-ing the user a Groove activation key and managed identity from the Groove management server. The user should then do the following:

1. Start up Groove virtual office software.

2. Choose the Activate Product item from the Groove Help menu and enter the activation key provided.

3. Accept the default option to convert the unmanaged account to a managed account.

Centrally Executing .GRV Files

You can execute .GRV files via SMS. In the Program section of SMS package definition, specify the full path and the file association that Groove uses for .GRV files. For example the program name might be:

C:\Program Files\Groove Networks\Groove\Bin\Groove.exe /grv: \\servername\dist-dir\component_name.grv

Make sure to specify the exact server and share (distribution directory) names that SMS has created. SMS creates each package with a unique directory on the distribution server


and the SMS server name and associated distribution directory must be exact to ensure successful deployment of the .grv file.

Final Restarting of Client Devices

Most Windows operating systems do not require a restart after Groove installation if they are up to date with the current Internet Explorer version and service patches. If you are not sure whether client systems are up to date, set the MSI notification (or SMS advertise-ment) to restart the computer upon completion of the installation. End users will receive an alert indicating that the computer must be restarted.

Note that in some cases, such as after installing or upgrading Windows Scripting Host installation or upgrade, the restart requires logging into the client device as Administrator in order to complete installation successfully.

Updating and Overinstalling Groove

You can update or overinstall Groove virtual office software without destroying existing Groove identities, using the upgrade method (described in “Updating Groove” earlier in this guide). The MSI-based Enterpise Installer will uninstall any previous Groove versions (such 2.5) before installing new files.

Note: The upgrade process applies only to Groove version 2.5j or later.

However, if the update or upgrade involves a change from an unmanaged to a managed device and/or the addition of a managed identity, take the following precautions, to avoid loss of a user’s previously unmanaged account:

• If you register a user device in a management domain with a device policy that allows managed identities only, the device immediately becomes managed upon Groove reboot or activation, and device users can no longer access any unmanaged identity or account data on that device. Therefore, warn users to backup existing unmanaged accounts if they wish to restore them on another unmanaged device (and be re-invited to their spaces).

• If you do not register user devices in a management domain, you can over-install any previously existing versions of Groove without jeopardizing the user’s unmanaged account data. However, when activating a new managed identity, users with existing accounts should be instructed to accept a new account, rather than converting an existing account, in order to keep unmanaged data intact.


Glossary

This document defines the main administrative terms used in describing Groove Manage-ment Services.

Component A feature or tool created by Groove Networks or a third party for use in the Groove application.

Contact Properties A virtual business card that contains contact information for each user identity. The contact properties are created from the information assembled to define the identity.

Default identity The user identity assumed for all subsequent Groove spaces (those cre-ated after the default is set). When a user installs the product activation key (sent to them by their domain administrator) into Groove, that identity becomes the default identity for Groove spaces that the user creates from then on. Users can change their default identity at any time by setting another identity as the default.

Device A device is a client (user) computer that is running Groove. Devices are automat-ically associated with users during the initial Groove installation. Administrators can manage these devices by applying a registry setting (a pointer to the domain) to the devices. This makes the devices part of a management domain. Once devices are regis-tered with a domain, administrators can manage Groove use on these devices by setting device policies, for example, to control password creation or regulate Groove component downloads on these devices.

DMZ In the context of computer networks, a DMZ (demilitarized zone) is an area on a corporate network that houses corporate servers that require limited access to external communications. A combination of firewalls, proxy devices, and other related equipment determine the extent of external network access.

Domain See Management Domain.

Domain member A Groove user who has installed the activation key with its associated identity information sent by the Groove administrator. This creates a managed identity for the user, giving the user domain membership and placing the user under the domain administrator’s management. Domain members gain access to domain licenses, subject to domain policies, and are directed to domain relay servers (if registered on the management server).

Enterprise Management Server (EMS) A Groove Networks Web application that pro-vides comprehensive services for deploying and managing Groove in an enterprise. The application resides on an IIS server installed on a corporate network and is supported by a

Groove Software Deployment Glossary 51

SQL server. With an onsite management server, server administrators can install, config-ure, and monitor the server, as well as manage Groove users and devices, distribute prod-uct licenses, set device and user policies, deploy managed relay servers, and monitor Groove usage.

Enterprise Relay Server (ERS) A Groove Networks server-based application, that facil-itates data transmission among Groove users. This server, hosted by Groove Networks or at a company site, provides various services that support Groove, including message han-dling for offline devices, device presence detection, firewall transparency, and bandwidth optimization,.

Groove Hosted Management Services - Groove management services hosted by servers at Groove Networks. These services allow administrators to manage Groove users and devices, distribute Groove product licenses, set policies to ensure the security of its resources, deploy any onsite relay servers, and monitor Groove usage.

Groove Hosted Relay Services - Groove relay services hosted by servers at Groove Net-works. These services allow administrators to manage the distribution of relay services to Groove users.

Groove Installer Service Groove service that enables Groove component updates on locked-down desktops.

Groove space See Workspace.

Group From a management server context, a sub-category of a domain.

Identity See User Identity.

IIS - Microsoft Internet Information Services, installed on a Windows Server machine.

License In the context of this guide, the formal permission to access a specific Groove tool set, tool, or tool component. Licenses are purchased by a company for a management domain as part of Groove product packages. Groove users gain access to product licenses when they join a domain. In addition, domain administrators can issue individual product packages, via an activation key, to Groove users who have not received domain activation keys from a domain administrator and who, therefore, are not management domain mem-bers. The management server also lets administrators revoke domain membership along with access to all domain products, or to revoke individual products from specific non-members.

Management domain A management domain (in the context of this guide) is a collec-tion of Groove products containing licenses, users and devices that administrators manage in a centralized manner. Associated with domain users and devices are identity and device policies, and any managed relay servers assigned to their domain. A company may have one or more Groove management domains. For example, a domain can be defined for an entire company or for a division within the company. Groove users acquire domain mem-bership by installing the product activation key, with an associated identity sent to them by their domain administrator. Devices can be included in a domain by applying a Groove-supplied registry setting to them according a company’s established procedures.

Member See Domain Member.


NewServiceInstall An Enterprise Installer command line flag that sets the Groove Installer Service to start automatically.

Policy A rule applied to all managed identities in a domain or group, or to all managed devices in a domain or group. Preventing publication of managed identity contact infor-mation is an example of an identity policy. Restricting downloads of Groove components on managed devices to a specific source (such as a specified onsite server) is an example of a device policy.

Public relay server Groove Networks-hosted relay server employed when managed onsite Enterprise Relay Servers or Groove Hosted Relay Services are not in use.

Quiet mode Unattended (silent) installation of software application on client device. Silent installations do not require end-user input. Including the -s switch in the Enterprise Installer command line specifies silent mode installation.

Relay server See Enterprise Relay Server, Groove Hosted Relay Services, or Public relay server.

Registry file A .reg file that contains information stored in the Windows Registry.

Silent mode Unattended (quiet) installation of software application on client device. Silent installations do not require end-user input. Including the -s switch in the Enterprise Installer command line specifies silent mode installation.

Tool A Groove program or application that Groove space members use to interact. Each member of a Groove space has access to the same tools (such as chat, calendar, and sketchpad tools) and can use them to affect Groove space data.

Update In the context of Groove, migrating to the next minor version of Groove, from 2.x to 2.y, for example.

Upgrade In the context of Groove, migrating to the next major version of Groove (from 2.0 to 3.0, for example), or to the next edition (from Standard to Professional, for exam-ple).

UI mode User-attended installation of software application on client device. Silent instal-lations depends on end-user input. This is the default mode of Groove installation.

User account A file, stored on a user’s computer, that maintains usage data, including information about the user’s identities, secret encryption keys, devices (computers) on which the user runs Groove, Groove spaces, and contacts.

User identity A persona in Groove virtual office software. Groove users create an initial default identity when they install Groove. A user can have one or more identities in a sin-gle account and selects one to be the default.

Workspace A user-created space, accessible via the Groove transceiver, that enables col-laboration among small groups of users.


Appendix A. Registry Changes for Mail/Messaging Integration

In support of Groove integration with other applications, the Groove installer modifies Lotus Notes, Microsoft Outlook, and MSN messenger, depending on which is installed on the PC (at the time of installation). The following sections summarize these changes:

• For Lotus Notes R5

• For Microsoft Outlook 2000 (or later, including XP)

• For MSN Messenger

For Lotus Notes R5

The Groove installer adds the following line to the notes.ini file:

AddinMenus=C:\PROGRA~1\Groove\GRC3C6~1.DLL

The short Windows file path and name above may vary.

For Microsoft Outlook 2000 (or later, including XP)

The Groove installer adds the following Groove-specific integration settings to the Out-look AddIn branch of the Windows Registry:

• FriendlyName = GrooveExport

• Description = GrooveExport

• LoadBehavior = dword:00000003

• CommandLineSafe = dword:00000000

If Groove is installed for the current user only, registry settings reside in:

HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Groove.Out-lookAddIn

If Groove is installed for the computer (all users on the computer), registry settings reside in:

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Outlook\Addins\Groove.Out-lookAddIn

Groove Software Deployment Appendix A. Registry Changes for Mail/Messaging Integration 54

For MSN Messenger

The Groove installer adds the following Groove-specific integration settings to the Mes-sengerService Apps branch of the Windows Registry:

• Name = Groove

• Path = C:\\Program Files\\Groove\\Groove.exe /MSGR

• URL = http://www.groove.net/go/invite

If Groove installed for the current user only, registry settings reside in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\MessengerService\SessionMan-ager\Apps\{E5D30DCC-A3A7-4241-92BF-99EE9977281E}

If Groove is installed for the computer (all users on the computer), registry settings reside in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MessengerService\SessionMan-ager\Apps\{E5D30DCC-A3A7-4241-92BF-99EE9977281E}

Groove Software Deployment Appendix A. Registry Changes for Mail/Messaging Integration 55

Appendix B. Managed Install Permissions

The following tables summarize the default directories used to store Groove program and data directories, and the required permissions.

Program Files

Windows NT 4.0 Windows 2000 Windows XP

Groove directory (Contains Groove program and related files.)

Default Path: C:\Program Files\Groove Networks\Groove



Security Permissions:

Everyone (group)

Add & Read (RWX) (RX)

Users (group)

Read & Execute

List Folder Contents

Read

Users (group)

Read & Execute


Read

Growth: Stable and should not grow significantly. Any growth will be related to platform upgrades and tool/component injections.

Groove/Data directory (Contains Groove data that is typically shared by with all Groove users of the PC, including certificates, help, skins, and tool components.)

Default Path: C:\Program Files\Groove Networks\Groove\Data

C:\Program Files\Groove Networks\Groove\Data

C:\Program Files\Groove Networks\Groove\Data


Everyone (group)

Change (RWXD) (RWXD)

Users (group)

Modify

Read & Execute


Read

Write

Users (group)

Modify

Read & Execute


Read

Write

Growth: Expect growth to be on the order of a few to tens of mega bytes.

Groove Software Deployment Appendix B. Managed Install Permissions 56

User Data Files

Windows NT 4.0 Windows 2000 Windows XP

User account and device files, and related files (Includes Groove workspaces (.tsp files) and Groove space logs (.log files).)

Default Path: C:\WINNT\Profiles\[username]\Application Data\Local Settings\Groove Networks\Groove

C:\Documents and Settings\[username]Local Settings\Application Data\Groove Networks\Groove

C:\Documents and Settings\[username]\Local Settings\Application Data\Groove Networks\Groove


[username] (for logged on user)

Full Control (All) (All)


Full Control

Modify

Read & Execute


Read

Write


Full Control

Modify

Read & Execute


Read

Write

Growth: Expect growth to be on the order of hundreds of mega bytes (to giga bytes for power users).

System Data Windows NT 4.0 Windows 2000 Professional

Windows XP

Groove system data files (Typically shared by all Groove users of the PC, including the binary file store, system temp files used for installing components and other diagnostic outputs. This folder must always be accessible by all Groove users that use their account on the PC since it contains each user’s files and attachments from their respective Groove spaces.)

Default Path: C:\Program Files\Groove Networks\Groove\Data\System





Everyone (group)

Change (RWXD) (RWXD)

Users (group)

Modify

Read & Execute


Read

Write

Everyone (group)

Full Control

Modify

Read & Execute


Read

Write

Growth: Expect growth to be on the order of hundreds of mega bytes (to giga bytes for power users).


Appendix C. Controlling Local Virus Scanning and Filtering

Groove software provides virus scanning and filtering capabilities for imported and exported Groove files. Groove administrators can control these capabilities via Windows registry settings. The virus scanning capability involves a single registry key to enable scanning via an existing registered virus scan provider. The virus filtering capability involves registry keys that specify filtering by file size and type for all Groove instant messages, invitations, and Groove Networks-supplied tools.

The following table describes the Windows registry settings that control virus scanning and filtering of Groove files:

Registry Key* Value:

{product_registry_key}\FilterEnableScan (REG_SZ) 1 (or other non-zero value) to enable use of registered virus scanning software installed on site.

If this value is 0 or not set, the anti-virus code does not attempt to find or use a registered virus scan provider.

{product_registry_key}\FilterFileMaxSize (REG_SZ) Maximum size in bytes of files that can be attached or added to Groove. No conversions (such as 1024Kb = 1 Megabyte) are made.**

If this value is 0 or not set, files of any size can be applied to Groove.

For more information about file filtering, see the notes below.

{product_registry_key}\FilterFileTypes (REG_SZ) Comma-separated list of file types that cannot be attached or added to Groove. Wildcards are acceptable.**

If this value is not set, any file types are allowed.

Examples: *.ocx, Foo???.*

Groove Software Deployment Appendix C. Controlling Local Virus Scanning and Filtering 59

Note: If FilterFileMaxSize is set to 40,000, a 40,000-byte file can be attached but 40,001-byte file is not allowed.

Note: If FilterFileTypes is set to *.mp3, *.dll, *.ocx, q*.*, *.ra?, the following imported files are handled as shown:

Note: If FilterAllowFileTypes is set to *.mp3, *.dll, *.ocx, q*.*, *.ra? the behavior described for FilterFileTypes applies, only in reverse.

Note: To avoid conflicting file parameters between allowable vs filtered file types, set allowable file types to *.doc, *.xls and filtered (non-permissible) file types to *.doc and *.x??. This is resolved according to these basic rules:

1. Allowable types always trump filtered types. If allowable file types are configured, only allowable file types can be added to Groove.

2. Filtered types are only checked if the allowable list is empty or not specified.

{product_registry_key}\FilterAllowFileTypes (REG_SZ)

Comma-separated list of file types that can be attached or added to Groove. Wildcards are accepable.**

If this value is not set, all files types are allowable.**

Examples: *.ocx, Foo???.*

*{product_registry_key} = HKEY_LOCAL_MACHINE\SOFTWARE\Groove Networks, Inc.\Groove

** See Notes below for addition examples and information.

Imported File Name Action

Beatles.mp3 Rejected because of the mp3 extension (*.mp3 rule)

Beatles.wma Accepted. WMA files are not filtered

Kernel32.dll Rejected because of the dll extension (*.dll rule)

AutoCad.exe Accepted. EXE files are not filtered

Quicken.exe Rejected because files that begin with the letter 'Q' are filtered (q*.* rule)

Stones.ram Rejected because files with extensions beginning with 'RA' are filtered (*.ra? rule)

Settings.ras Rejected because files with extensions beginning with 'RA' are filtered (*.ra? rule)

Registry Key* Value:


Examples:

Filename = Foo.jpg

Allowable = *.*

Filtered = *.jpg

Result: Allowable always takes precedence. Foo.jpg matches patterns against *.* so the file is allowed.

Filename = Foo.jpg

Allowable = *.doc

Filtered =

Result: Not allowed. Foo.jpg fails to match patterns against *.doc so the file is not allowed.

Filename = Foo.jpg

Allowable =

Filtered = *.jpg,*.bmp

Result: Not allowed. Allowable file types are not specified. Foo.jpg does match patterns against *.jpg so the file is not allowed.

Filename = Foo.jpg

Allowable =

Filtered = *.exe,*.dll,*.zip

Result: The file is allowed. Allowable types are not specified and the file does not match patterns against the filtered types.


End User License Agreement

END USER LICENSE AGREEMENT (for Groove Client Software)

Thank you for licensing Groove software. Please read this End User License Agreement ("EULA") carefully and be sure you understand it. This EULA is a legal agreement between you (either an individual or a single entity) and Groove Networks, Inc., a Dela-ware corporation ("Groove Networks"). You must review and either accept or reject the terms of this EULA before installing or using the Software. Clicking the "I ACCEPT" button below is just like signing a contract written on paper. By clicking the "I ACCEPT" button or installing or using the software, you acknowledge that you have read all of the terms and conditions of this EULA, understand them, and agree to be legally bound by them.

If you have entered into a separate agreement with Groove Networks permitting you to use the Software, that agreement, rather than this EULA, will govern your use of the Software. If all or some portion of the Software has been licensed by another party for your use (e.g., your employer or an individual or company with which you conduct business), your right to use that Software and to obtain any related Services is subject to the terms and condi-tions of the agreement(s) between Groove Networks and the other party, whether the other party has agreed to the terms of this EULA or to the terms of a separate, written agree-ment. If the Software you are installing is beta or other pre-release Software, however, the terms of this EULA will apply, regardless of whether you or the party sponsoring your use of Software has a separate agreement with Groove Networks. Even if your use of the Software is sponsored by another party, the terms of our Groove Software Privacy State-ment and our Acceptable Use Policy, both of which are accessible on our web site at http://www.groove.net (and which are incorporated into this EULA by this reference), apply to you. You are agreeing to the terms and conditions of these policies by clicking the "I ACCEPT" button below, and we encourage you to review them before you do so. By clicking "I ACCEPT," you also are consenting to the Software's establishment of peer-to-peer connections as described below in Section 9.

If you are installing trial, evaluation use, or beta Software, please note that special terms and conditions apply, as described below in Sections 4, 5 and 6.

Groove Software Deployment End User License Agreement 62

If you use the Software on a Computer that you share with other End Users, and if another End User installs a new version of the Software and accepts a new version of this EULA, you agree to be bound by the new version of the EULA. Please refer to the Help menu in the Software for the most current version of this EULA.

1. DEFINITIONS. The following capitalized terms used in this EULA have the meanings indicated:

(a) "Account" means a set of Groove shared spaces and identities accessible by a single login to the Software.

(b) "Computer" means a personal computer or personal computing device.

(c) "Delivery Date" means (i) in the case of Software that utilizes an activation key, the date on which Groove Networks sends or otherwise makes available to you the activation key(s) for the Software or a method for creating them; and (ii) in the case of Software that does not utilize an activation key, the date on which Groove Networks sends you a CD, diskette, or a digital file containing the Software.

(d) "Documentation" means any online help text and/or manuals provided with the Soft-ware.

(e) "End User" means you and any human being whose use of the Software you sponsor.

(f) "Hosted Services" means any server-based services provided by Groove Networks to support use of Software.

(g) "Server" means a computer server owned, leased or otherwise controlled by you or a third party on which a licensed copy of a Groove Networks' server-based software product is installed.

(h) "Services" means Hosted Services, software maintenance services, support services (including deployment support services), and any other services Groove Networks may provide you in connection with your use of the Software.


(i) "Software" means the Groove software accompanying this EULA, in object code form, together with any of the following that may form a part of it or subsequently be provided by Groove Networks for use with it: (A) tools, toolsets, "skins" and other software appli-cations or components; (B) graphical, video or audio content; (C) Documentation; and (D) any Updates and Upgrades.

(j) "Trademark Usage Policy" means the document accessible on the Web Site that sets forth certain terms and conditions related to use of Groove Networks' trademarks, as it may be amended by Groove Networks from time to time.

(k) "Updates" means bug fixes, patches, or other revisions to or modifications of Software that Groove Networks provides to you or any End User, including those it makes generally available to customers that subscribe to its software maintenance services. An Update typically is identified by a change in a number and/or letter to the right of the first decimal point in a product's version number. Updates do not include Upgrades.

(l) "Upgrade" means a major release of Software, as determined by Groove Networks in its sole discretion. An Upgrade typically is identified by a new product name or a new number to the left of the first decimal point in the version number of an existing product name.

(m) "Web Site" means Groove Networks' web site located at http://www.groove.net.

2. OWNERSHIP. The Software is licensed, not sold. All Software (including any changes you may request or suggest) is the property of Groove Networks and/or its licen-sors. Title to each copy of the Software and all related intellectual property rights embod-ied in or represented by the Software will remain with Groove Networks and/or its licensors at all times, as will all other rights not explicitly granted to you under this EULA.

3. LICENSE GRANT. Groove Networks grants you a perpetual, nonexclusive, world-wide, limited license to install and use the Software solely in object code form, provided you comply with all the terms and conditions of this EULA:

(a) Software. You may use the Software in up to one Account on up to five (5) Computers regularly and primarily used by you. If you have licensed multiple copies of the Software, then, for each copy of the Software you have licensed, you may permit one End User to install and use the Software in up to one Account on up to five (5) Computers regularly and primarily used by that End User. You and any End User you validly permit to use the Software may use it via its user interface, its application program interface, or its network


protocol interface. You hereby accept responsibility for each End User's use of the Soft-ware and Services and their compliance with the terms of this EULA. If the Software you are installing is preview or trial Software, evaluation use Software, or beta Software, your rights are limited as described below in Section 4, 5 or 6. You may make one copy of the Software solely for backup or archival purposes.

(b) Hosted Services. Your use of Hosted Services is subject to the terms, conditions and limitations pertaining to the service level, if any, to which you have subscribed, as described in a separate agreement or a formal service offering description posted on the Web Site.

(c) Third-Party Access to Software Functionality. You may permit any number of indi-vidual users to access the Software's functionality directly or indirectly via its application program interface or network protocol interface, provided that each user who accesses the Software's functionality in either manner must possess current and valid license rights to a copy of the Software. This right does not apply to trial or preview Software.

(d) U.S. Government End Users. The Software is a "commercial item" as defined at 48 C.F.R. 2.101, consisting of "commercial computer software" and "commercial computer software documentation." Notwithstanding anything to the contrary in this EULA, the U.S. Government sometimes makes certain minimum rights of use, reproduction, and dis-closure a condition of its purchase or acquisition of commercial software. Accordingly:

(i) GSA Supply Schedule Acquisitions. For government purchases or acquisitions through a GSA Supply Schedule contract, use, reproduction, and disclosure of the Soft-ware are subject to restrictions set forth (in March 2002) in 8 of GSA's "Terms and Con-ditions Applicable to . . . [SINs] 132-32 . . ., 132-33 . . . and 132-34 . . .." Note, however, that any modification or combination of the Software under those rights will entirely void the warranty per Section 10(a) of this EULA.

(ii) FAR Acquisitions. For government purchases or acquisitions under the authority of Federal Acquisition Regulation ("FAR") Part 12, the rights of use, reproduction, and dis-closure are only as stated in Sections 3 and 7 of this EULA.

(iii) DOD Acquisitions. For government purchases or acquisitions by the Department of Defense, the rights of use, reproduction, and disclosure are only as stated in Section 3 and 7 of this EULA, per DFARS 227.7202-3(a).

(iv) RESTRICTED RIGHTS NOTICE (JUN 1987). For all other government purchases


or acquisitions (that is, under authority other than a GSA Supply Schedule contract, FAR Part 12, or the DFARS), the Software is submitted with restricted rights under FAR 52.227-14 Alt. III. It may not be used, reproduced, or disclosed by the government except as provided in paragraph (b) of FAR 52.227-14 Alt. III or as otherwise expressly stated in Sections 3 and 7 of this EULA. Note, however, that any modification, adaptation, or com-bination of the Software under those rights will entirely void the warranty per Section 10(a) of this EULA.

4. TRIAL SOFTWARE. If the Software is marked "preview" or "trial" (or a similar des-ignation), then your rights are limited as described in this section. If you use the Software primarily for personal purposes (whether at home, at your office or elsewhere), you may use the Software (and any Services Groove Networks chooses to provide you) in a manner consistent with the terms of this EULA until such time as you breach this EULA or Groove Networks elects to terminate your use of the Software and/or Services, which it may do without notice at any time. If you use the Software primarily for commercial pur-poses (whether at home, at your office or elsewhere), or if you use the Software for per-sonal or commercial purposes in conjunction with third party software or a third party service that utilizes the Software's application program interfaces or network protocol interfaces (excluding any software or service that the third party makes generally available without charge and without receiving payment from another party for or in connection with the distribution or provision of the software or service), you may use the Software (and any Services Groove Networks chooses to provide you) in a manner consistent with the terms of this EULA until the earlier of 60 days from the Delivery Date, your breach of this EULA, or such time as Groove Networks elects to terminate your use of the Software and/or Services, which it may do without notice at any time. In either case, in light of the fact that trial Software is provided to you free of charge, Groove Networks disclaims the limited warranty set forth below in Section 10, and neither Groove Networks nor any Released Party will be liable for direct damages related to trial Software, as explained more fully in Section 11(b). If you use trial Software behind a firewall, your use will be deemed to be primarily for commercial purposes. Trial Software may contain a mecha-nism that will automatically disable use of the Software, alter its functionality, and/or notify you of term limits after a predetermined period of time.

5. EVALUATION SOFTWARE. If Groove Networks provides Software to you for eval-uation use, then your rights are limited as described in this section. You may use the Soft-ware (and any Services Groove Networks chooses to provide you in connection with it) in a manner consistent with the terms of this EULA solely for evaluation purposes for 90 days from the Delivery Date, or for such other period as may be indicated in writing by Groove Networks at or after the time of delivery. In light of the fact that evaluation Soft-ware is provided to you free of charge, Groove Networks disclaims the limited warranty set forth below in Section 10, and neither Groove Networks nor any Released Party will be liable for direct damages related to evaluation Software, as explained more fully in Sec-tion 11(b). Evaluation copies of Software may include a "time-out" mechanism that will automatically downgrade the Software to trial-level Software or disable use of the Soft-ware and prevent access to Services at the end of the evaluation period.


6. BETA SOFTWARE.

(a) Use. If the Software is designated as pre-release or beta software, then you may use it (and any Services Groove Networks chooses to provide you in connection with it) in a manner consistent with the terms of this EULA solely to test the product internally, test the compatibility of your application or other product(s) that operate in conjunction with the Software, and to evaluate the Software for the purpose of providing Feedback regard-ing it to Groove Networks. You may use the Software until the earlier of (i) 120 days from the Delivery Date, (ii) the date of the commercial release of the non-beta version of the Software, or (iii) 10 days after the date on which you or we send written notice to the other terminating your right to use the beta Software, which either of us may do at any time. You may not use the Software in a live operating environment where it may be relied upon to perform in the same manner as a commercially released product or with data that has not been sufficiently backed up. You may not use the Software for bench-mark or performance testing.

(b) Acknowledgement and Additional Liability Limitation and Warranty Disclaimer. You acknowledge that all Software designated as pre-release or beta Software may contain bugs, may not operate properly or perform all intended functions, may interfere with the functioning of other software applications, and may cause errors, data loss or other prob-lems. WE STRONGLY ADVISE YOU NOT TO INSTALL BETA SOFTWARE ON A COMPUTER ON WHICH YOU HAVE INSTALLED AN EARLIER VERSION OF THE SOFTWARE. YOU SHOULD NOT INSTALL BETA SOFTWARE ON THE SAME COMPUTER ON WHICH YOU HAVE INSTALLED AN EARLIER VERSION OF THE SOFTWARE, UNLESS YOU ARE CERTAIN YOU HAVE CONFIGURED YOUR COMPUTER SO THAT THE BETA SOFTWARE WILL NOT REPLACE THE EARLIER VERSION. In light of the fact that pre-release or beta Software is provided to you free of charge, Groove Networks disclaims the limited warranty set forth below in Section 10 with respect to pre-release or beta Software, and neither Groove Networks nor any Released Party will be liable for direct damages related to pre-release or beta Soft-ware, as explained more fully in Section 11(b).

(c) Feedback. You agree to provide to Groove Networks reasonable suggestions, com-ments and feedback regarding beta Software, including but not limited to usability, bug reports and test results, with respect to Software testing (collectively, "Feedback"). You grant Groove Networks, under all of your intellectual property and proprietary rights, the following worldwide, non-exclusive, perpetual, irrevocable, royalty free, fully paid up rights: (i) to make, use, copy, modify, and create derivative works of, the Feedback as part of any Groove Networks product, technology, service, specification or other documenta-tion (collectively, "Groove Offerings"), (ii) to publicly perform or display, import, broad-cast, transmit, distribute, license, offer to sell, and sell, rent, lease or lend copies of the Feedback (and derivative works thereof) as part of any Groove Offering, (iii) solely with


respect to your copyright and trade secret rights, to sublicense to third parties the forego-ing rights, including the right to sublicense to further third parties, and (iv) to sublicense to third parties any claims of any patents owned or licensable by you that are necessarily infringed by a third party product, technology or service that uses, interfaces, interoperates or communicates with the Feedback or portion thereof incorporated into a Groove Net-works product, technology or service. Further, you warrant that your Feedback is not sub-ject to license terms that will require, or claim to require, that any Groove Offering that incorporates any Feedback (or any intellectual property therein) be licensed to any third party on specified terms. Due to the nature of the development work, Groove Networks provides no assurance that any specific errors or discrepancies in the Product will be cor-rected.

(d) Confidentiality. All beta Software, including its existence and features and related information, are proprietary and confidential information to Groove Networks. You agree not to disclose or provide beta Software, its Documentation, or any related information (including the Software features or the results of use or testing) to any third party, for a period of one year following the Delivery Date of the Software or until its commercial release, whichever occurs first; provided that, thereafter, you agree not to disclose or pro-vide to any third party any information regarding the Software that has not been made public by Groove Networks as of its commercial release. These restrictions will not apply to any information that (a) is publicly known at the time of its disclosure; (b) is lawfully received from a third party not obligated to maintain it in confidence; (c) is published or otherwise made known to the public by Groove Networks; (d) you generated indepen-dently before you received it, as evidenced by your records; or (e) is required to be dis-closed under any law, governmental rule or regulation or a valid court order, provided you give Groove Networks reasonable written notice prior to disclosure and comply with any applicable protective order or equivalent.

(e) Support and Maintenance. Groove Networks is not obligated to provide maintenance, technical support, or updates to you for beta Software, but any Updates or other supple-mental Software provided to you in connection with beta Software will be subject to the terms and conditions of this EULA. In no event will Groove Networks be obligated to provide you, free of charge, a copy of the commercial release version of the Software in connection with your participation in any testing program. Groove Networks is not obli-gated to make beta Software commercially available.

7. RESTRICTIONS AND LIMITATIONS. You agree to comply with the following restrictions and limitations, and you agree not to permit others (including any End User whose use of the Software you sponsor) to violate them:

(a) Copying, Distribution and Use. You may not copy the Software, except in connection with installation of the Software as provided above in Section 3(a) and to make one copy of the Software solely for backup or archival purposes. You may not sell, rent, lease, sub-


license or redistribute Software or its activation key(s), or use or permit others to install or directly or indirectly access or use the Software, its functionality, or its activation key(s), except as provided in this EULA.

(b) Proprietary Notices. You may not alter or remove any copyright, trademark, patent, or other protective notices contained in or on Software, except that Customer may alter or remove Groove Networks' trademarks and other branding elements from the user interface of the Software to the limited extent that may be permitted under the Trademark Usage Policy, as it may be amended from time to time.

(c) Reverse Engineering, Decompilation, and Disassembly. You may not reverse engi-neer, decompile, or disassemble the Software or otherwise attempt to derive its source code, except and only to the extent that any of these activities is permitted by applicable law despite this restriction. To the extent that the right to decompile, disassemble, or reverse engineer the Software is permitted by applicable law, you agree not to do so if Groove Networks makes available to you a separate software module that allows you to achieve interoperability of an independently created computer program for use with the Software. You agree that, prior to attempting to achieve such interoperability, you will obtain written notification from Groove Networks that it is unwilling to make such a soft-ware module available within a reasonable period of time.

(d) Modifications and Derivative Works. You may not modify or create derivative works of the Software, but computer code written to current application programming interfaces for the Software that are published by Groove Networks or otherwise disclosed by Groove Networks to you or a third party and which are not marked "preview," "trial," "beta," or some similar designation will not be considered modifications or derivative works for pur-poses of this restriction.

(e) Interference with Certain Features. You may not modify, disable, circumvent, deacti-vate or otherwise interfere with features of the Software that enforce license restrictions or limits or report technical or statistical information regarding the Software or its use to Groove Networks.

(f) Use of Prior Versions. You may not continue to use prior versions of any Software after installing an Upgrade of the Software or any Update that wholly replaces the Soft-ware.

(g) Acceptable Use. You may not use the Software for a purpose or in a manner not per-mitted by the terms of Groove Networks' Acceptable Use Policy (as it may be amended from time to time), including, without limitation, infringement of intellectual property


rights. Groove Networks' Acceptable Use Policy is accessible on the Web Site.

(h) Activation Keys. Each Software activation key and Account is intended solely for your use (or use by another End User for whom you have acquired and paid for a license). You (and your licensed End Users) are solely responsible for maintaining the confidential-ity and security of your activation key(s) and Account(s). You are solely responsible and liable for any and all use of your activation key(s) and Account(s) and for activities that occur on or through your activation key(s) or Account(s). You agree to notify us immedi-ately about any unauthorized access to or use of any of your activation key(s) or Account(s). The Software contains technological measures designed to prevent its unli-censed or illegal use. You agree that we may use those measures.

(i) Use of Third Party Software. You may not use third party software applications specif-ically developed for use with the Software with any edition of the Software other than the Professional Edition (or any successor thereto).

(j) Development Use. If you are a developer creating products or services for use with the Software, you may use the Software in accordance with the terms of this EULA for devel-opment purposes, but you must acquire a licensed copy of the Professional Edition of the Software (or any successor thereto) within 60 days after you first acquire any lesser edi-tion of the Software. In other words, you can conduct your development work using a lesser edition of the Software for 60 days, after which you must acquire a licensed copy of the Professional Edition of the Software to support your work.

8. MAINTENANCE AND SUPPORT. Technical support for the Software may be found in the Help menu within the Software and on the Web Site. Unless you subscribe to an enhanced maintenance and/or support offering, you are not entitled to receive additional maintenance or support for the Software (though any Updates or Upgrades Groove Net-works may provide you will be covered by this EULA, unless Groove Networks requires you to accept a new agreement at the time they are provided). If you subscribe to a Groove Networks maintenance and/or support offering, Groove Networks will provide you with maintenance and/or support services corresponding to the service level(s) to which you have subscribed, as set forth in the Maintenance and Support Terms and Condi-tions accessible on the Web Site (at http://www.groove.net/support/maintenance.html) or the terms of any separate agreement you may enter into with Groove Networks related to such services. Whether or not you subscribe to a maintenance and/or support offering, Groove Networks reserves the right to provide you with updates or supplements to the Software via automatic download when we consider it necessary to do so to ensure that the Software functions properly. Any technical information you provide Groove Networks in connection with support services it provides you may be used by Groove Networks for its business purposes, including product and service development, subject to the terms of our Groove Software Privacy Statement, which is accessible on the Web Site.


9. CONSENT TO ESTABLISHMENT OF PEER-TO-PEER CONNECTIONS. The Software is designed to enable "peer-to-peer" connections among End Users and comput-ers for purposes of direct communication, data exchange and interaction among people and machines, with minimum involvement of central computer servers. The Software makes certain information about your Groove account and Computer known to other End Users and computers with which you interact. Peer-to-peer data exchange may occur whenever the Software is running on your Computer, whether or not you are active in a "shared space" or even actively using the Software. You acknowledge and consent to the fact that the Software creates such peer-to-peer connections, and you agree that Groove Networks is not responsible for the conduct of any party (or their computers) who interacts with you or your Computer as a result of your installation or use of Software or Services.

10. LIMITED WARRANTIERS AND WARRANTY DISCLAIMER.

(a) Groove Networks warrants that, for a period of 90 days after the Delivery Date, the Software (including any Upgrades for which Groove Networks does not require you to accept the terms of a replacement agreement, but excluding Updates) will function sub-stantially in accordance with its Documentation. As your exclusive remedy for breach of this warranty, Groove Networks will, at its option, either replace or repair the defective Software or refund the license fee paid for it, as well as any associated fees pre-paid for maintenance, support and/or Hosted Services for the twelve (12) month period following the Delivery Date of the defective Software; provided, however, that, with respect to a defective Upgrade that you received as part of a maintenance and support plan subscrip-tion, the total fees to be refunded to you will be the maintenance and support fee for the twelve (12) month period during which the Upgrade was delivered to you. Notwithstand-ing the foregoing, Groove Networks will not be responsible for any breach of warranty not reported during the warranty period; any malfunctioning of Software that you, an End User, or a third party has modified, misused, or damaged; or any malfunctioning of Soft-ware caused by hardware or network configuration or malfunctioning or by third party software or services. THIS WARRANTY DOES NOT APPLY TO SOFTWARE COV-ERED BY SECTION 4, 5 OR 6 OF THIS EULA.

This warranty gives you specific legal rights. You may also have other legal rights that vary from state to state and country to country.

(b) If you have subscribed to a paid Hosted Services offering (i.e., Hosted Services Level 2 or above), Groove Networks warrants that it will, subject to the terms of this EULA, maintain the availability of such Hosted Service(s) at least 99.9% of the time each calen-dar month during the term of your subscription, exclusive of interruptions due to Force Majeure Events (as defined below) and scheduled maintenance periods. Scheduled main-tenance periods consist of regular, monthly maintenance windows not to exceed two hours


in the aggregate per month; and exceptional maintenance windows not to exceed two hours for any single window and four hours per calendar quarter in the aggregate, pro-vided that Groove Networks must give at least 14 days' advance notice of each exceptional maintenance window via email. As your sole and exclusive right and remedy for any breach of this warranty, and provided you are in compliance with the terms of this EULA, you will be entitled to receive a refund as described in this section. Any refund owed to you for unexcused downtime during a given calendar quarter will be paid by Groove Net-works within thirty (30) days after the end of that quarter (e.g., any refund owed as of March 31 will be paid by April 30), provided that Groove Networks will not be required to make a refund if its amount would be less than US$125, unless you specifically request payment of the lesser refund amount within twenty (20) days after the end of the calendar quarter for which a refund is payable, and unpaid refunds will not carry over to subsequent quarters. The amount of the refund, if any, will equal the amount actually paid by you for the affected Hosted Service(s) during the quarter in question, multiplied by a fraction, the numerator of which will be 0.999 minus the actual percentage uptime for the quarter (less excused interruptions) and the denominator of which will be 0.999. You agree that Groove Networks' calculations of uptime and refund amounts will be conclusive. You acknowledge that, as Groove Networks' provision of Hosted Services is partially depen-dent on the services of third parties providing Internet connectivity, and, as the Internet is neither owned nor controlled by any particular party, Groove Networks can make no guar-anty that any given user will be able to access Hosted Services at any given time. "Force Majeure Event" means an event or circumstance beyond the reasonable control of Groove Networks that prevents it from performing its obligations or which makes it commercially impracticable to do so, including, but not limited to, strikes, lockouts, and other labor dis-turbances; equipment failure; power or communication line failures; failure of third party service providers or suppliers to perform; policies or restrictions of governments (includ-ing restrictions on export, import or other licenses); severe weather conditions or natural disasters; or vandalism, civil disturbances, war, or terrorist acts. This warranty does not apply to Hosted Services provided to you in connection with beta Software, Software pro-vided for evaluation use, Software provided free of charge, or Software provided as a ben-efit of participation in a Groove Networks sales or marketing program (e.g., the Groove Networks Partner Program).

(c) EXCEPT FOR THE LIMITED WARRANTY SET FORTH IN SECTION 10(a), GROOVE NETWORKS AND ITS LICENSORS AND LICENSORS' DISTRIBUTORS DISCLAIM ALL WARRANTIES WITH RESPECT TO ALL SOFTWARE AND SER-VICES AND ALL THIRD PARTY PRODUCTS OR SERVICES YOU OR END USERS MAY UTILIZE IN CONNECTION WITH SOFTWARE OR SERVICES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MER-CHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NONIN-FRINGEMENT. IN PARTICULAR, GROOVE NETWORKS DOES NOT REPRESENT THAT THE SOFTWARE OR SERVICES ARE ERROR FREE, WILL OPERATE IN AN UNINTERRUPTED MANNER, ARE COMPLETELY SECURE, OR WILL INTEROPERATE WITH THIRD PARTY SOFTWARE OR SERVICES. UNLESS YOU HAVE SUBSCRIBED TO A HOSTED SERVICES OFFERING THAT GUARANTEES A PARTICULAR LEVEL OF SERVICE AND/OR A FIXED TERM


OF SERVICE (AS EXPLICITLY SPECIFIED IN A SEPARATE AGREEMENT OR A FORMAL OFFERING DESCRIPTION POSTED ON THE WEB SITE, AND THEN ONLY TO THE EXTENT SO SPECIFIED), ALL HOSTED SERVICES ARE PRO-VIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS AND ARE SUBJECT TO CHANGE OR TERMINATION AT ANY TIME AND FOR ANY REASON WITHOUT NOTICE. THE SOFTWARE AND SERVICES ARE NOT DESIGNED OR MANU-FACTURED FOR USE IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILI-TIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT SYSTEMS, OR WEAPON OR COMBAT SYS-TEMS, IN WHICH THEIR FAILURE COULD LEAD DIRECTLY TO PERSONAL INJURY, DEATH, OR PROPERTY OR ENVIRONMENTAL DAMAGE. GROOVE NETWORKS DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH USES.

(d) U.S. Government Customers and End Users. The Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101, consisting of "commercial computer software" and "commercial computer software documentation." For government purchases or acquisi-tions through a GSA Supply Schedule contract, the government customer and end user accept the standard, commercial Groove Networks warranty terms per 2.a of GSA's "Terms and Conditions Applicable to . . . [SINs] 132-32 . . ., 132-33 . . . and 132-34 . . .." For government purchases or acquisitions under the authority of Federal Acquisition Reg-ulation ("FAR") Part 12, the government customer and end user accept the standard, com-mercial Groove Networks warranty terms and 48 C.F.R. 52.212-4(p). For all government purchases or acquisitions that are not through a GSA Supply Schedule contract or FAR Part 12, the government customer and end user accept the standard, commercial Groove Networks warranty per 48 C.F.R. 46.709 (prime contracts) or 52.244-6 (subcontracts).

11. EXCLUSION OF DAMAGES AND LIMITATION OF LIABILITY.

(a) TO THE MAXIMUM EXTENT PERMITTED BY LAW (INCLUDING ANY APPLICABLE CONSUMER PROTECTION LAW OF A FOREIGN JURISDICTION), NEITHER GROOVE NETWORKS NOR ANY OF ITS DIRECTORS, OFFICERS, EMPLOYEES, CONTROLLED OR CONTROLLING ENTITIES, LICENSORS OR LICENSORS' DISTRIBUTORS (EACH, A "RELEASED PARTY"), WILL HAVE ANY LIABILITY TO YOU OR ANY END USERS FOR INDIRECT, INCIDENTAL, SPE-CIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES (INCLUDING, WITHOUT LIMITATION, ANY LOSS OF USE, LOST PROFITS, BUSINESS OR REVENUE, LOSS OF GOODWILL OR OTHER ECONOMIC ADVANTAGE, OR LOSS OF PRI-VACY) ARISING OUT OF OR RELATED TO THIS EULA, THE SOFTWARE OR THE SERVICES, EVEN IF GROOVE NETWORKS OR A RELEASED PARTY HAS BEEN ADVISED OF, OR KNEW OR SHOULD HAVE KNOWN OF, THE POSSIBIL-ITY OF SUCH DAMAGES.


(b) NOTWITHSTANDING PARAGRAPH 11(a) ABOVE OR ANYTHING ELSE TO THE CONTRARY SET FORTH IN THIS EULA, IF YOUR CLAIMED DAMAGES ARISE FROM OR RELATE TO SOFTWARE OR SERVICES COVERED BY SEC-TION 4, 5 OR 6 OF THIS EULA, THEN, TO THE MAXIMUM EXTENT PERMITTED BY LAW (INCLUDING ANY APPLICABLE CONSUMER PROTECTION LAW OF A FOREIGN JURISDICTION), NEITHER GROOVE NETWORKS NOR ANY RELEASED PARTY WILL HAVE ANY LIABILITY TO YOU OR ANY END USERS FOR DAMAGES OF ANY KIND ARISING OUT OF OR RELATED TO THIS EULA, THE SOFTWARE OR THE SERVICES, INCLUDING BUT NOT LIMITED TO DIRECT DAMAGES, EVEN IF GROOVE NETWORKS OR A RELEASED PARTY HAS BEEN ADVISED OF, OR KNEW OR SHOULD HAVE KNOWN OF, THE POS-SIBILITY OF SUCH DAMAGES.

(c) WITHOUT LIMITING THE SCOPE OR EFFECT OF SECTIONS 11(a) OR (b) ABOVE, IN NO EVENT WILL GROOVE NETWORKS' AND THE RELEASED PAR-TIES' TOTAL LIABILITY WITH RESPECT TO ALL CLAIMS ARISING OUT OF OR RELATED TO THIS EULA, THE SOFTWARE OR THE SERVICES (INCLUDING CLAIMS OF NEGLIGENCE AND STRICT LIABILITY) EXCEED THE LOWER OF (i) THE AGGREGATE DIRECT DAMAGES ACTUALLY INCURRED BY YOU AND YOUR END USERS, OR (ii) US$5OO.

(d) SOME JURISDICTIONS LIMIT THE EXCLUSION OF DAMAGES OR LIMITA-TION OF LIABILITY, SO THE ABOVE EXCLUSIONS AND LIMITATIONS MAY NOT APPLY TO YOU. IF ANY PART OF THE EXCLUSIONS OF DAMAGES OR LIMITATIONS OF LIABILITY SET FORTH IN THIS EULA IS UNENFORCEABLE UNDER APPLICABLE LAW, GROOVE NETWORKS' AND THE RELEASED PAR-TIES' AGGREGATE LIABILITY WILL BE LIMITED TO THE MAXIMUM EXTENT PERMITTED BY LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.

12. TERM AND TERMINATION. The term of this EULA will commence upon installa-tion or use of the Software and continue perpetually, unless you and Groove Networks enter into a new agreement that entirely replaces this EULA or Groove Networks termi-nates this EULA as provided herein. Without prejudice to any other rights, Groove Net-works may terminate this EULA if you fail to comply with its terms and conditions. If Groove Networks terminates this EULA, (i) you must immediately stop using the Soft-ware and destroy all copies of the Software and all of its component parts, and (ii) Groove Networks will have no further obligation to provide any Services being provided to you or any End Users as of the termination date. The parties' respective rights and obligations under Sections 2 (Ownership), 7 (Restrictions), 10 (Limited Warranty and Warranty Dis-claimer), 11 (Exclusion of Damages and Limitation of Liability), and Section 13 (General Provisions) will survive the termination of this EULA. The term of any Services offering to which you subscribe will be extended automatically for successive periods of twelve


(12) months (or, if greater than twelve (12) months, the duration of the initial subscription period), and on Groove Networks' standard terms and prices then in effect, unless either party gives notice of cancellation to the other at least sixty (60) days before the subscrip-tion expires.

13. GENERAL PROVISIONS.

(a) Export Restrictions. You agree to comply with all applicable laws and regulations of governmental bodies and agencies related to use of the Software and Services and your performance under this EULA. In particular, you acknowledge that the Software is of United States origin, is subject to United States export laws and regulations, and may not be exported or re-exported to certain countries (currently Cuba, Iran, Libya, North Korea, Sudan and Syria) or to persons or entities prohibited from receiving U.S. exports (includ-ing Denied Parties, Specially Designated Nationals, and entities on the Bureau of Export Administration Entity List or involved with missile technology or nuclear, chemical or biological weapons). The Software also may be subject to the export, import or other laws of other countries. You represent that you are eligible to receive favorable treatment under current United States export control laws and regulations, and that you will not use or transfer the Software in violation of any U.S. or foreign laws or regulations, or permit others to do so.

(b) Data Protection. Each party undertakes to comply with its obligations under the rele-vant EU data protection and privacy legislation including (where applicable) the EC Data Protection Directive (95/46) and equivalent national legislation.

(c) Application Sharing. The Software may contain features that enable software applica-tions to be shared among two or more computers. Use of third party software through any application sharing functionality in the Software may require the third party's consent. Please consult the license agreement associated with the third party software or contact the third party regarding permitted uses of its software.

(d) Waiver. No delay or omission by either party to exercise any right or power arising upon the other party's nonperformance or breach will impair that right or power or be con-strued as a waiver of it. Any waiver must be in writing and signed by the waiving party. A waiver on one occasion will not be construed as a waiver of any subsequent event of nonperformance or breach.

(e) Severability. If any provision of this EULA is declared to be unenforceable for any reason, the remainder of this EULA will continue in full force and effect, and the unen-forceable provision will be deemed modified to the extent necessary to comply with the


applicable requirements of law, while retaining to the maximum extent permitted by law its intended effect, scope and economic effect.

(f) Governing Law. The interpretation and performance of this EULA will be governed by the laws of the Commonwealth of Massachusetts, USA, applicable to contracts exe-cuted in and performed entirely within Massachusetts, but excluding any choice of law principles that would result in the application of the laws of another jurisdiction. The par-ties expressly agree that the United Nations Convention on Contracts for the International Sale of Goods will not apply to this EULA.

(g) Dispute Resolution. Any litigation arising under or related to this EULA will be brought only in the United States District Court for the District of Massachusetts, or, if federal subject matter jurisdiction is lacking, then in the Massachusetts state trial court for the division and county in which Groove Networks' or its successor's or assign's principal office in Massachusetts is then located. You hereby submit to the personal jurisdiction of these courts and waive all objections to placing venue exclusively before them. The pre-vailing party in any litigation arising under or related to this EULA, in addition to any other relief granted to it, will be entitled to recover from the losing party its reasonable attorneys' fees and costs incurred in connection with the litigation. Notwithstanding the foregoing, Groove Networks acknowledges that the Contract Disputes Act, its implement-ing regulations, and its judicial interpretations may take precedence when the U.S. Gov-ernment is the party accepting this EULA, if required by law; whenever commercial item protections or other exceptions permit the commercially offered disputes resolution clause to apply, however, it applies in full force.

(h) Returns. If you are a consumer in a European Union member state, you have the rights conferred by this section. In the European Union, you are entitled to cancel your order for the Software and any associated Services within 14 working days from the date on which you downloaded the Software. You are not entitled to cancel your order for Software or Services if you accept this EULA and install the Software. To cancel your order please discontinue the installation process and notify us of your decision in writing or by email within 14 working days of download at the postal or e-mail address indicated below. Groove Networks will refund the amount you paid for the cancelled Software and Services within 30 days. If you request a refund, you will not be not be entitled to use the Software or obtain Services unless you place a new order and pay all charges that then apply.

Groove Networks, Inc.

Sales and Marketing Operations

100 Cummings Center, Suite 535Q

Beverly, MA 01915 USA


[email protected]

(i) Payment and Taxes. You agree to pay all applicable fees and other charges for Soft-ware and Services you acquire. Unless prepaid, all fees and charges are payable in U.S. dollars and are due net thirty (30) days from the date of invoice. Groove Networks may charge a late fee of 1.5% per month or the maximum rate allowable by law, whichever is greater, on any balance remaining unpaid for more than thirty (30) days, except that inter-est on payments by U.S. government customers will be calculated according to the Prompt Payment Act and its implementing regulations. Prices are exclusive of all applicable taxes. You agree to pay all taxes (including but not limited to sales, use, excise, and value-added taxes), tariffs, duties, customs fees or similar charges imposed or levied on all Soft-ware and Services you acquire, with the exception of taxes on Groove Networks' net income.

(j) Software and EULA Transfer. Except with respect to Software covered by Section 4, 5 or 6, the initial licensee of the Software may make a one-time, permanent transfer of this EULA and the Software directly to an individual or a single entity. The transfer must include all of the Software (including all component parts and Documentation) and this EULA, and it may not occur by way of consignment or any other indirect transfer. The transferee of the one-time transfer must agree to comply with the terms of this EULA, including the obligation not to further transfer this the Software. You may not otherwise transfer the Software or assign any of your rights or obligations under this EULA.

(k) Entire Agreement. This EULA and Groove Networks' Acceptable Use Policy, Groove Software Privacy Statement, Trademark Usage Policy, and product and service descrip-tions for Software and Services, all of which are accessible on the Web Site and incorpo-rated by reference into this EULA as they may be amended from time to time, set forth the entire agreement between you and Groove Networks with respect to their subject matter, and they supersede all prior communications, understandings and agreements, as well as the terms and conditions set forth in or on any purchase order, acknowledgement form, check, or any other document or instrument you may issue to Groove Networks or trans-mit in connection with any payment for Software or Services.

Copyright Groove Networks, Inc. 2000-2005. All Rights Reserved. Groove, Groove Net-works, Groove Workspace, the Groove interlocking circles logo are trademarks of Groove Networks, Inc. Manufactured under U.S. Patents 6,446,113 B1 and 6,640,241. Addi-tional U.S. and foreign patents pending.

Groove Client Software v. 3.1 (and later) EULA


Index

Numerics63304

Heading3Command Line Options 28

AActivating Groove

after SMS-driven installation 37Activating Groove in a Managed Environment 7Adiministration, troubleshooting 43Administrative login 48Audit Service 25Auto-activation ,of Groove 32

CC Runtime Library 43CD installation 21Centralized Distribution Software, setting up 6Client login as administrator 48Command Line Format 25Command Line with Setup.exe 26Component, definition 51Config.xml 28, 29Contact properties, definition 51Customizing the Installation 5

DDefault identity, definition 51Default identity, defintion 51Deploying Groove, silent mode 21Deployment process 2, 6Device Management 29Device registry files, centrally deploying 49Device registry key 29Device, definition 51Device, defintion 51DMZ, definition 51Domain member 51Domain member, definition 51Domain member, defintion 51Domain, definiion 51

EEnd 62End User License Agreement 62

Groove Software Deployment Index 78

Enterprise Installer 17Enterprise installer

running 21Enterprise Installer, running 21Enterprise Management Server (EMS)

definition 51Enterprise Relay Server (ERS)

definition 52EULA 62Executing .GRV files, from SMS 49

GGlossary 51Groove 2

activating after SMS-driven installation 37Help, accessing 20

Groove activation 7Groove Audit Service 25Groove Components application, running 39Groove Components, installing from onsite server or Web site 39Groove Deployment

flow chart 4Groove deployment

enterprise requirements 9Groove editions 53Groove Enterprise Installer, running 21Groove Hosted Management Services

definition 52Groove Hosted Relay Services

definition 52Groove installation directory, changing 48Groove installation, customizing 5, 25Groove installation, unattended mode 48Groove Installer Service 24

defintion 52Groove Software Deployment Guide 8Groove space, definition 52Groove space, defintion 52Groove update, definition 53Groove updates, controlling 32Groove upgrade, definition 53Groove Users and Devices, identifying 5Groove users, migrating to new machines 32Groove, upgrading 32GROOVE_ADD_TO_DESKTOP 23GROOVE_ADD_TO_STARTUP 23GROOVE_NOTES_INTEGRATION 24GROOVE_OUTLOOK_INTEGRATION 23GrooveAuditService 25GrooveInstallerService 24GROOVESYSTEMDATADIR 23GROOVEUSERDATADIR 23


Group, definition 52H

Hardware requirements 9Help, getting 20

IIdentity, definition 52Installation logs 31Installation problems 43Installation, customizing 5Installation, customizing from command line 25Installation, customizing via Transforms 22INSTALLDIR 23Installer Service

definition 52Installer service 24Installer Service, controlling 33INSTALLERSERVICE flag, using 33Installing Groove Components 39Installing Groove in an enterprise 17Installing Groove, unattended 48InstallShield 38InstallShield,Package for the Web 38Internal Web site distribution 6

LLicense, definition 52Logging installation events 31Login to client as administrator 48

MManagement domain, definition 52Management domain, defintion 52Management services 1Managing Groove devices 29Member, definition 52Microsoft C Runtime Library 43MSI, Transforms, Groove 22

NNewServiceInstall 53NewServiceInstall1 24NewServiceInstall2 25Notes

GrooveNotes integration, requirements 11O

OfficeGroove/Office integration requirements 11

OutlookGroove/Outlook integration requirements 11

PPolicy, definition 53Pre-requisistes 7Public relay server 53


QQuickStart 19Quiet install, definition 53

RRebooting client devices after installation 50Registry file, definition 53Registry key, device 29Registry Upates 29Relay server, definition 53Relay services 2Requirements

hardware 9Rrequirements

software 10Run time problems 46Running the Enterprise Installer 6Runtime Library, Microsoft C 43

SScripting Host, Windows, requirement for 35Silent install, definition 53Site preparation 7SMS, executing .GRV files from 49Software requirments 10

TTool, definition 53Transforms, using to customize installation 22Trouble shooting 43

UUI mode

definition 53UI mode installation

uninstalling 33Unattended mode installation 48Updating Groove, definition 53Upgrading Groove 32Upgrading Groove, defintion 53User account 53User account, definition 53User account, defintion 53User identity 53User identity, definition 53User identity, defintion 53Users, migrating Groove user data to new machines 32

WWindows registry settings 29Windows Script files 43Windows Scripting Host files 43Windows Scripting Host, requirement 35Workspace, definition 53Workspace, defintion 53


Groove Software Deployment

Documents

Transcript of Groove Software Deployment