liquid machines gateway for sharepoint installation guide...from sharepoint, the user could use them...

Liquid Machines Gateway for SharePoint

Installation Guide

Liquid Machines, Inc.

100 Fifth Avenue, 5th Floor

Waltham, MA 02451

1.877.88LIQUID (1.877.885.4784)

www.liquidmachines.com

mailto:[email protected]?subject=Contact%20from%20Web%20site

Liquid Machines Gateway for SharePoint Installation Guide

Liquid Machines, Inc. Page ii

Copyright/Disclaimer

Copyright © 2003 - 2008 Liquid Machines, Inc. All rights reserved. Confidential and proprietary information of Liquid Machines, Inc.

The material in this document may not in whole or in part be copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable form without the prior written consent of Liquid Machines. The information in this document is for informational use only, is subject to change without notice, and should not be construed as a commitment by Liquid Machines. Liquid Machines assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

This document and the software described in this document are furnished under a license accompanying the software and may be used only in accordance with the terms of such license. By using this document, you agree to the terms and conditions of that license.

>> For other copyright and trademark information, see the Liquid Machines Copyright, included in this document package.

How to Contact Liquid Machines, Inc. Liquid Machines, Inc.

100 Fifth Avenue, 5th Floor

Waltham, MA 02451

Phone: 1.877.88LIQUID (1.877.885.4784)

www.liquidmachines.com

mailto:[email protected]?subject=Contact%20from%20Web%20site


Liquid Machines, Inc. Page iii

Table of Contents

Copyright/Disclaimer ....................................................................................................................... ii

Preface ................................................................................................................................... v

Book Conventions ....................................................................................................................... v

Intended Audience ...................................................................................................................... v

Related Documents .....................................................................................................................vi

SharePoint Documents ............................................................................................................vi

Using this Manual ........................................................................................................................vi

Chapter 1: Introduction .............................................................................................................. 1-1

What is SharePoint? ................................................................................................................. 1-2

Information Rights Management on SharePoint ....................................................................... 1-2

Extending SharePoint with IRM with the Liquid Machines Gateway for SharePoint .................. 1-4

Supported File Types ............................................................................................................ 1-5

Collaboration Outside of SharePoint ..................................................................................... 1-6

Roles of Personnel Associated with the Gateway for SharePoint ............................................. 1-7

Common Workflow ................................................................................................................... 1-7

Chapter 2: Installing the Gateway for SharePoint ...................................................................... 2-1

System Requirements .............................................................................................................. 2-2

Software Requirements ......................................................................................................... 2-2

Before You Begin ..................................................................................................................... 2-2

Creating a Service User Account for the Gateway for SharePoint ......................................... 2-3

Turning off User Account Control (UAC) ............................................................................... 2-4

Running the Gateway for SharePoint Setup Wizard ................................................................. 2-5

Notifying the Site Owner of the Gateway for SharePoint ......................................................... 2-12

Uninstalling the Gateway for SharePoint ................................................................................ 2-13

Modifying the File Types Supported by the Gateway for SharePoint ...................................... 2-15

Chapter 3: Troubleshooting ....................................................................................................... 3-1

Introduction .............................................................................................................................. 3-2

Common Problems ................................................................................................................... 3-3

Appendix A: Sample Email to Notify the Site Owner of the Gateway for SharePoint .................... A-1

Appendix B: Mapping SharePoint Permissions to IRM Rights ...................................................... B-1

Index ......................................................................................................................... Index-1


Liquid Machines, Inc. Page iv


Liquid Machines, Inc. Page v

Preface

Welcome to the Liquid Machines Gateway for SharePoint Installation Guide. This document introduces SharePoint and the Liquid Machines Gateway for SharePoint. It also describes the requirements for installation and the installation procedure. It provides troubleshooting procedures related to installation and administration of the Gateway for SharePoint.

Book Conventions

CAUTION: Cautions the user of actions that may result in operational issues or data loss.

NOTE: Identifies important points, helpful hints, special circumstances, or alternative methods.

This guide also uses the following typographical conventions:

>> Blue indicates a cross-reference. A cross reference provides the location of additional information related to the topic. For example: >> For more information, see Intended Audience on page v.

Bold Indicates a selection from a menu or a button name. For example:

From the Settings menu, select Document Settings Library.

Bold is also used for file names and emphasis.

Intended Audience This guide is intended for the System Administrator who is responsible for installing the Liquid Machines Gateway for SharePoint on the SharePoint server. This person is often a member of the IT department and is responsible for setting up SharePoint.


Liquid Machines, Inc. Page vi

Related Documents This section lists documents related to the Gateway for SharePoint and SharePoint in general.

Liquid Machines Gateway for SharePoint User’s Guide

SharePoint Documents The following documents provide information on SharePoint:

MSDN‟s Information Rights Management in Windows SharePoint Services Overview: http://msdn.microsoft.com/en-us/library/ms458245.aspx

Microsoft Technet Office SharePoint Server 2007: http://technet.microsoft.com/en-us/library/cc303422.aspx

Microsoft Technet Plan Information Rights Management: http://technet.microsoft.com/en-us/library/cc261728.aspx

Microsoft Technet Configure Information Rights Management (Office SharePoint Server): http://technet.microsoft.com/en-us/library/cc262566.aspx

The following documents provide information on Microsoft RMS:

Microsoft website: http://www.microsoft.com/windowsserver2003/technologies/rightsmgmt/default.mspx

Using this Manual This user guide contains the following chapters and appendices:

Chapter 1: Introduction – Introduces SharePoint, IRM, and the Liquid Machines Gateway for SharePoint and provides a typical workflow for the product.

Chapter 2: Installing the Gateway for SharePoint – Describes the requirements and prerequisites for installing the Gateway for SharePoint. It also provides the detailed installation procedure.

Chapter 3: Troubleshooting – Describes troubleshooting if problems occur during the installation or use of the Gateway for SharePoint.

Appendix A: Sample Email to Notify the Site Owners of the Gateway for SharePoint – Provides a sample email that you can use to notify SharePoint Site Owners of the capabilities of the Gateway for SharePoint.

Appendix B: Mapping SharePoint Permissions to IRM Permissions – Describes how SharePoint permissions map to IRM permissions.

Index – Provides an index to aid you in locating information.

http://msdn.microsoft.com/en-us/library/ms458245.aspx

http://technet.microsoft.com/en-us/library/cc303422.aspx



http://www.microsoft.com/windowsserver2003/technologies/rightsmgmt/default.mspx


Liquid Machines, Inc. Page 1-1

Chapter 1: Introduction

This chapter introduces the Liquid Machines Gateway for SharePoint.

Topics included in this chapter:

What is SharePoint?

Information Rights Management on SharePoint

Extending SharePoint with IRM with the Liquid Machines Gateway for SharePoint

Supported File Types

Collaboration Outside SharePoint

Roles of Personnel Associated with the Gateway for SharePoint

Common Workflow



What is SharePoint? Microsoft® Office SharePoint® Server 2007 (MOSS 2007) is an integrated suite of server capabilities that provide content management, enterprise search, and workflow management to facilitate information sharing across the organization. MOSS is built on top of Windows SharePoint Server Services 3.0. SharePoint Server 2007 includes a browser-based tool and supports intranet, extranet, and Web applications across the enterprise

A central feature of SharePoint is the ability to centrally store and control access to documents. SharePoint Site Owners can create document management policies to control access rights, specify retention period and expiration actions, and track content through document-auditing settings. Integration with information rights management further enables usage control by applying persistent enterprise rights management policies to be automatically applied to documents, helping to ensure that confidential information is better protected, even when the document is not stored in a SharePoint server.

Information Rights Management on SharePoint Until the introduction of MOSS 2007, SharePoint could only control who could open documents that were stored in SharePoint and who could upload changes. Once documents were removed from SharePoint, the user could use them however they wanted, and could share the documents with anyone. MOSS 2007 enhances document security by adding the ability to enforce Microsoft Rights Management Services (RMS) protections to documents that are removed from SharePoint, through its implementation of Information Rights Management (IRM). This means that IRM-enabled applications like Microsoft Office can enforce permissions such as read, edit, and print, and can even cause access to documents to expire when they are used outside of SharePoint.

Administrators can enable IRM for one or more SharePoint libraries or lists.



NOTE: Throughout this document, the terms “SharePoint library or list,” or “library or list” refers to all the types of libraries and lists that can be IRM-protected in SharePoint. These include the following:

Libraries

Document Library

Forms Library

Connection Library

Report Library

Slide Library

Communications

Announcements

Contacts

Discussion Board

Tracking

Calendar

Tasks

Project Tasks

Issue Tracking

Links and Surveys

Custom Lists

Custom List

Custom List in Database View

KPI

When IRM is enabled, documents in that library or list are protected with IRM permissions (essentially an RMS custom policy) when they are removed or opened from SharePoint. This policy encrypts the file and controls how the authorized users can work with the document. Users with the appropriate rights can view or modify documents downloaded from SharePoint, but the protections remain in place no matter where the document is used or how it is distributed.

Files are not protected when stored within SharePoint. SharePoint calls an IRM protector to convert stored files to an encrypted format each time a file is downloaded. When a file with rights management control is uploaded, SharePoint again calls the IRM protector to decrypt the file for storage in SharePoint. This enables users to use SharePoint search capabilities normally.

In summary, files are protected by IRM when they are downloaded from SharePoint and unprotected when they are uploaded to SharePoint.



Extending SharePoint with IRM with the Liquid Machines Gateway for SharePoint Liquid Machines Gateway for SharePoint, working together with the Liquid Machines Document Control Client (LMDC Client) or the Liquid Machines Viewer (LM Viewer) extends Microsoft‟s Information Rights Management (IRM) by adding a custom autonomous IRM protector that adds support for additional file formats and enhancing the ability to securely collaborate outside of SharePoint. Like the IRM protectors built into SharePoint 2007, the Gateway for SharePoint associates Rights Management Service (RMS) permissions to files when they are checked out of a library or list and removes the protection when the file is uploaded to SharePoint.

Additionally, the Gateway for SharePoint (and the LMDC Client or LM Viewer) enables the following additional features:

The Gateway for SharePoint provides an autonomous protector which allows SharePoint to protect additional file types.

LMDC Client and LM Viewer are IRM-aware client side agents which allow end users to work with these additional IRM protected file types.

The Liquid Machines protector creates an issuance license which includes all authorized users, therefore allowing all authorized users to share protected information outside of SharePoint, without requiring that each user download the files directly from SharePoint.



Supported File Types The file types supported by the Gateway for SharePoint are shown in Table 1-1. The files are listed in groups according to settings that can be made from the Gateway for SharePoint Setup Wizard.

Table 1-1: File Types Supported by the Gateway for SharePoint

Selection Files Included

Most Common doc, docm, docx, dot, dotm, dotx, pdf, ppsm, ppsx, ppt, pptx, pot, potm, potx, pps, xla, xls, xlam, xlsm, xlsx, xltx, xps

LMDC Client

Typical

3dxml, cgm, cgr, dfx, dif, dlt, doc, docm, docx, dot, dotm, dotx, dwg, dxf, emf, emz, eprt, eps, fdf, gif, ids, jpg, mht, mhtml, mst, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, prnps, psd, rtf, slk, svg, svgz, tif, tmp, txt, vda, vsd, vst, wps, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

LM Viewer Typical

123, 3dxml, all, ans, ascasp, bmp, cgm, cgr, db, dbf, dif, dlt, doc, docm, docx, dot, dotm, dotx, dwg, dxf, emf, emz, eprt, eps, fdf, fm3, gif, ids, jpg, lwp, mcw, mht, mhtml, mpp, msg, mst, odg, odp, ods, odt, pct, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, pptx, prn, prz, ps, psd, qpw, rtf, sda, sdc, sdd, sdw, shw, slk, svg, svgz, sxc, sxd, sxi, sxw, tif, tmp, txt, uue, vda, vsd, vst, wk1, wk3, wk4, wks, wmf, wpd, wps, wq1, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

Custom 123, 3dxml, ai, all, ans, asc, asm, asmdot, asp, bmp, cgm, cgr, db, dbf, dif, dlt, doc, docm, docx, dot, dotm, dotx, drw, drwdot, dwg, dxf, easm, edrw, emf, emodel, emz, eprt, eps, fdf, fm3, frm, gif, hcg, hdm, hsf, htm, ids, igs, jpg, lwp, map, mcw, mht, mhtml, mpp, msg, mst, odg, odp, ods, odt, pct, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, pptx, prn, pro, prt, prtdot, prz, ps, psd, qpw, rtf, sat, sda, sdc, sdd, sdw, shw, sec, sldasm, sldblk, sldbomtbt, slddrw, sldlfp, sldprt, sldsffvt, sldwekdfvt, slk, step, stl, svg, svgz, sxc, sxd, sxi, sxw, swj, swp, sym, tbl, tif, tmp, txt, u3d, uue, vda, vsd, vss_out, vst, win, wk1, wk3, wk4, wks, wmf, wpd, wps, wrl, wq1, x_b,xaml, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

NOTE: Files will only be protected if their file types have been specifically selected during the installation of the Gateway for SharePoint. If SharePoint users need to protect file types that are not selected during the installation, the SharePoint Site Owner may contact you to request that you add additional file types. This can be accomplished by modifying a Registry key.

>> For more information on modifying the list of file types supported by the Gateway for SharePoint, see Modifying the File Types Supported by the Gateway for SharePoint on page 2-15.



Collaboration Outside of SharePoint SharePoint 2007‟s built-in IRM capabilities do not allow a user to share a file protected by SharePoint with another user outside of SharePoint, even if that user‟s permissions, as defined by SharePoint, grant them access to that file. Using SharePoint‟s existing capabilities, the following actions take place when two users collaborate on a document:

User 1 opens the file from SharePoint.

User 1 edits the file.

User 1 saves the changes back to SharePoint.

User 1 informs User 2 that changes have been made.


User 2 reviews the changes and edits the file as needed.


User 2 informs User 1 that the changes have been made.




Each user must remove the file from SharePoint and save the file back to SharePoint for the other user to see their changes.

Using the Gateway for SharePoint, the process of collaboration is made easier. Assuming that both users have permission to access the selected file, the following steps describe the collaboration:


User 1 edits the file and saves the changes.

User 1 emails the file to User 2 (or shares the file in any way).


User 2 saves the changes.

User 2 emails the file back to User 1 (or shares the file in any way).



NOTE: Even though the Gateway for SharePoint allows collaboration outside of SharePoint, users who normally do not have access to files on SharePoint will still not have access to those files when they are outside of SharePoint.



Roles of Personnel Associated with the Gateway for SharePoint Three specific roles are associated with the Gateway for SharePoint.

System Administrator – The System Administrator installs the Gateway for SharePoint to extend SharePoint 2007‟s IRM capabilities. Once the installation is complete, the System Administrator informs the SharePoint Site Owner that the Gateway for SharePoint is ready to be configured.

SharePoint Site Owner – The SharePoint Site Owner enables IRM on the SharePoint library or list and manages access rights to the libraries and lists they own. The SharePoint Site Owner may specify SharePoint Permission Levels which define SharePoint permissions which are mapped to IRM permissions. The SharePoint Site Owner is responsible for informing SharePoint users of the file types that can be supported in their installation and of the ability to collaborate outside of SharePoint.

SharePoint User – The SharePoint User is the end user who accesses the protected content from SharePoint. The Gateway for SharePoint is transparent to the SharePoint user, except that he or she will be able to protect/consume additional file formats using the LMDC Client or the LM Viewer. The Site Administrator will inform the SharePoint User of any additional capabilities provided.

Common Workflow After the Gateway for SharePoint has been installed, the SharePoint Site Owner enables IRM and manages IRM access and usage rights, and SharePoint Users access the protected content.

Figure 1-1 shows a typical usage scenario for the Gateway for SharePoint.



Figure 1-1: Typical Usage Scenario of the Gateway for SharePoint



In this scenario, the SharePoint Site Owner gives Users A, B, and C access to the content in a document library called “DocLib1” on the SharePoint server. The administrator normally assigns users or groups to a SharePoint Group (like Owner, Member, or Visitor), which maps to a set of SharePoint Permission Levels, and thus a set of permissions. Alternatively, the administrator can grant SharePoint Permission Levels directly (Full Control, Contribute, Read, etc.). The SharePoint Site Owner enables Information Rights Management (IRM) for the document library and sets specific IRM permissions. In addition, when IRM is enabled on the document library, many SharePoint permissions are translated to IRM permissions.

>> For details on permission mapping, see the Table B-2 and the Liquid Machines Gateway for SharePoint User’s Guide.

The following lists the SharePoint Groups assigned in this example:

User A, the Site Owner and Site Administrator, is in the SharePoint Group “Owners” by default, which gives users the “Full Control” permissions in SharePoint.

User B is added to the SharePoint Group “Members”, which gives users “Contribute” permissions in SharePoint.

User C is added to the SharePoint Group “Visitors”, which gives users “Read” permission.

User D is not given access to the content in the DocLib1 library.

(Table 1-2 below describes how permissions are mapped for this example. This table assumes that the default SharePoint Groups and Permission Levels are in place and unchanged.)

User A creates a document called SampleDoc on his or her desktop. The file can be of any of the file types supported for the current installation of the Gateway for SharePoint.

User A saves SampleDoc and uploads it to the SharePoint library DocLib1. The file is stored unprotected on the SharePoint server.

User B then downloads SampleDoc from the DocLib1 library. An IRM policy is created and applied to the document when it is downloaded to User B. The use license includes permissions for all authorized users. Each user‟s permissions are based on a combination of their SharePoint permissions and the IRM permissions specified for this library (see Table 1-2 below). User B can read, edit, copy, save and print the document for the next 30 days. He or she can then choose to share SampleDoc with User C and User A (for example he or she could send User A and User C SampleDoc by email).

User A, who has Full Control and therefore full rights to the document, can edit the document and then upload SampleDoc to the SharePoint library DocLib1. The protected file is unprotected at upload time, for storage back in the DocLib1 on the SharePoint Server. (User A could have also sent the document back to User B for review.)

User C can also read and print SampleDoc, but does not have the rights to copy and save the document. The SampleDoc document remains protected outside SharePoint, but users with rights to files from DocLib1 can collaborate on the document (as their rights allow) without it being uploaded back to SharePoint.

If User B emailed or otherwise shared SampleDoc to User D, User D would not be able to view or modify SampleDoc because he or she was not granted rights to files downloaded from the DocLib1 library on SharePoint.



The following table describes how IRM permissions are mapped to the use license on a document based on the combination of the users‟ SharePoint permissions and the IRM permissions set for that library or list. This table is based on the example provided above.

Table 1-2: Mapping IRM Permissions to Document Use License Based on SharePoint and IRM Permissions

User SharePoint Group

SharePoint Permissions Associated with the Selected SharePoint Group, which Map to IRM Permissions

IRM Permissions Specified for the Library or List

Permissions User Will Have for Document

A Owners Full Control

Read

Edit

Copy

Save

Modify permissions

Print

30 license length

Cannot access content program-matically

Users with full control will retain full control. All other users will be consistently allowed or denied in the above permissions based on the IRM setting for the library or list.

Full Control

Read

Edit

Copy

Save

Modify permissions

Print

Unlimited license length

Can access content program-matically

B Members Contribute

Read

Edit

Copy

Save

Read

Edit

Copy

Save

Print

30 day license length


C Visitor Read

Read

Read

Print

30 day license length


D None None None None



Chapter 2: Installing the Gateway for SharePoint

This chapter describes how to install the Liquid Machines Gateway for SharePoint on the SharePoint server.

Topics included in this chapter are:

System Requirements

Before You Begin

Running the Gateway for SharePoint Setup Wizard

Notifying the SharePoint Site Owner that Installation is Complete

Uninstalling the Gateway for SharePoint

Modifying the File Types Supported by the Gateway for SharePoint



System Requirements For each SharePoint server, you install one instance of the Gateway for SharePoint. The SharePoint Server must be Information Rights Management (IRM)-enabled to use the Gateway for SharePoint.

>> If the SharePoint server is not IRM-enabled, refer to the Microsoft SharePoint documentation for instructions on enabling IRM.

Software Requirements Microsoft Office SharePoint Server (MOSS) 2007 or Microsoft Windows SharePoint Server

(WSS) 3.0

.NET Framework 3.5

Before You Begin This section describes the prerequisites that must be in place before installation.

Verify that SharePoint is installed and configured to be IRM-enabled.

Create a service user account.

Turn off User Account Control (only required if you are installing the Gateway for SharePoint on a Windows 2008 server)

Know which file types you want to protect.



Creating a Service User Account for the Gateway for SharePoint Before installing the Gateway for SharePoint, you must create a service user account for the Gateway for SharePoint service. This user provides a Windows identity under which the service runs and communicates with Microsoft Right Management Services (RMS). This account will never be used by an actual user, but it must be created before you run the setup wizard because the User Name and Password of the service user account are required to complete the installation.

To create the service user account, you access the domain controller and set up a Windows identity under which the service runs.

The service account must meet the following requirements before installing the Gateway for SharePoint. The service account must be:

A SharePoint Farm administrator (set in Central Admin | Operations).

A Site Collection administrator (from a site within the collection: Site Actions | Site Settings | Users and Permissions | Site collection administrators).

In the db_owner role for the site collection‟s content database on the SQL Server.

The service user requires the following permissions:

“Log on as service” (Windows permission), and

“Site Owner” (SharePoint permission, for any site enabled with IRM).

From the SharePoint perspective, the service user should have:

Full control on the parent web – in the case when the inherited permissions are set up for the document library, or

Full control on the document library – in the case when there are unique rights for the document library (these rights are not inherited).

If the service user account is not configured properly, and you install the Gateway for SharePoint, you may find that that documents protected by the Gateway for SharePoint either fail to open or the documents may open unprotected. If this occurs, check the Windows Event logs and the SharePoint logs for errors.

>> For information on error messages that may appear in the logs if the service user is not configured correctly, see Chapter 3: Troubleshooting on page 3-1.



Turning off User Account Control (UAC) If you are installing the Gateway for SharePoint on a Windows 2008 server, you will need to turn off User Account Control before installing the Gateway for SharePoint.

To perform this procedure, you must be able to log on with or provide the credentials of a member of the local Administrators group.

To turn off User Account Control:

1. Select the Start button, and then select Control Panel.

2. In the Control Panel, select User Accounts.

3. In the User Accounts window, select User Accounts.

4. In the User Accounts tasks window, select Turn User Account Control on or off.

5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Select Continue.

6. Uncheck the Use User Account Control (UAC) to help protect your computer check box, and then select OK.

7. Select Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.



Running the Gateway for SharePoint Setup Wizard The Setup wizard is used to prepare for the installation and then perform the installation. To run the Gateway for SharePoint Setup Wizard:

1. Launch the Gateway for SharePoint Setup Wizard.

The Welcome screen displays (see Figure 2-1).

Figure 2-1: Welcome Screen



2. Select Next to continue with the installation.

The End-User License Agreement displays (see Figure 2-2).

Figure 2-2: End-User License Agreement Screen

3. Read the License Agreement. (To print the agreement, select Print.)

4. Select the check box to accept the terms in the License Agreement.

5. Select Next to continue. The Destination Folder screen displays (see Figure 2-3).

Figure 2-3: Destination Folder Screen



6. The default destination folder displays on this screen. To install the Gateway for SharePoint in the default destination folder, select Next.

To install the Gateway for SharePoint to an alternate location, select Change. The Change Destination Folder screen displays (see Figure 2-4). Browse to the selected folder and select OK, and then select Next.

Figure 2-4: Change Destination Folder Screen



7. The Enter Service User screen displays (see Figure 2-5).

Figure 2-5: Enter Service User Screen

Enter the User Name and Password of the Service User on this screen. The User Name must be entered using the following syntax: .

If the Service User has not been defined, the installation cannot be completed.

>> For more information on defining the Service User, see Creating a Service User Account for the Gateway for SharePoint on page 2-3.

8. Select Next.

The installer will attempt to validate the entered credentials. If the User Name or Password is incorrect, a dialog displays (see Figure 2-6).

Figure 2-6: User Name or Password of Service User was Incorrect

Select OK and re-enter the User Name and Password on the Enter Service User screen.



9. The Select File Extensions screen displays (see Figure 2-7).

Figure 2-7: Select File Extensions Screen

10. From this screen, select the file extensions that will be automatically IRM-protected for this installation of the Gateway for SharePoint. In most cases, you will only want to select file types that can be consumed by the IRM-enabled client agent that your organization has chosen. The Select File Extension screen simplifies this action by providing Predefined File Extension Sets on the left side of the screen which correspond to the file types supported by each Liquid Machines client agent. The possible choices for the Predefined File Extension Sets are provided in Table 2-1.



NOTE: Liquid Machines PDF for RMS users should choose the Most Common selection.

Table 2-1: Predefined File Extension Sets for the Gateway for SharePoint

Selection Files Included

Most Common doc, docm, docx, dot, dotm, dotx, pdf, ppsm, ppsx, ppt, pptx, pot, potm, potx, pps, xla, xls, xlam, xlsm, xlsx, xltx, xps

LMDC Client

Typical

3dxml, cgm, cgr, dfx, dif, dlt, doc, docm, docx, dot, dotm, dotx, dwg, dxf, emf, emz, eprt, eps, fdf, gif, ids, jpg, mht, mhtml, mst, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, prnps, psd, rtf, slk, svg, svgz, tif, tmp, txt, vda, vsd, vst, wps, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

LM Viewer Typical

123, 3dxml, all, ans, ascasp, bmp, cgm, cgr, db, dbf, dif, dlt, doc, docm, docx, dot, dotm, dotx, dwg, dxf, emf, emz, eprt, eps, fdf, fm3, gif, ids, jpg, lwp, mcw, mht, mhtml, mpp, msg, mst, odg, odp, ods, odt, pct, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, pptx, prn, prz, ps, psd, qpw, rtf, sda, sdc, sdd, sdw, shw, slk, svg, svgz, sxc, sxd, sxi, sxw, tif, tmp, txt, uue, vda, vsd, vst, wk1, wk3, wk4, wks, wmf, wpd, wps, wq1, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

Custom 123, 3dxml, ai, all, ans, asc, asm, asmdot, asp, bmp, cgm, cgr, db, dbf, dif, dlt, doc, docm, docx, dot, dotm, dotx, drw, drwdot, dwg, dxf, easm, edrw, emf, emodel, emz, eprt, eps, fdf, fm3, frm, gif, hcg, hdm, hsf, htm, ids, igs, jpg, lwp, map, mcw, mht, mhtml, mpp, msg, mst, odg, odp, ods, odt, pct, pcx, pdf, pln, png, pot, potm, potx, ppa, pps, ppsm, ppsx, ppt, pptm, pptx, prn, pro, prt, prtdot, prz, ps, psd, qpw, rtf, sat, sda, sdc, sdd, sdw, shw, sec, sldasm, sldblk, sldbomtbt, slddrw, sldlfp, sldprt, sldsffvt, sldwekdfvt, slk, step, stl, svg, svgz, sxc, sxd, sxi, sxw, swj, swp, sym, tbl, tif, tmp, txt, u3d, uue, vda, vsd, vss_out, vst, win, wk1, wk3, wk4, wks, wmf, wpd, wps, wrl, wq1, x_b,xaml, xfdf, xla, xlam, xls, xlsb, xlsm, xlsx, xlt, xltx, xlw, xps, zip

11. If you select a predefined set of file extensions, you will have the opportunity to add or remove file extensions from the list.

If you choose Custom, the list of files types available displays in the Available Extensions List. Select one or more file types to be supported by the Gateway for SharePoint in the Available Extensions List and use the controls described in Table 2-2 to select the files. Selected files appear in the Selected Extensions List.

If you choose Most Common, LMDC Client Typical, or LM Viewer Typical, you can also use this screen to add or remove file extensions from the selected list to customize these predefined selections. The files supported in the predefined list are shown in the Selected Extensions List and all other file types available are listed in the Available Extensions List. Use the controls listed in Table 2-2 to move files in or out of the Selected Extensions List, as needed.



Table 2-2: Controls on Select File Extensions Screen

Control Description

>> Moves all files from the Available Extensions List to the Selected Extensions List.

> Moves the selected files from the Available Extensions List to the Selected Extensions List. To select multiple files, use the standard Windows controls for selecting multiple files. (Holding Shift while selecting files selects the range of files between your first and last selection, and holding CTRL while selecting files selects only the specific files you click on.)

< Moves the selected files from the Selected Extensions List to the Available Extensions List. Use this selection to remove files that you do not want supported by the Gateway for SharePoint. To select multiple files, use the standard Windows controls for selecting multiple files. (Holding Shift while selecting files selects the range of files between your first and last selection, and holding CTRL while selecting files selects only the specific files you click on.)

<< Moves all files from the Selected Extensions List to the Available Extensions List. Use this selection to clear the list of supported files and begin again.

Based on the selections made on this screen, the Windows Registry keys listing the supported files for this installation are defined. Once you have completed the wizard, you can modify the file types selected by modifying the following key in the Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\LQMI.LMSG.IrmProtector.Impl\

>> For details on changing the file types supported by the Gateway for SharePoint, see Modifying the File Types Supported by the Gateway for SharePoint on page 2-15.

12. When you are satisfied with the file extension settings, select Next.

13. The Ready to Install Liquid Machines Gateway for SharePoint screen displays (see Figure 2-8).

Figure 2-8: Ready to Install Liquid Machines Gateway for SharePoint



You are now ready to start the installation of the Gateway for SharePoint.

Select:

Install, to begin the installation,

Back, to review or change your installation settings, or

Cancel, to exit the wizard.

14. When the installation is complete, the completed screen (see Figure 2-9).

Figure 2-9: Completed the Gateway for SharePoint Setup Wizard Screen

15. Click Finish to exit the Setup Wizard.

Notifying the Site Owner of the Gateway for SharePoint When the installation is complete, contact the SharePoint Site Owner to advise him or her that the installation is complete and provide him or her with a listing of the files supported for this particular installation.

>> A sample email that you can use as a model is provided in Appendix A: Sample Email to Notify the Site Owner of the Gateway for SharePoint.



Uninstalling the Gateway for SharePoint You can uninstall the Gateway for SharePoint using the Add or Remove Programs selection from the Windows Control Panel. (You can also re-run the installation program to uninstall the Gateway for SharePoint. When you re-run the installation program, an option to uninstall the program displays.)

NOTE: Before uninstalling the Gateway for SharePoint, please consider the following ramifications:

When you uninstall the Gateway for SharePoint, after it has been used, the SharePoint reverts back to native IRM protection.

If you remove the Gateway for SharePoint, files of the file types that were previously protected by the Gateway for SharePoint may not be protected when they are downloaded and you may not be able to upload these files. Also, the files may behave like files with protections that were added outside of SharePoint (incompatible protections).

>> For information on unprotecting files that were previously protected by the Liquid Machines Gateway for SharePoint, see Chapter 3: Troubleshooting on page 3-1.

To uninstall the Gateway for SharePoint from the Control Panel:

1. Select Add or Remove Programs (or Programs and Features in Microsoft Windows Server 2008) from the Control Panel.

NOTE: All screenshots in this section apply to Windows Server 2003. The procedure is the same for both Widows 2003 and Windows 2008, although the screens may be slightly different.

2. Select Liquid Machines Gateway for SharePoint in the list of currently installed programs (see Figure 2-10).

Figure 2-10: Locate the Liquid Machines Gateway for SharePoint Application



3. Select Remove. You are asked to confirm that you want to remove the application (see Figure 2-11).

Figure 2-11: Confirm That You Want to Remove the Application

4. Select Yes. The application is removed. A progress bar displays indicating the progress of the removal (see Figure 2-12).

Figure 2-12: The Progress Bar Showing the Removal of the Gateway for SharePoint



Modifying the File Types Supported by the Gateway for SharePoint You can modify the list of file types supported by the Gateway for SharePoint by editing the following key in the Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\LQMI.LMSG.IrmProtector.Impl\

To edit the Registry key:

1. Click on the Start menu and select Run.

2. In the Run dialog that displays, type regedit (see Figure 2-13) and click OK.

Figure 2-13: Run Dialog Box

The Registry Editor screen displays.

3. Open the string value Extensions and view the list of file extensions. To add or modify the file extensions, edit the string value.

NOTE: The file extensions to be protected should be included in this string value separated only by commas. Do not insert spaces between the file extensions and do not insert periods (.) before each file extension.

The following are examples of valid and invalid strings:

VALID STRING: "txt,csv,pdf,doc"

INVALID STRING: "csv, txt, pdf, doc,"

INVALID STRING: ".txt,.csv,.pdf,.doc,"

Entering an invalid string in this Registry key will result in a failure of the Gateway for SharePoint to protect the desired file extensions.



4. If you must edit the registry because certain file extensions were added (or removed) the changes will not take effect until you reset IIS as follows:

Open a command prompt.

Type iisreset and press Enter.

5. After IIS has been reset, the user must close and restart their browser to ensure that the changes will take place.

NOTE: If you prefer not to edit the Registry, you can change the list of file types supported by re-running the installer and selecting the correct set of file types to be supported.



Chapter 3: Troubleshooting

This chapter describes how to troubleshoot problems with installation or other problems reported by the SharePoint Site Owner.

Topics included in this chapter are:

Introduction

Common Problems



Introduction You can view the Event Log or the Error Logs to locate possible problems if the Gateway for SharePoint is not operating properly. If the events or errors are related to the Liquid Machines Gateway for SharePoint, you can attempt to correct the problem, as described in this chapter.

If you are unable to correct the problem, contact Liquid Machines technical support and provide the technician with the information provided from the Event Log or error listings to aid in resolving the issue.

The Event Log is displayed from the Windows Event Viewer.

SharePoint gathers all logs in the following location:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

Log entries related to the Gateway for SharePoint are written to that location in the Enterprise Management Rights category.

>> For information on common problems with the installation of the Gateway for SharePoint, see Common Problems on page 3-3.



Common Problems Table 3-1 lists some common problems, their possible causes, and suggested actions.

Table 3-1: Common Problems for the Gateway for SharePoint

Troubleshooting Scenarios and Possible Cause(s)

Suggested Actions

You wish to change the account under which the Content Protection Service runs.

Possible Cause(s):

The service user account information was entered incorrectly.

The service user account was removed from the domain.

Verify that the User Name and Password for the Service User are correct. The Service User account can be specified using the Component Services Management Console as follows:

From the Start button, select Run.

Type dcomcnfg.exe and click OK.

Select Expand Component Services >> Computers >> My Computer >> COM+ Applications.

Right-click on LQMI Content Protection Service and then select Properties >> Identity Tab.

Specify the User Name and Password for the Service User account on the Identity tab.

Check the rights of the user in the SharePoint library or list, and on the SharePoint Server machine.




Suggested Actions

The following errors may appear in the Windows Application Event Log:

Source: Enterprise Rights Management Message: Can't compose ACL, list <list-id>is missing: System.Data.SqlClient.SqlException: Cannot open database "<content database name>" requested by the login. The login failed. Login failed for user '<service account name>'.

Source: Windows SharePoint Services 3 Message: Insufficient SQL database permissions for user <service account name> in database “<content database name>” on SQL Server instance „<SQL server instance name>'. Additional error information from SQL Server is included below. EXECUTE permission denied on object 'proc_GetTpWebMetaDataAndListMetaData', database <content database name>', schema 'dbo'.

Possible Cause(s):

The service account cannot access the SharePoint object model because it does not have access to the content database.

Grant the service account read/write access to the content database on the SQL server.




Suggested Actions

Service accounts require access to the administrative object model. If the service account does not have permissions to access some part of that model, the following messages may appear in the Windows Application Event log:

Source: Enterprise Rights Management Message: Exception occurred: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Possible Cause(s):

The service account cannot access the SharePoint object model because it does not have the SharePoint administrative rights to do so.

The service account must be named as a site collection administrator and must have owner permissions on all contained lists on which IRM is enabled (if not inheriting permissions from the site collection).

The following message may appear in the Windows Security Event Log:

Keywords: Audit Failure Source: Microsoft Windows Security Auditing Task Category: Logon Details: An account failed to log on. (The account name listed will be the service account)

OR

The following message may appear in the Windows System Event Log:

Source: DistributedCOM EventID: 1004 General: DCOM got error "1326" and was unable to logon <service account name> in order to run the server: {4425BD94-9B1E-48D0-B0B6-A74AC141C5AA}

Possible Cause(s):

The service has failed to start because the service account could not log on to the SharePoint Server. Reasons for this include:

Bad credentials.

OR

The account was disabled, locked out or deleted.

If the account has been disabled or locked out, the system administrator must re-enable the account. If the account does not exist, or if it is no longer valid to use the original service account credentials, the credentials can be changed by setting the identity of the LQMI Content Protection Service COM+ application using the Component Services Management Console.




Suggested Actions

One or more file types that you expect to be protected are not being protected.

Possible Cause(s):

IRM is not enabled.

OR

Files are being opened from the cache.

OR

The file extension for the selected file type was not selected during the installation of the Gateway for SharePoint.

Try the following actions:

Verify that IRM is enabled for the server.

To verify that IRM is enabled server, the SharePoint Site Owner (or any other user with Full Control access) can perform the following steps:

Open SharePoint.

Select the library of interest.

Open the Settings menu and select Document Library Settings. The Customize Selected Library or List screen displays.

If the Information Rights Managements selection appears in the Permissions and Management menu, then IRM has been enabled. If the Information Rights Managements selection does not appear, refer to the Microsoft SharePoint documentation listed in Related Documents on page vi for information on how to enable IRM.

If IRM is enabled for the server, verify that IRM is enabled for the SharePoint library or list containing the file in question.

To verify that IRM is enabled for the selected library or list, the SharePoint Site Owner (or any other user with Full Control access) can perform the following steps:

Open SharePoint and select the library of interest.

Open the Settings menu and select Document Library Settings. The Customize Selected Library or List screen displays.

Select Information Rights Managements from the Permissions and Management menu and select the permissions you wish to grant users of the library or list.

If IRM is enabled, but the file is still unprotected, verify that the file is still unprotected when it is downloaded from its original source by performing the following steps:

Clear your Internet cache.

Close and then restart your Browser.

Open the file again.

Continued on next page…




Suggested Actions

From previous page…

If the file remains unprotected after performing the actions above, check the Registry on the SharePoint Server to verify that the extension for the file in question has been included in the installation.

Open the Registry Editor and navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Shared Tools\Web Server Extensions\LQMI.LMSG.IrmProtector.Impl\

Open the string value Extensions and view the list of file extensions. If the file extension is not listed, you can add it by editing the string value to include it.

If the file extension is missing, add it as described in Modifying the File Types Supported by the Gateway for SharePoint on page 2-15.

Files are not protected when they are downloaded and files either will not upload or they upload with protections from outside of SharePoint.

This behavior may be the result if you have downloaded the files and then the file type was removed from the list of supported file extensions for this installation of the Gateway for SharePoint. You may also see this behavior if files were downloaded, then the Gateway for SharePoint was uninstalled.

To determine the cause of the problem:

Verify that either the file type was removed from the Gateway for SharePoint, or the Gateway for SharePoint was uninstalled.

If the file type has been removed or the Gateway for SharePoint has been uninstalled, there are four methods (using an RMS-enabled client or another tool) to unprotect documents that had been previously protected by the Gateway for SharePoint.

Method 1: For Users with Full Rights to the Document. If you have full rights to the document, then simply open the document in the native application and remove the protection. If the document is a native Office document (Word, Excel or PowerPoint), use Office 2003 or 2007 with or without the LMDC Client, just as you would work with any other protected document. Older versions of Office will require that you have the LMDC Client or LM Viewer.

If the document is not native Office, then you will need the LMDC Client installed to unprotect the document.

NOTE: You cannot work with protected documents, either with or without the Gateway for SharePoint, if the proper application software is not installed.

Continued on next page…




Suggested Actions

From previous page…

Method 2: For Users Who Do Not Have Full Rights. If you do not have full rights, then any user who DOES have full rights can unprotect the documents. This can be done using Method 1 above, but by a different user.

A user has full rights if he or she is an "Owner" in a library or list, or if the user under which the Gateway account was running.

Method 3: Imassignpolicy (if you have purchased the LMDC client). Using lmassignpolicy, you can supply credentials of any Full Rights user (see above) and use the "unprotect" flag to unprotect any files that have been downloaded to one's desktop or network share. An example of how to use lmassignpolicy follows:

If necessary, unzip the contents of lmassignpolicy.zip to your desktop.

Open a command prompt and navigate to the folder containing lmassignpolicy.

Type: lmassignpolicy [email protected] password=password -u c:\file-location-and-file-name

If the user has full rights to the documents, then there is no need to supply the username and password. You can simply enter the following on the command line:

lmassignpolicy -u c:\file-location-and-file-name

NOTE: The user can also use wildcards to unprotect several files at once:

lmassignpolicy -u "c:\My Documents\SharePoint Drafts\*"

NOTE: If the username and password are used, the username and password are in CLEAR TEXT (visible for all to see).

Method 4: lmunsecure (if you have purchased the LMDC Client). The lmunsecure tool allows you to unprotect multiple documents at once. To use lmunsecure for RMS protected documents, supply the credentials of an RMS SuperUser. For more information, refer to the lmunsecure documentation.

mailto:[email protected]


Liquid Machines, Inc. Page A-1

Appendix A: Sample Email to Notify the Site Owner of the Gateway for SharePoint

This appendix provides a sample email that can be used to notify the SharePoint Site Owner that the installation of the SharePoint for Gateway is complete.

To: SharePoint Site Owners

From: IT Department Responsible for Installing the Liquid Machines Gateway for SharePoint

Subject: Liquid Machines Gateway for SharePoint Installation Complete

The Gateway for SharePoint has been installed on the following front end web servers:

MachineName_1

MachineName_2

MachineName_3

All three machines have been set up to enable IRM protection for the following commonly used file types:

doc ppsx xla docm ppt xls docx pptx xlam dot pot xlsm dotm potm xlsx dotx potx xltx pdf pps xps ppsm

You can set up IRM protection for a document library or list by selecting the Settings menu, then selecting Document Library Settings, and then selecting Information Rights Management. For more information on using the Gateway for SharePoint, see the Liquid Machines Gateway for SharePoint User’s Guide.

If you need additional file types protected, contact IT to request such changes.

If you have any questions regarding the installation, please contact IT at X1234.

Thank you,

John Doe

Acme Corp IT Department


Liquid Machines, Inc. Page A-2


Liquid Machines, Inc. Page B-1

Appendix B: Mapping SharePoint Permissions to IRM Rights

This appendix describes how SharePoint rights are mapped to IRM rights.

Previous examples in this document have assumed that your organization is using the default SharePoint Groups and SharePoint Permission Levels. If that is not the case, then the following section will help you to understand how permissions are mapped and how use licenses are constructed. For additional details on customizing SharePoint Groups and SharePoint Permission Levels, see your System Administrator or documentation from Microsoft.

As described in Information Rights Management on SharePoint on page 1-2, when documents are accessed from an IRM-enabled library or list, an IRM license is generated that includes all authorized users, with each user‟s specific permissions including a combination of the IRM rights specified on the library‟s or list‟s Information Rights Management settings page, and some additional IRM rights derived from the user‟s SharePoint Permissions.

There are 33 SharePoint Permissions, six of which grant user permissions which are mapped to IRM Permissions. Table B-1 describes how these six SharePoint user permissions map to IRM Permissions.

Table B-1: SharePoint User Permissions that Map to IRM Permission

Office SharePoint Server 2007 Permissions IRM Permissions

1. Manage Permissions

2. Manage Web

Full control, as defined by the client. This generally allows a user to read, edit, copy, save, and modify the permissions of rights-managed content.

3. Edit List Items,

4. Manage List

5. Add and Customize Pages

Read, edit, copy, and save permissions. You can optionally enable users with these permissions to print documents from the library or list.

6. View List Item Read permissions. A user can read the document, but cannot copy or update its content. You can optionally enable users with view list item permissions to print documents from the library or list.

Other No other permissions map to IRM permissions.



Users may be assigned SharePoint Permissions as a result of being assigned to a default or customized Permission Level or by being assigned to a SharePoint Group that is assigned to a Permission Level.

For example, the default setting for the Contribute SharePoint Permission level includes the Edit List Items and View List Item SharePoint permissions, but none of the others listed above. When mapped to IRM permissions, the user license will include the most permissive set of IRM permissions of all of the SharePoint Permissions that the user has.

In this example, Edit List Items gives the user read, edit, copy and save permissions, but View List Item only gives the user Read permission. Since the user has both Edit List Items and View List Item SharePoint permissions, the user will receive the most permissive IRM permissions of the two (read, edit, copy, and save permissions).

If the SharePoint Permission level has been customized, you can derive the user‟s IRM permissions by understanding the mapping between SharePoint Permissions and IRM permissions in Table B-1.

SharePoint Groups provide an easy way to associate a set of users with a SharePoint permission level. Like Permission Levels, SharePoint Groups may be customized by your organization. Table B-2 describes the default mappings and can be used together with Table B-1 to help you define the mapping at your organization, if you do not use SharePoint‟s default settings.



Table B-2: Default Mappings

SharePoint Default Definitions

SharePoint Permission Levels Map to Many Individual SharePoint Permissions Including Those Below, Which are Mapped to IRM Permissions

IRM Permissions derived from SharePoint Permission

List Permissions Site Permissions

Site Permissions SharePoint Groups

SharePoint Permission Level for this SharePoint Group

Ma

nag

e L

ists

Ed

it Ite

ms

Vie

w I

tem

s

Ma

nag

e

Perm

issio

ns

Ma

nag

e W

eb

Sit

e

Ad

d &

Cu

sto

miz

e

Pag

es

<Site> Owner

Users who create and manage sites.

Full Control Read

Edit

Copy

Save

Read

Edit

Copy

Save Read Full

Control Full

Control

Read

Edit

Copy

Save Full Control

<Site> Members

Collaborative users who add and modify content.

Contribute

none

Read

Edit

Copy

Save Read none none none

Read

Edit

Copy

Save

<Site> Visitors

Users who can access, but cannot modify content.

Read

none none Read none none none Read

Approvers

Used in workflows.

Approve

none

Read

Edit

Copy

Save Read none none none

Read

Edit

Copy

Save

Hierarchy Managers Users who create and manage sites. May be delegated down from higher level person

Manage Hierarchy Read

Edit

Copy

Save

Read

Edit

Copy

Save Read Full

Control Full

Control

Read

Edit

Copy

Save Full Control

Restricted Readers

Users who are more restricted than Visitors. They cannot see version history of minor versions, if major and minor versions exist.

Restricted Read

none none Read none none none Read

Quick Deploy Users Style Resource Readers

Designed to give access to a specific list, library, item, or document, without giving access to the entire site.

Limited Access

◄ ▬ No permissions that map to IRM ▬ ► none

There is no default SharePoint Group with the Design Permission Level

Design Read

Edit

Copy

Save

Read

Edit

Copy

Save Read none none

Read

Edit

Copy

Save

Read

Edit

Copy

Save


Liquid Machines, Inc. Index-1

Index

.

.NET Framework 3.5, 2-2

A

Audience, v

B

Book conventions, v

C

Collaboration outside of SharePoint, 1-6

Creating service user account, 2-3

D

Disabling user account control, 2-4

Documents SharePoint, vi

F

File types modifying types supported by installation, 2-15 selecting, 2-9 supported, 1-4, 2-10

G

Gateway for SharePoint features, 1-4 installation wizard, 2-5 installing, 2-1 notifying site owners of new capabilities, 2-12,

A-1 system requirements, 2-2 uninstalling, 2-13 user roles, 1-7 workflow, 1-7

I

Information Management Rights. See IRM Installation

prerequisites for, 2-2 Installation wizard

Gateway for SharePoint, 2-5 Installing

Gateway for SharePoint, 2-1, 2-5 IRM

on SharePoint, 1-2 permissions mapped from SharePoint, B-1

L

Liquid Machines Gateway for SharePoint. See Gateway for SharePoint

LM Gateway for SharePoint. See Gateway for SharePoint

M

Mapping permissions, 1-10, B-1 Modifying

selected file types, 2-15 MOSS 2007, 2-2

P

Permissions default mapping, B-3 mapping, 1-10, B-1 mapping SharePoint permissions to IRM, B-1

Prerequisites for installation, 2-2

R

Requirements software, 2-2 system, 2-2

Roles for Gateway for SharePoint, 1-7


Liquid Machines, Inc. Index-2

S

Selecting file types, 2-9

Service user account creating, 2-3

SharePoint collaboration outside of, 1-6 defined, 1-2 documents, vi IRM, 1-2 mapping permissions to IRM, B-1

Supported file types, 1-4 System requirements, 2-2

T

Troubleshooting, 3-1

U

Uninstalling Gateway for SharePoint, 2-13

User account control turning off, 2-4

Using this Manual, vi

W

Workflow for Gateway for SharePoint, 1-7

WSS 3.0, 2-2