Groove Software Deployment

Transcription

1 Groove Software Deployment Version 3.1 Administrator s Guide

2 Copyright Copyright , 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 parties identified by the following notices. Copyright 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 Solutions 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 <jef@acme.com>. All rights reserved. Groove Software Deployment Copyright i

3 Table of Contents Copyright i Table of Contents ii Overview 1 Groove Clients and Servers 1 A Process for Deployment 2 Setting 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 7 The Groove Software Deployment Guide 8 Preparing for Deployment 9 Requirements 9 Hardware 9 Software 10 Expertise 12 Planning 12 User and Device Management 12 Component Update Management 13 Groove Data and User Account Backup 14 Client Account Backup 14 Managed Account Backup 14 Groove Space Backup 15 Password Reset and Data Recovery 15 Client Auditing 15 Installing Groove with Enterprise Installer 17 Enterprise Installer Basics 18 QuickStart 19 Groove Software Deployment Table of Contents ii

4 Before You Begin 20 Getting Help 20 Prerequisites 20 Running the Groove Enterprise Installer 21 Customizing Groove Installation Using MSI Transforms 22 Customizing Groove Installation from the Command Line 25 Command Line Format 25 Command Line with Setup.exe 26 Command Line with Setup.exe and Transform 26 Command Line with MSIExec.exe 27 Command Line with MSIExec.exe and Transform 27 Command Line Options 28 Specifying Unattended Installation 28 Changing 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 31 Activating Groove 31 Updating Groove 32 Controlling Groove Updates 32 Controlling the Groove Installer Service 33 Uninstalling the Groove Enterprise Installer 33 Centralized Deployment with the Enterprise Installer 34 Before You Begin 34 Active Directory GPO Installations 35 SMS Installations 36 SMS Packages 36 Creating SMS Advertisements 37 Activating Groove After a Centralized Installation 37 Website Deployment 38 Installing Groove Components 39 Requirements 39 Hardware 39 Software 40 Installing Groove Components on a Server 40 Enabling Manual Client Upgrades from Groove Components 41 MIME Types in IIS version Troubleshooting 43 Installation Problems 43 Groove User Activation Problems 44 Run Time Problems 46 Common Administrative Tasks 48 Logging into Client Devices as Administrator 48 Installing Groove in Unattended Mode 48 Groove Software Deployment Table of Contents iii

5 Changing the Groove Installation Directory 48 Centrally Deploying Device Registry Files 49 Making a Device Managed Without Losing Previous Data 49 Converting an Unmanaged Identity to a Managed Identity 49 Centrally Executing.GRV Files 49 Final Restarting of Client Devices 50 Updating and Overinstalling Groove 50 Glossary 51 Appendix A. Registry Changes for Mail/Messaging Integration 54 For Lotus Notes R5 54 For 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

6 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, security policies, and IT practices. IT administrators may choose to standardize Groove deployment with a single organization-wide installation package, or choose to create custom installations that target specific departments. The installation may be conducted from a centralized deployment server running a software management service, or it may be stationed on an internal server available to device users for download. For small deployments, 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 system 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 component services hosted by onsite servers or Groove Networks, in addition to the Groove client 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

7 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 desirable, 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 following table: Question Is unattended installation necessary? Should Groove installation parameters be standardized? Is the user-base large enough to merit centralized Groove deployment? Do security practices involve locked-down desktops (users without administrative access to their PCs)? Is device management required to support corporate network and security practices? Is Groove user management required to support corporate network and security practices? If Yes, Suggested Solution is: Use the Groove Enterprise Installer to conduct the deployment without requiring end-user input. Use the Groove Enterprise installer to customize Groove installation paths and options, and to ensure standard installation settings throughout an enterprise or department. Use the Enterprise Installer with a centralized distribution system, such as Active Directory to conduct an automated, customized organization-wide installation. 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. Use Groove management and relay servers, along with the Enterprise Installer, to assemble Groove devices into a management domain. Use Groove management and relay servers to assemble Groove users into a management domain. A Process for Deployment If the answer to all of the above questions is No, Groove is best installed manually on individual 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 Groove Software Deployment Overview 2

8 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 Groove Software Deployment Overview 3

9 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, Groove Software Deployment Overview 4

10 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 corporate server. Verifying Management Domains and Policies In a managed Groove environment, where Groove devices and users are subject to centralized 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 installation. Customizing the Installation The MSI-based Enterprise Installer lets administrators customize the Groove installation to suit corporate requirements. Customization parameters, including installation directories 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 section of this guide. Groove Software Deployment Overview 5

11 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 Policy 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 centralized 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 centralized 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 customized, (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. Groove Software Deployment Overview 6

12 Distributing Managed Identities Managed Groove user identities are pre-defined on Groove management servers by administrators, then distributed to users via . The 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 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 environment 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 managed 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 s that contain their managed identities, users activate Groove, immediately 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 managed 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. Groove Software Deployment Overview 7

13 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 Groove Software Deployment Overview 8

14 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 Hardware 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 - details.aspx?displaylang=en&familyid=4b6140f9-2d fa1-6f8a0f5dca8f Microsoft Active Directory - The following table lists overall client and server hardware requirements for an enterprise- Groove Software Deployment Preparing for Deployment 9

15 wide deployment of Groove, as of this publication. 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 SharePoint TM 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 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) Web Site Server For onsite Groove component update services: Windows Server 2000 (or later) running the latest version of Groove Components, as described in Installing Groove Components. For an internal Web site-based deployment, you need: Web server, such as Microsoft Information Services (IIS) server Software The following table lists Groove client and server software requirements, as of this publi- Groove Software Deployment Preparing for Deployment 10

16 cation. System Component Specifications Client Software See 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) Groove Software Deployment Preparing for Deployment 11

17 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 environment over the long term. This section addresses decisions best made at the outset, including: 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 methodologies 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 managed in order to respond to component installation, data recovery, and other domain policies 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- Groove Software Deployment Preparing for Deployment 12

18 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 installation 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 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 component installations on client devices. Some components may require testing in accordance 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 intervals. In unmanaged environments, users need only accept the notification and new software 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 administrators 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 standard company practice before conducting a Groove deployment. In this way, you can arrange for Groove component updates throughout your organization as safely and efficiently as possible. For detailed information about managing Groove component updates, see the Managing Devices section of the Groove Management Server Domain Administrator 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 Service in the Running the Enterprise Installer section of this guide. Groove Software Deployment Preparing for Deployment 13

19 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 endusers can run whenever they choose. In case of account loss, disk failure or other problems, 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 administrators, 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 management 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 directories 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 Groove Software Deployment Preparing for Deployment 14

20 Guide. Groove Space Backup If you want to backup Groove workspace data to a central location, you can consider utilizing the Enterprise Backup Service which runs in conjunction with the Groove Enterprise 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 system. 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 company 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 features 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 client 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 Groove Software Deployment Preparing for Deployment 15

21 Server and supporting SQL server. See the Groove Enterprise Management Server Administrator s Guide for information about Groove client auditing. Groove Software Deployment Preparing for Deployment 16

22 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 centralized 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 companywide deployment, use the recommended method, which involves the following steps: Groove Software Deployment Installing Groove with Enterprise Installer 17

23 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 accompanying the software or visit 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 automatically 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 for example). It also sets client device read/write permissions on directories where Groove program and data directories will reside, necessary for Groove product operation. In a secure enterprise environment, these directories are typically locked down. Groove Software Deployment Installing Groove with Enterprise Installer 18

24 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 automatically. 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 administrators 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 version 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 organization-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 conduct 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. Groove Software Deployment Installing Groove with Enterprise Installer 19

25 You are running the installation directly on a individual client devices (without a centralized software distribution system). 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. 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 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. Groove Software Deployment Installing Groove with Enterprise Installer 20

26 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 software 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. Groove Software Deployment Installing Groove with Enterprise Installer 21