OpenText™ Enterprise Connect and

OpenText™ Office Editor

Installation Guide

This guide explains how to install and configure Enterprise

Connect Framework, Office Editor, and Enterprise Connect
Plug-in for Content Server.

NGDCORE210200-IGD-EN-01
OpenText™ Enterprise Connect and OpenText™ Office Editor
Installation Guide
NGDCORE210200-IGD-EN-01
Rev.: 2021-Feb-19
This documentation has been created for OpenText™ Enterprise Connect and OpenText™ Office Editor CE 21.2.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 Planning for Enterprise Connect ............................................. 9
1.1 Introducing Enterprise Connect .......................................................... 9
1.1.1 Enterprise Connect Client Integrations .............................................. 11
1.1.1.1 Outlook Integration .......................................................................... 11
1.1.1.2 Explorer Integration ......................................................................... 14
1.1.1.3 Office Integrations ........................................................................... 15
1.1.1.4 Acrobat Integration .......................................................................... 16
1.1.1.5 IBM Notes Integration ...................................................................... 16
1.1.1.6 Extended Integration ....................................................................... 17
1.1.2 Enterprise Connect Viewer .............................................................. 17
1.1.3 Authentication and Security ............................................................. 17
1.1.4 Offline Support ................................................................................ 18
1.1.5 OpenText Office Editor .................................................................... 19
1.1.6 OpenText Enterprise Connect Plug-in for Content Server .................. 20
1.1.7 Extending Enterprise Connect .......................................................... 21
1.2 System Requirements ..................................................................... 21
1.2.1 Server Requirements ...................................................................... 22
1.2.2 Client and Integration Requirements ................................................. 22
1.2.3 Citrix® Requirements ....................................................................... 23

2 Installing Enterprise Connect Framework and Office

Editor ........................................................................................ 25
2.1 Installing the Framework Using Setup ............................................... 25
2.2 Installing the Framework Silently ...................................................... 28
2.3 Connecting Enterprise Connect to Content Server ............................. 29
2.3.1 Editing the Registry to Establish the Connection ................................ 29
2.3.2 Using the Manage Plug-ins Dialog Box to Establish the Connection ... 33
2.4 Modifying or Reinstalling the Framework .......................................... 34
2.5 Removing the Framework ................................................................ 35
2.6 Upgrading the Framework ............................................................... 35
2.7 Installing a Stand-alone Version of Office Editor ................................ 36

3 Configuring System Options .................................................. 39

3.1 Configuring Authentication ............................................................... 39
3.1.1 Determining the Authentication Method ............................................ 39
3.1.1.1 Using Content Server Accounts ....................................................... 40
3.1.1.2 Using Windows Credentials ............................................................. 40
3.1.1.3 Using SSL Client Certificates ........................................................... 40
3.1.1.4 Using Web Access Management Systems ........................................ 41
3.1.2 Using Content Server Domains ........................................................ 42
3.1.3 Managing Enterprise Connect Credential Storage Options ................. 42

NGDCORE210200-IGD-EN-01 Installation Guide iii

Table of Contents

3.1.3.1 Configuring Storage of Enterprise Connect Credentials ..................... 42

3.1.3.1.1 To Configure How Enterprise Connect Credentials Are Stored ........... 43
3.1.3.2 Editing the Registry to Prevent Enterprise Connect from Storing
Credentials ..................................................................................... 43
3.1.4 Requiring Users to Sign In with a Browser ........................................ 44
3.1.5 Preventing Authentication When Content Server Connection
Attempts are Redirected .................................................................. 45
3.2 Optimizing Performance .................................................................. 46
3.3 Making Enterprise Connect Accessible from the Content Server
Web Interface ................................................................................. 46
3.3.1 To Make Enterprise Connect Accessible from the Content Server
Web Interface ................................................................................. 46
3.4 Enabling the Mail as attachment Command on the Send to Menu ...... 47
3.4.1 To Enable the Mail as attachment Command on the Send to Menu .... 47
3.5 Supporting Previous Versions of Enterprise Connect Framework ....... 48
3.5.1 To Configure Supported Versions of the Enterprise Connect
Framework ..................................................................................... 48
3.6 Working with Additional Modules ...................................................... 49
3.6.1 Using Remote Cache ...................................................................... 49
3.6.1.1 Specifying Link Paths ...................................................................... 50
3.6.1.1.1 To Specify Link Paths ...................................................................... 50
3.6.2 Using Records Management to File Emails as Records ..................... 50
3.7 Setting Timeouts for HTTP Requests ............................................... 51
3.8 Managing Content Server Browser Extensions .................................. 52
3.8.1 Enabling Browser Extensions ........................................................... 52
3.8.1.1 Installing the Browser Extension for Microsoft Edge ........................... 53
3.8.1.2 Adding Office Editor to the List of Allowed Native Messaging Hosts
in Chrome ....................................................................................... 56
3.8.2 Configuring Domain Verification for Browser Extensions .................... 56

4 Configuring Navigation and Display Options ....................... 59

4.1 Configuring the Enterprise Connect Tree Structure and List Pane ...... 59
4.1.1 To Configure the Tree Structure and List Pane .................................. 60
4.2 Modifying Labels ............................................................................. 61
4.2.1 Modifying Menu and Tree Labels ..................................................... 61
4.2.2 Modifying Language-Specific Labels ................................................ 62
4.3 Displaying Additional Columns ......................................................... 63
4.3.1 Configuring Column Displays ........................................................... 64
4.3.1.1 To Configure Column Displays ......................................................... 65
4.4 Configuring Reading Pane Options .................................................. 66
4.4.1 Selecting a Viewer for the Reading Pane .......................................... 66
4.4.1.1 To Select a Viewer .......................................................................... 67
4.4.2 Setting the Default Reading Pane Display ......................................... 67

iv OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 Table of Contents

4.4.3 Displaying Tabs in the Reading Pane ............................................... 68

4.5 Managing Context Menu and Ribbon Commands .............................. 69
4.5.1 Configuring Enterprise Connect Context Menu Items ......................... 69
4.5.1.1 To Show or Hide Enterprise Connect Context Menu Items ................. 70
4.5.2 Configuring the Advanced Context Menu .......................................... 70
4.5.2.1 To Configure the Advanced Context Menu ........................................ 72
4.5.3 Configuring Context Menu Actions ................................................... 72
4.5.3.1 To Configure the Context Menu ....................................................... 74
4.5.4 Launching Context Menu Commands in a Full Browser ..................... 74
4.5.4.1 To Launch Context Menu Commands in a Full Browser ..................... 75
4.6 Displaying Hidden Items in Enterprise Connect ................................. 76
4.6.1 To Display Hidden Items in Enterprise Connect ................................. 76
4.7 Managing Folders ........................................................................... 76
4.7.1 Setting the Folder Cache Timeout Value ........................................... 76
4.7.2 Limiting the Number of Folders Displayed in the Tree Structure ......... 77
4.8 Configuring Language Settings ........................................................ 79
4.8.1 Changing the Enterprise Connect Language Setting .......................... 79
4.8.2 Changing the Office Editor Language Setting .................................... 80

5 Configuring Editing Options .................................................. 81

5.1 Using Office Editor .......................................................................... 81
5.1.1 Specifying the Location of the Document Cache ................................ 82
5.1.1.1 Configuring the Document Cache Location to Support Citrix
Session Pools ................................................................................. 84
5.1.2 Configuring the My Working Documents List Dialog Box .................... 86
5.1.3 Configuring Office Editor Logging ..................................................... 87
5.1.4 Specifying the Frequency of the Notification Message ....................... 88
5.1.5 Configuring How Office Editor Interacts with Application Processes .... 89
5.1.5.1 Specifying Processes To Ignore When Syncing Documents ............... 90
5.1.5.2 Removing the Ability to Edit Specific File Types ................................ 91
5.1.5.3 Specifying Locking and Non-locking Applications and File Types ....... 93
5.1.5.4 Examples of using IgnoredProcesses, EditorBehavior, and
LockableApplications ....................................................................... 96
5.1.6 Enabling Office Editor to Store Credentials ....................................... 97
5.1.7 Customizing the Office Editor Installation or Upgrade Message .......... 98
5.1.8 Configuring Double-click Behavior in the My Working Documents
List Dialog Box ................................................................................ 98
5.1.9 Disable the creation of the Office Editor desktop shortcut ................... 99
5.1.10 Configuring Editor Precedence and Availability Options ..................... 99
5.1.11 Redirecting OpenText™ WebDAV URLs ........................................ 102
5.1.12 Configuring Link Rewriting ............................................................. 104
5.2 Configuring the Upload Mode for Edited Documents ........................ 105
5.3 Configuring Double-click Actions for Documents ............................. 108

NGDCORE210200-IGD-EN-01 Installation Guide v

Table of Contents

5.3.1 To Configure Double-click Actions for Documents ........................... 109

5.4 Forcing the Use of the Enterprise Connect Open and Save As
Dialog Boxes ................................................................................ 109
5.4.1 Forcing the Use of the Enterprise Connect Open Dialog Box ............ 110
5.4.2 Forcing the Use of the Enterprise Connect Save Dialog Box ............ 111
5.5 Configuring Extended Integration ................................................... 112
5.5.1 Specifying Which Applications Support Extended Integration ........... 112
5.5.2 Limiting the Number of Items Displayed in Extended Integration
Open and Save As Dialog Boxes ................................................... 114
5.6 Mapping MIME Types to File Extensions ........................................ 115
5.7 Enabling Users to Insert Document Properties in Office ................... 115
5.7.1 Configuring Insertable Document Properties Settings ...................... 116
5.7.1.1 To Configure Insertable Document Properties Settings .................... 117
5.7.2 Example of Configuring an Insertable Document Property for
Enterprise Connect ....................................................................... 118

6 Configuring Email Handling Options ................................... 123

6.1 Configuring Settings for Capturing Email Attachments, Duplicate
Emails, and Email Subtypes .......................................................... 123
6.1.1 To Configure Settings for Capturing Email Attachments ................... 125
6.2 Defining Email Naming Conventions ............................................... 126
6.2.1 To Define The Message Properties to Use in Email Names ............. 127
6.2.2 To Define the Separator Strings Between Message Properties ......... 128
6.2.3 To Remove Strings from Email Names ........................................... 128
6.2.4 To Specify the Date and Time Formats in Email Names .................. 128
6.2.5 To Handle Emails with the Same Name .......................................... 130
6.2.6 To Specify Naming Conventions Used When Adding Emails from
Windows Explorer ......................................................................... 131
6.3 Handling Email Attachments With the Same Name ......................... 131
6.3.1 To Configure How Enterprise Connect Handles Email Attachments
With the Same Name .................................................................... 132
6.4 Configuring Outlook ...................................................................... 133
6.4.1 Configuring the Enterprise Connect Add-ins for Outlook to Remain
Enabled ........................................................................................ 133
6.4.2 Using the Outlook Viewer Instead of the Enterprise Connect Viewer . 134
6.4.3 Hiding Options in Outlook .............................................................. 135
6.4.4 Configuring Outlook to Use Native Folder Icons .............................. 137
6.4.5 Specifying Settings for the Easy Access Pane ................................. 137
6.4.6 Enhancing Performance When Emails are Added to Content Server
in Outlook ..................................................................................... 140
6.4.7 Configuring Outlook Indicator Columns ........................................... 141
6.4.7.1 To Configure Outlook Indicator Columns ........................................ 142
6.4.8 Adding Quick Steps to HKEY_LOCAL_MACHINE ........................... 142

vi OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 Table of Contents

6.4.9 Specifying a default starting location for the Send and Save and
Copy/Move to Enterprise Connect dialog boxes .............................. 144
6.5 Configuring Enterprise Connect to Work with Email Archiving for
Microsoft Exchange ....................................................................... 145
6.5.1 Editing Email Archiving Settings on the Enterprise Connect
Administration Pages .................................................................... 146
6.5.1.1 Configuring Email Archiving ........................................................... 146
6.5.1.1.1 To Configure Email Archiving Settings ............................................ 147
6.5.2 Specifying the Content Server Plug-in for Email Archiving ................ 148
6.5.3 Using Enterprise Connect to Archive Emails ................................... 149
6.5.4 Configuring How Enterprise Connect Moves or Copies Email Stubs
into Content Server ....................................................................... 150
6.5.5 Specifying Outlook Items for Which Archiving Is Not Attempted ........ 152
6.6 Configuring Double-click Actions for Compound Emails ................... 153
6.6.1 To Configure Double-click Actions for Compound Emails ................. 153
6.7 Configuring the Enterprise Connect Integration with IBM Notes ........ 153
6.7.1 Modifying IBM Notes Labels .......................................................... 154
6.7.2 Enabling the Attach Documents Command in IBM Notes ................. 154
6.7.3 Specifying a Format for IBM Notes Emails ...................................... 156
6.7.3.1 To Specify a Format for IBM Notes Emails ...................................... 156

7 Configuring Search Options ................................................. 157

7.1 Configuring Search Profiles ........................................................... 157
7.1.1 To Configure Search Profiles ......................................................... 159
7.2 Specifying the Number of Search Results on Each Page ................. 160
7.2.1 To Specify the Number of Search Results On Each Page ................ 160
7.3 Specifying Quick Search Location Modifiers .................................... 160
7.3.1 To Specify Quick Search Location Modifiers ................................... 161
7.4 Specifying the Default Advanced Search Location ........................... 161
7.4.1 To Specify the Default Advanced Search Location .......................... 161
7.5 Using Quick Search ...................................................................... 162
7.6 Setting Search Columns ................................................................ 162
7.7 Displaying the Score Column in Search Results .............................. 164
7.7.1 To display the Score Column in Search Results .............................. 164

8 Configuring Copy and Move Options .................................. 165

8.1 Configuring When Users Are Required to Provide Metadata ............ 165
8.1.1 Configuring Content Capture Options ............................................. 166
8.1.1.1 To Configure Content Capture Settings .......................................... 167
8.1.2 Enabling MIME Type Category Mappings ....................................... 168
8.2 Configuring the Copy/Move Command ........................................... 168
8.2.1 To Specify Where Users Can Access the Copy/Move Command ..... 168
8.3 Configuring Object Types When Dragging Folders .......................... 169

NGDCORE210200-IGD-EN-01 Installation Guide vii

Table of Contents

8.3.1 To Configure Object Types When Dragging Folders ........................ 169

8.4 Configuring the Send to Desktop location Command ....................... 170
8.4.1 Specifying Which Subtypes Can Be Sent to the Desktop ................. 170
8.4.1.1 To Specify Which Subtypes Can Be Sent to the Desktop ................. 170
8.4.2 Setting a Maximum File Size for Downloads to the Desktop ............. 171
8.4.3 Specifying When the Download to Desktop XML Results File is
Created ........................................................................................ 172
8.5 Filtering File Types Copied to Enterprise Connect From the Local
File System ................................................................................... 172
8.6 Mapping Custom Subtypes to File Extensions ................................. 173
8.6.1 To Map a Custom Subtype to a File Extension ................................ 173
8.7 Controlling the Name of Content Server Shortcuts Created by
Dragging ...................................................................................... 174
8.7.1 To Control the Name of Content Server Shortcuts Created by
Dragging ...................................................................................... 174
8.8 Working with Briefcases ................................................................ 174
8.8.1 Adding Annotations to Briefcases ................................................... 175
8.8.1.1 To Add Annotations to Briefcases .................................................. 175
8.9 Specifying Types of Containers Available in Enterprise Connect
Save As ........................................................................................ 176
8.9.1 To Specify Types of Containers Available in Enterprise Connect
Save As ........................................................................................ 176
8.10 Enabling the Drag and Drop Panel ................................................. 177
8.10.1 To Enable the Drag and Drop Panel ............................................... 178

9 Configuring Offline Options ................................................. 179

9.1 Specifying Which Subtypes Can Be Taken Offline ........................... 179
9.1.1 To Specify Which Subtypes Can Be Taken Offline .......................... 179
9.2 Configuring Offline Mode ............................................................... 180
9.3 Enabling Offline Search ................................................................. 182

10 Registry Setting Reference ................................................... 185

10.1 Registry Settings for Enterprise Connect Framework ....................... 185
10.2 Registry Settings for Office Editor ................................................... 194
10.3 Configuring Plug-in Definitions ....................................................... 197

11 Troubleshooting .................................................................... 201

11.1 Viewing the Log Files .................................................................... 201
11.2 Enabling the Outlook Add-in .......................................................... 203
11.3 Clearing the Client Cache .............................................................. 203
11.4 Resolving Content Server Connection Issues .................................. 204
11.5 Resolving Issues with Saving Office Documents to Content Server .. 204
11.6 Displaying the Enterprise Connect Menu in Windows Explorer ......... 204
11.7 Enabling Macros in the Office Startup Folder .................................. 205

viii OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 1
Planning for Enterprise Connect

This chapter covers the following topics:

• Introducing Enterprise Connect.

• System requirements.

1.1 Introducing Enterprise Connect

OpenText Enterprise Connect provides integrated, interactive access to content and
functionality from supported Enterprise systems. Using Enterprise Connect, you can
work with content from various repositories directly in the applications that you use
on a daily basis, including Windows® Explorer, Microsoft® Outlook®, and Microsoft
Office applications such as Microsoft Word and Microsoft® Excel®.

Enterprise Connect consists of the following main components:

• Framework.
• OpenText™ Content Server plug-in and module.
• Integrations.
• OpenText™ Office Editor.

Figure 1-1 shows the main components of Enterprise Connect.

NGDCORE210200-IGD-EN-01 Installation Guide 9

Chapter 1 Planning for Enterprise Connect

Figure 1-1: Enterprise Connect Components

The Enterprise Connect Framework is installed on all client systems. It manages the
interaction between Content Server and the integrations.

Integrations let users work with Enterprise Connect through applications on their
desktop. Enterprise Connect supports integrations with Windows Explorer and
Microsoft Outlook, with Microsoft Office applications including Word and Microsoft
Excel, with Adobe® Acrobat®, with IBM® Notes®, and with additional applications
including Notepad, Corel® WordPerfect®, and Adobe® Reader®. Each integration
exposes Enterprise Connect functionality in the application user interface. During
installation, you can choose the integrations you want to make available on the
client.

10 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.1. Introducing Enterprise Connect

1.1.1 Enterprise Connect Client Integrations

You can integrate Enterprise Connect with the following applications:

• Microsoft Outlook
• Windows Explorer
• Microsoft Office (Word, Excel, Microsoft® PowerPoint®, Microsoft® Project, and
Microsoft® Visio®)
• Adobe Acrobat
• IBM Notes
• Extended support for additional applications including Notepad, Adobe Reader,
and Corel WordPerfect

For more information about using the client integrations, see OpenText Enterprise
Connect - User Getting Started Guide (NGDCORE200400-UGD). You can also view the
Enterprise Connect help by choosing Enterprise Connect on the Help menu in
Outlook or Explorer. A help file is also available for each plug-in that you install on
the client.

1.1.1.1 Outlook Integration

Figure 1-2 shows the main Enterprise Connect elements in the Outlook interface:

• A: Enterprise Connect group and tab

• B: Toolbars
• C: Tree Structure
• D: List Pane
• E: Reading Pane
• F: Easy Access pane

NGDCORE210200-IGD-EN-01 Installation Guide 11

Chapter 1 Planning for Enterprise Connect

Figure 1-2: Enterprise Connect Outlook Interface Elements

The Enterprise Connect interface includes the following elements:

• The Enterprise Connect group on the Outlook Home tab contains commands for
copying or moving items, managing and applying Quick Steps, and copying or
moving items to recently-accessed folders.
• The Enterprise Connect tab on the Ribbon contains commands for performing
actions on items, managing the Easy Access pane, and specifying options.
• The Navigation Pane includes the Tree Structure, which exposes a view of the
folders and other containers that each plug-in makes available to the current
user.
• The List Pane displays the contents of the selected container in the Tree
Structure. The top of the List Pane contains a quick search toolbar that you can
use to search the contents of the selected folder in the Tree Structure.
• The Reading Pane displays a detailed view of the currently-selected item in the
List Pane. By default, previews are provided by Outlook Viewer. You can also
choose to use the Enterprise Connect Viewer, which enables users to preview the
contents of documents and images in a variety of standard formats.

The layout of the interface can vary depending on selected options. For example,
Outlook lets you position the Reading Pane to the right of the List Pane.

The Outlook integration includes the following features:

• Drag-and-drop functionality that enables you to move or copy items in the

repository by dragging them to folders in the Tree Structure.

12 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.1. Introducing Enterprise Connect

• A Send to > Desktop location command that lets you download an Enterprise
Connect folder and all its contents to the desktop.
• A Send To > Desktop (Create Shortcut) context menu command that lets you
send a shortcut to an Enterprise Connect folder to the desktop.
• A Send and Save button that lets you send emails and store them in the
repository with the click of a button.
• Copy Message and Copy Attachments buttons that let you copy an email, or just
its attachments, to Enterprise Connect.
• A Copy to Enterprise Connect context menu command that lets you copy
selected emails, folders, or attachments to Enterprise Connect.
• A Send To > Inbox context menu command that lets you send a copy of an email
stored in an Enterprise Connect repository to the Outlook Inbox.
• An Attach Item button that lets you attach links or copies of Enterprise Connect
items to emails, meeting requests, and appointments.
• The Easy Access pane. For more information, see “Easy Access Pane”
on page 13.
• Enterprise Connect Quick Steps, which let you copy or move emails to
preselected folders with a single click.
• Enterprise Connect columns, which show information about emails stored in
Enterprise Connect.
• The Suggested command, which lets you copy or move selected items to
recently-accessed folders. If the selected items are emails that all belong to the
same conversation, then the suggested folder might contain previously copied or
moved emails from the same conversation.

Note: You can edit registry settings to hide some of the Enterprise Connect
commands in Outlook. For more information, see “Configuring Outlook”
on page 133.

Easy Access Pane

The Easy Access pane is an optional pane that displays the Enterprise Connect tree.
You can position the Easy Access pane to float over the Outlook window, or dock it
along one of the sides of the window. You can drag emails or documents to the
pane, use the pane to browse the tree, perform saved and advanced searches from
the quick search box at the top of the pane, and use search profiles. If email
archiving is enabled, you can use the pane to archive emails.

For more information on using the pane, see section 2.8 “Using the Easy Access Pane
in Outlook” in OpenText Enterprise Connect - User Getting Started Guide
(NGDCORE200400-UGD), and “Using Enterprise Connect to Archive Emails”
on page 149. For more information on configuring Easy Access pane settings, see
“Specifying Settings for the Easy Access Pane” on page 137 and “Modifying
Language-Specific Labels” on page 62. For more information on creating search
profiles, see “Configuring Search Profiles” on page 157.

NGDCORE210200-IGD-EN-01 Installation Guide 13

Chapter 1 Planning for Enterprise Connect

1.1.1.2 Explorer Integration

Figure 1-3 shows the main Enterprise Connect elements in the Explorer interface:

• A: Enterprise Connect menu

• B: Toolbars
• C: Tree Structure
• D: List Pane
• E: Reading Pane

Figure 1-3: Enterprise Connect Explorer Interface Elements

The Enterprise Connect interface includes the following elements:

• The Menu Bar includes an Enterprise Connect menu that contains commands for
performing actions on items, searching, copying items, and specifying options.
• The Navigation Pane includes the Tree Structure, which exposes a view of the
folders and other containers that each plug-in makes available to the current
user.
• The List Pane displays the contents of the selected container in the Tree
Structure. The top of the List Pane contains a quick search toolbar that you can
use to search the contents of the selected folder in the Tree Structure.

14 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.1. Introducing Enterprise Connect

• The Reading Pane displays a detailed view of the currently-selected item in the
List Pane. The previews are provided by the Enterprise Connect Viewer, which
enables users to preview the contents of documents and images in a variety of
standard formats.

The layout of the interface can vary depending on selected options. For example,
Explorer lets you hide the Navigation Pane.

The Explorer integration includes the following features:

• Drag-and-drop functionality that lets you move or copy items in the repository
by dragging them to folders in the Tree Structure or List Pane. You can also add
a document as a new version by dragging it over a document in the List Pane.
• A Send to > Desktop location command that lets you download an Enterprise
Connect folder and all its contents to the desktop.
• A Send To > Desktop (Create Shortcut) context menu command that lets you
send a shortcut to an Enterprise Connect folder to the desktop.
• A Save To Briefcase context menu command that lets you create a working
folder on the file system to edit documents outside of Enterprise Connect. For
more information, see “Working with Briefcases” on page 174.

1.1.1.3 Office Integrations

The Office integrations add Enterprise Connect Open and Save As commands in all
supported Office applications. The commands are available as buttons on the
Enterprise Connect tab in the ribbon. These commands let you perform the
following tasks:

• Open an item from the repositories available in the Tree Structure, and modify it
within the application.
• Save an item to a location in the Tree Structure. You can save new items, or new
versions of existing items.
• Dynamically create folders and other containers when saving documents to
repositories.

In addition, the Enterprise Connect tab contains the following commands:

• Insert Document, which lets you insert embedded Enterprise Connect

documents, or links to Enterprise Connect documents, into the currently open
document.
• Send To, which lets you send links to the clipboard, or embed a link to the
document in an email.
• Properties, which displays properties for the open document.
• Insert Property, which lets you insert document properties into the document. If
you are using Word, you can also configure Enterprise Connect to support
inserting properties as Word fields. For more information, see “Enabling Users to
Insert Document Properties in Office” on page 115.

NGDCORE210200-IGD-EN-01 Installation Guide 15

Chapter 1 Planning for Enterprise Connect

• Upload and Finalize On Close, which let you determine upload methods for the
document. For more information, see “Configuring the Upload Mode for Edited
Documents” on page 105.

You can also edit registry settings to require users to use the Enterprise Connect
Open and Enterprise Connect Save As dialog boxes when working in Office. For
more information, see “Forcing the Use of the Enterprise Connect Open and Save As
Dialog Boxes” on page 109.

1.1.1.4 Acrobat Integration

The Acrobat integration adds Enterprise Connect Open and Save As commands in
supported versions of Acrobat Standard and Professional. The commands are
available on the File > Enterprise Connect menu. These commands let you perform
the following tasks:

• Open an item from the repositories available in the Tree Structure, and modify it
within the application.
• Save an item to a location in the Tree Structure. You can save new items, or new
versions of existing items.
• Dynamically create folders and other containers when saving documents to
repositories.

Note: The Acrobat integration only applies to Acrobat Standard or

Professional. It does not apply to Adobe Reader. Enterprise Connect provides
Adobe Reader support through the Extended Integration option. For more
information, see “Extended Integration” on page 17.

1.1.1.5 IBM Notes Integration

The integration with IBM Notes adds the following commands to the IBM Notes
Action menu:

• Copy/Move Messages to Enterprise Connect

• Open from Enterprise Connect
• Copy Attachments to Enterprise Connect

These commands let you copy or move emails from IBM Notes to Enterprise
Connect, open read-only versions of Enterprise Connect items, and copy email
attachments to Enterprise Connect.

The Enterprise Connect installation also provides the option of installing the
Message Viewing Integration for IBM Notes. The Message Viewing Integration lets
you open IBM Notes emails for viewing when you are working in Enterprise
Connect in Outlook or Explorer. The emails open in the Notes client.

For example, if the Message Viewing Integration is installed, and you double-click
an IBM Notes email in a Content Server folder, the email opens in the Notes client in
read-only format.

16 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.1. Introducing Enterprise Connect

You can also enable users to attach Enterprise Connect documents to IBM Notes
emails. For more information, see “Enabling the Attach Documents Command in
IBM Notes” on page 154.

1.1.1.6 Extended Integration

The Extended Integration option lets you open and save documents to Enterprise
Connect from applications' native Open, Save, and Save As dialog boxes. By
default, Extended Integration supports all desktop applications.

You can restrict Extended Integration to specific applications by editing registry

settings on the Enterprise Connect client. For more information, see “Specifying
Which Applications Support Extended Integration” on page 112.

1.1.2 Enterprise Connect Viewer

Enterprise Connect Viewer is installed by default with Enterprise Connect. The
Viewer enables you to preview items in supported formats in a View tab at the
bottom of the Reading Pane, even when the item's native application is not installed.
A toolbar also appears on the Reading Pane, giving users the ability to print, search,
copy text or images, rotate, and zoom in and out on documents and images.

The Enterprise Connect Viewer provides support for formats that include Microsoft
Office, WordPerfect, RTF, PDF, ZIP, text files, JPEG and raster images, AutoCAD,
Virtual Reality Modelling Language, SolidWorks, XGL, CGM, PostScript, and STL.

The View tab only appears for plug-ins that support the Viewer. The OpenText
Enterprise Connect Plug-in for Content Server gives the administrator the option of
using Enterprise Connect Viewer or OpenText™ Document Filters. The View tab is
displayed in both cases. However, the toolbar is only displayed if Enterprise
Connect Viewer is enabled. For more information, see “Selecting a Viewer for the
Reading Pane” on page 66.

In Outlook, the native Outlook viewer is used to preview items by default. You can
change the default behavior to use the Enterprise Connect Viewer instead. For more
information, see “Using the Outlook Viewer Instead of the Enterprise Connect
Viewer” on page 134.

1.1.3 Authentication and Security

Each plug-in provides its own methods to authenticate user credentials. The
OpenText Enterprise Connect Plug-in for Content Server provides single-sign on
support if Content Server is configured to support it through OpenText™ Directory
Services. If Content Server users have internal accounts, Enterprise Connect stores
their credentials in encrypted format on the client. For more information, see
“Determining the Authentication Method” on page 39.

All content security and user permissions are managed by the applications that are
exposed through the plug-ins. For example, you can only view the contents of a
Content Server Folder in the Tree Structure if you have Read permissions for the
Folder in Content Server.

NGDCORE210200-IGD-EN-01 Installation Guide 17

Chapter 1 Planning for Enterprise Connect

1.1.4 Offline Support

Enterprise Connect enables users to work offline. While offline, users can edit local
copies of documents that they previously downloaded from content repositories.
When they go back online, users can upload the edited documents as new versions.

Offline features in Enterprise Connect include the following:

• A Work Offline or Work Online command on the Enterprise Connect menu in

Outlook and Explorer. This command lets you control whether Enterprise
Connect is offline or not.

• Download Offline Version and Discard Offline Version context menu

commands on documents that support offline editing. These commands enable
you to download and delete offline versions of the selected documents. You can
also download offline folder versions to quickly take large numbers of
documents offline. Items downloaded for offline appear in the Office Editor My
Working Documents List dialog box, and can be managed from there.

• A My Working Documents List command on the Enterprise Connect menu.

This command opens the Office Editor My Working Documents List dialog box,
which lets you edit or discard offline documents, and manage any
synchronization conflicts or issues.

• An Offline Sync command on the Enterprise Connect menu. This command

enables you to manually synchronize online and offline content.

• An Offline Synchronization setting in the Options dialog box, which enables

you to schedule automatic syncs of offline content, and configure Enterprise
Connect to always perform a synchronization after switching to online mode.

• The ability to preview documents with the Enterprise Connect Viewer, by

clicking the Preview button in the List Pane.

• The ability to search offline content using the Enterprise Connect quick search
box. For more information, see “Enabling Offline Search” on page 182.

• The ability to copy or move items to Enterprise Connect folders while in offline
mode. The standard copy and move operations, such as dragging items, are
supported. The ability to copy or move folders to Enterprise Connect in offline
mode is not supported.

When Enterprise Connect is offline, the Tree Structure shows only offline versions of
documents, along with the folders that contain these documents. A standard set of
columns, including Name, Date Modified, and Size, is displayed for all offline
documents.

Some plug-ins might also allow administrators to specify additional columns to be

available offline. For example, the Enterprise Connect Plug-in for Content Server
gives administrators the ability to make email columns available offline. For more
information, see “Configuring Column Displays” on page 64.

18 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.1. Introducing Enterprise Connect

When you work offline, you can only edit the content of offline documents. You
cannot update document metadata, such as properties or attributes. You also cannot
move or copy offline documents.

Most Enterprise Connect functionality is not available offline. Any commands that
require a connection to a plug-in are not available. For a complete list of unavailable
functionality, as well as for details on how to work with Enterprise Connect in
offline mode, see section 6 “Managing Offline Content” in OpenText Enterprise
Connect - User Getting Started Guide (NGDCORE200400-UGD).

Offline functionality is enabled by default when you install the Framework. After
installation, you can edit a registry setting to disable offline functionality on the
client. You can also edit the registry to set a maximum size for the offline data store.
For more information, see “Configuring Offline Mode” on page 180.

Note: The Enterprise Connect offline feature is designed to provide flexibility

and to accommodate a range of user scenarios. By default, it does not impose
any restrictions or limits on the number or size of documents that can be taken
offline by a single user. Depending on network latency, average document size,
and user patterns, you can configure the maximum size in megabytes (MB) of
the offline document store. OpenText recommends that you perform your own
testing to determine what is an acceptable and workable size for the offline
data store. For more information on how to configure the size of the offline
data store, see “Configuring Offline Mode” on page 180. The offline feature is
not intended to act as an offline version of Content Server. Users must not take
more than 2500 documents offline in total, because document synchronization
performance can degrade above this limit.

1.1.5 OpenText Office Editor

Enterprise Connect uses OpenText Office Editor to manage the editing process for
items on the client. Office Editor is installed on the client as part of the Enterprise
Connect Framework installation. Office Editor provides the following features and
functionality:

• A cache that stores local copies of documents that you open for editing from
Enterprise Connect. When you edit or open a document, the document is added
to the Office Editor document cache. Office Editor manages the items in the
cache.

• The My Working Documents List dialog box, which you can access by clicking
the Office Editor icon in the notification area. This dialog box displays all the
items that are currently stored in the document cache. You can use My Working
Documents List to edit or open recently edited documents, synchronize local
documents with their server versions, resolve synchronization errors and
conflicts, and upload, finalize, unreserve, and discard local documents. For more
information, see section 7 “Managing Your Working Documents List” in
OpenText Enterprise Connect - User Getting Started Guide (NGDCORE200400-UGD).

NGDCORE210200-IGD-EN-01 Installation Guide 19

Chapter 1 Planning for Enterprise Connect

• Integration with Enterprise Connect offline functionality. You can view and
manage all Enterprise Connect offline documents in the My Working
Documents List dialog box.

You can edit the client registry to control the location of the document cache, specify
settings for the My Working Documents List dialog box, and enable logging for
Office Editor. For more information, see “Using Office Editor” on page 81 and
“Registry Settings for Office Editor” on page 194.

You can also use the Content Server General Editor Settings and Office Editor
Settings administration page to configure settings for Office Editor. For more
information, see the online help for the General Editor Settings and Office Editor
Settings administration pages.

Note: You can also install a stand-alone version of Office Editor. For more
information, see “Installing a Stand-alone Version of Office Editor”
on page 36.

1.1.6 OpenText Enterprise Connect Plug-in for Content

Server
You can configure the OpenText Enterprise Connect Plug-in for Content Server as
part of your Enterprise Connect configuration. The OpenText Enterprise Connect
Plug-in for Content Server lets you view and work with objects including
Documents, Folders, Projects, Task Lists, LiveReports, Compound Documents,
Channels, and News. You can also perform repository searches on the plug-in and
include it in quick searches. For more information, see the Enterprise Connect
section of the Content Server user help.

The root node of the plug-in appears directly beneath the Enterprise Connect root
node in the Tree Structure. By default, it displays a Server node that contains the
following items:

• Enterprise Workspace
• Favorites
• My Workspace for the current user

You can use the Enterprise Connect administration pages in Content Server to add
Volumes and Other Items nodes to the display. You can also specify which nodes
the Server, Personal, Volumes, and Other Items nodes contain, according to the
needs of your users and the compatibility of the nodes within Enterprise Connect.
For more information, see “Configuring the Enterprise Connect Tree Structure and
List Pane” on page 59.

Enterprise Connect also supports the use of Content Server Domains if they are
enabled. For more information, see “Using Content Server Domains” on page 42.

The plug-in also lets you open and edit documents from the repository directly in
Office applications, and save your changes to the repository. In addition, you can

20 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.2. System Requirements

open documents from Outlook or Explorer, edit them in Office, and use the native
Save command to save your changes as new versions.

You can also configure Enterprise Connect to work with OpenText™ Email
Archiving for Microsoft® Exchange. You can archive emails by dragging them to the
Easy Access pane or by using the Copy/Move to Enterprise Connect command in
Outlook. For more information, see “Configuring Enterprise Connect to Work with
Email Archiving for Microsoft Exchange” on page 145.

Note: Plug-ins enable Enterprise Connect users to interact with Enterprise

repositories and applications. This guide includes instructions on configuring
the plug-in that connects to OpenText Content Server. Additional Enterprise
Connect plug-ins might also be available to support integrations with different
applications. For instructions on installing and configuring additional plug-ins,
consult the documentation for the plug-ins. A help file might also be available
for each plug-in that you install on the client. You can view the help by
choosing Enterprise Connect on the Help menu in Outlook or Explorer.

1.1.7 Extending Enterprise Connect

The Enterprise Connect Client SDK exposes a set of COM interfaces that enable
developers to access Enterprise Connect repositories from third-party applications.
Using the SDK, you can customize an application to invoke the Enterprise Connect
Open and Save As dialog boxes, as well as download documents to a local file
system, and open documents from and save them to Enterprise Connect
repositories. For more information, see OpenText Enterprise Connect Client SDK
Developer’s Guide.

1.2 System Requirements

Before you can install Enterprise Connect, you must install and configure the
applications required for the plug-ins and integrations you plan to support.

For detailed system requirements and supported versions, see the Release Notes. For
instructions on installing and configuring required applications, see the product
documentation for the applications.

Note: Only the products and versions specified in the Release Notes are
supported. Other versions have not been tested and are therefore not officially
supported for this version. The Release Notes contain the definitive list of
supported versions. Any other versions mentioned in the product
documentation are superseded by the versions specified in the Release Notes.

NGDCORE210200-IGD-EN-01 Installation Guide 21

Chapter 1 Planning for Enterprise Connect

1.2.1 Server Requirements

Enterprise Connect requires a connection to a Content Server instance with the
following modules:

• Enterprise Connect
• Email Services
• Content Server Web Edit (Office Editor)

By default, these modules are included in the Content Server installation. You might
need to install patches for the modules before installing Enterprise Connect.

Consult the Release Notes for supported versions of Content Server and patch
requirements.

1.2.2 Client and Integration Requirements

Ensure the following prerequisites are installed on the client before installing
Enterprise Connect:

• Microsoft .NET Framework Version 4.0.30319 or higher (full version is required)

• Microsoft® Internet Explorer® (see the Release Notes for supported versions)

The offline search feature has the following requirements:

• The Windows Search feature must be enabled.

Notes

– On Windows Server® 2008 R2, the File Services role must be added to
allow the Windows Search feature to be enabled.
– On Windows Server 2012, the Windows Search Service feature must be
installed to allow the Windows Search feature to be enabled.
• To enable indexing and searching of document formats that Windows Search
does not support by default, appropriate filters must be installed on the clients.

Integrations have the following requirements:

• Adobe Acrobat
A supported version of Acrobat Standard or Professional must be installed.
Supported versions include Acrobat Standard or Professional X, XI, and DC.
Adobe Reader is not supported for this integration.
• IBM Notes
A supported version of the IBM Notes client must be installed. The supported
versions are IBM Notes 9.0.1 and 8.5.3. Both Basic and Multi-user clients are
supported.

22 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 1.2. System Requirements

To enable users to attach Enterprise Connect documents to IBM Notes emails,

you must make changes to the Mail.ntf template file in IBM Domino Designer.
For more information, see “Enabling the Attach Documents Command in IBM
Notes” on page 154.
• Microsoft Office
At least one supported Office application must be installed. Supported Office
applications include Word, Excel, PowerPoint, Microsoft Project, and Visio.
Supported versions include Office Service Pack 1 (32-bit and 64-bit), Office 2016,
and Office 2019.
• Microsoft Outlook
A supported version of Outlook must be installed. Supported versions include
Outlook 2013 (32-bit and 64-bit), Outlook 2016, and Outlook 2019.

Notes

– OpenText recommends that you configure Outlook to prevent Enterprise

Connect add-ins from being disabled because of performance issues such
as slow startup times. You can do this by setting a Group Policy Object
(GPO) after the client is installed. For more information, see “Installing
Enterprise Connect Framework and Office Editor“ on page 25 and
“Configuring the Enterprise Connect Add-ins for Outlook to Remain
Enabled” on page 133.
– Before installing Enterprise Connect, ensure that Outlook has been
started at least once and that a profile has been created for the user.

For more information, see the Release Notes.

If you subsequently upgrade your version of Office or Outlook, you must reinstall
Enterprise Connect to ensure the integrations continue to work properly. For more
information, see “Modifying or Reinstalling the Framework” on page 34.

1.2.3 Citrix® Requirements

Enterprise Connect supports the following:

• Hosted virtual desktops provided through Citrix® XenDesktop®.

• Application virtualization through Citrix® XenApp®. For example, Enterprise
Connect supports the provision of Microsoft Office applications such as Word
through XenApp.

Consult the Release Notes for supported XenDesktop and XenApp versions.

Notes

• If you are configuring Enterprise Connect to work with XenApp on

Windows Server 2008, ensure that Microsoft Internet Explorer is configured
to accept cookies.

NGDCORE210200-IGD-EN-01 Installation Guide 23

Chapter 1 Planning for Enterprise Connect

• The Enterprise Connect and Office Editor document cache does not support
multiple concurrent connections from different clients. If your Citrix
configuration permits users to run multiple concurrent Enterprise Connect
or Office Editor sessions on different clients, you must ensure that each
session uses a separate document cache. For more information on specifying
the location of the document cache, see “Specifying the Location of the
Document Cache” on page 82 and “Configuring the Document Cache
Location to Support Citrix Session Pools” on page 84.

24 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 2

Installing Enterprise Connect Framework and Office

Editor

This chapter describes how to install Enterprise Connect Framework and Office
Editor.

Before installing Enterprise Connect Framework, ensure that you have met the
requirements for the client and the integrations. For more information, see “Client
and Integration Requirements” on page 22 and the Release Notes.

After installing Enterprise Connect Framework, you must modify the registry to
establish a connection with Content Server.

Note: A number of Enterprise Connect settings are controlled through registry

values. You can push these registry values out at the same time as you install
Enterprise Connect, or you can modify the registry after installation. For more
information, see “Registry Setting Reference“ on page 185.

2.1 Installing the Framework Using Setup

You must install Enterprise Connect Framework before installing the plug-ins that
you want to include on the client. The installation account requires local
administration rights on the system.

Use one of the following .msi files to install the Enterprise Connect Framework:

EnterpriseConnect_Framework_<version>.msi
For 32-bit operating systems

EnterpriseConnect_Framework_<version>_x64.msi
For 64-bit operating systems

Note: You use the same Enterprise Connect Framework.msi file to install
Enterprise Connect in all supported languages. By default, the language that
Enterprise Connect is displayed in corresponds to the client’s display language
setting. If the client language is not supported, Enterprise Connect is displayed
in English. For information on manually changing the Enterprise Connect
language, see “Changing the Enterprise Connect Language Setting”
on page 79. For more information on supported languages, see the Release
Notes.

When you install the Framework you are given the option of installing the Outlook,
Explorer, and Office integrations.

NGDCORE210200-IGD-EN-01 Installation Guide 25

Chapter 2 Installing Enterprise Connect Framework and Office Editor

Office Editor is automatically installed as part of the Enterprise Connect Framework

installation. If a stand-alone version of Office Editor is already installed, OpenText
recommends removing it before installing Enterprise Connect. You should manage
installations of stand-alone Office Editor and Enterprise Connect Framework
separately.

To install Enterprise Connect Framework:

1. Do one of the following to make the .msi file accessible on the client system:

• Copy the file to the system.

• Place the file in a network share that is accessible from the system.
2. Double-click the Setup file.

Note: If a dialog box instructs you to install one or more prerequisites,

click OK, click Finish, and then install the prerequisites. For more
information, see “Client and Integration Requirements” on page 22.
3. On the Welcome page, click Next.
4. On the License Agreement page, review the license agreement, select the I
accept the terms in the License Agreement check box to accept the agreement,
and then click Next.
5. On the Custom Setup page, click one of the following options for each client
integration in the list:

This feature will be installed on local hard drive.

The integration is installed on your system.
This feature will not be available.
The integration is not installed on your system.

The available client integrations can include the following options:

• Outlook Client
• Explorer Client
• Office Client
• IBM Notes Client
• Adobe Acrobat Client
• Extended Integration

Notes

• For more information about clients, see “Enterprise Connect Client

Integrations” on page 11.
• If the prerequisites for a client integration are not installed, the
integration will not be available for selection. For more information

26 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.1. Installing the Framework Using Setup

about prerequisites, see “Client and Integration Requirements”

on page 22.

6. To enable users to open IBM Notes emails for viewing from Outlook or
Explorer, expand IBM Notes Client, click Message Viewing Integration, and
then click This feature will be installed on local hard drive. For more
information on the Message Viewing Integration, see “IBM Notes Integration”
on page 16.

7. To change the default destination directory specified in the Install path box,
click Browse, and then specify a different directory.

8. Click Disk Usage to verify that you have sufficient disk space to install all
specified features, click OK, and then do one of the following:

• If you have sufficient disk space, click Next.

• If you do not have sufficient disk space, remove one or more selected
features from the Custom Setup page, or specify a location on a disk with
sufficient space in the Destination Folder page.

9. If you are installing the Enterprise Connect client for Outlook, follow the link to
the Knowledge Base article presented in the Additional Information page. For
more information, see “Configuring the Enterprise Connect Add-ins for
Outlook to Remain Enabled” on page 133 and KB521424 (https://
knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/KB521424).

10. On the Ready to Install page, click Install.

11. On the Completing the installation page, click Finish.

12. Connect Enterprise Connect to Content Server. For more information, see
“Connecting Enterprise Connect to Content Server” on page 29.

Notes

• You are required to restart the system after installation is complete.

• If you installed the Explorer integration, you can start Enterprise Connect in
Explorer by clicking Programs > OpenText > OpenText Enterprise Connect
on the Start menu after installation is complete.

NGDCORE210200-IGD-EN-01 Installation Guide 27

Chapter 2 Installing Enterprise Connect Framework and Office Editor

2.2 Installing the Framework Silently

You can use Windows Installer to perform silent installations of the Enterprise
Connect Framework and plug-ins. The standard msiexec.exe command line
options are supported. You must also specify custom values for the Enterprise
Connect components. OpenText recommends that you enable logging when
performing silent installations for Enterprise Connect.

Important

• All custom values are case-sensitive. You must enter them using the exact
case specified in this section.
• The installation account requires local administration rights on the system.

You can specify the following properties for the Framework silent installation:

ADDLOCAL
You can specify the following options for the ADDLOCAL property:
Explorer_client, Outlook_client or Outlook_client_64, Office_client or
Office_client_64, LotusNotes_client, Acrobat_client, Extended_
Integration, Core
These values determine which client integrations are installed. You must
always specify Core if you include the ADDLOCAL property in the list of
options. If you do not specify the ADDLOCAL property, all supported
integrations are installed by default.
The Office, Outlook, Acrobat, and IBM Notes integrations require that you
first install supported versions of these applications. If they are not already
present on the client, the corresponding integrations are not installed.
LotusNotes_viewer
Specifying LotusNotes_viewer installs the Message Viewing Integration for
IBM Notes, which enables users to open IBM Notes emails for viewing from
Outlook or Explorer. If you specify LotusNotes_viewer, you must also
specify LotusNotes_client.
The following example shows a silent installation on a 32-bit client with the
Explorer and Outlook integrations:
msiexec /qn /i C:\EnterpriseConnect_Framework_16.0.3_x64.msi
ADDLOCAL="Explorer_client,Outlook_client,Core"

SKIP_VSTO_CHECK="yes"
You can specify the SKIP_VSTO_CHECK="yes" property to disable the
installation’s check for Visual Studio 2010 Tools for Office Runtime. This can be
useful in situations where Outlook is present on the client but you are not
installing the Enterprise Connect Outlook integration. For example:
msiexec /qn /i C:\EnterpriseConnect_Framework_16.2.0_x64.msi SKIP_
VSTO_CHECK="yes" ADDLOCAL="Explorer_client,Core"

28 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.3. Connecting Enterprise Connect to Content Server

2.3 Connecting Enterprise Connect to Content

Server
Before connecting Enterprise Connect to Content Server, ensure the correct versions
of the modules are installed on the server. For more information, see “Server
Requirements” on page 22.

You need to modify the registry on each Enterprise Connect client to establish a
connection with Content Server. You can do this in one of two ways:

• Directly edit the registry by adding a new key to HKEY_LOCAL_MACHINE. This

connection becomes available to all users with accounts on the client.
• Use the Manage Plug-ins dialog box to create the connection. Connections added
through Manage Plug-ins are stored in the registry in HKEY_CURRENT_USER and
are only available for the user who creates the connection. This applies even if an
administrator account is used to create the plug-in.

Note: If a plug-in registry key in HKEY_LOCAL_MACHINE has the same unique

identifier as one in HKEY_CURRENT_USER, the key in HKEY_LOCAL_MACHINE takes
precedence.

2.3.1 Editing the Registry to Establish the Connection

Editing the registry requires that you create a new key in the following location on
the clients:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Solutions

(on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Solutions (on 64-bit systems)

The name of this key represents the plug-in's unique ID. You can use any unique
alphanumeric string. Do not use other characters such as spaces or punctuation
characters, including question marks (?) or backslashes (\). Use the same name on
all clients.

Note: OpenText recommends using lowercase for the Unique ID.

You must also create the following registry settings in the plug-in key:

Required Settings

BaseHREF (String)
The URL to the Enterprise Connect Module for Content Server, in the following
format:
<http or https>://<server name>/<service name>/<livelink.exe,
llisapi.dll, or cs.exe>?func=ngd.ucroot

NGDCORE210200-IGD-EN-01 Installation Guide 29

Chapter 2 Installing Enterprise Connect Framework and Office Editor

For example:
http://csserver/otcs/cs.exe?func=ngd.ucroot
Important
Be sure to specify the full URL, including the ?func=ngd.ucroot request
handler at the end.
DisplayName (String)
The label that appears for the plug-in in the following locations:

• Root node in Tree Structure.

• Repository search command on the Enterprise Connect menu in Outlook
and Explorer.
• Help command that appears on the Enterprise Connect Help submenu in
Outlook and Explorer.

IsHidden (DWORD)
An internal value that should always be set to the following: 0
ProgID (String)
An internal value that should always be set to the following: OpenText.
EnterpriseConnect.XmlPlugin

Optional Settings

AllowAutoAuthentication (DWORD)
An optional setting that indicates whether a user’s Windows login credentials
are used for authentication when automatic login is enabled for the plug-in, for
example if Windows Integrated Authentication (IWA) is in effect. This setting
only comes into effect if Content Server is configured to support automatic login
using Windows login credentials.
If the value of the setting is 1, the Windows login credentials are used. If the
credentials do not succeed, the user is prompted to manually enter credentials.
If the value of this setting is 0, the user is prompted to manually enter
credentials the first time the user accesses the plug-in. Enterprise Connect then
stores the credentials for use in future sessions.
If this setting is missing, the default value of 1 is used.
AuthorizationCookieNames (String)
An optional setting that only applies to environments that use a third-party Web
access management system such as CA SiteMinder as an authentication
provider. If this setting exists and is configured correctly, users are not required
to re-enter credentials for the authentication provider after doing one of the
following in the Content Server Web interface:

• Clicking Open or Edit for a document, when Office Editor manages the open
or edit action.
• Clicking Enterprise Connect from Here.

30 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.3. Connecting Enterprise Connect to Content Server

To enable this setting, you must enter the name of the cookie used by the third-
party authentication provider to manage authentication. If more than one cookie
is required, enter the cookie names as a comma-separated list. For example, if
you use SiteMinder, you would enter SMSESSION as the value of this setting.

Note: This setting only works with Internet Explorer. In a different

browser, or if this registry setting is not configured, users might be
required to re-authenticate with the third-party authentication provider
after clicking Open, Edit, or Enterprise Connect from Here in the Content
Server Web interface.
EnableDocumentCaching (DWORD)
An optional setting that indicates whether documents are stored in the Office
Editor document cache. If this setting exists and is 0, items are only stored in the
document cache while they are open for reading or editing. After an item is
closed and unreserved, it is removed from the cache and is no longer displayed
in the My Working Documents List dialog box. If this setting is 1 or does not
exist, items are always stored in the cache.
Important
The UploadDocumentSavesImmediately and DefaultFinalizeOnClose
registry settings can affect whether or not a document is unreserved when
it is closed. For more information, see “Configuring the Upload Mode for
Edited Documents” on page 105.
UseNativeCertificateAuthentication (DWORD)
An optional setting that only applies if you are using SSL client certificates and
the authentication process for your certificates fails in Enterprise Connect but
succeeds in Internet Explorer. In this case, assign this setting a value of 1 to
cause the native operating system processes to manage certificate handling
rather than Enterprise Connect. In this case, users are always prompted to enter
their certificate information each time they start a new Enterprise Connect
session. If this setting does not exist or is 0, Enterprise Connect manages the
certificate handling process. For more information, see “Using SSL Client
Certificates” on page 40.

The following image shows the registry key and values for a Content Server
connection on a 64-bit client. In this example, the unique ID of the connection is
content_server, and the DisplayName is Content Server:

NGDCORE210200-IGD-EN-01 Installation Guide 31

Chapter 2 Installing Enterprise Connect Framework and Office Editor

Caution
Errors made when modifying registry values can have a negative impact on
system performance and stability. For this reason, OpenText recommends
that the registry be backed up before it is edited, and that only qualified
personnel modify the registry in accordance with your organization's
accepted processes.

If you want to connect to two separate Content Server instances, you need to add a
separate registry key and values for each instance. The registry key name must be
unique for each instance. Users can specify a separate set of credentials for each
server. A separate command is also displayed on the Search menu to represent each
server's repository search form.

If you remove the Framework, the key and values that you created are removed
from the registry.

Note: Users must log on to a new Windows session to make changes to

Enterprise Connect registry settings take effect.

32 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.3. Connecting Enterprise Connect to Content Server

2.3.2 Using the Manage Plug-ins Dialog Box to Establish the

Connection
You can use the Manage Plug-ins command on the Enterprise Connect menu in
Outlook or Explorer to create the connection to Content Server. Local administrator
permissions are not required. This can be useful in test environments or if you want
individual users to create Content Server connections themselves.

Connections created through the Manage Plug-ins dialog box are stored in the
registry in HKEY_CURRENT_USER, and only apply to the user who creates them. If a
plug-in with the same unique ID is defined in the registry in HKEY_LOCAL_MACHINE,
that plug-in takes precedence. This applies even if an administrator account is used
to create the plug-in.

To connect to Content Server from Enterprise Connect:

1. On the Enterprise Connect menu in Explorer or Outlook, click Manage Plug-
Ins.
2. Click New, and then type the following values:

Unique ID
A unique identifier for the plug-in. You can use any unique alphanumeric
string. Do not use other characters such as spaces or punctuation characters,
including question marks (?) or backslashes (\). Use the same name on all
clients. For example: content_server.
Note: OpenText recommends using lowercase for the Unique ID. All
Unique ID values that are added through the Manage Plug-ins dialog
box in Enterprise Connect are automatically converted to lowercase.
Display Name
The label that identifies the plug-in in the Enterprise Connect display. For
example: Content Server.
URL
The URL to the Enterprise Connect Module for Content Server, in the
following format:
<http or https>://<server name>/<service name>/<livelink.exe,
llisapi.dll, or cs.exe>?func=ngd.ucroot
For example:
http://cs1/OTCS/cs.exe?func=ngd.ucroot

3. Click OK.
The associated key and values are created in the registry at HKEY_CURRENT_USER
\SOFTWARE\Open Text\Enterprise Connect\Solutions.

Notes
• When the plug-in is created, the AllowAutoAuthentication registry setting
is set to 1 for the plug-in. You can change this value by editing the plug-in

NGDCORE210200-IGD-EN-01 Installation Guide 33

Chapter 2 Installing Enterprise Connect Framework and Office Editor

registry setting in HKEY_CURRENT_USER. For more information about

AllowAutoAuthentication, see “Editing the Registry to Establish the
Connection” on page 29.
• The EnableDocumentCaching and UseNativeCertificateAuthentication
settings are not added when the plug-in is created. You must manually add
these settings if you want to use them. For more information, see “Editing
the Registry to Establish the Connection” on page 29.

2.4 Modifying or Reinstalling the Framework

You can modify the Enterprise Connect Framework to change the installed
integrations. For example, if you subsequently install Office on the client, you can
add the Office integration to the Framework.

You can also reinstall the Framework. Reinstalling restores all files and registry
settings to their initial post-installation state.

Note: If you change the version of Office or Outlook on your system, you must
reinstall the Framework to ensure that the Office or Outlook integration
continues to function properly. Only reinstall the Framework after you change
the version of Office or Outlook.

To modify the Framework installation:

1. Open the Control Panel, and then click Programs and Features.

2. Click OpenText Enterprise Connect Framework, and then click Change.

3. Click Next.

4. On the Change, Repair, or Remove Installation page, click Add or Remove

Features.

5. On the Custom Setup page, specify the integrations you want to include, and
then click Next.

6. Click Install.

7. Click Finish.

To reinstall the Framework:

1. Double-click the .msi file.

2. Click Next.

3. On the Change, Repair, or Remove Installation page, click Reinstall or Repair.

4. On the Ready to Install page, click Repair.

5. Click Finish.

34 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.5. Removing the Framework

Note: You can also reinstall the Framework by clicking the Change option for
the Framework in Uninstall or change a program.

2.5 Removing the Framework

Remove any plug-ins installed on the client before you remove the Framework. The
account that performs the removal requires local administration rights. After
removing the Framework, you must restart the system.

Removing the Enterprise Connect Framework does not remove the following items.
You must delete these items manually if you do not want to retain them:

• The C:\Users\<user>\AppData\Roaming\OpenText\Enterprise Connect

folder. This folder contains configuration data for the user, such as stored
credentials in encrypted format.
• The C:\Users\<user>\AppData\Roaming\OpenText\Enterprise Connect
Offline Store folder. This folder contains metadata for the user’s offline items.

• The registry keys and entries stored in the HKEY_CURRENT_USER\SOFTWARE\Open

Text\Enterprise Connect key.

• The Office Editor document cache, which stores recently edited documents and
Enterprise Connect offline items. For more information on the location of the
cache, see “Specifying the Location of the Document Cache” on page 82.

To remove the Framework:

1. Open the Control Panel, and then click Programs and Features.

2. Click OpenText Enterprise Connect Framework, and then click Uninstall.

2.6 Upgrading the Framework

To upgrade the Framework, install the latest version of the Framework on the client
systems. You do not need to manually remove the existing Framework version
before performing the upgrade.

To determine what sequence to use when upgrading a plug-in along with the
Framework, consult the upgrade documentation for the plug-in.

Notes

• You cannot perform a stand-alone upgrade of the Office Editor client to 16.2
if Enterprise Connect Framework 10.5.2 or earlier is also installed. In this
case you must upgrade the Framework to 16.2.
• The 16.2 versions of Enterprise Connect Framework and Office Editor client
require that the 16.0 or later versions of the Enterprise Connect and Web Edit
modules are installed on the server.

NGDCORE210200-IGD-EN-01 Installation Guide 35

Chapter 2 Installing Enterprise Connect Framework and Office Editor

To upgrade the Framework using Setup:

1. Do one of the following to make the .msi file accessible on the client system:

• Copy the file to the system.

• Place the file in a network share that is accessible from the system.

2. Double-click the Setup file.

Note: If a dialog box instructs you to install one or more prerequisites,

click OK, click Finish, and then install the prerequisites. For more
information, see “Client and Integration Requirements” on page 22.

3. In the Upgrade Installation message, click Yes.

4. Complete the installation as described in “Installing the Framework Using

Setup” on page 25.

Notes

• During upgrades, if Outlook is already configured to keep the Enterprise

Connect add-ins enabled, you do not need to select the Set policy to prevent
Outlook from disabling Enterprise Connect due to slow add-in response
times check box again.

• If a Files in Use message appears, click Ignore, and then continue the
upgrade. The system restarts after the upgrade finishes.

2.7 Installing a Stand-alone Version of Office Editor

If you install Enterprise Connect Framework, Office Editor is automatically installed
as well. However, you can install a stand-alone version of Office Editor if you do not
want Enterprise Connect to be available on the client.

If Enterprise Connect Framework is already installed, OpenText recommends

removing it before installing Office Editor. You should manage installations of
stand-alone Office Editor and Enterprise Connect Framework separately.

The installation account requires local administration rights on the system.

Use one of the following .msi files to install a stand-alone version of Office Editor:

OFFICEEDITOR_CLIENT_<version>.msi
For 32-bit operating systems

OFFICEEDITOR_CLIENT_<version>_x64.msi
For 64-bit operating systems

36 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 2.7. Installing a Stand-alone Version of Office Editor

Note: You use the same .msi file to install Office Editor in all supported
languages. By default, the language that Office Editor is displayed in
corresponds to the client’s display language setting. If the client language is not
supported, Office Editor is displayed in English. For information on manually
changing the Office Editor language, see “Changing the Office Editor
Language Setting” on page 80. For more information on supported
languages, see the Release Notes.

To install a stand-alone version of Office Editor:

1. Do one of the following to make the .msi file accessible on the client system:

• Copy the file to the system.

• Place the file in a network share that is accessible from the system.

2. Double-click the Setup file.

3. On the Welcome page, click Next.

4. On the License Agreement page, review the license agreement, select the I
accept the terms in the License Agreement check box to accept the agreement,
and then click Next.
5. On the Ready to Install page, click Install.

6. On the Completing the installation page, click Finish.

Notes

• Use Programs and Features in Control Panel to remove Office Editor.

• For a list of registry settings you can edit for Office Editor, see “Registry
Settings for Office Editor” on page 194.

NGDCORE210200-IGD-EN-01 Installation Guide 37

Chapter 3
Configuring System Options

This chapter describes the following system options that you can configure for
Enterprise Connect:

• Authentication methods and settings, including the use of Content Server

Domains and how credentials are stored on the client.
• Recommendations for optimizing system performance.
• Making Enterprise Connect accessible from the Content Server Web interface.
• Enabling the Mail as attachment command on the Send to menu in Smart View.
• Supporting previous versions of the Enterprise Connect Framework.
• Recommendations and requirements to note when making Enterprise Connect
work with additional Content Server optional modules.
• Settings that you can use to modify HTTP timeout request values for Enterprise
Connect.
• Configuring and enabling browser extensions on the client.

3.1 Configuring Authentication

This section describes the following topics:

• Determining the authentication method.

• Using Content Server Domains.
• Configuring credential storage.
• Requiring users to always sign in using the browser.

3.1.1 Determining the Authentication Method

Enterprise Connect and Office Editor support a variety of authentication options for
Content Server.

All user login attempts are recorded as Log-in or Failed Log-in Attempt events in
the Content Server audit log.

Note: if you experience difficulties when authenticating with Enterprise

Connect or Office Editor, you can make Enterprise Connect or Office Editor
display a browser window to enable users to authenticate separately with
Content Server. For more information, see “Requiring Users to Sign In with a
Browser” on page 44.

NGDCORE210200-IGD-EN-01 Installation Guide 39

Chapter 3 Configuring System Options

3.1.1.1 Using Content Server Accounts

Users with internal Content Server accounts are prompted to specify their
credentials the first time they start Enterprise Connect and click the root node of the
plug-in. Enterprise Connect then stores the credentials in encrypted format on the
client. As long as their credentials remain valid, users are not prompted to enter
them again. If their credentials change on the server, users are prompted to update
the copy of their credentials that is stored on the client.

If you do not want Enterprise Connect to store user credentials locally, you can edit
a server setting or a registry setting that requires users to re-enter their credentials at
the start of each Enterprise Connect session. For more information, see “Configuring
Storage of Enterprise Connect Credentials” on page 42 and “Editing the Registry to
Prevent Enterprise Connect from Storing Credentials” on page 43.

Caution
Users cannot update their Content Server passwords from Enterprise
Connect. If a user’s password expires, the user must connect to Content
Server using a Web browser to enter a new password.

3.1.1.2 Using Windows Credentials

If OpenText Directory Services (OTDS) is configured to support SSO (single sign-
on), Enterprise Connect supports single sign-on to Content Server using the
Windows logon credentials. For more information, see OpenText Directory Services -
Installation and Administration Guide (OTDS200203-IWC).

If the user’s credentials are not valid for OTDS, the user is prompted to provide a
different set of credentials for authentication. These credentials are stored for use in
subsequent sessions.

Enterprise Connect supports two factor authentication if you have enabled it for
OTDS. For more information, see section 7.1 “Configuring two-factor
authentication” in OpenText Directory Services - Installation and Administration Guide
(OTDS200203-IWC).

3.1.1.3 Using SSL Client Certificates

Enterprise Connect supports authentication through SSL (secure socket layer) client
certificates, if the Content Server Web server is configured to support client
certificate authentication. In this case, Enterprise Connect prompts the user to select
the correct client certificate the first time the user clicks the root node of the plug-in.
Enterprise Connect attempts to use this certificate for all subsequent connections
without prompting the user again. If the certificate is no longer valid, the user is
prompted to select a different certificate.

If you are using a type of certificate validation process that succeeds in Internet
Explorer but that fails in Enterprise Connect, you must add the
UseNativeCertificateAuthentication setting to the plug-in registry definition

40 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.1. Configuring Authentication

and set its value to 1. This setting causes the native operating system processes to
manage certificate handling rather than Enterprise Connect. In this case, users must
enter their certificate information for each new Enterprise Connect session. For
example, you might need to add this setting if your certificate validation process
requires users to enter PIN numbers. For more information, see “Editing the
Registry to Establish the Connection” on page 29.

Note: If the user launches a Web browser view of Content Server from
Enterprise Connect, the user is prompted to select the client certificate again.
The selection persists for the duration of the browser session.

3.1.1.4 Using Web Access Management Systems

Enterprise Connect also supports authentication through third-party Web access
management systems. OpenText Directory Services is required. The following Web
access management systems are supported:

• RSA Access Manager

• CA SiteMinder
• Entrust TruePass

For more information on creating an authentication handler in OpenText Directory

Services to work with third-party Web Access Management systems, see section 4.10
“Integrating Directory Services with Web Access Management applications” in
OpenText Directory Services - Installation and Administration Guide (OTDS200203-IWC).
OpenText recommends configuring the Web Access Management system to
intercept the Content Server URL, rather than intercepting calls to OTDS.

When third-party Web access management authentication is enabled, users will be

prompted to enter credentials by the application before they access Content Server.
Users will need to re-enter their credentials each time their sessions time out.

Caution
If you are using a third-party Web Access Management system, you must
enter the URL for the server in the Trusted Referring Websites setting on
the Content Server Configure Security Parameters administration page.

NGDCORE210200-IGD-EN-01 Installation Guide 41

Chapter 3 Configuring System Options

3.1.2 Using Content Server Domains

Enterprise Connect supports the use of Content Server Domains.

To make each user’s Domain Workspace appear in the Enterprise Connect Tree
Structure, you must move the Domain Workspace item to the list of items to display
in the Server Node on the Configure Display Settings administration page. For
more information, see “Configuring the Enterprise Connect Tree Structure and List
Pane” on page 59.

3.1.3 Managing Enterprise Connect Credential Storage

Options
By default, Enterprise Connect stores credentials in encrypted format on the local
file system when a user is prompted to enter credentials when connecting to a plug-
in. You can use the following settings to prevent Enterprise Connect from storing
credentials locally:

• The Allow Enterprise Connect client to store user credentials on disk check box
on the Configure Enterprise Connect System Settings Content Server
administration page. Clearing this check box prevents credentials from being
stored on all Enterprise Connect clients.
• The DontStoreCredentialsLocally registry entry on the Enterprise Connect
client. Setting this entry to 1 in a client’s registry prevents Enterprise Connect
from storing credentials on the client.

3.1.3.1 Configuring Storage of Enterprise Connect Credentials

The Allow Enterprise Connect client to store user credentials on disk check box
enables you to control how Enterprise Connect credentials are stored, and to push
this configuration out to all Enterprise Connect users accessing this instance of
Content Server. By default, when users sign into Enterprise Connect, their
credentials are stored on the local file system, in an encrypted format. This means
that users are not prompted to provide their credentials each time they start a new
Enterprise Connect session, unless their stored credentials become invalid. If
required, you can specify that user credentials are not stored, which means users
will be prompted to provide their credentials each time that they start a new
Enterprise Connect session.

Note: Your selection in this check box takes precedence over the option
specified in the DontStoreCredentialsLocally registry setting. For example,
if you clear this check box, credentials are never stored locally, regardless of
the registry setting. For more information, see “Editing the Registry to Prevent
Enterprise Connect from Storing Credentials” on page 43.

42 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.1. Configuring Authentication

3.1.3.1.1 To Configure How Enterprise Connect Credentials Are Stored

To configure how Enterprise Connect credentials are stored:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the System Settings link.

2. In the Credentials Management area, do one of the following:

• Select the Allow Enterprise Connect client to store user credentials on disk
check box if you want to store user credentials locally. By default, the check
box is selected.
• Clear the Allow Enterprise Connect client to store user credentials on disk
check box if you do not want to store user credentials locally.

3. Click Save Changes.

3.1.3.2 Editing the Registry to Prevent Enterprise Connect from Storing

Credentials
You can edit the following registry setting to prevent Enterprise Connect from
storing user credentials:

DontStoreCredentialsLocally (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

If this setting is 0 (the default), Enterprise Connect stores user credentials locally on
the file system. Users are not required to re-enter credentials between sessions
unless their stored credentials are no longer valid.

If this setting is 1, Enterprise Connect does not store user credentials. The user must
re-enter credentials when connecting to a plug-in for each new Enterprise Connect
session.

Note: The Allow Enterprise Connect client to store user credentials on disk
check box on the Enterprise Connect Configure System Settings
administration page in Content Server takes precedence over the
DontStoreCredentialsLocally setting. If you clear this check box on the
administration page, credentials are never stored locally on the client,
regardless of the value of DontStoreCredentialsLocally. If you select the
check box on the administration page, the registry setting determines whether
credentials are stored locally. For more information, see “Configuring Storage
of Enterprise Connect Credentials” on page 42.

NGDCORE210200-IGD-EN-01 Installation Guide 43

Chapter 3 Configuring System Options

3.1.4 Requiring Users to Sign In with a Browser

In some cases, you might want to require browser-based authentication with
Content Server. You can configure a registry setting to make Enterprise Connect
display a browser window to enable users to authenticate separately with Content
Server. The browser window is an embedded Internet Explorer window that is
closed after the authentication process is successfully completed.

This setting is useful in the following situations:

• Your environment uses a more complex authentication scheme where using

native Enterprise Connect authentication is not possible.
• You want improved support in Enterprise Connect for the session management
options available in Content Server, such as session expiry and termination
settings.

If this setting is enabled, Enterprise Connect is not involved in the authentication

process and does not cache user credentials. Users are required to re-authenticate at
each new session, as well as whenever their credentials have expired.

You can edit the following registry setting to require users to sign in with a browser:

ForceBrowserAuthentication (Multi-value String)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Content Server Desktop\

Connectivity (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Content Server
Desktop\Connectivity (on 64-bit systems)

You can enter hostname or URL values to specify which connections require users to
sign in with a browser. The URL can be a full or partial match to the URL used in the
connection. The hostname must match the hostname used in the URL. Enter each
hostname or URL on a separate line.

For example, if the Content Server URL is http://mycshost.acme.com:8080/cs/

cs.exe, the following entries are all valid:

http://mycshost.acme.com:8080

mycshost.acme.com

http://mycshost.acme.com:8080/cs/cs.exe

In this example, entering just mycshost would not be valid, because the fully-
qualified domain name is used in the URL.

Notes

• You can also manually add ForceBrowserAuthentication to the HKEY_

CURRENT_USER\SOFTWARE\OpenText\Content Server Desktop\

44 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.1. Configuring Authentication

Connectivity registry key for each Enterprise Connect user. Any values in
the HKEY_CURRENT_USER location are evaluated in addition to the values in
HKEY_LOCAL_MACHINE.

• This setting is also available for stand-alone installations of the Office Editor
client.

3.1.5 Preventing Authentication When Content Server

Connection Attempts are Redirected
In some environments, users who attempt to connect to Content Server when it is
unavailable are redirected to a different URL. For example, users connecting to
Content Server outside the corporate network might be redirected to a different web
page that instructs them to first sign in to the network through a VPN (virtual
private network). In such cases, Enterprise Connect or Office Editor could interpret
the redirected URL as a Content Server authentication prompt, which could lead to
pop-up browser windows being repeatedly displayed. This could also interfere with
Enterprise Connect switching to offline mode, depending on the value of the
OfflinePromptMode registry setting.

To prevent these issues from occurring, you can edit a registry setting to specify a
list of URLs that Enterprise Connect or Office Editor should not attempt to
authenticate against if redirected to when connecting to Content Server. You can edit
the following registry setting to specify the URLs:

DisableBrowserAuthentication (Multi-value String)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Content Server Desktop\

Connectivity (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Content Server

Desktop\Connectivity (on 64-bit systems)

You can enter hostname or URL values to specify which URLs Enterprise Connect or
Office Editor will not attempt to authenticate against if redirected to them. The URL
value can be a full or partial match to the URL. The hostname value must match the
hostname used in the URL. Enter each hostname or URL value on a separate line.

For example, if the URL is http://myredirectedhost.acme.com/redirect, the

following entries are all valid:

http://myredirectedhost.acme.com

myredirectedhost.acme.com

http://myredirectedhost.acme.com/redirect

In this example, entering just mycshost would not be valid, because the fully-
qualified domain name is used in the URL.

NGDCORE210200-IGD-EN-01 Installation Guide 45

Chapter 3 Configuring System Options

Note: For more information on OfflinePromptMode, see “Configuring Offline

Mode” on page 180.

3.2 Optimizing Performance

To ensure optimal response times between Enterprise Connect clients and Content
Server, consider enabling HTTP compression on the Web server that hosts Content
Server. HTTP compression can help to improve response times on the client. For
more information, see Best Practices for Web Server Configuration and High Performance
(https://knowledge.opentext.com/go/14469718).

3.3 Making Enterprise Connect Accessible from the

Content Server Web Interface
You can enable users to access Enterprise Connect when they are working with
specified content types in the Content Server Web Interface. When this feature is
available, users can access the Function menu for a supported item, choose
Enterprise Connect from Here, and the selected item appears in the Drag and Drop
panel. As administrator, you determine which item types this feature is available for.
By default, this action is labelled Enterprise Connect from Here. You can rename
this label if required.

Note: This feature is only available in Internet Explorer. In addition, it is only

available in the Content Server Web Interface for the items that you specify.

Tip: You can also specify which type of view users see when they use the
Enterprise Connect from Here command. For more information about the
Compact and Windows Explorer views, see “Enabling the Drag and Drop
Panel” on page 177.

3.3.1 To Make Enterprise Connect Accessible from the

Content Server Web Interface
To make Enterprise Connect accessible from the Content Server web
interface:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Enterprise Connect from Here area, enter the label that you want to
appear in the context menu in the Label for ‘Enterprise Connect from Here’
box. By default, Enterprise Connect from Here is used.

3. In the Enterprise Connect from Here area, do one of the following:

• In the Available list, select the items for which you want to make Enterprise
Connect from Here available and click Add.

46 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.4. Enabling the Mail as attachment Command on the Send to Menu

• In the Selected list, select items for which you do not want to have
Enterprise Connect from Here available and click Remove.

Note: By default, the following item types support this feature:

• Folders (0)
• Enterprise Workspaces (141)
• Personal Workspaces (142)
• Projects (202)
• Email Folders (751)
• Virtual Folders (899)

Tip: Click Add All to make Enterprise Connect from Here available for
all items. Click Remove All to make Enterprise Connect from Here
unavailable for all items.

4. Click Save Changes.

3.4 Enabling the Mail as attachment Command on

the Send to Menu
If this setting is enabled, the Mail as attachment command will be available on the
Send to menu in Content Server Smart View. Users can select one or more items in
Content Server Smart View, access the Mail as attachment command from the Smart
View Send to menu, and then email the selected items as attachments. This
command is available by default and is supported for Microsoft Outlook and IBM
Notes.

This command is only available for Documents and Emails.

Note: This feature is only available if you are using Enterprise Connect Client
version 20.2.0 or later.

3.4.1 To Enable the Mail as attachment Command on the

Send to Menu
To enable the Mail as attachment command on the Send to menu:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Smart View area, do one of the following in the Enable “Mail as
attachment” in the “Send to” menu check box:

• Select the check box to make the Mail as attachment command available on
the Smart View Send to menu. This is the default setting.

NGDCORE210200-IGD-EN-01 Installation Guide 47

Chapter 3 Configuring System Options

• Clear the check box to remove the Mail as attachment command from the
Smart View Send to menu.

3. Click Save Changes.

3.5 Supporting Previous Versions of Enterprise

Connect Framework
By default, users are permitted to use previous versions of the Enterprise Connect
Framework to connect to Content Server. However, you can force users to upgrade
to the most recent version of the Enterprise Connect Framework. If you enable this
function, users receive a message prompting them to upgrade to the most recent
version of the Enterprise Connect Framework when they initiate a new session. They
will not be permitted to sign in until they have successfully completed the upgrade.
Default text is provided for the message, but you can create a custom message if
required. For example, you could provide information about who to contact
regarding the upgrade or a link to an upgrade procedure.

For more information about upgrading the Enterprise Connect Framework and
module, see “Upgrading the Framework” on page 35.

3.5.1 To Configure Supported Versions of the Enterprise

Connect Framework
To configure supported versions of the Enterprise Connect Framework:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the System Settings link.

2. In the Client Compatibility area, do one of the following:

• Select the Prevent backwards compatibility with older versions of the

Enterprise Connect client check box if you want to force users to
immediately upgrade their instance of Enterprise Connect Framework. You
can update the message if required.

• Clear the Prevent backwards compatibility with older versions of the

Enterprise Connect client check box if you want to permit users to use their
current version of the Enterprise Connect Framework.

• If required, customize the upgrade message.

3. Click Save Changes.

48 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.6. Working with Additional Modules

3.6 Working with Additional Modules

This section provides information on how Enterprise Connect works with the
following additional modules:

• OpenText™ Remote Cache

• OpenText™ Records Management

Note: If OpenText™ Tempo™ Box, Content Server Edition is installed,

Enterprise Connect does not display the Tempo Box folder under the My
Workspace node. If you want to work with Tempo Box from the desktop,
OpenText recommends that you install OpenText Tempo Box Windows
Desktop Client. For more information, see OpenText Tempo Box, Content Server
Edition - Installation and Administration Guide (SYNC160102-IGD).

3.6.1 Using Remote Cache

Enterprise Connect supports the Remote Cache module. Consider the following
when configuring Enterprise Connect to work with Remote Cache:

• You must install the Remote Cache module on the Primary Server. Consult the
Enterprise Connect Release Notes for the required versions of the module.
• If you are using a version of Remote Cache earlier than 16.0–H009 or 16.2-H008,
you must copy the ngdrc.oll file to the ospace folder on all Remote Cache
servers. Do not copy this file to the Primary Server. The file is available in the
download section for Enterprise Connect on OpenText My Support.
• To connect a user to a specific Remote Cache server, specify the server name in
the Enterprise Connect Plug-in for Content Server URL. You must also ensure
that the Remote Cache server is assigned to the user in the user's Content Server
profile.
• Enterprise Connect supports both Remote Cache IP redirection and Primary
Server redirection. If the Enterprise Connect Plug-in for Content Server URL
connects to the Primary Server, the user will be redirected to the appropriate
Remote Cache server based on the redirection rules defined by the administrator.
• You can configure whether the links created by the Copy link to Clipboard and
Send to as link commands specify the user’s Remote Cache server or the
Primary Server. For more information, see “Specifying Link Paths” on page 50.

NGDCORE210200-IGD-EN-01 Installation Guide 49

Chapter 3 Configuring System Options

3.6.1.1 Specifying Link Paths

If you are using Remote Cache servers in your environment, you can specify the
destination that is copied to the Clipboard when users use the Copy Link to
Clipboard or Send To > Mail Recipient as Link options. It also applies when users
insert a link to a document in Office applications.

If you select User’s Remote Cache Server, the links will to point to the current user's
Remote Cache server. Choose this option, which is the default setting, if the users
who will access the links are all using this same Remote Cache server. However, if
users on different Remote Cache servers might access the links, you could select
Primary Server. This option causes all links to point to the Primary server.

Note: This setting is only available if Remote Cache servers are part of your
environment.

3.6.1.1.1 To Specify Link Paths

To specify link paths:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Item Links area, do one of the following in the When working with
document and folder links, create links that point to list:

• Click Primary Server if you want links to point to the Primary server.

• Click User’s Remote Cache Server if you want links to point the user’s
Remote Cache server. This is the default setting.

3. Click Save Changes.

3.6.2 Using Records Management to File Emails as Records

To enable Enterprise Connect users to file emails as records using Records
Management, you must do the following:

• Enable the Records Management module.

• Add object ID 749 (the email object ID) to the SubTypes line of the
[Classification] section in the opentext.ini file. If this line is not present
you must add it. For example:
SubTypes={0,136,144,145,749}

• Configure emails as managed object types on the Records Management

Administration Managed Objects page.

If you enable OpenText Records Management, you can also configure Content
Server to create cross-references between email records and their attachments when
copies of the attachments are filed as separate records. For detailed procedures and

50 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.7. Setting Timeouts for HTTP Requests

more information, see OpenText Content Server - Records Management

(LLESRCM200400-UGD).

For more information about configuring Content Server to store separate copies of e-
mail attachments, see “Configuring Content Capture Options” on page 166.

To enable cross-references between email and attachment records:

1. In Content Server Administration, navigate toRecords Management

Administration > Managed Objects, and then configure email as a managed
object type.

2. In the Records Management Workspace, navigate to Records Management

Administration > Table Maintenance, and then create a Cross Reference Code
and Related Code.

3. in the Records Management Workspace, navigate to Records Management

Administration > System Settings > RM Settings.

4. In the E-mail Attachment Cross Reference list box, click the Cross Reference
code you created to use for linking attachments to emails.

Note: This procedure does not apply if you enable compound emails.

3.7 Setting Timeouts for HTTP Requests

You can set the following timeout values for Enterprise Connect HTTP requests to
the server:

HttpFileTransferTimeout (DWORD)
Specifies how many seconds Enterprise Connect waits for a response to all
HTTP requests that cause a file to be uploaded. Default is 600.
HttpRequestTimeout (DWORD)
Specifies how many seconds Enterprise Connect waits for a response to all
HTTP requests except for requests that cause a file to be uploaded. Default is
300.

In most cases, OpenText recommends keeping the default settings. If users

experience frequent timeouts when attempting to upload or download large files, try
increasing the value of HttpFileTransferTimeout. The maximum value for both
settings is 10080. Setting either value to 0 causes the default value to be used.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\

HttpSettings (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\HttpSettings (on 64-bit systems)

NGDCORE210200-IGD-EN-01 Installation Guide 51

Chapter 3 Configuring System Options

3.8 Managing Content Server Browser Extensions

The Enterprise Connect and Office Editor clients interact with Content Server
extensions for some supported browsers. When users work in a browser, these
extensions enable certain actions in Content Server, such as editing or opening a
document with Office Editor.

Some Content Server browser extensions are installed as part of the Enterprise
Connect and Office Editor client installations. In other cases, users might need to
manually install or enable browser extensions before they can use them.

3.8.1 Enabling Browser Extensions

In some cases, the Content Server extension might not be installed or enabled in the
browser. If necessary, you must do the following to manually enable the extension:

Google Chrome™
The Enterprise Connect and Office Editor client installers automatically connect
to the Chrome web store and download and install the browser extension
during installation. If the installer is unable to connect to the store and
download the extension, each user must navigate to the store and manually
download and install the Content Server Browser Web Extension for Chrome
after the installation is complete.
By default, the extension is disabled when it is installed in Chrome. To enable
the extension, click Customize and control Google Chrome > More tools >
Extensions, and then select the Enable check box for the Content Server
Browser Web Extension.

Note: If native messaging hosts are restricted in Chrome, you might need
to add Office Editor to the list of allowed native messaging hosts. For more
information, see “Adding Office Editor to the List of Allowed Native
Messaging Hosts in Chrome” on page 56.
Mozilla® Firefox®
The Enterprise Connect and Office Editor client installers automatically deploy
the Firefox exension during installation. No connection to the Firefox store is
required.
For Firefox version 73 or previous, or for the Extended Support Release (ESR)
edition, the extension is installed automatically.
For non-ESR Firefox version 74 or later, you must manually install the browser
extension from file after installing Enterprise Connect or Office Editor. To do

this, click Tools > Add-ons > Extensions > Tools for all add-ons , and then
click Install add-on from file. The extension is stored in one of the following
locations:

• C:\Users\<username>\AppData\Local\Mozilla Firefox (for user

installations)

52 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.8. Managing Content Server Browser Extensions

• C:\Program Files\Mozilla Firefox\browser\extensions (for 64-bit

system installations)
• C:\Program Files (x86)\Mozilla Firefox\browser\extensions (for 32-
bit system installations)

If the extension is installed but not enabled, you can enable it by clicking Tools >
Add-ons > Extensions, and then clicking Enable next to Content Server
Browser Web Extension. The extension might have a different name, such as
OpenText Office Editor.
Internet Explorer
The Enterprise Connect and Office Editor client installers automatically install
the Internet Explorer exension during installation. No connection to the
Microsoft store is required. To enable the extension in Internet Explorer, click
Tools > Manage add-ons > Toolbars and Extensions. Under Show, make sure
All add-ons is selected. In the list of extensions, under Open Text Corporation,
right-click OpenText Office Editor, and click Enable.
Microsoft® Edge (Chromium edition)
The Chromium edition of Microsoft Edge uses the same browser extension as
Chrome. The Enterprise Connect and Office Editor client installers do not install
this extension. Users must manually navigate to the Chrome web store and
download and install the Content Server Browser Web Extension for Chrome.
Users must also enable the browser to allow extensions from other stores to be
installed.
Microsoft Edge
The Enterprise Connect and Office Editor client installers do not install the
extension for Microsoft Edge. Each user must install the extension using an
installation file that is included with the Office Editor module in Content Server.
No connection to the Microsoft store is required. For more information, see
“Installing the Browser Extension for Microsoft Edge” on page 53.

Note: For detailed instructions on enabling browser extensions, see the Content
Server Smart View User Help.

3.8.1.1 Installing the Browser Extension for Microsoft Edge

If a user attempts to edit a Content Server Document in Microsoft Edge, and they do
not have the extension installed, a message is displayed that contains a link to the
installation file for the extension. The user can click this link to install the extension
in Microsoft Edge.

Note: The information in this section applies only to the non-Chromium

edition of Microsoft Edge. for the Chromium edition of Microsoft Edge, users
must download and install the Content Server Browser Web Extension for
Chrome from the Chrome web store.

NGDCORE210200-IGD-EN-01 Installation Guide 53

Chapter 3 Configuring System Options

The name of the installation file is

contentserverwebextension_<version>.appxbundle. This file is stored in the
<Content_Server_Home>\support\webedit directory.

To enable the installation file to open correctly in the browser, you might need to
map the following MIME type and file extension on the Content Server Web server:

File extension
appxbundle

MIME type
application/appxbundle

If you use Microsoft Internet Information Services, you are required to add this
mapping.

To add the MIME type mapping in Microsoft IIS:

1. Start Internet Information Services (IIS) Manager.

2. In the Home pane, double-click MIME Types.

3. In the Actions pane, click Add.

4. In the Add MIME Type dialog box, enter the following, and then click OK:

File name extension

appxbundle

MIME Type
application/appxbundle

To install the browser extension for Microsoft Edge using the downloaded
appxbundle file:

1. In the Install Content Server Web Extension for Edge? dialog box, click Install.

54 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.8. Managing Content Server Browser Extensions

2. When the installation is completed, click Close.

3. In the Content Server Browser Web Extension just got added dialog box, click
Turn it on.

NGDCORE210200-IGD-EN-01 Installation Guide 55

Chapter 3 Configuring System Options

3.8.1.2 Adding Office Editor to the List of Allowed Native Messaging

Hosts in Chrome
The browser extension in Chrome uses native messaging to communicate with
Office Editor. If the Chrome NativeMessagingBlocklist registry key is configured
on the client to use the wildcard (*), all native messaging hosts are blocked by
default from communicating with Chrome extensions. In this case, you must edit the
registry and add Office Editor to the list of allowed native messaging hosts.

For more information, see CHROME ENTERPRISE POLICY LIST > NATIVE
MESSAGING (https://cloud.google.com/docs/chrome-enterprise/policies/
#nativeMessaging).

To add Office Editor to the list of allowed native messaging hosts in Chrome:

1. Add the following key to the registry if it does not already exist:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\
NativeMessagingAllowlist

2. In the NativeMessagingAllowlist key, create a STRING value with the

following attributes:

Name
If no other values exist in the key, name the value 1. If other values exist,
name the value the next available integer in the sequence.
Data
Assign the following data to the value: com.opentext.desktop.webext.
messaging

3.8.2 Configuring Domain Verification for Browser

Extensions
If a user performs an action in Content Server that uses a browser extension to
interact with an application, the application attempts to verify the security of the
domain on which Content Server is running. First, settings in the registry are
checked to see if the domain name is included in a list of verified domains. If it is
not, by default the user is prompted to manually verify that the domain name is
secure. If the domain name is verified, the application is invoked.

If the domain name is not verified, the application is not invoked, and the action
initiated by the user is not completed.

You can edit the following registry settings to configure how applications such as
Enterprise Connect and Office Editor verify domains for browser extensions:

TrustedDomains (Multi-value String)

You can edit this setting to specify a list of one or more fully-qualified domain
names that you want to be automatically verified, on a per-application basis.

56 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 3.8. Managing Content Server Browser Extensions

Enter each domain name on a separate line. The domain name must match the
name that is included in the URL that is displayed in the user’s browser.
For example, if users can connect to Content Server on the following URLs:
https://contentserver1.acme.com/otcs/llisapi.dll
https://contentserver2.acme.com/otcs/llisapi.dll
you would specify the following domain names:
contentserver1.acme.com
contentserver2.acme.com
You can use a period (.) at the beginning of a fully-qualified domain name as a
wildcard to match a range of domain names. As well, you can specify a partial
domain to match the end of a domain name. For example, if you specify .acme.
com or acme.com, all fully-qualified domain names that end in acme.com are
verified.
You can use an asterisk (*) to specify that all domain names are verified.
You can also specify IP addresses.
This setting is stored in the following location in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Browser Web
Extension\Applications\<Application_name> (on 32-bit systems)
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\OpenText\Content Server
Browser Web Extension\Applications\<Application_name> (on 64-bit
systems)
Notes

• The TrustedDomains setting is also stored at the following location in

the registry:
HKEY_CURRENT_USER\SOFTWARE\OpenText\Content Server Browser
Web Extension\Applications\<Application_name>
This setting stores domain names that the user manually verifies after
being prompted. See the description of the
TrustedDomainsPromptBehavior setting for more information.
• In addition to the TrustedDomains setting, Enterprise Connect and
Office Editor also check the plug-in or repository URL stored in the
registry to see if it matches the domain name in the browser. If they
match, the domain name is verified. This means that you do not need to
add names to the TrustedDomains setting if your users always connect
to the same Content Server URL, and the same domain name is also used
in the Enterprise Connect plug-in or the Office Editor repository URL. If
you are using Office Editor on its own without Enterprise Connect, by
default users will be prompted to verify the domain the first time they
attempt to open or edit a document unless you specify the domain name
in the TrustedDomains setting for Office Editor.
TrustedDomainsPromptBehavior (DWORD)
Determines what happens if an application is unable to verify a domain name.

NGDCORE210200-IGD-EN-01 Installation Guide 57

Chapter 3 Configuring System Options

You can specify the following values for this setting:

0
The user is never prompted to verify the domain. The domain can only be
verified by the application. If the application cannot verify the domain, the
user is unable to complete the requested action.
1 (default)
The user is prompted to manually verify the domain. If the user verifies the
domain, the domain name is added to the TrustedDomains setting in HKEY_
CURRENT_USER.

This setting is stored in the following location in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Browser Web
Extension\Applications (on 32-bit systems)
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\OpenText\Content Server
Browser Web Extension\Applications (on 64-bit systems)

Note: The domain verification process and registry settings described in this
section are not supported for Internet Explorer.

58 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 4
Configuring Navigation and Display Options

This chapter describes the following navigation and display options that you can
configure for Enterprise Connect:

• The nodes that appear in the Tree Structure.

• The labels that are used for items such as the Enterprise Connect menu and root
node in the Tree Structure.
• The columns that appear when users browse Enterprise Connect.
• Configuration options for the Reading Pane, including which viewer is used to
preview documents.
• The availability of context menu and ribbon commands.
• Whether hidden Content Server items are shown in Enterprise Connect.
• Options for managing folders, including setting the folder cache timeout value,
and specifying the maximum number of folders that can appear under a node in
the Tree Structure.
• Language settings for Enterprise Connect and Office Editor.

4.1 Configuring the Enterprise Connect Tree

Structure and List Pane
You can select which nodes appear in the Server Node in the Enterprise Connect
Tree Structure. You can also add items to the Volumes folder and the Other Items
folder. In addition, you can change the order in which the items appear in the Tree
Structure. A default configuration is provided, but you can modify this if required.

Note: If you are using Domain Workspaces, you must move it from the
Available Items list to the Items to Use list to make it available to users. The
Domain Workspace then becomes visible to the Enterprise Client tree and is for
the Domain that the user is a member of.

If you want Enterprise Connect users to be able to access the Public Email Volume,
their Personal Email Volume, and any delegated Email Volumes in the Enterprise
Connect tree, move the Email Volume node from the Available Items list to the
Items to Use list in the Server Node area. The Email Volume node only appears in
the list of Available Items if you have successfully installed and configured support
for Email Archiving.

Note: Enterprise Connect users with administrative privileges will also be able
to access the System Email Volume.

NGDCORE210200-IGD-EN-01 Installation Guide 59

Chapter 4 Configuring Navigation and Display Options

You can also specify which items appear in the Personal node in the Enterprise
Connect Tree Structure. Some items appear by default, and you can add or remove
items if required. Available items include those that appear in the Web UI Personal
menu. However, the available items may vary depending on the Content Server
modules installed in your environment. For some items, you may see a Web UI
view.

4.1.1 To Configure the Tree Structure and List Pane

To configure the Tree Structure and List Pane:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Display Settings link.

2. In the Server Node area, do the following:

• In the Available Items list, select the items that you want to display in the
Server Node and click Add.

Note: Include Volumes Node and Other Items in this list if you want
to expose these items and their contents in the Server Node. Any items
remaining in the Available Items list are not displayed.
• To change the order of the items in the Server Node, select the appropriate
item in the Items to Use list, and then click Move Up or Move Down as
required.

3. In the Volumes Node and Other Items Node areas, do the following:

• In the Available Items list, select the items that you want to display and
click Add.
• To change the order of the items, select the appropriate item in the Items to
Use list, and then click Move Up or Move Down as required.

4. In the Personal Node area, do the following:

• In the Available Items list, select the items that you want to display and
click Add.
• To change the order of the items, select the appropriate item in the Items to
Use list, and then click Move Up or Move Down as required.

Note: The My Settings item enables Enterprise Connect users to launch

the My Enterprise Connect Settings page, where they can control settings
for generating email names. This page includes many of the settings that
are available in the Enterprise Connect Configure Email Settings page.
Users will be able to override any settings that you have applied. By
default, this item is in the Items to Use list. If you do not want users to
access this page, move it to the Available Items list. For more information
about email naming rules, see “Defining Email Naming Conventions”
on page 126.

60 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.2. Modifying Labels

5. Click Save Changes.

Tip: Click Add All or Remove All to move all items from the Available Items
or Items to Use lists as required.

4.2 Modifying Labels

You can modify the labels for the Enterprise Connect menus that are displayed in
applications such as Office and Outlook, as well as the name of the root node in the
Enterprise Connect tree.

You can also modify language-specific labels for the Enterprise Connect Easy Access
pane.

4.2.1 Modifying Menu and Tree Labels

You can edit the following string values to configure Enterprise Connect labels that
appear in Explorer, Outlook, Office, and Acrobat:

AdobeAcrobatMenuLabel
String label of the command that is displayed in the Acrobat File menu. By
default, this is Enterpr&ise Connect. Place an ampersand (&) before the
character that you want to configure as a keyboard shortcut for the command.
Do not use a key that conflicts with the Office keyboard shortcuts.
EnterpriseConnectDisplayName
String label of the root node that is displayed in the Tree Structure. This value is
also applied to the Enterprise Connect Copy/Move dialog box. By default, this
is Enterprise Connect.

Note: In Outlook 2016, this label might be automatically converted to

lowercase. For example, Enterprise Connect might become enterprise
connect in the Outlook Tree Structure.
MenuLabel
String label of the menu that is displayed in the Outlook or Explorer menu bar.
By default, this is Enterprise &Connect. Place an ampersand (&) before the
character that you want to configure as a keyboard shortcut for the command.
Do not use a key that conflicts with the Outlook or Explorer keyboard shortcuts.
OfficeRibbonKeyTip
The default KeyTip for the Enterprise Connect tab that is displayed on the
ribbon in Office. By default, this is C. Do not use a key that conflicts with another
Office KeyTip.
OfficeRibbonLabel
String label of the Enterprise Connect tab that is displayed on the ribbon in
Office. By default, this is Enterprise Connect.

Note: This registry setting is not compatible with the Customize the
Ribbon command in Office. You can use either the OfficeRibbonLabel

NGDCORE210200-IGD-EN-01 Installation Guide 61

Chapter 4 Configuring Navigation and Display Options

setting, or the Customize the Ribbon command, but not both, to configure
the name of the tab.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

4.2.2 Modifying Language-Specific Labels

You can edit registry settings in the following location to specify new values for
language-specific labels that appear in the user interface:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\CustomUI

\<language_code> (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\CustomUI\<language_code> (on 64-bit systems)

You can specify a different value for each supported language. The language codes
include the following:

ar
Arabic
ca-ES
Catalan
de
German
en
English
es
Spanish
fi-FI
Finnish
fr
French
it
Italian
ja
Japanese
kk-KZ
Kazakh

62 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.3. Displaying Additional Columns

nl
Dutch
pt
Portuguese
ru
Russian
sv
Swedish
uk-UA
Ukrainian
zh-CN
Chinese

By default, the registry settings are empty and the values for the labels are set
internally by Enterprise Connect. You can override the default label by specifying a
value for the corresponding setting in the appropriate language-specific key in the
registry.

The label that actually appears in the display corresponds to the language that
Enterprise Connect is currently set to use. For more information, see “Changing the
Enterprise Connect Language Setting” on page 79.

You can edit the following string settings:

EasyAccessMenu
The label for the Easy Access pane button that is displayed in the Outlook
ribbon.
EasyAccessPaneCaption
The label for the Easy Access pane title.

4.3 Displaying Additional Columns

As administrator, you can use the Configure Browse View Columns Settings
administration page to configure which columns are displayed by default in the
Enterprise Connect display in Outlook and Explorer, as well as in the Enterprise
Connect Open dialog box. For more information, see “Configuring Column
Displays” on page 64.

The columns that are available to configure include the following:

• Standard Content Server columns, such as Size or File Type.

• Email Services columns.
• Additional columns provided by Content Server optional modules, such as
Records Management.

NGDCORE210200-IGD-EN-01 Installation Guide 63

Chapter 4 Configuring Navigation and Display Options

Note: In Content Server, you can create custom columns from data sources in
the Content Server Facets Volume, and configure these columns to appear
globally or on selected folders in the Content Server Browse View. These
custom columns also appear on the folders in Enterprise Connect. However,
you cannot use the Configure Browse View Columns Settings administration
page to configure these columns. These columns appear by default at the far
right of the column view in Enterprise Connect.

For default search result columns, you can configure the default Search Form in
Content Server. For more information, see “Setting Search Columns” on page 162.

After a column becomes visible in Enterprise Connect, users can personalize their
views by showing or hiding available columns in Explorer, Outlook, and the
Enterprise Connect Open dialog box. Column selections apply to all folders of the
same subtype, on a per-integration basis. For example, if a user adds a column to the
view of a Project in Explorer, the column is automatically displayed for all Projects
in Explorer. For more information, see section 2.3.3 “Specifying Columns in the List
Pane” in OpenText Enterprise Connect - User Getting Started Guide (NGDCORE200400-
UGD).

Note: If you make a change to the default set of columns, users who have
modified the default column display in the client will not see the change unless
they manually update their column display. For example, if you add a column
to a container type, users who have customized the default column display for
that container type must either manually add the new column to the display,
or use the Reset View command to revert to the default column configuration.
One exception to this is if you remove a column from the default column
display. In this case, users will no longer see the column, even if they have
customized the column display on the client.

4.3.1 Configuring Column Displays

You can specify column behavior when users are browsing in Enterprise Connect.
For Content Server containers, such as Folders, Compound Folders, and Milestones,
you can specify which columns users can see by default, as well as which columns
users can add or remove when they are working in Outlook and Windows Explorer.
You can also specify the order that the selected columns appear in and custom
widths for columns. You can use the Other option to specify these settings for
container types that are not included in the container list, such as Workflows or
Projects.

The columns available will vary depending on the type of container, but can include
the default columns for Enterprise Connect, columns specific to Content Server
modules such as Records Management, and Content Server dynamic global
columns. Because Content Server dynamic local columns are unique for each folder,
they do not appear in this page. However, they are available to users in the Explorer
and Outlook column choosers.

Users can add, remove, or reorganize the column settings to suit their preferences in
the Enterprise Connect client. If a user has customized the default column display on

64 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.3. Displaying Additional Columns

their client, any changes that you make on this page are only applied if the user
resets their column display to the default setting or adds the individual columns
using the Explorer or Outlook column choosers. If you specify that a column is not
available, it will be automatically removed from the client UI.

4.3.1.1 To Configure Column Displays

To configure column displays:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Browse View Columns Settings link.

2. In the Columns area, click the <container type> button in the Action column
of the container that you want to configure.

Note: In the Enterprise Connect client, users can add, remove, and
reorganize columns for containers according to their preferences. For more
information about working with columns, see OpenText Enterprise Connect
- User Getting Started Guide (NGDCORE200400-UGD).

3. In the configuration page for the selected container, do the following for each of
the listed columns:

a. In the Available column, clear the check box of any column that you do not
want to make available to users. By default, some columns may be selected,
which means that you must clear the check box of any columns that you
want to hide from users.
b. In the Display by Default column, select the check box of any column that
you want users to see by default.
c. In the Column Width column, specify the width, in pixels, that you want to
apply to specific columns.

Note: If you do not apply a value, Enterprise Connect will

automatically size the column.
d. In the Display Order column, click the Move Up button or the Move
Down button to move the selected column in the appropriate location.

4. Click Save Changes.

NGDCORE210200-IGD-EN-01 Installation Guide 65

Chapter 4 Configuring Navigation and Display Options

4.4 Configuring Reading Pane Options

You can do the following to configure the Enterprise Connect Reading Pane:

• Specify which viewer to use for previewing documents in the Reading Pane.
• Set the default initial state of the Reading Pane.
• Specify whether tabs are displayed for documents in the Reading Pane.

4.4.1 Selecting a Viewer for the Reading Pane

The Enterprise Connect Viewer enables users to view items in supported formats
using the View tab in the Reading Pane, even if the native application is not
installed. For example, a user can view an item that was created in Microsoft Project,
even if the user does not have Project installed. The Enterprise Connect Viewer
enables users to print, search, copy, and adjust the view of the selected item. The
Enterprise Connect Viewer is installed automatically with Enterprise Connect and
no additional configuration is required.

As an alternative to the Enterprise Connect Viewer, you can use OpenText™

Document Filters to enable users to view items in supported formats. You can
specify which viewer you want to use in the Viewer area of the Enterprise Connect
Display Settings page. Enterprise Connect Viewer is used by default. For more
information about Document Filters, see OpenText Document Filters - Administrator's
Guide (LLESCF-AGD).

If you are using Enterprise Connect Viewer, you can specify the maximum size of
documents that users can preview when they are working in Windows Explorer or
the Enterprise Connect Open dialog box. You might need to enable this setting to
avoid long downloads of large documents.

When users attempt to preview a document that is larger than the specified
maximum, an error message explains that the document exceeds the maximum size.

By default this setting is disabled, which means that there is no size limit for
previewed documents in Windows Explorer and the Enterprise Connect Open
dialog box.

Notes

• To access this feature, you must be working with version 16.2.5 or later of the
Enterprise Connect client and server.
• This feature does not apply to documents previewed in Microsoft Outlook.

66 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.4. Configuring Reading Pane Options

4.4.1.1 To Select a Viewer

To select a viewer:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Display Settings link.

2. In the Viewer area, click one of the following to specify which viewer you want
to use to view items in the View tab in the Reading Pane:

• OpenText Document Filters

• Enterprise Connect Viewer

3. Optional If you are using Enterprise Connect Viewer, select the Limit size of
documents for viewer check box, and then specify a maximum value in the
Specify maximum document size (MB) box.

4. Click Save Changes.

4.4.2 Setting the Default Reading Pane Display

You can use the following registry setting to specify whether the Reading Pane is
hidden or displayed when a user starts Enterprise Connect for the first time:

PreviewState (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

If this setting is 1, the Reading Pane is displayed by default. If this setting is 0 (the
default), the Reading Pane is hidden by default.

When a user clicks the Preview button to change the state of the Reading Pane, this
setting no longer applies. The state of the Reading Pane is subsequently controlled
by the Preview button, and is recorded by the following registry setting:

HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect\PreviewState

NGDCORE210200-IGD-EN-01 Installation Guide 67

Chapter 4 Configuring Navigation and Display Options

4.4.3 Displaying Tabs in the Reading Pane

You can use the following registry setting to specify whether the Reading Pane
displays tabs for documents:

ShowOnlyContentInPreview (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

If this setting is 1 (the default), no tabs are displayed in the Reading Pane when a
document is selected in the List Pane. The Reading Pane displays only the document
preview.

If this setting is 0, all available tabs are displayed in the Reading Pane when a
document is selected in the List Pane.

If this setting is 2, document preview is not available. The View tab is not displayed
in the Reading Pane when a document is selected in the List Pane. All other tabs are
displayed.

This setting does not apply to folders or other containers. When a container is
selected in the List Pane, tabs for the container are always displayed in the Reading
Pane.

This setting can also be added to the following location in HKEY_CURENT_USER:

HKEY_CURENT_USER\SOFTWARE\Open Text\Enterprise Connect

If this setting is in HKEY_CURENT_USER, it takes precedence over the setting in HKEY_

LOCAL_MACHINE.

Note: In Outlook, the UseOutlookToPreviewDocuments setting takes

precedence over ShowOnlyContentInPreview. If
UseOutlookToPreviewDocuments is set to 1, the Outlook viewer is used to
preview content in the Outlook Reading Pane, regardless of the value of
ShowOnlyContentInPreview. For more information, see “Using the Outlook
Viewer Instead of the Enterprise Connect Viewer” on page 134.

68 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.5. Managing Context Menu and Ribbon Commands

4.5 Managing Context Menu and Ribbon Commands

You can do the following to manage commands on Enterprise Connect context
menus and ribbons:

• Show or hide core Enterprise Connect menu commands.

• Configure which commands are available on the Advanced context menu.
• Configure which Content Server context menu commands are available in
Enterprise Connect.
• Specify whether context menu commands are launched in a full browser.

Note: You can also use the Enterprise Connect Menu Settings administration
page to manage the following context menu command settings:

• For the Send to Desktop Location command, you can specify which
subtypes can be downloaded to the desktop. For more information, see
“Specifying Which Subtypes Can Be Sent to the Desktop” on page 170.
• For the Download Offline command, you can specify which subtypes can
be taken offline. For more information, see “Specifying Which Subtypes Can
Be Taken Offline” on page 179.
• For the Copy/Move command, you can specify which subtypes support it.
For more information, see “Configuring the Copy/Move Command”
on page 168.

4.5.1 Configuring Enterprise Connect Context Menu Items

Using the Show or hide Enterprise Connect menu items lists, you can specify
which Enterprise Connect context menu items are available to your users. This
setting also applies to those context menu items that appear in the Enterprise
Connect ribbon in Office and Outlook, such as Properties. By default, all Enterprise
Connect context items commands are available except for the following:

• Send To / Clipboard as Download Link

• Send To / Clipboard as Open Link
• Send To / Clipboard as Overview Link
• Send To / Clipboard as Properties Link

NGDCORE210200-IGD-EN-01 Installation Guide 69

Chapter 4 Configuring Navigation and Display Options

4.5.1.1 To Show or Hide Enterprise Connect Context Menu Items

To show or hide Enterprise Connect context menu commands:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Basic Menu Items area, do one of the following:

• In the Hidden list, select the context menu items that you want to show and
click Add.
• In the Shown list, select the context menu items that you want to hide and
click Remove.

Tip: Click Add All to make all items in the Hidden list available to users.
Click Remove All to make all items unavailable to users.

3. Click Save Changes.

4.5.2 Configuring the Advanced Context Menu

By default, some Content Server context menu commands are available in the
Advanced context submenu. You can move selected commands to the top level of
the context menu using the Promote these actions in Advanced context menu to
Top Level box. Promoted commands are automatically grouped together in the top-
level context menu. For example, the Zip and Download command is located on the
Advanced context submenu. If your users frequently use this command, you can
add ZipDwnld to the box and this command will be promoted to the top level of the
context menu.

The following table lists the command IDs for some commonly used context menu
items.

Command Command ID
Add Item AddItem
Add to Favorites MakeFavorite
Add Version AddVersion
Browse from Here BrowsefromHere
Collect Collect
Configure EditConfig
Copy Copy
Copy Link to Clipboard CopyLinktoClipboard
Delete Delete
Download Download

70 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.5. Managing Context Menu and Ribbon Commands

Command Command ID
Edit (Poll) EditPoll
Find Similar OTCIndexResultFindSimilar
Go to Original Location Gotooriginallocation
Launch in Browser LaunchInBrowser
Make Generation CreateGeneration
Make News CreateNewsAndAttach
Make Shortcut CreateAlias
Move Move
New CreateChild
Open Rendition openrendition
Overview Overview
Permissions Permissions
Print Print
Properties Properties
Rate It RateIt
Remove from Collection Removefromcollection
Rename Rename
Reserve (Documents) ReserveDoc
Reserve (Compound Documents) Reserve
Set as Exemplar SetExemplar
Set Notification SetNotification
Unreserve (Documents) Unreservedoc
Unreserve (Compound Documents) Unreserve
Zip and Download ZipDwnld
Zip and Email ZipEmail

NGDCORE210200-IGD-EN-01 Installation Guide 71

Chapter 4 Configuring Navigation and Display Options

4.5.2.1 To Configure the Advanced Context Menu

To configure the Advanced context menu:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Menu Behavior area, enter the appropriate command IDs in the Promote
these actions in Advanced context menu to Top Level box.

Notes

• Use a comma to separate the command IDs.

• Do not use spaces between the commas and the command IDs.
• Command ID values are not case sensitive.

3. Click Save Changes.

4.5.3 Configuring Context Menu Actions

By default, almost all Content Server context menu items or commands are available
to Enterprise Connect users. You can remove a context menu item by entering its ID
in the Exclude these actions from the context menu box.

For example, if you do not want users to access the Zip and Download command
from the context menu, add ZipDwnld to the excluded item list, and this command
will no longer appear in the context menu. The following table lists the command
IDs for some commonly used context menu items.

Note: By default, the Download command is excluded from the Content

Server context menu. If required, you can remove it from the excluded item list
to make it available to Enterprise Connect users.

Command Command ID
Add Item AddItem
Add to Favorites MakeFavorite
Add Version AddVersion
Browse from Here BrowsefromHere
Collect Collect
Configure EditConfig
Copy Copy
Copy Link to Clipboard CopyLinktoClipboard
Delete Delete
Download Download

72 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.5. Managing Context Menu and Ribbon Commands

Command Command ID
Edit (Poll) EditPoll
Find Similar OTCIndexResultFindSimilar
Go to Original Location Gotooriginallocation
Launch in Browser LaunchInBrowser
Make Generation CreateGeneration
Make News CreateNewsAndAttach
Make Shortcut CreateAlias
Move Move
New CreateChild
Open Rendition openrendition
Overview Overview
Permissions Permissions
Print Print
Properties Properties
Rate It RateIt
Remove from Collection Removefromcollection
Reserve (Documents) ReserveDoc
Reserve (Compound Documents) Reserve
Set as Exemplar SetExemplar
Set Notification SetNotification
Unreserve (Documents) Unreservedoc
Unreserve (Compound Documents) Unreserve
Zip and Download ZipDwnld
Zip and Email ZipEmail

Important

• OpenText recommends that you do not remove the Open context menu
item.
• The Printer Friendly View, WebDAV Folder View, and Copy/Move
context menu commands for non-container items are never available to
Enterprise Connect users.

NGDCORE210200-IGD-EN-01 Installation Guide 73

Chapter 4 Configuring Navigation and Display Options

4.5.3.1 To Configure the Context Menu

To configure the context menu:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Excluded Actions area, enter the command ID of any additional context
menu items that you do not want Enterprise Connect users to access in the
Exclude these actions from the context menu box.

Notes

• Use a comma to separate the command IDs.

• Do not use spaces between the commas and the command IDs.
• Command ID values are not case sensitive.

3. Click Save Changes.

4.5.4 Launching Context Menu Commands in a Full Browser

You can specify if you want certain context menu commands to launch in a full
browser by entering their IDs in the Launch these context menu actions in a full
browser box, in the Menu Behavior area. By default, no commands are specified.

For example, enter the Rename command. When users select an item and then choose
this context menu command, a new browser will launch, where users can rename
the selected item.

The following table lists the command IDs for some commonly used context menu
items.

Command Command ID
Add Item AddItem
Add to Favorites MakeFavorite
Add Version AddVersion
Browse from Here BrowsefromHere
Collect Collect
Configure EditConfig
Copy Copy
Copy Link to Clipboard CopyLinktoClipboard
Delete Delete
Download Download
Edit (Poll) EditPoll

74 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.5. Managing Context Menu and Ribbon Commands

Command Command ID
Find Similar OTCIndexResultFindSimilar
Go to Original Location Gotooriginallocation
Launch in Browser LaunchInBrowser
Make Generation CreateGeneration
Make News CreateNewsAndAttach
Make Shortcut CreateAlias
Move Move
New CreateChild
Overview Overview
Permissions Permissions
Print Print
Properties Properties
Rate It RateIt
Remove from Collection Removefromcollection
Rename Rename
Reserve (Documents) ReserveDoc
Reserve (Compound Documents) Reserve
Set as Exemplar SetExemplar
Set Notification SetNotification
Unreserve (Documents) Unreservedoc
Unreserve (Compound Documents) Unreserve
Zip and Download ZipDwnld
Zip and Email ZipEmail

4.5.4.1 To Launch Context Menu Commands in a Full Browser

To launch context menu commands in a full browser:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Menu Behavior area, enter the appropriate command IDs in the Launch
these context menu actions in a full browser box.

Notes

• Use a comma to separate the command IDs.

• Do not use spaces between the commas and the command IDs.

NGDCORE210200-IGD-EN-01 Installation Guide 75

Chapter 4 Configuring Navigation and Display Options

• Command ID values are not case sensitive.

3. Click Save Changes.

4.6 Displaying Hidden Items in Enterprise Connect

You can control if items that have been marked as hidden in Content Server appear
in Enterprise Connect. If you select the Display hidden items check box, hidden
items, such as Folders, Documents, or Task Lists are fully accessible in the Enterprise
Connect tree. Users can view hidden items in the List Pane for both Outlook and
Explorer and they are included in search results.

4.6.1 To Display Hidden Items in Enterprise Connect

To display hidden items in Enterprise Connect:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Display Settings link.
2. In the Hidden Items area, do one of the following:

• Select the Display hidden items check box to display all hidden items in
Enterprise Connect.
• Clear the Display hidden items check box if you do not want to display
hidden items in Enterprise Connect. This is the default setting.
3. Click Save Changes.

4.7 Managing Folders

You can do the following to manage folders in Enterprise Connect:

• Set the timeout value for the folder cache, which determines how frequently the
display of folder contents is updated.
• Set a limit to the number of folders that can be displayed beneath each folder in
the Tree Structure.

4.7.1 Setting the Folder Cache Timeout Value

By default, when a user opens a folder, Enterprise Connect refreshes its cache of the
folder’s contents in the display if three minutes or more have passed since the folder
was last opened. For example, consider the following sequence of events:

• A user opens a folder in Enterprise Connect. The display of the folder’s contents
is cached by Enterprise Connect.
• A second user adds a document to the same folder.
• After three minutes have passed, the first user reopens the same folder.
Enterprise Connect refreshes the cache of the folder’s contents, and updates the
display to show the document that was added by the second user.

76 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.7. Managing Folders

In this example, if the first user opens the folder before three minutes have passed,
the display is not updated to show the newly added document, because the folder
cache timeout has not yet been reached. The user would need to manually use the
Refresh command or reopen the folder after the timeout is reached in order to see
the updated folder contents.

You can edit the following registry setting to specify a different timeout value for the
Enterprise Connect cache of folder contents:

FolderCacheTimeout (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

This setting specifies, in seconds, how much time must have passed before
Enterprise Connect refreshes the cache of folder contents that a user visits in an
Enterprise Connect session. By default, the value is 180 seconds (three minutes). If
this setting is 0, Enterprise Connect never refreshes the folder content cache.
Decreasing this value can result in a more up-to-date display of folder contents, but
can also have a negative impact on tree browsing performance.

Note: The display of an open folder’s contents in the tree is not updated unless
the user manually reopens the folder. Enterprise Connect only updates the
cache of a folder’s contents if the user triggers an update by reopening the
folder in the tree after the timeout specified by FolderCacheTimeout is
reached.

4.7.2 Limiting the Number of Folders Displayed in the Tree

Structure
Unlike the List Pane, the Enterprise Connect Tree Structure does not support
pagination when displaying items. To make navigation easier and improve response
time, you can set a limit on how many folders are displayed beneath each folder that
appears in the Tree Structure. This limit can be useful when one or more folders in
the tree contain a very large number of subfolders.

The following registry setting controls the Tree Structure folder limit:

TreePaneItemLimit (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

NGDCORE210200-IGD-EN-01 Installation Guide 77

Chapter 4 Configuring Navigation and Display Options

The default value is 1000. When this setting is 0, no limit is applied to the number of
folders that can appear beneath a folder in the Tree Structure. To set a limit, specify a
positive integer of 1 or greater. For example, if you specify 500, no folder in the Tree
Structure can display more than 500 folders underneath it when it is expanded.

The total number of folders displayed can still be more than the limit, since the limit
applies to individual folders only. For example, if the limit is 500, you could expand
two folders that each contain 500 folders, and the total number of folders displayed
in the Tree Structure would be more than 1000.

The folders are truncated based on the order in which they are returned by the
server. Changing the default sort order by clicking a column header in the List Pane
does not affect which folders are displayed.

The folder limit applies to the Tree Structure that is displayed in the following
locations:

• The Explorer and Outlook navigation panes.

• The left pane of the Enterprise Connect Open and Enterprise Connect Save As
dialog boxes.
• The left pane of the native Windows Open and Save As dialog boxes for
Extended Integration applications, such as Notepad, that use these dialog boxes.
This does not include Adobe Reader.
• The left pane of other dialog boxes that support navigation to Enterprise
Connect, such as the Insert File dialog box in Word.
• The Enterprise Connect Copy/Move dialog box in Explorer and Outlook.
• The Copy/Move to Enterprise Connect dialog box in IBM Notes.
• The Search Enterprise Connect dialog box in Explorer and Outlook.
• The Easy Access pane in Outlook.

This limit does not apply to the folder view in the List Pane (the right pane), which
always displays the contents of the folder selected in the Tree Structure. It applies to
the Saved Search and Search History nodes, but not to the immediate children of
the History node that appears in the Enterprise Connect Open and Enterprise
Connect Save As dialog boxes.

Caution
If you limit the number of folders that can be displayed in the Tree
Structure, users might be unable to navigate to all folders in the Enterprise
Connect Copy/Move and Copy/Move to Enterprise Connect dialog boxes,
or in the Enterprise Connect Save As dialog box when saving a new
document. The search and history functions in the Enterprise Connect
Save As dialog box can still be used to locate and access a folder that is not
displayed in the Tree Structure.

78 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 4.8. Configuring Language Settings

4.8 Configuring Language Settings

By default, Enterprise Connect and Office Editor are displayed in the language
corresponding to the client’s display language setting. You can edit the registry to
specify different language settings for these applications.

4.8.1 Changing the Enterprise Connect Language Setting

By default, Enterprise Connect is displayed in the language corresponding to the
client’s display language setting. If the display language is not supported, Enterprise
Connect is displayed in English.

You can add the following registry setting to specify a different language setting for
Enterprise Connect:

Locale (string)

You must add this setting to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

In this setting, enter the appropriate two-letter code for the language you want to
use. Only enter a code for a language that is supported by the version of Enterprise
Connect installed on the client. For more information on supported languages and
language codes, see the Release Notes.

You can also add the Locale setting to the following location in HKEY_CURRENT_
USER. The setting in this location takes precedence over the one in HKEY_LOCAL_
MACHINE:

HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect

Note: Office Editor uses a separate Locale setting to determine which

language it uses. If you change the Enterprise Connect language setting, you
must also change the Office Editor setting to ensure that both components are
displayed in the same language. For more information, see “Changing the
Office Editor Language Setting” on page 80.

NGDCORE210200-IGD-EN-01 Installation Guide 79

Chapter 4 Configuring Navigation and Display Options

4.8.2 Changing the Office Editor Language Setting

By default, Office Editor is displayed in the language corresponding to the client's
display language setting. If the display language is not supported, Office Editor is
displayed in English.

You can add the following string registry setting to specify a different language
setting for Office Editor:

Locale

You must create this setting in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

In this setting, enter the appropriate two-letter code for the language you want to
use. Only enter a code for a language that is supported by the version of Office
Editor installed on the client. For more information on supported languages and
language codes, see the Release Notes.

You can also add the Locale setting to the following location in HKEY_CURRENT_
USER. The setting in this location takes precedence over the one in HKEY_LOCAL_
MACHINE:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences

Note: Enterprise Connect uses a separate Locale setting to determine which

language it uses. If you change the Office Editor language setting, you must
also change the Enterprise Connect setting to ensure that both components are
displayed in the same language. For more information, see “Changing the
Enterprise Connect Language Setting” on page 79.

80 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 5
Configuring Editing Options

This chapter describes the following navigation and display options that you can
configure for Enterprise Connect:

• Configuring Office Editor.

• Specifying the upload mode for edited documents.
• Configuring double-click actions for Office documents.
• Forcing the use of the Enterprise Connect Open and Save As dialog boxes in
Office and Acrobat.
• Specifying which applications support Extended Integration.
• Mapping MIME types to file extensions.
• Removing the ability to edit specific file types.
• Enabling users to insert properties in Office documents.

5.1 Using Office Editor

You can do the following to configure Office Editor:

• Specify the location of the document cache.

• Configure the My Working Documents List dialog box.
• Configure logging.
• Specify the frequency of the notification message.
• Specify processes to ignore when syncing documents.
• Enable Office Editor to store credentials locally.
• Customize the Office Editor installation or upgrade message.
• Specify non-lockable and lockable file types.
• Configure double-click behavior for documents in the My Working Documents
List dialog box.
• Configure editor precedence and availability.
• Redirect OpenText™ WebDAV URLs.
• Configure link rewriting.

Note: You can also use the Content Server General Editor Settings and Office
Editor Settings administration page to configure settings for Office Editor,
including the following:

NGDCORE210200-IGD-EN-01 Installation Guide 81

Chapter 5 Configuring Editing Options

• Supported MIME types for editing.

• Supported new document types.
• Functionality of the Content Server Open command, specifically whether
Office Editor is required for opening documents.

Some of the settings on these administration pages only apply to stand-alone

installations of Office Editor. For more information, see OpenText Content Server
- Administering Editor Settings (LLESWBE-AGD).

5.1.1 Specifying the Location of the Document Cache

The document cache is the folder where Office Editor stores local versions of
recently edited documents. It is also the location where Enterprise Connect offline
documents are stored.

By default, the cache is stored in the following location:

C:\Users\<username>\AppData\Roaming\OpenText\OTEdit

You can create the following registry settings to specify a different location of the
document cache:

CacheRootCSIDL
A DWORD value that specifies the base directory for the document cache. This
must be a numeric value corresponding to a CSIDL constant.
If this registry setting does not exist, the default value is 26, which corresponds
to the CSIDL_APPDATA constant. On Windows 7, for example, this represents the
C:\Users\<username>\AppData\Roaming directory. Other possible values
include the following (all values are in decimal):
5
The user’s My Documents folder (CSIDL_MYDOCUMENTS).
16
The user’s Desktop folder (CSIDL_DESKTOPDIRECTORY).
28
The user’s local Appdata folder (CSIDL_LOCAL_APPDATA). For example:
C:\Users\<username>\AppData\Local

40
The user’s profile folder (CSIDL_PROFILE). For example:
C:\Users\<username>

For more information on CSIDL constants, see MSDN (http://

msdn.microsoft.com/en-us/library/windows/desktop/bb762494%28v=vs.
85%29.aspx).

Note: The CacheRootCSIDL setting only takes effect if the CacheLocation

setting is not set to an absolute path.

82 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

CacheLocation
A string value that can specify either an absolute or partial directory for the
location of the document cache. If the value is an absolute directory, such as C:
\office_editor\cache\%USERNAME%, then it determines the location of the
cache. In this case, the CacheRootCSIDL setting does not apply.
If the value is a partial directory, such as OfficeEditor\cache, then the
directory is relative to the root directory specified by CacheRootCSIDL.
If this registry setting does not exist, the default value is OpenText\OTEdit.
You can include environment variables in the CacheLocation. You must place a
percent sign (%) immediately before and after the environment variable name.
For example: \\fileserver\OfficeEditor\cache\%USERNAME%

Important
The location of the document cache must be unique for each user. Methods
you can employ to ensure each user has a unique cache location include
locating the cache under a user-specific directory (for example, by setting
CacheRootCSIDL to 5, which corresponds to the My Documents folder),
specifying the %USERNAME% environment variable in the directory path, or
setting a unique absolute path in CacheLocation for each user.

Notes

• If you specify a UNC path for CacheLocation, you must include a

subfolder in the path beneath the top-level folder share. For example, \
\fileserver\OfficeEditor\%USERNAME% is a valid UNC directory, but
\\fileserver\%USERNAME% is not. If the subfolder does not exist, Office
Editor will create it. Also, you must ensure that each user has a unique
UNC path. Users cannot share the same location for their document
caches.
• The Enterprise Connect and Office Editor document cache does not
support multiple concurrent connections from different clients. If your
configuration permits users to run multiple concurrent Enterprise
Connect or Office Editor sessions on different clients, you must ensure
each session uses a separate cache. If you are using a pool of Citrix
servers to enable multiple sessions, see “Configuring the Document
Cache Location to Support Citrix Session Pools” on page 84.

You can add these settings to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Config (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\Config (on
64-bit systems)

You can also add these settings to the following location in HKEY_CURRENT_USER.
Settings in this location take precedence over those in HKEY_LOCAL_MACHINE:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Config

NGDCORE210200-IGD-EN-01 Installation Guide 83

Chapter 5 Configuring Editing Options

5.1.1.1 Configuring the Document Cache Location to Support Citrix

Session Pools
The information in this section applies if the following conditions describe your
environment:

• Your users can connect to more than one instance of Enterprise Connect and
Office Editor at the same time, running in different Citrix sessions.
• You are running a pool of Citrix servers to which your users connect on a
rotating basis.

In such environments, you need to store the document cache on a file share to
ensure users can access it across Citrix sessions. However, because the document
cache does not support multiple concurrent connections, you cannot specify the
same cache location for all Enterprise Connect and Office Editor sessions. In this
case, you can create the following additional registry settings to ensure that your
users can work with multiple concurrent sessions while being able to access cached
documents across sessions:

EnableMultiSessionDocumentCache (DWORD)
If this setting is 0 or does not exist, Enterprise Connect and Office Editor support
one connection at a time to the document cache.
If this setting is 1, the document cache location must be set to a file share. Each
active Enterprise Connect and Office Editor session automatically creates a
separate document cache under the specified location. If a user is working in
multiple sessions, each session has its own My Working Documents List dialog
box with its own collection of documents. When a session is closed, the
documents from its My Working Documents List collection are moved to the
remaining active session’s My Working Documents List.
MultiSessionDocumentCacheScanInterval (DWORD)
This setting stores an integer value that represents how frequently, in seconds,
Office Editor merges inactive My Working Documents List collections from
previous sessions with the currently active session. If this setting does not exist,
the default frequency is 1 hour (3600 seconds).

You can add these settings to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Config (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\Config (on
64-bit systems)

Behavior
When you start a new Citrix session, Office Editor scans for any My Working
Documents List collections from previous sessions and moves their contents to the
current session, including documents that are synchronized, reserved, and in a
conflict state. Periodically during a session, at a frequency determined by the

84 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

MultiSessionDocumentCacheScanInterval registry setting, Office Editor moves

the My Working Documents List contents of sessions that have ended to the active
session as necessary.

If Office Editor identifies another active session, the contents of that session’s My
Working Documents List are not moved, and both sessions use separate document
caches.

If Office Editor detects that a document has been locally modified in both the current
session and in a previous session, the modified document from the previous session
is copied to the active session’s My Working Documents List, and (Recovered) is
appended to the file name. You can use the active session’s My Working
Documents List dialog box to upload the recovered document, or open it to access
its contents.

When running multiple Citrix sessions, users might see multiple Office Editor icons
appear in the notification area of the task bar. Users can double-click the icons to
access the My Working Documents List dialog box for each active instance of Office
Editor. Because active sessions’ cached documents are not merged, each My
Working Documents List dialog box might display a different set of documents.

Limitations
If EnableMultiSessionDocumentCache is enabled, you must disable offline mode.
Users should not take documents offline, work offline, or perform offline syncs. For
more information, see “Configuring Offline Mode” on page 180.

The active session’s My Working Documents List dialog box is not immediately
updated with documents from previous sessions. Depending on the value of
MultiSessionDocumentCacheScanInterval, it can take several minutes or longer
for My Working Documents List to be updated.

Example
The following example shows how Office Editor monitors previous sessions and
moves content to the active My Working Documents List:

• UserA connects to server1, and starts a virtual session in Word.

• UserA edits and saves several documents, and then ends the session.

• UserA then connects to server2, and starts a virtual session in Excel.

• The server2 instance of Office Editor discovers the My Working Documents List
collection of documents that was created for the previous session on server1.
Office Editor moves this collection of documents to server2’s My Working
Documents List instance.

• While keeping the connection to server2 open, UserA connects to server3, and
starts a virtual session in Outlook.

NGDCORE210200-IGD-EN-01 Installation Guide 85

Chapter 5 Configuring Editing Options

• The server3 instance of Office Editor discovers server2’s My Working

Documents List. Because server2 is an active session, nothing is moved to
server3. Both sessions remain active with separate My Working Documents List.

5.1.2 Configuring the My Working Documents List Dialog Box

You can create the following registry settings to configure the behavior of the My
Working Documents List dialog box:

BulkEditConfirmationMin
A string value that specifies the minimum number of items that the user must
select for editing or opening read-only in the My Working Documents List
dialog box before a warning prompt is displayed. If this registry setting does not
exist, the default value is 5.
BulkEditMaxLimit
A string value that specifies the maximum number of items that a user can
select at once for editing in the My Working Documents List dialog box. If this
registry setting does not exist, the default value is 100.
DocumentsMRUMaxSize
A string value that specifies the maximum number of recently-edited items
that can appear in the My Working Documents List dialog box and in the
document cache. If this registry setting does not exist, the default value is 1000.
This setting does not apply to Enterprise Connect offline documents, or to
documents that are in a pending upload or conflict state. If this value is reached,
existing items are removed as additional items are added to the document cache.

The specified value for each of these settings must be an integer value that is 0 or
higher.

You must add these settings to the following location in the registry:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences

You can also use the following registry settings to configure the My Working
Documents List dialog box display:

DisableLocationLink (DWORD)
Edit this setting to specify if the Location column in the My Working
Documents List dialog box contains active links or not. If this setting is 0 (the
default), the folder locations in the Location column are links to the Content
Server Web UI. The behavior of the link is determined by the Classic Link
Behavior setting on the My Settings: General page in Content Server. If this
setting is 1, the folder locations do not link to the Web UI.
ShowFilterComboBox (DWORD)
Use this setting to display a filter list box that allows users to show only pending
documents, recently edited documents, or documents that are downloaded
offline. If this setting is 1, the list box is displayed. If this setting is 0, the list box

86 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

is not displayed. By default, this setting is not stored in the registry. You must
manually create it if you want to display the list box in the My Working
Documents List dialog box.

These settings are stored, or must be created, in the following location in the
registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

Note: You can also add the EnableDocumentCaching registry setting to an

Enterprise Connect plug-in definition to specify if Enterprise Connect
documents remain in the document cache when they are not being edited. For
more information, see “Editing the Registry to Establish the Connection”
on page 29.

5.1.3 Configuring Office Editor Logging

You can create the following registry settings to configure logging for Office Editor:

LogFileLocation
A string value that specifies the location of the log files on the client system. If
this registry setting does not exist, the default location is <Local_appdata>
\OpenText\OTEdit\logs, where <Local_appdata> represents the default location
for non-roaming application data. On Windows 7, for example, the default log
location is C:\Users\<username>\AppData\Local\OpenText\OTEdit\logs.
LogFileName
A string value that specifies the name of the log file. If this registry setting is
empty or does not exist, the default log file name is the process name. You can
use the following variables in the file name:
%PID%
The process identifier.
%PNAME%
The process name.
%TSTAMP%
An integer value that represents the time the log file is created.
For example, if you set LogFileName to %PNAME%_%PID%_%TSTAMP%, the
corresponding log file name could look like the following:
OTEditTray_2904_63557880594.log

LogLevel
A string value that indicates the level of events that are included in the logs.
Possible values include the following:

NGDCORE210200-IGD-EN-01 Installation Guide 87

Chapter 5 Configuring Editing Options

• Off
• Error
• Warning (default)
• Info
• Debug

MaximumLogSize
The maximum size of the log files, in bytes. If this registry setting does not exist,
the default is 10000000.
If this maximum size is reached while Office Editor is running, the current .log
file is renamed to _.log, and a new .log file is started. In addition, each time
Office Editor starts, the previous .log is renamed to _.log, and a new .log file
is started.

Note: The previous log file is only renamed to _.log if its name would be
otherwise identical to the new log file. If the log file name includes a
variable that causes the two file names to be different, the previous log file
is not renamed. For example, if the log file name includes the %TSTAMP%
variable, the previous log file would not be renamed to _.log when Office
Editor starts, because the value of %TSTAMP% would be different for each
file.

You must add these settings to the following location in the registry:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences

5.1.4 Specifying the Frequency of the Notification Message

If Office Editor is unable to upload a locally edited file to the server, the Documents
Need Attention notification is displayed in the notification area, instructing the user
that there are documents in the My Working Documents List dialog box that
require attention. By default, this notification appears whenever Office Editor starts,
and every 60 minutes subsequently, until the issue is resolved. You can edit the
following registry setting to specify a different display frequency for this
notification:

NotificationBalloonInterval (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

This setting specifies how frequently, in minutes, the Documents Need Attention
notification is displayed in the notification area. The default value of 60 means that

88 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

the message is displayed once every 60 minutes. If the value of this setting is 0 or the
setting does not exist, the notification is displayed only when Office Editor starts.

Note: The Documents Need Attention notification is only displayed if Office

Editor is unable to upload a locally edited file to the server. If the user clicks
the notification, the My Working Documents List dialog box opens, displaying
documents in a Pending state. A message next to the affected document
indicates that Office Editor was unable to upload the document.

5.1.5 Configuring How Office Editor Interacts with Application

Processes
This section describes various registry entries you can use to configure how Office
Editor interacts with application processes when opening, reserving, unreserving,
and synchronizing documents. You can edit registry settings to do the following:

• Use the IgnoredProcesses setting to specify application processes to ignore

when Office Editor determines which documents in the cache require
synchronization. For example, antivirus applications can access documents and
make it appear that they have been modified when this is not actually the case.
You can tell Office Editor to ignore an antivirus or other application process
when evaluating whether a document has been modified or not.
• Use the EditorBehavior setting to specify that some applications do not support
editing and only open documents as read-only. You can do this to remove the
Edit command from specific file types, and to ensure that an application such as
a browser does not inadvertently cause a document to be reserved when a user
opens the document with the application’s Open dialog box.
• Use the LockableApplications setting to specify whether certain application
processes or file types support document locking. Lockable documents are
locked on disk and cannot be modified by another user when you have the file
open in an application that supports locking. Some applications always lock
documents, other applications never lock documents, and some applications only
lock documents when they open for editing but not when they are read-only. If
Office Editor knows which method an application uses it is better able to manage
the reservation and synchronization process for documents open in the
application.

This section also includes examples on when you might want to modify these
registry settings to resolve specific issues users are seeing when opening or editing
documents with Office Editor.

NGDCORE210200-IGD-EN-01 Installation Guide 89

Chapter 5 Configuring Editing Options

5.1.5.1 Specifying Processes To Ignore When Syncing Documents

Office Editor monitors the document cache to determine which documents have
been modified and require syncing with the server.

In some cases, processes that are not involved in opening or editing documents can
still access documents and trigger unnecessary syncs. For example, some antivirus
software can scan documents, prompting Office Editor to attempt to sync the
documents even though they have not been modified.

To prevent such unnecessary sync attempts, you can edit the following registry
setting:

IgnoredProcesses (string)

By default, this registry setting specifies a number of processes that are not involved
in opening or editing documents.

You can edit this setting by adding a comma-separated list of processes that Office
Editor will ignore when determining if a document has been modified and needs to
be synced. For example:

IgnoredProcesses=msoia,Snagit32,SnagitEditor,SnagPriv,mcshield,
searchprotocolhost,Parity

Do not include spaces around the commas. Specify the process names without
extensions, for example mcshield, not mcshield.exe.

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

You can also create this setting in the following location in the registry:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences

If IgnoredProcesses is specified in both HKEY_LOCAL_MACHINE and HKEY_CURRENT_

USER, the contents of each setting are combined, and all specified processes are
ignored.

Notes

• You do not need to specify explorer in the list of ignored processes. The
explorer process is always ignored.

• You cannot enable extended integration for applications listed in the

IgnoredProcesses registry setting. For more information, see “Specifying
Which Applications Support Extended Integration” on page 112.

90 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

5.1.5.2 Removing the Ability to Edit Specific File Types

You can use the EditorBehavior registry key to do the following for applications
that do not support editing:

• Disable the Edit command in Enterprise Connect for certain file types, if the
application that opens them does not provide the ability to edit. For example,
some users might have the PDF file type associated with Acrobat so that they can
edit PDFs, while other users might have the PDF file type associated with Adobe
Reader because they only need to open PDFs as read-only. For the second set of
users, you might want to remove the Edit command from PDF file types only for
these users.
• Ensure that documents opened using the application’s native Open dialog box
are treated as read-only and are not reserved. For example, if a user opens a PDF
from Enterprise Connect in Adobe Reader, adding Adobe Reader to the
EditorBehavior registry key ensures that the PDF is not reserved.

To disable the Edit command for specific file types, and ensure documents opened
in the application are treated as read-only, add a string value to the following
registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences\
EditorBehavior (on 32-bit systems)

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\Preferences\
EditorBehavior (on 64-bit systems)

You must set the name of the string to the executable file name for the application,
and set its value to READONLY. For Windows 8.1 and Windows 10, you might also
need to add a separate string value for the application that specifies the Application
User Model ID for the application. A procedure in this section explains how to locate
the Application User Model ID and determine if it needs to be added as a separate
registry value.

When an application is set to READONLY in this registry key, documents with the
associated file extension cannot be opened for editing in Enterprise Connect. The
Edit command is not available from Enterprise Connect menus or ribbons, or from
the Office Editor My Working Documents List dialog box. Users can only open
read-only versions of documents with these file types, and the documents are not
reserved when they are opened. Double-clicking a document also opens it as read-
only. In the Content Server Web interface, clicking Edit results in a message offering
to open the document as read-only, and the document is not reserved.

By default, the following string values are stored in this key and set to READONLY:

AcroRd32.exe
The executable file name for Adobe Reader.
chrome.exe
The executable file name for Chrome.

NGDCORE210200-IGD-EN-01 Installation Guide 91

Chapter 5 Configuring Editing Options

explorer.exe
The executable file name for Windows Explorer.

firefox.exe
The executable file name for Firefox.

iexplore.exe
The executable file name for Internet Explorer.

MicrosoftEdge.exe
The executable file name for Microsoft Edge.

Microsoft.MicrosoftEdge!MicrosoftEdge
The Application User Model ID value for the Microsoft Edge browser, which in
some cases can be the default application used to open PDF files.

Microsoft.Reader!Microsoft.Reader
The Application User Model ID value for the Microsoft Reader, which in some
cases can be the default application used to open PDF files.

msedge.exe
The executable file name for the Chromium edition of Microsoft Edge.

To determine the Application User Model ID value to use when adding an

EditorBehavior setting in Windows 8.1 and 10:

1. Right-click the Start button, and then click Run.

2. Enter shell:AppsFolder in the Open box, and then click OK.

3. In the Applications window, click View > Details.

Note: You might need to press the F10 key to see the View menu.

4. Click View > Choose Details, and then select the AppUserModelId check box.

5. Locate the appropriate application in the list, and note the corresponding entry
in the AppUserModelId column.

Note: The two supported forms for Application User Model IDs are a
value ending in .exe or in ProductFamily!AppId format. For example,
the EditorBehavior value for AppUserModelId {7C5A40Ef-
A0FB-4BFC-874A-C0F2E0B9FA8E}\Adobe\Acrobat Reader DC\AcroRd32.
exe is AcroRd32.exe, which is the same as the executable file name. In this
case, you only need to add one setting to the registry key to specify the
executable file name. The EditorBehavior value for AppUserModelId
Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge is
Microsoft.MicrosoftEdge!MicrosoftEdge, which is different from the
executable file name of MicrosoftEdge.exe. In this case, you must add
two settings to the registry key, one for the application’s file name and one
for the Application User Model ID.

92 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

To determine the executable file name associated with a specific file type:

1. In the registry, open the HKEY_CLASSES_ROOT hive, and then click the key that
represents the appropriate file extension. For example, HKEY_CLASSES_ROOT >
.pdf.

2. Note the key’s Default value, and then navigate to the corresponding key in
HKEY_CLASSES_ROOT. For example, HKEY_CLASSES_ROOT > AcroExch.Document.

3. Open the Shell > Open > Command subkey, and then view the Default value to
determine the executable name. For example, AcroRd32.exe.

5.1.5.3 Specifying Locking and Non-locking Applications and File Types

If an application supports locking, this means that it locks files on disk when a user
opens them through the application. For example, if a user opens a document in
Word, that document cannot be modified, moved, or deleted by anyone else until it
is closed and the lock is removed. Applications that do not support locking do not
lock files on disk when a user opens them. For example, if a user opens a document
in Notepad, the document can still be modified, moved, or deleted by someone else.

A locking document is a document that you open in an application that supports

locking. A non-locking document is a document that you open in an application that
does not support locking.

Office Editor manages the editing process differently for locking and non-locking
documents:

• For a locking document, Office Editor uploads and unreserves the edited
document when you close the document.
• For a non-locking document, Office Editor uploads and unreserves the edited
document when you close the application used to edit it.

For example, Office Editor treats all documents open in Notepad as non-locking by
default. If you open a Content Server text document in Notepad and edit it, when
you save your changes and close the document, the document remains reserved.
Office Editor only unreserves and uploads the edited text document to Content
Server when you close the Notepad application itself.

In most cases, the default settings are sufficient to ensure that Office Editor correctly
identifies locking and non-locking documents. However, in some cases Office Editor
might not handle the reservation and upload process correctly for locking
documents if it does not realize that they are locking. As well, some applications
only lock documents for editing and treat documents opened as read-only as non-
locking, which can cause issues with storing the document in the cache if Office
Editor does not know how the application behaves. Excel is an example of an
application that locks documents for editing but not if they are open read-only.

If necessary, you can use the following registry keys and settings to change which
applications and file types Office Editor treats as locking or non-locking:

NGDCORE210200-IGD-EN-01 Installation Guide 93

Chapter 5 Configuring Editing Options

LockableApplications (key)
You can use this registry key to specify that specific applications support or do
not support locking. In this registry key, create a DWORD setting and give it the
name of an application’s process. For the value of the setting, specify one of the
following:
0
The application does not support locking.
1
The application supports locking.
2
The application supports locking for documents opened for editing, but
does not support locking for documents opened as read-only.
Any document that you edit in the application is treated as locking or non-
locking on the basis of this setting.
By default, this key contains the following settings, which all have the value of 1,
indicating that the applications associated with these processes all support
locking:

• acrobat ( Acrobat)
• acrord32 (Adobe Reader)
• chrome (Chrome)
• firefox (Firefox)
• iexplore (Internet Explorer)
• microsoftedge (Microsoft Edge)
• msedge (Microsoft Edge, Chromium edition)
• outlook (Microsoft Outlook)
• powerpnt (PowerPoint)
• visio (Visio)
• winproj (Project)
• winword (Word)

By default, this key also contains the following settings, which all have the value
of 0, indicating that the applications associated with these processes do not
support locking:

• notepad (Notepad)
• mspaint (Paint)
• wordpad (WordPad)

By default, this key also contains the following settings, which all have the value
of 2, indicating that the applications associated with these processes support

94 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

locking for documents that are opened for editing, and do not support locking
for documents that are opened as read-only:

• excel (Excel)
• soffice.bin (LibreOffice)
• wpwin* (WordPerfect) (the asterisk (*) is a wildcard that represents version
numbers)

You can also add an asterisk (*) wildcard as a setting to this registry key. In this
case, any application that is not explicitly specified in this key is treated as
locking or non-locking depending on the value of the wildcard.

Note: This registry key takes precedence over the LockableTypes key. If
you edit a document using an application that is specified in the
LockableApplications key, the locking status is determined by the
LockableApplications setting, even if there is an entry in
LockableTypes for the document’s specific file type. If you specify the *
wildcard as a setting in LockableApplications, then none of the settings
in LockableTypes is ever applied.
LockableTypes (key)
You can add settings to this registry key to specify that specific file types are
lockable or non-lockable. In this registry key, create a DWORD setting and give
it the name of the extension associated with the file type.

Note: In most cases, you do not need to change the default value of
LockableTypes.

For the value of the setting, specify one of the following:

0
The file type is non-locking.
1
The file type is locking.
2
The file type is locking when the document is opened for editing, but is non-
locking when the document is opened as read-only.
For example, to specify that XML files are non-locking, create a setting with the
name XML and the value 0.
This key contains an asterisk (*) wildcard setting that applies to all file types that
are not otherwise specified in this key. By default, this wildcard is set to a value
of 0, which means that all file types not otherwise listed in this key are treated as
non-locking, unless they are edited in an application that is specified in the
LockableApplications key with a value of 1.

Note: The LockableApplications settings take precedence over the

LockableTypes settings. If you are editing a document in an application

NGDCORE210200-IGD-EN-01 Installation Guide 95

Chapter 5 Configuring Editing Options

that is specified in one of the LockableApplications settings, the file type

settings specified in LockableTypes do not apply to the document.

These registry keys and settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

5.1.5.4 Examples of using IgnoredProcesses, EditorBehavior, and

LockableApplications
This section describes some issues you might encounter with Office Editor that can
be resolved by adding application processes to the IgnoredProcesses,
EditorBehavior, and LockableApplications registry settings. Unless otherwise
specified, references to opening or editing documents assume the documents reside
in Content Server and are being opened or edited through Office Editor or
Enterprise Connect.

Example: IgnoredProcesses

An antivirus application might periodically scan the documents in the Office Editor cache,
resulting in the following behavior:

• Without user interaction, Office Editor might attempt to synchronize documents from the
cache back to the server, resulting in conflict messages being displayed in My Working
Documents List.
• Users might see random authentication pop-up windows, related to Office Editor
attempting to synchronize files in the cache.

Adding the antivirus process name to IgnoredProcesses fixes the issues.

Example: EditorBehavior

You might encounter the following issues when opening or saving documents as read-only:

• In a browser application, when you attach a file from Enterprise Connect to an email in
Webmail, the file is reserved in Content Server, even though you never opened it for
editing.
• In an email application, when you print an email as a PDF and save it to Enterprise
Connect, the PDF is reserved in Content Server and cannot be unreserved.

In these cases, adding the application file names as string values to the EditorBehavior
registry key and setting them to READONLY resolves the issues.

In another case, you might have some users who have PDF editing software installed, and
other users who only have a read-only PDF application installed. You might want to remove
the Edit command from PDFs for the second group of users. You can do this by adding the
filename and, if it is different, the Application User Model ID for the read-only PDF
application to the EditorBehavior key on these users’ workstations, and assign the settings
a value of READONLY.

96 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

Example: LockableApplications

You might encounter the following issues when opening or editing documents, which can be
resolved by adding the relevant application process to the LockableApplications key and
setting it to the appropriate value:

• If you edit a document in a locking application, after you save and close the document it
remains reserved until the application is closed. You can resolve this issue by adding the
application’s process name as a string value to the LockableApplications key, and
assigning it a value of 1 to indicate the application supports locking. When you do this,
Office Editor automatically unreserves and synchronizes the edited document as soon as
the document is closed.
• You might work with an application that edits documents without any problems, but
when you open a document as read-only in the application, the document is removed
from the Office Editor cache while the document is still open. In this case it is possible that
the application locks documents for editing, but does not lock them for read-only viewing.
If this is the case, you can resolve the issue by adding the application’s process name as a
string value to the LockableApplications key, and assigning it a value of 2 to indicate
the application does not support locking for read-only documents. This ensures that read-
only documents remain in the cache as long as they are open in the application.

5.1.6 Enabling Office Editor to Store Credentials

By default, Office Editor does not store credentials for Content Server users. You can
edit the following registry setting to make Office Editor store user credentials:

DontStoreCredentialsLocally (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

If this setting is 1 (the default), Office Editor does not store credentials for Content
Server users. If this setting is 0, Office Editor stores credentials for Content Server
users. If a user signs out of Office Editor, the user is prompted to re-enter credentials
the next time he or she attempts to access a document in Office Editor.

This setting only applies to Content Server instances that do not have an Enterprise
Connect plug-in configured on the client. If an Enterprise Connect plug-in is
configured, the Enterprise Connect DontStoreCredentialsLocally setting applies
instead. For more information, see “Managing Enterprise Connect Credential
Storage Options” on page 42. This setting also does not apply if a third-party Web
access management system such as SiteMinder is used to manage authentication.

NGDCORE210200-IGD-EN-01 Installation Guide 97

Chapter 5 Configuring Editing Options

5.1.7 Customizing the Office Editor Installation or Upgrade

Message
If a user clicks Edit for a Content Server document in a browser, and a supported
version of Office Editor client is not installed on the user’s workstation, a message is
displayed indicating that the Office Editor client must be installed or upgraded. By
default, this message includes the text Please contact your Administrator for
additional information. You can replace this text with a message that you specify
yourself.

Note: This message appears if the Office Editor client is not installed on the
user’s workstation, or if you have configured Content Server to only allow
editing with the most recent client and the user has an outdated version. You
can configure this on the Editor Administration > Configure Office Editor
Settings administration page. For more information, see the Office Editor
section in the Content Server administration online help.

You can create a custom message by editing a text file in the <Content_Server_
home>\support\webedit directory on Content Server. A separate file is provided
for each supported language, allowing you to provide translated text as required.

To customize the Office Editor installation or upgrade message:

1. Navigate to the <Content_Server_home>\support\webedit directory.

2. In a text editor, open the appropriate CustomContactAdmin_<language_
code>.txt file, where <language_code> represents the language of the message.
You need to edit a separate language file for each supported language pack in
Content Server.
3. Enter the text of the message you want to display. The text is interpreted as
HTML fragments. If you want to display reserved characters such as angle
brackets (< >) or ampersands (&), you must escape them. For example, use &lt;
for left angle bracket (<).
4. Save the file with UTF-8 encoding.

5.1.8 Configuring Double-click Behavior in the My Working

Documents List Dialog Box
By default, when you double-click a document in the My Working Documents List
dialog box, it is opened as read-only. You can edit the following registry setting to
cause documents in My Working Documents List to be opened for editing when
double-clicked:

EditOnDoubleClick (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)

98 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

When this setting is 0 (the default), documents in the My Working Documents List
dialog box are opened as read-only when double-clicked. When this setting is 1,
documents are opened for editing when double-clicked.

You can also add this setting to the following location in the registry:

HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences

If you add this setting to HKEY_CURRENT_USER, it takes precedence over the one in
HKEY_LOCAL_MACHINE.

5.1.9 Disable the creation of the Office Editor desktop

shortcut
By default, when Office Editor is run for the first time after being installed or
upgraded it creates a shortcut called OpenText Office Editor on each user’s
desktop. The shortcut opens the My Working Documents List dialog box.

You can add the following setting to the registry to prevent the shortcut from being
created:

DisableDesktopIconCreation(DWORD)

You can add this setting to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

If this setting is 1 (the default), the desktop shortcut is not created on the client. If the
shortcut was previously created, it is removed the next time Office Editor starts. If
this setting is 0 or does not exist, the Office Editor desktop shortcut is created on the
client.

5.1.10 Configuring Editor Precedence and Availability Options

You can configure Content Server to support multiple editors, including Office
Editor and Microsoft® Office Online. If multiple editors are supported, you can do
the following to administer how users are able to work with them:

• Configure whether or not editors are available, at the system or group level. You
can configure system-level editor availability on the Editor Administration >
General Editor Settings administration page in Content Server. You can
configure group-level availability settings by editing a group from the Users and
Groups page, and then clicking Configure Editor Group Settings. Group editor
availability settings take precedence over the system level settings.

NGDCORE210200-IGD-EN-01 Installation Guide 99

Chapter 5 Configuring Editing Options

• Set the editor precedence for users who are able to use more than one editor. The
precedence setting determines which editor is used when a user clicks the
promoted Edit or Open command in the Content ServerWeb UI. You can
configure editor precedence on the Editor Administration > General Editor
Settingsadministration page.

Note: The only editor that Enterprise Connect supports is Office Editor.
Enterprise Connect does not support using Office Online to open or edit
documents. You can only use Office Online through the Content Server Web
UI.

Example: Consider the following scenario for configuring editor options for a Content Server
instance that is configured to support both Office Editor and Office Online:

• The majority of users only use Office Editor.

• A group of users has Office Online licenses, so they are able to use both Office Online and
Office Editor. is the preferred editor. These users belong to the Office Online Users group.
• A small group of users are external to the organization, and are unable to use any editor.
These users belong to the External Users group.

The following example procedure shows how you could configure Content Server to support
such a scenario:

1. Navigate to the Editor Administration > General Editor Settings administration page.
2. In the Default Availability area, do the following:

• In the Available by Default column, select the check box for Office Editor and clear
the check box for O365 Office Online.
• In the Editor Rank column, use the arrows to move O365 Office Online above Office
Editor.

This makes Office Editor available by default, and Office Online unavailable by default,
unless a user belongs to a group that overrides these settings. This also ensures that Office
Online is invoked when a user who is able to use Office Online clicks the promoted Edit
or Open link in Content Server. For users who are not given access to Office Online, the
next-highest editor is used instead, which in this case is Office Editor.

3. Navigate to Enterprise > Users and Groups, search for the Office Online Users group,
click Edit next to the group name, and then click Configure Editor Group Settings.
4. In the Editor Availability for Group Members area, for O365 Office Online, click
Available for members of this group in the box, and then click Save Changes.

100 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

For all members of this group, this overrides the system setting which makes Office
Online unavailable by default.

5. Navigate to the Configure Editor Group Settings page for the External Users group, and
do the following in the Editor Availability for Group Members area:

• For Office Editor, click Unavailable for members of this group in the box.
• For O365 Office Online, click Unavailable for members of this group in the box.

For all members of this group, this makes both editors unavailable, regardless of the
system settings or other group settings.

NGDCORE210200-IGD-EN-01 Installation Guide 101

Chapter 5 Configuring Editing Options

5.1.11 Redirecting OpenText™ WebDAV URLs

This section is applicable if you have removed WebDAV from Content Server, but
you still want a way to redirect hard-coded WebDAV URLs to open or display the
appropriate content in a browser. For example, if a user clicks a WebDAV URL that
was inserted into an email or Office document, by following the procedures in this
section you can ensure that a browser will open to display the appropriate
document or folder. To do this you must configure the Web server that is running
Content Server to redirect the WebDAV URL to an Office Editor request handler.
The request handler opens the item in the format specified by the user’s Classic
Link Behavior setting in Content Server.

Notes

• This section only applies to the process of opening WebDAV URLs in a

browser. It does not apply to other WebDAV operations or link formats.
• In the following procedures, the Content Server URL is presented as
http://hostname/otcs/cs.exe, and the WebDAV URL is presented as
http://hostname/contentserverdav. When following these procedures,
replace these URLs, or their elements such as the virtual directory names
otcs and contentserverdav, with the ones appropriate to your Content
Server and WebDAV configuration.

To configure Microsoft Internet Information Services:

1. Ensure that HTTP Redirection is installed as a Microsoft IIS feature.

2. Create a folder called weblink in the <Content_Server_Home> directory.

3. Start Internet Information Services (IIS) Manager.

4. In the Connections pane, under Sites, right-click the Default Web Site, and then
click Add Virtual Directory.

5. In the Add Virtual Directory dialog box, configure the following settings, and
then click OK:

Alias
contentserverdav

Physical path
<Content_Server_Home>\weblink

Note: Ensure that the authentication for contentserverdav is the same as

for otcs.

6. In the Connections pane, click contentserverdav.

7. In the contentserverdav Home pane, right-click HTTP Redirect, and then click
Open Feature.

102 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.1. Using Office Editor

Note: If HTTP Redirection is not installed as a Microsoft IIS feature, you

will need to install it. For an example of how to install HTTP Redirection,
see HTTP Redirects (https://docs.microsoft.com/en-us/iis/configuration/
system.webserver/httpredirect/).

8. In the HTTP Redirect pane, select the Redirect requests to this destination
check box, enter the following in the box, and then click Apply to save your
changes:
/otcs/cs.exe?func=webedit.resolve&path=

Note: In the Redirect Behavior area, ensure that the check boxes are
cleared, and that the Status code is set to the default value of Found (302).

9. In the contentserverdav Home pane, right-click Request Filtering, click Open

Feature, and then click the HTTP Verbs tab.

10. For each of the following verbs, click the Deny Verb action, enter the verb in the
Deny Verb dialog box, and then click OK:
COPY, DELETE, MOVE, LOCK, OPTIONS, PROPFIND, PROPPATCH,
UNLOCK

To configure Apache HTTP Server™:

1. Open the httpd.conf file in a text editor.

2. Add the following to the httpd.conf to enable the rewrite_module module:

LoadModule rewrite_module modules/mod_rewrite.so

3. Add the following to the httpd.conf file:

RewriteEngine on
RewriteCond % {REQUEST_METHOD} !^(COPY|DELETE|MOVE|LOCK|PROPFIND|
PROPPATCH|UNLOCK)
RewriteRule "^/contentserverdav/(.+)$" "http://hostname/otcs/cs.
exe?func=webedit.resolve&path=$1"

4. Save and close the httpd.conf file.

5. Restart the Apache HTTP Server.

To configure Apache® Tomcat™:

1. In a text editor, create a file called rewrite.config and save it in the following
location:
<TOMCAT_HOME>/conf/Cataline/hostname

2. Add the following to the rewrite.config file, and then save and close it:
RewriteCond %{REQUEST_METHOD} !^(COPY|DELETE|MOVE|LOCK|PROPFIND|
PROPPATCH|UNLOCK)

NGDCORE210200-IGD-EN-01 Installation Guide 103

Chapter 5 Configuring Editing Options

RewriteRule ^/contentserverdav/(.+)$ /otcs/cs.exe?func=webedit.

resolve&path=$1

3. Open the Tomcat server.xml file in a text editor, add the following in the
<Host> section just after the <Host> tag, and then save and close the file:

<Valve className="org.apache.catalina.valves.rewrite.RewriteValve"
/>

4. Restart Tomcat.

To verify the WebDAV URL redirection:

1. In a browser, open the following link:

• http://hostname/contentserverdav/enterprise

2. Verify that the browser is redirected to the Enterprise workspace Link Action in
Content Server.

5.1.12 Configuring Link Rewriting

Enterprise Connect and Office Editor provide support for maintaining links between
Office documents when the documents are stored in Content Server. For more
information and detailed examples, see OpenText™ Enterprise Connect Document
Linking White Paper (https://knowledge.opentext.com/knowledge/llisapi.dll/
Properties/18878100) on OpenText My Support.

Link rewriting is the process of inspecting a document upon an upload or upon an

edit and then converting the embedded links to some other format. Office Editor
performs link rewriting to ensure that links work when documents are downloaded
to the document cache.

To configure link rewriting, you can edit the following settings:

EnableLinkRewritingForLocalDocuments (DWORD)
When the value of this setting is 1 (the default), Office Editor performs link
rewriting during document edits and uploads. To disable link rewriting, set this
value to 0.

EnableExcelQuerylinkRewriting (DWORD)
This setting is not added by default when you install Office Editor. You must
manually add it to the registry.
When the value of this setting is 1, Office Editor performs link rewriting for
links between Excel workbooks created using the Get Data > From File > From
Workbook command in Excel 2016 and later.
This setting only applies if EnableLinkRewritingForLocalDocuments is set to
1 and the executing verision of Excel is at least 16.0.

104 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.2. Configuring the Upload Mode for Edited Documents

Notes

• Setting EnableExcelQuerylinkRewriting to 1 can have an impact on

system performance.
• Links created using the Get Data > From File > From Workbook
command are not accessible if you use a version of Excel prior to 16.0 to
open the document.

These settings are stored, or must be created, in the following location in the
registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

5.2 Configuring the Upload Mode for Edited

Documents
You can edit the following settings to specify the default upload mode for
documents that users edit through Office Editor or Enterprise Connect:

UploadDocumentSavesImmediately (DWORD)

DefaultFinalizeOnClose(DWORD)

FinalizeOnCloseModifiable(DWORD)

The DefaultFinalizeOnClose and FinalizeOnCloseModifiable settings only

apply if UploadDocumentSavesImmediately is set to 0. If
UploadDocumentSavesImmediately is set to 1, DefaultFinalizeOnClose and
FinalizeOnCloseModifiable have no effect.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\OTEdit\
Preferences (on 64-bit systems)

UploadDocumentSavesImmediately Set to 0
If this setting is 0 (the default), the document is reserved when the user opens it for
editing. The document is saved locally each time the user saves changes using the
application’s native save function (for example, by pressing CTRL+S or clicking File
> Save). The server version is not updated each time the document is saved. The
following conditions apply for the specified applications when users edit documents
through Office Editor or Enterprise Connect:

NGDCORE210200-IGD-EN-01 Installation Guide 105

Chapter 5 Configuring Editing Options

Enterprise Connect only: all Office applications

The following controls are displayed on the Enterprise Connect tab on the
Office ribbon:

• The Upload button. If the user clicks this button, pending changes are
uploaded to the server. The document remains reserved and open in the
application.
• The Finalize on Close check box. If this check box is selected, pending
changes are only uploaded to the server when the user closes the document.
The document is also unreserved on close.
If the Finalize on Close check box is cleared, when the user closes the
document, the document remains reserved, and pending changes are not
uploaded to the server. To upload a new version to the server and unreserve
the document, the user must click the Finalize link for the document in the
My Working Documents List dialog box.

All Office applications with Office Editor stand-alone, Acrobat, and all Extended
Integration applications that support locking (such as WordPerfect)
The document is saved locally each time the user saves changes using the
application’s native save function. When the user closes the document, the
DefaultFinalizeOnClose setting determines what happens to the document.

Note: For more information on locking and non-locking applications, see

“Specifying Locking and Non-locking Applications and File Types”
on page 93.
All Extended Integration applications that do not support locking (such as
Notepad)
The document is not uploaded to the server when the user saves changes using
the application’s native save function. After the user closes the document, it
remains reserved until the user exits the application that was used to edit the
document. When the user exits the application, the DefaultFinalizeOnClose
setting determines what happens to the document.

UploadDocumentSavesImmediately Set to 1
If this setting is 1, the document is reserved when the user opens it for editing. Each
time the user saves changes to the document using the application’s native save
function (for example, by pressing CTRL+S or clicking File > Save), a new version of
the document is uploaded to the server. The following conditions apply when users
edit documents through Office Editor or Enterprise Connect:

Enterprise Connect only: all Office applications

The Upload button and Finalize on Close check box are not displayed on the
Enterprise Connect tab on the Office ribbon. A new version of the document is
uploaded to the server each time the user saves changes using the application’s
native save function. When the user closes the document, the document is
unreserved.

106 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.2. Configuring the Upload Mode for Edited Documents

All Office applications with Office Editor stand-alone, Acrobat, and all Extended
Integration applications that support locking (such as WordPerfect and Adobe
Reader)
A new version of the document is uploaded to the server each time the user
saves changes using the application’s native save function. When the user closes
the document, the document is unreserved.
All Extended Integration applications that do not support locking (such as
Notepad)
A new version of the document is uploaded to the server each time the user
saves changes using the application’s native save function. The document
remains reserved until the user exits the application that was used to edit the
document. A short time after this application is exited, the document is
unreserved. The user can also manually unreserve the document by clicking the
Unreserve link for the document in the My Working Documents List dialog
box.

Notes

• If a document is manually reserved by a user prior to being edited, the

document is not unreserved when it is closed. For example, if a user
manually reserves a document, and then subsequently edits it, the document
remains reserved even after the user closes the document.
• The descriptions in this section assume the document is opened for editing
through Office Editor or Enterprise Connect.
• If you change the value of UploadDocumentSavesImmediately, the change
does not apply to any documents that are currently in the document cache. If
the documents are removed from the cache and subsequently added again,
the new value of UploadDocumentSavesImmediately is applied to them.

DefaultFinalizeOnClose
The DefaultFinalizeOnClose setting only applies if
UploadDocumentSavesImmediately is set to 0.

If DefaultFinalizeOnClose is set to 1 (the default), the following conditions apply:

• The Finalize on Close check box on the Office ribbon is selected by default.
• For all locking applications that do not have the Finalize on Close check box,
pending changes to edited documents are uploaded when the documents are
closed, and the documents are unreserved.
• For non-locking applications such as Notepad, pending changes to edited
documents are not uploaded when the documents are closed. The documents
remain reserved until the user exits the application that was used to edit the
document. A short time after this application is exited, the document is
unreserved and uploaded. The user can also manually upload and unreserve the
document by clicking the Unreserve or Finalize link for the document in the My
Working Documents List dialog box.

NGDCORE210200-IGD-EN-01 Installation Guide 107

Chapter 5 Configuring Editing Options

If DefaultFinalizeOnClose is set to 0, the following conditions apply:

• The Finalize on Close check box on the Office ribbon is cleared by default.

• For all applications that do not have the Finalize on Close check box, pending
changes to edited documents are not uploaded when the documents are closed.
The documents remain reserved. To upload changes and unreserve, the user
must click the Unreserve or Finalize link for the document in the My Working
Documents List dialog box.

Note: If you change the value of DefaultFinalizeOnClose, the change does

not apply to any documents that are currently in the document cache. If the
documents are removed from the cache and subsequently added again, the
new value of DefaultFinalizeOnClose is applied to them.

FinalizeOnCloseModifiable
The FinalizeOnCloseModifiable setting only applies if
UploadDocumentSavesImmediately is set to 0.

If FinalizeOnCloseModifiable is set to 1 (the default), the Finalize on Close check

box is displayed in the Document Options group on the Office ribbon.

If FinalizeOnCloseModifiable is set to 0, the Finalize on Close check box and the

Document Options group are not displayed on the Office ribbon. Users cannot
change the default setting specified by DefaultFinalizeOnClose for individual
Office documents.

5.3 Configuring Double-click Actions for Documents

You can configure how documents open when users double-click them in Enterprise
Connect, in either Windows Explorer or Microsoft Outlook. This setting also applies
to Shortcuts that point to documents. The Always open document as read-only
option is the default setting, and you can use this option if you want users to open a
read-only version when they double-click a document. Use the Open document for
editing if permissions allow setting if you want users to be able to immediately edit
documents that they open by double-clicking.

Notes

• Users can only edit documents for which they have Modify and Reserve
permissions.

• This setting only applies to documents that users can edit using the
Enterprise Connect client. It does not apply to emails and other document
types that may be controlled by the EditorBehavior registry setting. For
more information, see “Registry Setting Reference“ on page 185.

108 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.4. Forcing the Use of the Enterprise Connect Open and Save As Dialog Boxes

5.3.1 To Configure Double-click Actions for Documents

To configure double-click actions for documents:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Double-click Action area, click one of the following options in the When
double-clicking a document list:

• Click Always open document as read-only if you want a read-only version

of the document to open.
• Click Open document for editing if permissions allow if you want users to
be able to edit documents.

3. Click Save Changes.

5.4 Forcing the Use of the Enterprise Connect Open

and Save As Dialog Boxes
You can edit two registry values to cause the Enterprise Connect Open and
Enterprise Connect Save As dialog boxes to appear if users attempt to open or save
documents in the Office applications supported by Enterprise Connect (Word, Excel,
PowerPoint, Project, and Visio). The Acrobat integration also supports forcing the
use of the Enterprise Connect Open and Enterprise Connect Save As dialog boxes.

Important
If you force the use of Enterprise Connect dialog boxes, the following
conditions apply:

• In Acrobat, forcing the use of both the Enterprise Connect Open and
Enterprise Connect Save As dialog boxes causes the Enterprise Connect
command to disappear from the File menu. Users must use the native
Open, Save, and Save As commands to open the Enterprise Connect dialog
boxes.
• In Office, the Open and Save As buttons always appear on the Enterprise
Connect tab on the ribbon, even if you force the use of the Enterprise
Connect Open and Enterprise Connect Save As dialog boxes.

Note: Forcing the use of only one of the dialog boxes in Acrobat does not
remove the Enterprise Connect commands. For example, if you force only the
use of the Enterprise Connect Open dialog box, the Enterprise Connect >
Open command remains available.

NGDCORE210200-IGD-EN-01 Installation Guide 109

Chapter 5 Configuring Editing Options

5.4.1 Forcing the Use of the Enterprise Connect Open Dialog

Box
The following registry value controls whether the Enterprise Connect Open dialog
box appears if users attempt to open documents in Office or Acrobat:

ForceEnterpriseConnectOpenDialog (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

When this value is set to 0 (the default), the Office and Acrobat Open commands
function as usual. Setting this value to 1 causes the Enterprise Connect Open dialog
box to appear when the user performs one of the following actions:

• In Acrobat, selects the Open command on the File menu.

• In Office, uses the CTRL+O keyboard shortcut.
• In Office, clicks the Open button on the Quick Access Toolbar.
• In Acrobat, attaches a file, adds an image, inserts pages from a file, selects items
for a document comparison, adds files to combine files, or locates a file for a
shared review.

Note: In Office, clicking the Open command on the File menu starts the native
Office Open dialog box, even if ForceEnterpriseConnectOpenDialog is set to
1.

In these cases, the user is required to open a document that is stored in a repository
accessible through Enterprise Connect.

When ForceEnterpriseConnectOpenDialog is set to 1, the Open Local File button

appears on the Enterprise Connect Open dialog box. This allows users to open a
document from their local file system if they are unable to access Enterprise
Connect.

The ForceEnterpriseConnectOpenDialog has no effect on other methods used to

open documents in Office or Acrobat. For example, double-clicking a local Office
document in Explorer causes the document to open in Office as usual.

110 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.4. Forcing the Use of the Enterprise Connect Open and Save As Dialog Boxes

5.4.2 Forcing the Use of the Enterprise Connect Save Dialog

Box
The following registry value controls whether the Enterprise Connect Save As
dialog box appears if users attempt to save documents in Office or Acrobat:

ForceEnterpriseConnectSaveAsDialog (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

When this value is set to 0 (the default), the Office and Acrobat Save As command
functions as usual. Setting this value to 1 causes the Enterprise Connect Save As
dialog box to appear if a user performs one of the following actions when a
previously-saved and editable document is open:

• In Acrobat, selects the Save As command on the File menu.

• In Office, uses the F12 keyboard shortcut.
• In Office, clicks the Save As button on the Quick Access Toolbar.

Note: In Office, clicking the Save As command on the File menu starts the
native Office Save As dialog box, even if
ForceEnterpriseConnectSaveAsDialog is set to 1.

In addition, setting this value to 1 also causes the Enterprise Connect Save As
dialog box to appear if a user performs one of the following actions when a new
(never-saved) document is open:

• In Acrobat or Office, selects the Save command on the File menu.

• Clicks the document or application Close or Exit button or command.
• In Office, clicks the Save button on the Quick Access Toolbar.
• In Office, uses the CTRL+W, ALT+F4, or CTRL+S keyboard shortcut.

Note: In PowerPoint, setting ForceEnterpriseConnectSaveAsDialog to 1

only causes the Enterprise Connect Save As dialog box to appear if the user
chooses the native Office Save command, either by selecting it on a menu, or
clicking the Save button. The other methods listed above do not apply to
PowerPoint.

The ForceEnterpriseConnectSaveAsDialog has no effect on other methods used

to save documents in Office or Acrobat. For example, opening a local document in
Word, editing it, and then clicking the Save button does not cause the Enterprise

NGDCORE210200-IGD-EN-01 Installation Guide 111

Chapter 5 Configuring Editing Options

Connect Save As dialog box to appear regardless of the value of

ForceEnterpriseConnectSaveAsDialog.

Disabling the Save Locally Button

When ForceEnterpriseConnectSaveAsDialog is set to 1, the Save Locally button
appears on the Enterprise Connect Save As dialog box. This button allows users to
save a document to their local file system if they are unable to access Enterprise
Connect.

You can use the following registry setting to disable the Save Locally button:

DisableLocalSave (DWORD)

When the value of this setting is 0 (the default), the Save Locally button appears if
ForceEnterpriseConnectSaveAsDialog is set to 1. If the value of this setting is 1,
the Save Locally button does not appear, regardless of the value of
ForceEnterpriseConnectSaveAsDialog.

5.5 Configuring Extended Integration

You can do the following to configure the Extended Integration option:

• Specify which applications support Extended Integration.

• Limit the number of items displayed in the right pane of the Open and Save As
dialog boxes for Extended Integration applications.

5.5.1 Specifying Which Applications Support Extended

Integration
If the Extended Integration option is installed, users can use the native Open, Save,
and Save As dialog boxes in selected applications to open and save items in
Enterprise Connect. You can edit the following registry settings to restrict Extended
Integration support to specific applications:

ExtendedIntegrationSupportedApplications (string)
This setting lists the executable file names for the applications that support
native Open, Save, and Save As dialog box integration with Enterprise Connect.
The file names must be separated by commas without spaces.
By default, this setting includes an asterisk (*) wildcard, which means that
Extended Integration is supported for all desktop applications. The following
applications are also specified, because they have been explicitly tested for
Extended Integration support:

acrord32.exe Adobe Reader

notepad.exe Notepad

112 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.5. Configuring Extended Integration

wpwin15.exe, WordPerfect
wpwin16.exe,
wpwin17.exe

If you delete the * wildcard from this setting, Extended Integration only
supports applications whose executable files are explicitly listed in this registry
setting.

ExtendedIntegrationExcludedApplications (string)
This setting lists the executable file names for applications that are explicitly not
supported for Extended Integration. It takes precedence over the
ExtendedIntegrationSupportedApplications setting. Any application listed
in this setting is not supported by Extended Integration, even if the
ExtendedIntegrationSupportedApplications setting contains the * wildcard
or also lists the application’s executable file.
This setting does not support the * wildcard.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

Caution
Extended integration introduces the ability to potentially save or open
documents from any desktop application. To validate this functionality for
your environment’s target applications, you must perform thorough testing
on any application you intend to use with Extended Integration in a
production environment. Any issues found with extended integration
should be raised with OpenText Global Technical Services. Extended
integration functionality is provided “as is” without warranty of any kind,
either expressed or implied. Issues concerning the extended integration
functionality will be evaluated on a case-by-case basis without any
guarantee of resolution.

Notes

• You cannot enable extended integration for applications that are listed in the
IgnoredProcesses registry setting. For more information, see “Specifying
Processes To Ignore When Syncing Documents” on page 90.

• Extended Integration does not support the Office Save and Save As dialog
boxes, even if the Office applications are included in the list of supported
applications.

NGDCORE210200-IGD-EN-01 Installation Guide 113

Chapter 5 Configuring Editing Options

5.5.2 Limiting the Number of Items Displayed in Extended

Integration Open and Save As Dialog Boxes
In an Extended Integration application, if you are using the Open or Save As dialog
box to browse an Enterprise Connect folder that contains a very large number of
items, in some cases you might be unable to open the folder or view its contents. To
prevent this, you can add the following registry setting:

ListPaneItemLimitForNativeDialogs (DWORD)

This setting restricts the maximum number of items shown in an Enterprise Connect
folder in an Extended Integration Open or Save As dialog box. If this setting is 1 or
greater, Enterprise Connect restricts the maximum number of items displayed in a
folder to the value of the setting. The limit applies to all item types, including
folders, and is applied according to the alphabetical sorting of the items on the
server. For example, if ListPaneItemLimitForNativeDialogs is set to 5000
(decimal), and you open a folder that contains 8,000 items, only the first 5,000 items
in the folder will be displayed.

Caution
Any items that exceed the limit are not displayed in the Open and Save As
dialog boxes and are not accessible through Extended Integration
applications. As well, Enterprise Connect does not take into account any
file type filters specified in the dialog box when limiting the number of
items shown. For example, if ListPaneItemLimitForNativeDialogs is set
to 10000 (decimal), and you browse to a folder in Adobe Reader that
contains 10,000 Office documents and 10,000 PDF documents, you might
not see all of the PDF documents, depending on the alphabetical sorting of
the documents on the server.

If this setting is 0 or does not exist (the default), Enterprise Connect places no
restrictions on the number of items shown in a folder in an Extended Integration
Open or Save As dialog box.

You can create this setting in one of the following locations in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

• HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect

The setting in HKEY_CURRENT_USER takes precedence over the one in HKEY_LOCAL_

MACHINE if the setting exists in both places.

114 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.6. Mapping MIME Types to File Extensions

5.6 Mapping MIME Types to File Extensions

You can edit the registry to manually map a MIME type to a file extension. You
might want to create such a mapping if a user encounters the following situation
when attempting to open an item in Enterprise Connect:

• The item is stored in Content Server without an extension.

• No mapping between the item’s MIME type and an extension is defined on the
user’s system. When the user attempts to open the item, they are required to
manually select an application.

In this case, you can create the following registry key to store mappings between
MIME types and extensions:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Mimetypes

(on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Mimetypes (on 64-bit systems)

Within this key, create a string entry for each MIME type you want to map. Set the
name of the entry to be the MIME type, and the value to be the extension. For
example, to map the TIFF MIME type to the .tif extension, create an entry with
name image/tiff and value .tif.

Note: Enterprise Connect can also use the entries in this key to determine the
appropriate MIME types for documents that users copy or move to Content
Server. If Enterprise Connect is otherwise unable to determine the MIME type
for a copied or moved document, it will consult this registry key to determine
an appropriate MIME type mapping.

5.7 Enabling Users to Insert Document Properties in

Office
You can make various insertable document properties available to users who are
working with Office documents. Users can then insert these properties into their
documents through the Insert Property button on the Enterprise Connect tab in the
Office ribbon. A number of standard document properties are available by default.
You can also optionally enable Content Server Document Properties
Synchronization (DPS) properties by using DPS module bindings.

Note: In order to use the standard Shortlink (Properties) and Shortlink

(Open) properties, you must first enable Notifications in Content Server.

NGDCORE210200-IGD-EN-01 Installation Guide 115

Chapter 5 Configuring Editing Options

5.7.1 Configuring Insertable Document Properties Settings

On the Enterprise Connect Insertable Document Property Settings page, you select
which standard or DPS properties (if available) you want to make available to your
users. You can also create a user-friendly display name for the insertable property
for each available language. If you do not provide a display name, the original name
of the insertable property is used by default.

The Metadata Source column displays the source of the property in Content Server.
You can specify a display format for some of the properties in the Display Format
column. The Document Property column displays the specified file properties for
DPS properties.

Standard insertable properties

Standard insertable properties are available by default, and can be used to insert a
static value into Office documents. For example, if you enable the Description
property, and a user inserts this property in a document, this value will never be
automatically updated. The following standard insertable properties are available by
default:

• Create Date
• Created By
• Data ID
• Description
• Name
• Nick Name
• Owned by
• Shortlink (Open)
• Shortlink (Properties)

If you enable the Create Date standard property, you must specify the date format
that you want to use. You can use the short or long Content Server display date
format or the ISO 8601 format.

If you enable the Created By or Owned by standard properties, you can specify a
display format for each, such as First Name, Last Name, Office Location, or Fax.
The default format is User Name.

Tip: The User Name format is specified in the Content Server Administration
pages, on the Languages > Configure User Name Display admin page.

DPS insertable properties

If your system has been configured to associate metadata sources with DPS
bindings, you can also make DPS insertable properties available to users. DPS

116 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.7. Enabling Users to Insert Document Properties in Office

properties will only be available if the DPS binding applies to that document type
and location and it meets all other DPS criteria. For more information about
configuring DPS, see OpenText Document Properties Synchronization - OpenText
Content Server (LLESDPS-AGD).

Note: The Keep synchronized with Content Server metadata check box is
only available in Word for DPS insertable properties. In Word, users can
choose if they want the values to be automatically updated or if they want a
static property value.

5.7.1.1 To Configure Insertable Document Properties Settings

To configure insertable document properties settings:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Insertable Document Property Settings link.

2. In the Insertable Properties area, do one of the following:

• In the Add Insertable Property list, click the insertable property that you
want to add. DPS properties will only be available if you have created them
in the DPS Administration pages.

• Click the Remove Component button in the appropriate Actions column

to remove an insertable property from the list.

Tips

• By default, all of the standard insertable properties are available.

• If you do not want users to access this feature, you can remove the
Insert Property button on the Enterprise Connect tab in the Office
ribbon using the Show or hide Enterprise Connect menu items setting
on the Enterprise Connect Menu Settings admin page. For more
information, see “Configuring Enterprise Connect Context Menu
Items” on page 69.

3. In the Display Name box for each insertable property, do the following:

• Enter a user-friendly name that describes the insertable property. This value
appears in the Property Name box in the Select Property to Insert dialog
box in the Enterprise Connect client.

• Click the Multilingual Values icon to provide the insertable property

display name in additional languages. If you do not provide a display name
for a language, the default language display name is used.

Tip: The Multilingual Values icon is only available if multiple

languages are available on your system.

NGDCORE210200-IGD-EN-01 Installation Guide 117

Chapter 5 Configuring Editing Options

4. Optional In the Display Format column, for date properties, select one of the
following display options:

• Short Display Date Format to use the standard short form Content Server
date format. This is the default setting.

• Long Display Date Format to use the standard long form Content Server
date format.

• ISO 8601 to use the ISO 8601 date format, for example yyyy-mm-
ddThh:mm:ss.

Note: The option to specify date format is only available for standard
properties that have date values. For DPS properties that are date values,
the Display Format column displays the date format that is specified in
the DPS configuration.

5. Optional In the Display Format column, for the Created By or Owned by

properties, select the appropriate display option. The default setting for both of
these properties is User Name.

6. Click Save Changes.

5.7.2 Example of Configuring an Insertable Document

Property for Enterprise Connect
The following example shows how you could configure Enterprise Connect to make
a Category Attribute available for insertion in Office documents. In this example, the
Category stores information related to contracts, and the Attribute represents the
start date of the contract. The example requires creating a DPS binding for the
attribute before configuring Enterprise Connect.

1. On the System Administration > Content Server Categories page, create a

Category called Contracts with a Date: Field Attribute called Start Date.

2. On the Document Properties Synchronization > Binding Volume page, create a

new binding called Contracts Binding. Edit this binding to add a Category
Attribute mapping that maps the Start Date Attribute from the Contracts
Category to a custom Office property called Start Date.

118 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.7. Enabling Users to Insert Document Properties in Office

3. On the Enterprise Connect Administration > Enterprise Connect Insertable

Document Property Settings page, add Contracts:Start Date [Property:Start
Date] as an insertable property.

4. Add a sample document called Contract1 to Content Server, assign the

Contracts Category to it, and enter a value in the Start Date Attribute.

5. Open Contract1 for editing in Word. Open the document footer and type
Contract Start Date:.

NGDCORE210200-IGD-EN-01 Installation Guide 119

Chapter 5 Configuring Editing Options

6. On the Enterprise Connect tab, click the Insert Property button. In the Property
Name list, click Contracts:Start Date [Property:Start Date].

7. Click Insert, keeping the Keep synchronized with Content Server metadata
check box selected. The Start Date Attribute is inserted as a Word field in the
footer.

120 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 5.7. Enabling Users to Insert Document Properties in Office

8. To update the field in Word if the Attribute is updated, download the latest
version of the document, open it in Word, select and right-click the field, and
click Update Field.

NGDCORE210200-IGD-EN-01 Installation Guide 121

Chapter 6
Configuring Email Handling Options

This chapter describes the following email handling options that you can configure
for Enterprise Connect:

• Settings for capturing email attachments, managing duplicate emails, and

configuring email subtypes.
• Email naming conventions.
• Options for handling attachments with the same name.
• Outlook configuration options.
• Integration of Enterprise Connect with Email Archiving.
• Double-click actions for Compound Emails.
• Options for configuring the Enterprise Connect integration with IBM Notes.

Note: You can use the Email Services module administration pages to manage
how Enterprise Connect users store emails in Content Server and view these
emails. In particular, you can use the Extracting Additional Email Properties
box on the Configure Email Services administration page to capture
additional properties when emails are added to Content Server through
Enterprise Connect. You can also use this page to specify which email fields are
shown and which fields can be edited when emails are added. For more
information, see the online help for the Email Services module administration
pages.

6.1 Configuring Settings for Capturing Email

Attachments, Duplicate Emails, and Email
Subtypes
You can specify which subtype should be applied to saved emails and how
attachments should be handled when users add emails with attachments to Content
Server. You can also specify how duplicate emails are identified and if users should
be notified each time they add a duplicate email to a folder, or if duplicates should
be ignored. The methods you select depend on your corporate processes for saving
emails and attachments.

Email Subtype
The email subtype option applies the email subtype (749) to all emails that users add
to Content Server. By default, all emails are saved as the email subtype. You can
then specify how attachments are handled. You can choose to not store separate
copies of email attachments, or you can choose to add separate copies of the

NGDCORE210200-IGD-EN-01 Installation Guide 123

Chapter 6 Configuring Email Handling Options

attachments as individual documents, in addition to the original email and

attachments. If appropriate, you can permit users to decide, for each email, whether
to add separate copies of the attachments, or to save the email and attachments as a
single item.

Tip: You can link emails and attachments using Cross-References if you have
installed the OpenText Records Management module and have enabled this
feature. For more information, see “Using Records Management to File Emails
as Records” on page 50.

Duplicate Emails in Microsoft Outlook

By default, duplicate emails are detected by comparing the name of emails that are
added to Content Server with emails that already reside in that folder. When you
choose this option, users are notified each time Enterprise Connect identifies a
duplicate email in the destination. Depending on the configuration, users may be
asked to rename duplicate emails or provide metadata.

For example, assume you are using the default name comparison to identify
duplicate emails. If a user has previously added an email to a folder, and then adds
an email with the same name but different content to the same folder, it will be
identified as a duplicate. Depending on your configuration, the user may be
prompted to rename the email and provide metadata.

Optionally, you can specify that duplicate emails are detected by comparing the
message ID that has been assigned to the email that users add to Content Server
with emails that already reside in that folder. The message ID is different for each
recipient. For example, if the same email is sent to two different users, each copy of
the email has a unique ID. As a further option, you can specify that duplicate emails
are detected by comparing the external message ID of the email that users are
adding to Content Server with the external ID of emails that already reside in the
folder. The external message ID applies only to emails that are received from outside
of the user’s domain. When you choose the message ID comparison options,
duplicate emails are not copied or moved to the destination, and users do not
receive notification about duplicate emails. Only new emails are added and
depending on your configuration, users may be prompted for metadata.

For example, assume that you have selected the Use message id to check for
duplicate emails check box. A user adds a batch of emails to a folder, and one of the
emails already in that folder has the same message ID as one of the emails in the
batch. The user will not receive a duplicate email notification about the duplicate
email. Depending on the configuration, users may be asked to provide metadata for
all of the new emails. In another case, assume that two users receive an email from
the same sender. If both users copy the email to the same folder, the emails would
not be considered duplicates because they have different IDs.

For example, assume that you selected the Use external message id to check for
duplicate emails check box. A user adds an email received from an external source
to a folder. If a colleague who received the same email adds their copy of that email
to the same folder, it will be identified as a duplicate and it will not be added. The
user will not receive a duplicate email notification.

124 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.1. Configuring Settings for Capturing Email Attachments, Duplicate Emails, and Email Subtypes

Important
It is important that as administrator, you decide how duplicate emails are
identified when you are first setting up Enterprise Connect. Changing these
settings after users have started to work with emails may cause problems.

Notes

• This functionality only applies to Microsoft Outlook.

• This feature does not affect Compound Emails.

Compound Email Subtype

The Compound Email option is only intended for OpenText Explorer users who are
migrating to Enterprise Connect and who have been using the Compound Email
subtype (subtype 557). When you select this option, all emails and associated
attachments are added to Content Server as Compound Emails. A Compound Email
combines the email message and any associated attachments into a single folder.
Compound Emails only appear in the List Pane in Enterprise Connect and in the
Easy Access pane, if it has been configured to display Documents. They are not
visible in the Microsoft Outlook or Explorer Tree Pane, or in the Microsoft Office
File Open dialog box. Users can view Compound Emails in the Reading Pane. If you
want users to be able to take Compound Emails offline, you must add the
Compound Email subtype to the list of subtypes that can be taken offline. For more
information, see “Specifying Which Subtypes Can Be Taken Offline” on page 179.

Important
The storage space required for Compound Emails is substantially larger than
that required for the standard email subtype. Ensure that you have adequate
disk space to accommodate this requirement if you apply the Compound Email
subtype.

6.1.1 To Configure Settings for Capturing Email Attachments

To configure settings for capturing email attachments:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.
2. Go to the Capture Behavior area.
3. If you want to work with email subtypes, click Save emails as email subtype to
apply the email subtype (749) to emails. This is the default setting. Choose one
of the following options from the When adding email with attachments list to
specify how you want to save attachments:

• Click Do not add separate copies of the attachments if you want to save the
email and attachments as a single item. This is the default setting.
• Click Add separate copies of the attachments if you want to save the email
and attachments as a single item, and in addition, save all attachments as
separate items.

NGDCORE210200-IGD-EN-01 Installation Guide 125

Chapter 6 Configuring Email Handling Options

• Click Ask the user to decide if you want to allow users to decide how they
save attachments. If you select this option, users will be presented with the
following options:

– Prompt for attachments to separate for each email: If users choose this
option, a dialog box containing a list of attachments appears and users
can choose which attachments they want to copy or move.
– Always separate all attachments: If users choose this option, the email
and all attachments are copied or moved to Content Server.
– Never separate any attachments: If users choose this option, only the
email is copied or moved to Content Server.

4. If you want to specify how duplicate emails are identified, do the following:

• Select the Use message id to check for duplicate emails check box if you
want Enterprise Connect to identify duplicate emails using message ID
comparison. By default, this check box is cleared and only name comparison
is used.
• Optionally, select the Use external message id to check for duplicate emails
check box if you want Enterprise Connect to identify duplicate emails using
an external ID comparison. By default, this check box is cleared.

Note: You can only select this option if you have selected the Use
message id to check for duplicate emails check box.

5. If you want to work with Compound Email subtypes, click Save emails, with or
without attachments, as compound emails to apply the Compound Email
subtype (557).

6. Click Save Changes.

6.2 Defining Email Naming Conventions

When users add emails to Content Server using Enterprise Connect, naming
conventions are applied to the email. The default naming convention uses the
subject of the email as the email name, with no separators or exclusions. You can
customize the naming conventions in the following ways:

• Define which message properties to use in email names.

• Define the separator string to be used between the individual message properties
that make up the name of the email.
• Specify strings that you want removed from the name of the email.
• Specify the format for the date in the email.
• Specify how to handle emails with the same name.
• Specify naming conventions used when adding emails from Windows Explorer.

126 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.2. Defining Email Naming Conventions

Notes

• Although Enterprise Connect applies the specified naming conventions

when users add emails to Content Server, users can rename the emails if
desired.
• If you make the My Settings page available to Enterprise Connect users,
they will be able to configure these email naming conventions to their own
preferences. For more information, see “To Configure the Tree Structure and
List Pane” on page 60.
• If Enterprise Connect generates a name for the email that has already been
used in the Content Server container, users will either be prompted to
resolve the naming conflict before the email can be added, or Enterprise
Connect will generate a new name for the email, with a suffix to distinguish
it from the email already in the target destination. The option available to
users depends on your administrative settings.
• However, if you are saving emails as email subtypes and you are identifying
duplicates by matching message IDs, duplicate emails are not added to the
target and users are never notified that there is a duplicate. Note that you
will be prompted to determine how duplicate Compound Emails are
handled, because they are excluded from this rule.

6.2.1 To Define The Message Properties to Use in Email

Names
To define the message properties to use in email names:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. Go to the Message Properties area.

3. Click the message property that you want to use from the Available Properties
list, and then click Add to move it to the Selected Properties list. Subject is the
default value.

Tip: Click Add All to make all message properties available or Remove
All to make all message properties unavailable.

4. To set the order in which the message properties appear in the email name, click
a message property in the Selected Properties list, and then click Move Up or
Move Down as required.
5. Click Save Changes.

NGDCORE210200-IGD-EN-01 Installation Guide 127

Chapter 6 Configuring Email Handling Options

6.2.2 To Define the Separator Strings Between Message

Properties
To define the separator strings between message properties:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. Go to the Property Separator area.

3. In the Separator string box, enter an appropriate value, such as & or -. If you do
not specify a value, a single space is used to separate the message properties in
the email name.

Important
?, *, /, \, <, >, |, ., :, and " cannot be used as separator values.

4. Click Save Changes.

6.2.3 To Remove Strings from Email Names

To remove strings from email names:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. In the Strings to Remove area, enter the name of the string to be excluded from
email names in the Selected Strings box, and then click the Add String button
. Click the Remove String button to delete a string.

Example: If you want to specify that RE: will not appear in email names, enter RE: in
the Selected Strings box, and then click the Add String button .

3. Click Save Changes.

6.2.4 To Specify the Date and Time Formats in Email Names

To specify the date and time formats in email names:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. Go to the Date and Time Format area.

3. In the Date format string box, specify the format for the date and time that you
want to use, leaving spaces between the values if required. You can use any
combination of values in any order. The default values are %m/%d/%Y %I:%M %p,
which results in 08/16/2011 12:50 PM. The following table lists the available
values.

128 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.2. Defining Email Naming Conventions

Value Description
%a Abbreviated name of the day. For
example, Tue for Tuesday.
%A Full name of the day.
%b Abbreviated name of the month. For
example, Aug for August.
%B Full name of the month.
%c The full date and time for your location.
For example, Tuesday, August 16,
2011 12:36:04 PM.
%d Day of the month expressed as a numeric
value. For example, 16 for the 16th day of
August.
%H Hour expressed in 24–hour clock format.
%I Hour expressed in 12–hour clock format.
%j Day of the year expressed as a numeric
value. For example, 228 for the 16th day
of August.
%m Month expressed as a numeric value. For
example, 08 for August.
%M Minute expressed as a numeric value. For
example, 39 if the time was 8:39.
%p AM and PM.
%S Seconds expressed as a numeric value. For
example, 06 if the time was 12:35:06.
%U Week of the year expressed as a numeric
value, with Sunday as the first day of the
week. Values range from 00 to 53. For
example, the week of August 14th would
be week 33.
%w Day of the week expressed as a numeric
value, with Sunday as day 0. For example,
Tuesday would be day 3.
%W Week of the year expressed as a numeric
value, with Monday as the first day of the
week. Values range from 00 to 53. For
example, the week of August 14th would
be week 33.
%x Date for the current location. For example,
Tuesday, August 16, 2011.
%X Time for the current location. For example,
12:44:14 PM.

NGDCORE210200-IGD-EN-01 Installation Guide 129

Chapter 6 Configuring Email Handling Options

Value Description
%y Year without the century, expressed as
numeric value. For example, 11 for 2011.
%Y Year with the century, expressed as a
numeric value. For example, 2011.
% Percentage symbol.

4. Click Test Date Format to view a sample of the format you have specified,
using the current date and time.

5. Click Save Changes.

6.2.5 To Handle Emails with the Same Name

To handle emails with the same name:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. Go to the Duplicate Names area.

3. In the When an email with the same name is added to a folder list, do one of
the following:

• Click Automatically generate a name with a suffix if you want Enterprise

Connect to automatically generate a new name for the duplicate email. A
new instance of the email, with a suffix to distinguish it from the instance
that already resides in the destination, will be added to the destination.
• Click Give the user the option of accepting a name with a suffix if you
want Enterprise Connect to ask users if they want to add the email that was
automatically renamed to the destination location. This is the default setting.
• Click Allow the user to enter a new name if you want users to be able to
enter a new name for the duplicate email.

4. Click Save Changes.

Note: These settings apply to emails, Compound Emails, and email stubs when
working with Windows Explorer, Microsoft Outlook, and IBM Notes.

130 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.3. Handling Email Attachments With the Same Name

6.2.6 To Specify Naming Conventions Used When Adding

Emails from Windows Explorer
To specify naming conventions used when adding emails from Windows
Explorer:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. In the Duplicate Names area, do one of the following:

• Select the Disable email name generation when adding emails from
Windows Explorer check box to ignore the specified email naming
conventions and use the current name of the email. For example, a user
copies an email from Outlook to their desktop, and renames the email to
Contract1. The user then drags the renamed email to a folder in Enterprise
Connect. The email will be added to the folder using the current name. Any
email naming conventions that have been specified elsewhere are not
applied.
• Clear the Disable email name generation when adding emails from
Windows Explorer check box to rename the email using the specified email
naming conventions. This is the default setting. For example, a user copies
an email from Outlook to their desktop, and renames the email. The user
then drags the renamed email to a folder in Enterprise Connect. The email
will be added to the folder following any email naming conventions that
have been specified.

Note: If there is an email in the destination folder with the same name,
duplicate name settings are still applied, regardless of your selection.

3. Click Save Changes.

6.3 Handling Email Attachments With the Same

Name
When users try to add an email with attachments to a destination, they may find
that an attachment with the same name already resides in the folder. You can specify
how Enterprise Connect handles email attachments with the same name.

Note: If you make the My Settings page available to Enterprise Connect users,
they will be able to configure these conventions to their own preferences. By
default, the settings you specify here are applied. For more information, see
“To Configure the Tree Structure and List Pane” on page 60.

You can ask users if they want to add the attachment with the duplicate name as a
new version of the existing document. You can also specify that this happens
automatically, any time that Enterprise Connect detects a document with the same
name. You can also ask users if they want to add the attachment with the duplicate

NGDCORE210200-IGD-EN-01 Installation Guide 131

Chapter 6 Configuring Email Handling Options

name as a new document. In this case, the duplicate document will keep its name,
but a numeric suffix is added to distinguish it from the original document. For
example, taxform(2).doc. You can also specify that this happens automatically, any
time that Enterprise Connect detects a document with the same name.

Note: This setting only applies to emails that are saved as email subtypes (749).

If you have Records Management (RM) installed, and you create a cross-reference
for email attachments, users will see cross-references to the appropriate instance of
the attachment. For example, a user moves an email with an attachment called
legalform.doc to a folder in Content Server, and a document with the same name
already resides in that folder. You have selected Automatically add attachments as
a new document version. With cross-references enabled, a new version of
legalform.doc will be added to the existing document. When the user opens the
email from the new location, there will be a link to the appropriate instance of
legalform.doc. In this case, it would be the second version of legalform.doc. For
more information about setting up RM cross-references, see OpenText Content Server
- Records Management (LLESRCM200400-UGD).

6.3.1 To Configure How Enterprise Connect Handles Email

Attachments With the Same Name
To configure how Enterprise Connect handles email attachments with the
same name:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. In the Attachments area, in the When an email attachment with the same
name is added to a folder list, do one of the following:

• Click Prompt user to add attachment as a new document version to let

users choose if they want to add attachments that have the same name as an
existing document in the destination as a new version of the existing
document. This is the default setting.
• Click Prompt user to add attachments as a new document with a unique
suffix to let users choose if they want to add attachments that have the same
name as an existing document in the destination. The new document will
have the same name and a numeric suffix to distinguish it from the existing
document.
• Click Automatically add attachment as a new document version to
automatically add attachments that have the same name as an existing
document in the destination as a new version of the existing document.
• Click Automatically add attachments as a new document with a unique
suffix to automatically add attachments that have the same name as an
existing document in the destination as a new document with the same
name and a numeric suffix to distinguish it from the existing document.

132 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

3. Click Save Changes.

6.4 Configuring Outlook

You can do the following to configure the Enterprise Connect Outlook integration:

• Configure the Enterprise Connect add-ins to ensure they remain enabled in

Outlook.
• Specify whether the native Outlook viewer is used for document previews.
• Hide Enterprise Connect options in Outlook.
• Configure Outlook to use native folder icons.
• Specify settings for the Easy Access pane.
• Enhance performance when emails are added to Content Server in Outlook.
• Configure Outlook indicator columns.
• Add Quick Steps to HKEY_LOCAL_MACHINE.

6.4.1 Configuring the Enterprise Connect Add-ins for Outlook

to Remain Enabled
If you are using Outlook, OpenText recommends setting a Group Policy Object
(GPO) to prevent the Enterprise Connect add-ins from being disabled because of
performance issues such as slow startup times. The add-ins can be still disabled if a
serious issue is encountered. If you set this GPO, users will be unable to manually
disable the add-ins. They will be able to manually re-enable the add-ins if a serious
issue causes them to become disabled.

Setting this GPO causes the following string settings to be added to the client
registry and set to a value of 1:

• OpenText.MsoAddin
• OpenText.EnterpriseConnect.OutlookAddin

These settings are stored in the following location in the registry:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\<15.0 for Outlook

2013 or 16.0 for Outlook 2016 and 2019>\Outlook\Resiliency\Addinlist

For more information, see KB521424 (https://knowledge.opentext.com/knowledge/

llisapi.dll/kcs/kbarticle/view/KB521424).

To set an Outlook Group Policy Object (GPO) to prevent the Enterprise

Connect add-ins from being disabled:

1. In Group Policy Management Editor, navigate to User Configuration >

Administrative Templates > Microsoft Outlook <version> > Miscellaneous, and
then double-click List of managed add-ins.

NGDCORE210200-IGD-EN-01 Installation Guide 133

Chapter 6 Configuring Email Handling Options

Tip: Because Outlook 2019 uses the same administrative templates as

Outlook 2016, the version number for both is 2016.

2. Click Enabled, and then click Show next to List of managed add-ins.

3. In the first row, type OpenText.MsoAddin in the Value name box, and then type
1 in the Value box.

4. In the second row, type OpenText.EnterpriseConnect.OutlookAddin in the

Value name box, and then type 1 in the Value box.

5. Click OK, and then click Apply.

Tip: If you do not set the GPO, and the Enterprise Connect add-ins are
disabled in Outlook, you can manually set the add-ins to remain always
enabled. Restart Outlook, click File > Manage add-ins, and then click Always
enable this add-in under Enterprise Connect Outlook Add-in and Enterprise
Connect Task Pane.

6.4.2 Using the Outlook Viewer Instead of the Enterprise

Connect Viewer
You can edit the following registry setting to specify whether the Enterprise Connect
Outlook client uses the native Outlook viewer to preview items, or the Enterprise
Connect Viewer:

UseOutlookToPreviewDocuments (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Outlook (on

32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Outlook (on 64-bit systems)

When this setting is 1 (the default), the Outlook client uses the native Outlook
viewer to preview items. In this case, when a user selects an item in the List Pane in
Outlook, the Reading Pane displays a preview of the item using the Outlook viewer.
If the Outlook viewer does not support the item type, a message appears instead.
The properties tabs that typically appear in the Reading Pane are not displayed.

When this setting is 0, the Enterprise Connect Outlook client uses the Enterprise
Connect Viewer to preview items.

134 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

6.4.3 Hiding Options in Outlook

You can edit the following DWORD registry settings to determine if Enterprise
Connect options are hidden or displayed in Outlook:

HideAttachECDocument
This setting determines if the Enterprise Connect Attach Item button is available
on emails, meeting requests, and appointments in Outlook. The default value of
0 means that the button is displayed. A value of 1 means that the button is
hidden.
HideCopyAttachments
This setting determines if the Enterprise Connect Copy Attachments button is
available on emails in Outlook. It also determines if the Copy to Enterprise
Connect context menu is available on email attachments. The default value of 0
means that the button and command are displayed. A value of 1 means that the
button and command are hidden.
HideCopyMessage
This setting determines if the Enterprise Connect Copy Message button is
available on emails, meeting requests, and appointments in Outlook. The default
value of 0 means that the button is displayed. A value of 1 means that the button
is hidden.
HideCopyMove
This setting determines if the following commands are hidden in Outlook:

• The Copy/Move command on the Enterprise Connect tab.

• The Copy/Move to Enterprise Connect context menu command on Outlook
folders and items.

The default value of 0 means that the commands are displayed. A value of 1
means that the commands are hidden.

Note: This setting has no effect on the Copy/Move to Enterprise Connect

context menu command that appears on items inside Enterprise Connect.
HideLegacyTabInsertActions
This setting determines if the commands on the Enterprise Connect group on
the Home and Message tabs are also available on the Enterprise Connect tab in
Outlook. These commands include Quick Steps, Suggested, and Copy/Move on
the main Outlook ribbon, as well as the Copy Message and Copy Attachments
commands on the email ribbon. The default value of 1 means that these
commands are only available on the Outlook Home and Message tabs. When
this setting is 0, these commands are also available on the Enterprise Connect
tab.
HideQuickSteps
This setting determines if the Enterprise Connect Quick Steps commands are
available on the Enterprise Connect tab in the Outlook ribbons, as well as on
context menus. The default value of 0 means that the Enterprise Connect Quick

NGDCORE210200-IGD-EN-01 Installation Guide 135

Chapter 6 Configuring Email Handling Options

Steps commands are available. When this setting is 1, the Quick Steps
commands are not available, and users cannot create or use Quick Steps to move
or copy items to Enterprise Connect.
For more information on Quick Steps, see section 2.9 “Working with Enterprise
Connect Quick Steps in Outlook” in OpenText Enterprise Connect - User Getting
Started Guide (NGDCORE200400-UGD).
HideSendAndSave
This setting determines if the Enterprise Connect Send and Save button is
available on emails in Outlook. The default value of 0 means that the button is
displayed. A value of 1 means that the button is hidden.
HideSuggested
This setting determines if the Enterprise Connect Suggested command is
available in Outlook. The default value of 0 means that the command is
displayed. A value of 1 means that the command is hidden.
PreventDragAndDrop
This setting determines whether users are prevented from using the following
methods in Outlook to copy or move items and folders into Enterprise Connect.
If enabled, the setting also prevents users from using these methods to copy or
move items within Enterprise Connect:

• Dragging items.
• Using the Outlook Cut, Copy, and Paste commands, as well as related
Outlook commands, such as Move to folder.
• Using the CTRL+C, CTRL+X, and CTRL+V keyboard shortcuts.

The default value of 0 means that all these methods are supported. A value of 1
means that none of these methods is supported.
If enabled, this setting restricts users from using the listed methods to copy or
move items or folders into a location in Enterprise Connect. Regardless of the
value of this setting, users can still employ these methods to copy or move items
from Enterprise Connect to a folder in Outlook or Explorer. As well, this setting
does not affect the availability of the Copy/Move command, which is controlled
by the HideCopyMove registry setting.

Caution
If this setting is enabled, Enterprise Connect users are unable to copy or
move items within Content Server in Outlook. This setting does not
prevent users from copying or moving items to the Easy Access pane.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Outlook (on

32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Outlook (on 64-bit systems)

136 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

6.4.4 Configuring Outlook to Use Native Folder Icons

When connecting to Content Server, by default, Enterprise Connect displays Content
Server icons in the Tree Structure in Outlook. However, you can configure
Enterprise Connect to use the native Outlook icons. In some cases, this change may
improve performance for Outlook users. To make this change, you must create the
following registry setting:

UseNativeFolderIcons
A DWORD value that determines which icons are displayed in the Enterprise
Connect Tree Structure in Outlook. If this registry setting does not exist or if the
value is set to 0, then Enterprise Connect uses its own icons. If the value is set to
1, then the native Outlook icons are used.

You must add this setting to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Outlook (on

32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Outlook (on 64-bit systems)

6.4.5 Specifying Settings for the Easy Access Pane

You can edit registry settings in the following location to specify settings for the
Enterprise Connect Easy Access pane in Outlook:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\

EasyAccessPane (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\EasyAccessPane (on 64-bit systems)

Notes

• You can also change the Easy Access Pane title and button name. For more
information, see “Modifying Language-Specific Labels” on page 62.
• After editing these settings, you must start a new user session for the
changes to take effect.

You can edit the following settings:

ActionLeftMouseDragDefault (string)
Specifies the default action when items are dragged to the Easy Access pane
with the left mouse button pressed. This value corresponds to the Outlook left
mouse drag and drop setting in the Easy Access pane Options dialog box.
Supported values are Copy and Move. The default value is Copy.
ActionLeftMouseDragModifiable (DWORD)
Controls whether a user can modify the Outlook left mouse drag and drop
setting in the Easy Access pane Options dialog box. The default value of 1

NGDCORE210200-IGD-EN-01 Installation Guide 137

Chapter 6 Configuring Email Handling Options

means that the user can modify the setting. If this setting is 0, the value of the
Outlook left mouse drag and drop setting is taken from
ActionLeftMouseDragDefault, and users cannot modify the setting.

DragAutoExpandMillisecondsDefault (DWORD)
Specifies how long, in milliseconds, it takes for a folder in the Easy Access Pane
to expand when a user hovers over it while dragging an item. The default value
is 5000 (5 seconds). The minimum value is 1000 (1 second). If you specify a value
below 1000, it is ignored and the value is set to 1000 instead.
DragAutoExpandMillisecondsModifiable (DWORD)
Specifies whether you can override DragAutoExpandMillisecondsDefault. If
the value is 1 (the default), you can override the
DragAutoExpandMillisecondsDefault setting in HKEY_LOCAL_MACHINE by
manually creating a DragAutoExpandMilliseconds setting in the following
location and specifying a different value for it:
HKEY_CURRENT_USER\Software\Open Text\Enterprise Connect\
EasyAccessPane
If the value of this setting is 0, you cannot override
DragAutoExpandMillisecondsDefault by creating a new setting in HKEY_
CURRENT_USER.

Note: Even if DragAutoExpandMillisecondsModifiable is set to 1, you

cannot modify the DragAutoExpandMilliseconds setting through the
Easy Access pane Options dialog box.
NavigationFolderContentsListViewOnSelectDefault (DWORD)
Controls whether the Show folder contents in list view on select check box in
the Easy Access pane Options dialog box is selected or cleared. The default
value of 0 means the check box is cleared by default. If this setting is 1, check
box is selected.
NavigationFolderContentsListViewOnSelectModifiable (DWORD)
Controls whether a user can modify the Show folder contents in list view on
select check box in the Easy Access pane Options dialog box. The default value
of 1 means that the user can modify the setting. If this setting is 0, the value of
the Show folder contents in list view on select check box is taken from
NavigationFolderContentsListViewOnSelectDefault, and users cannot
modify the check box.
NavigationIncludeDocumentsFolderExpansionDefault (DWORD)
Controls whether the Include documents when browsing check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. If this setting is 0, the check box is cleared by
default.
NavigationIncludeDocumentsFolderExpansionModifiable (DWORD)
Controls whether a user can modify the Include documents when browsing
check box in the Easy Access pane Options dialog box. The default value of 1
means that the user can modify the check box. If this setting is 0, the value of the
Include documents when browsing check box is taken from

138 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

NavigationIncludeDocumentsFolderExpansionDefault, and users cannot

modify the check box.

NavigationIncludeDocumentsSearchResultsDefault (DWORD)
Controls whether the Include documents when searching check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. If this setting is 0, the check box is cleared by
default.

NavigationIncludeDocumentsSearchResultsModifiable (DWORD)
Controls whether a user can modify the Include documents when searching
check box in the Easy Access pane Options dialog box. The default value of 1
means that the user can modify the check box. If this setting is 0, the value of the
Include documents when searching check box is taken from
NavigationIncludeDocumentsSearchResultsDefault, and users cannot
modify the check box.

OutlookEasyAccessPaneVisibleDefault (DWORD)
Controls whether the Easy Access pane is open by default when Outlook is first
started after Enterprise Connect is installed. The default value of 0 means that
the Easy Access pane is not open. If this setting is 1, the Easy Access pane is
open by default.

OutlookEasyAccessPaneVisibleModifiable (DWORD)
Controls whether the Easy Access Pane menu appears on the Enterprise
Connect tab in Outlook. The default value of 1 means that the menu is visible
and users can choose to display or hide the Easy Access pane and view and
modify options for the pane. If this setting is 0, the Easy Access Pane menu does
not appear on the Enterprise Connect tab, and users are unable to display and
work with the pane or modify options for it.

StartupAutoNavigateToLastViewDefault (DWORD)
Controls whether the Auto expand to last tree view check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. If this setting is 0, the check box is cleared by
default.

StartupAutoNavigateToLastViewModifiable (DWORD)
Controls whether a user can modify the Auto expand to last tree view check box
in the Easy Access pane Options dialog box. The default value of 1 means that
the user can modify the check box. If this setting is 0, the value of the Auto
expand to last tree view check box is taken from
StartupAutoNavigateToLastViewDefault, and users cannot modify the check
box.

VisibilityOnStartupDefault (String)
Controls the state of the Easy Access pane when Outlook starts. The default
PreviousState value means that the Easy Access pane is open or closed
depending on its state in the previous Outlook session. Other possible values are
Hide or Show, which mean that the Easy Access Pane is always closed or always
open when Outlook starts.

NGDCORE210200-IGD-EN-01 Installation Guide 139

Chapter 6 Configuring Email Handling Options

VisibilityOnStartupModifiable (DWORD)
Controls whether a user can modify the Show Easy Access Pane on startup box
in the Easy Access pane Options dialog box. The default value of 1 means that
the user can modify the box. If this setting is 0, the value of the Show Easy
Access Pane on startup box is taken from VisibilityOnStartupDefault, and
users cannot modify the check box.

6.4.6 Enhancing Performance When Emails are Added to

Content Server in Outlook
By preventing Enterprise Connect from passing on unnecessary data, you can speed
up the process of adding emails to Content Server. Depending on the Email Services
configuration options you have set in Content Server, you can edit the following
registry settings to minimize the amount of data that Enterprise Connect passes on
when emails are added to Content Server in Outlook:

DontSendEmailBody (DWORD)
When this setting is 1, Enterprise Connect does not pass on the email body as
metadata to be stored in the Content Server database. If Email Services is
configured to store email message bodies for HTML rendering, this setting must
be 0 to ensure that Enterprise Connect passes on the email body as metadata.
The default value is 0.

Note: This setting only controls whether the email body is passed on to be
stored in the Content Server database to enable HTML rendering. In all
cases, the full email file is passed on to be stored in Content Server.
DontSendEmailCustom (DWORD)
When this setting is 1, Enterprise Connect only provides core email metadata
properties to Content Server. For a list of core properties, see the Indexed Email
Metadata section of the Email Services administration page in Content Server.
If Email Services is configured to extract one or more custom email properties,
as determined by the Additional Email Metadata section on the Email Services
Settings administration page, this setting must be 0 to ensure that Enterprise
Connect passes on the additional email properties extracted by Email Services.
Additionally, if other modules are installed that require access to non-core email
properties, this setting should be also be set to 0. The default value is 0.

For more information on configuring Email Services to store email message bodies
and extract custom properties, see the online help for the Email Services Settings
administration page in Content Server.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Outlook (on

32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Outlook (on 64-bit systems)

140 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

Note: These settings only apply to Content Server. They do not apply to any
other plug-ins.

6.4.7 Configuring Outlook Indicator Columns

Using the Enable indicator columns in Outlook for emails stored in Content
Server setting, you can specify that Enterprise Connect adds Content Server
metadata to emails that users copy to Content Server using Microsoft Outlook. You
can also make the following columns that display this metadata available to Outlook
users:

• Stored, which indicates if the email is stored in Content Server. If the email is
stored in Content Server, the value is Yes. If the email is not stored in Content
Server, the column is empty.
• Stored Location, which provides the location of the email when it was first
added to Content Server.
• Stored ID, which provides the node ID of the email.

By default, these columns are not available in Outlook. Users can make these
columns visible if they choose.

Optionally, you can customize the default column names and select which columns
are displayed by default. In addition, you can specify custom column names for any
languages available on the system.

Notes

• If you have more than one instance of Content Server in your environment,
ensure that these settings are the same on all instances. If the settings are
different, Outlook will use the settings specified in the last Content Server
instance the user connected to.
• These columns are only available on emails that users have dragged to the
Easy Access Pane or copied to Content Server using the Copy/Move
command or the Send and Save command.
• These settings only apply to emails that users have added to Content Server
after you have enabled this setting.
• If you change these settings, the changes are not applied to the Enterprise
Connect client until users open a new Outlook session.
• These settings are only available for Enterprise Connect client version 16.2.4
and later.

NGDCORE210200-IGD-EN-01 Installation Guide 141

Chapter 6 Configuring Email Handling Options

6.4.7.1 To Configure Outlook Indicator Columns

To configure Outlook indicator columns:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.
2. In the Indicator Columns area, do one of the following:

• Select the Enable indicator columns in Outlook for emails stored in

Content Server check box if you want to make these columns available to
Outlook users.
• Clear the Enable indicator columns in Outlook for emails stored in
Content Server check box if you do not want users to access these columns.
This is the default setting.
3. If you want to make these columns available to users, do the following:

• In the Display column, select the check box of each column that you want to
display by default. By default, the Stored column is enabled and the Stored
Location and Stored ID columns are disabled.
• Optionally, in the Column Name column, for each column that you want to
display, enter a user-friendly name that describes the column. The default
values are Stored, Stored Location, and Stored ID.

• Optionally, click the Multilingual Values icon to provide the column

display name in additional languages. If you do not provide a display name
for a language, the default language display name is used.

Tip: The Multilingual Values icon is only available if multiple

languages are available on your system.
4. Click Save Changes.

6.4.8 Adding Quick Steps to HKEY_LOCAL_MACHINE

When you create a Quick Step in Outlook, the settings for the Quick Step are stored
in the HKEY_CURRENT_USER hive in the registry. You can also manually add Quick
Steps to the HKEY_LOCAL_MACHINE hive. Doing this makes it possible to push out a
standard set of Quick Steps to all your users.

Quick Steps that are defined in HKEY_LOCAL_MACHINE are available in the Quick
Steps menu, just like Quick Steps that are created in Outlook. However, you can
only edit or delete Quick Steps defined in HKEY_LOCAL_MACHINE by modifying their
values in the registry. They are not displayed in the Manage Enterprise Connect
Quick Steps dialog box in Outlook.

To add a Quick Step to HKEY_LOCAL_MACHINE, create the following subkey in the

registry:

142 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.4. Configuring Outlook

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\QuickSteps

\<Quick Step ID> (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\QuickSteps\<Quick Step ID> (on 64-bit systems)

Where <Quick Step ID> can be any unique ID. Inside this subkey, add the following
values:

Action (String)
The Quick Step action. Supported values are Copy or Move.
DisplayName (String)
The default display name for the Quick Step.
DisplayName_<languagecode> (String)
A language-specific display name for the Quick Step, where <languagecode> is a
two-character language code. You can create a separate value for each supported
language. For example, create DisplayName_fr to specify the French name for
the Quick Step. If no language-specific display name exists that matches the
Enterprise Connect display language, the default DisplayName value is used.
DisplaySize (String)
Determines the size of the Quick Step icon in the Quick Steps group on the
Enterprise Connect tab in the Outlook ribbon. Possible values are Small or
Large.
Note: This setting does not affect the display of Quick Step icons in the
Enterprise Connect group on the Home tab. Icons in this location are
always small. This setting only affects Quick Steps that are displayed on
the Enterprise Connect tab. In order for Quick Steps to be displayed on
this tab, the HideLegacyTabInsertActions registry setting must be set to
0. For more information, see “Hiding Options in Outlook” on page 135.

Location (String)
The Enterprise Connect destination for the move or copy action. To determine
the correct value for this setting, create a Quick Step in Outlook that uses the
desired location, and then copy the Location value for this Quick Step from the
following location in the registry:
HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect\QuickSteps
\<Quick Step ID>

Order (DWORD)
The order in which the Quick Step is displayed in the list of Quick Steps. The
first value is 1.
Note: All Quick Steps that are defined in HKEY_LOCAL_MACHINE are
displayed before Quick Steps that are defined in HKEY_CURRENT_USER.
PromptForMetadata (DWORD)
Specifies whether Content Server prompts the user to enter metadata during the
copy or move process. Set to 1 to prompt for metadata, or to 0 to disable the
prompt.

NGDCORE210200-IGD-EN-01 Installation Guide 143

Chapter 6 Configuring Email Handling Options

Note: If Content Server is configured to always prompt the user to enter

metadata, setting this value to 0 has no effect.

The following screen capture shows an example of a Quick Step added to HKEY_
LOCAL_MACHINE:

6.4.9 Specifying a default starting location for the Send and

Save and Copy/Move to Enterprise Connect dialog
boxes
You can edit the following registry settings to specify the default location that is
selected when the Send and Save and Copy/Move to Enterprise Connect dialog
boxes start:

SendAndSaveAutoNavigate (String)

CopyMoveAutoNavigate (String)

You can assign one of the following values to these settings:

Plugin (default for CopyMoveAutoNavigate)

The root plug-in node is selected as the default location. If there is more than
one plug-in, the plug-in that contains the last accessed folder or history location
is selected.

LastExpanded (default for SendAndSaveAutoNavigate)

The last-expanded folder is selected as the default location.

LastHistory
The last-accessed item in the History node is selected as the default location.

These settings are stored in the following locations in the registry:

144 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.5. Configuring Enterprise Connect to Work with Email Archiving for Microsoft Exchange

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Outlook (on

32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Outlook (on 64-bit systems)

• HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect\Outlook

Note: If a setting is present in both locations, the value in HKEY_CURRENT_USER

takes precedence.

6.5 Configuring Enterprise Connect to Work with

Email Archiving for Microsoft Exchange
You can configure Enterprise Connect to work with Email Archiving for Microsoft
Exchange.

Users can archive emails in two ways:

• By using the Email Management Client in Outlook. For more information, see
OpenText Email Management for Microsoft Exchange - User Guide (EA160400-UGD).

• By using the Enterprise Connect Outlook client. Users can archive emails by
using the Copy/Move to Enterprise Connect command on the Outlook ribbon,
or by dragging emails to the Easy Access pane. For more information, see “Using
Enterprise Connect to Archive Emails” on page 149.

You must do the following to enable Enterprise Connect support for Email
Archiving:

1. Install and configure Email Archiving for Microsoft Exchange. For more
information, see OpenText Email Archiving for Microsoft Exchange - Installation
Guide (EA160200-IGD).
2. Edit the Email Archiving settings in the Enterprise Connect administration
pages. For more information, see “Editing Email Archiving Settings on the
Enterprise Connect Administration Pages” on page 146.
3. Edit the registry on each client to specify the Content Server plug-in that
supports Email Archiving. For more information, see “Specifying the Content
Server Plug-in for Email Archiving” on page 148.

NGDCORE210200-IGD-EN-01 Installation Guide 145

Chapter 6 Configuring Email Handling Options

6.5.1 Editing Email Archiving Settings on the Enterprise

Connect Administration Pages
You can use the following Enterprise Connect administration pages in Content
Server to edit settings for Email Archiving:

• On the Configure Enterprise Connect E-mail Settings page, enable Email

Archiving, and specify the order mailbox resolution method and how orders are
added to the order mailbox. For more information, see “Configuring Email
Archiving” on page 146.
• Optionally, on the Configure Enterprise Connect Display Settings page, make
the Personal E-mail Volume visible in Enterprise Connect. For more information,
see “To Configure the Tree Structure and List Pane” on page 60. For more
information about the Personal Email Volume, see OpenText Email Archiving for
Microsoft Exchange - Installation Guide (EA160200-IGD).

For order mailbox resolution, you can configure Enterprise Connect to use the
Exchange server or administrative group. You could also use an Active Directory
user property. You must specify the same method as the one defined in the
Archiving Bridge configuration for Microsoft Exchange.

For adding orders to the order mailbox, you can choose to post them directly or send
them by email. You must specify the same method as the one defined in the
Archiving Bridge configuration for Microsoft Exchange.

For more information about configuring order mailbox resolution and order mailbox
transmission methods, see OpenText Email Archiving for Microsoft Exchange -
Installation Guide (EA160200-IGD).

6.5.1.1 Configuring Email Archiving

This setting allows you to specify if emails and their attachments should be archived
when users add them to Content Server from their Inbox. By default, email archiving
is not enabled. For more information about how to enable email archiving, and how
users can archive emails using Enterprise Connect, see OpenText Email Archiving for
Microsoft Exchange - Administration Guide (EA160200-AGD).

Note: If you enable email archiving, all of the other email settings on the
Enterprise Connect Email Settings page do not apply to emails that are
archived. Instead, when emails and their attachments are archived, the settings
you specified as part of the Email Management Services module configuration
are applied.

To enable email archiving, you will first need to specify how the appropriate order
mailbox is determined for each user. By default, the order mailbox is determined
based on the server or administrative group that the user belongs to. You could also
use an Active Directory user property, which is defined as a hex value. For more
information, see OpenText Email Archiving for Microsoft Exchange - Administration
Guide (EA160200-AGD).

146 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.5. Configuring Enterprise Connect to Work with Email Archiving for Microsoft Exchange

Note: This value must be the same as the value specified in the Email
Management Services module configuration. Microsoft Exchange 2013 requires
property-based order mailbox resolution.

You will also need to specify if archiving orders are posted directly to the order
mailbox, or if they are sent by email. By default, the Post orders to order mailbox
check box is selected. This is generally the most efficient method for posting
archiving orders. However, you will need modify permissions on the order mailbox
to enable this. For more information, see OpenText Email Archiving for Microsoft
Exchange - Administration Guide (EA160200-AGD).

Note: You must have the appropriate version of the Email Management
module installed to be able to use the email archiving functionality. An error
message in the Email Archiving Settings section will indicate if you need to
upgrade.

6.5.1.1.1 To Configure Email Archiving Settings

To configure Email Archiving settings:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.
2. In the Email Archiving area, do one of the following:

• Select the Enable Email Archiving for Enterprise Connect. This applies to
emails added to Content Server from the inbox check box if you want to
enable email archiving using Enterprise Connect.
• Clear the Enable Email Archiving for Enterprise Connect. This applies to
emails added to Content Server from the inbox check box if you do not
want to enable email archiving using Enterprise Connect. Instead, emails are
saved to the selected Content Server container and are not archived. By
default, the check box is cleared.
3. In the Order mailbox resolution area, do one of the following to specify how
the order mailbox is determined:

• Click Based on server or administrative group to select the order mailbox

using server or administrative group settings. This is the default setting.
• Click Based on property with value and then type the appropriate property
value in hexadecimal form in the Hex value of property box to select the
order mailbox using a property.

Caution
You must use the same values in the Enterprise Connect configuration
as you used when configuring the Email Management Services
module.

4. Do one of the following:

NGDCORE210200-IGD-EN-01 Installation Guide 147

Chapter 6 Configuring Email Handling Options

• Select the Post orders to order mailbox check box to post archive orders
directly to the order mailbox. This is the default setting.

• Clear the Post orders to order mailbox check box if you want to send
archive orders to the mailbox by email.

Caution
You must use the same values in the Enterprise Connect configuration
as you used when configuring the Email Management Services
module.

5. Click Save Changes.

6.5.2 Specifying the Content Server Plug-in for Email

Archiving
For each user, Email Archiving is only supported for a single Content Server
instance. To enable support for Email Archiving in Enterprise Connect, you must
edit the following registry setting on each client:

PluginIdentifier (String)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Email

Archiving (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Email Archiving (on 64-bit systems)

In this setting, specify the unique ID of the Content Server plug-in that supports
Email Archiving. This must be a Content Server instance for which Email Archiving
support is enabled. For more information, see “Editing Email Archiving Settings on
the Enterprise Connect Administration Pages” on page 146.

If this setting is empty or does not contain a valid unique ID for the plug-in, Email
Archiving support is not enabled on the client. The setting is empty by default. You
can only enable Email Archiving support for a single Content Server plug-in for each
client.

For more information about the unique ID of the Enterprise Connect Plug-in for
Content Server, see “Connecting Enterprise Connect to Content Server” on page 29.

Note: You can also edit a registry setting to specify how Enterprise Connect
moves or copies email stubs into Content Server. For more information, see
“Configuring How Enterprise Connect Moves or Copies Email Stubs into
Content Server” on page 150.

148 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.5. Configuring Enterprise Connect to Work with Email Archiving for Microsoft Exchange

6.5.3 Using Enterprise Connect to Archive Emails

If Enterprise Connect is configured to support Email Archiving, Outlook users can
archive emails by copying or moving them to Enterprise Connect in one of the
following ways:

• By dragging emails to the Easy Access pane in Outlook. Dragging with either the
left or right mouse button held down is supported.
• By using the Copy/Move to Enterprise Connect command on the Enterprise
Connect tab in the Outlook ribbon.
• By right-clicking an email and selecting the Copy/Move to Enterprise Connect
command.
• By using the Enterprise Connect Copy Message command on an open email.

No other methods for copying or moving items to Enterprise Connect support

archiving.

Users can only archive emails that are stored on the Exchange server. If an operation
involving one of the methods listed above results in a situation where archiving
does not take place, the operation continues as a typical copy or move to Enterprise
Connect. This is the case in the following situations:

• The user copies or moves documents or folders.

• Enterprise Connect is offline.
• The destination folder requires mandatory Category Attributes.
• The Prompt for metadata when content is added setting is set to Always on the
server or in the user’s My Settings page.
• The user selects the Prompt for Metadata check box in the Copy/Move to
Enterprise Connect dialog box.
• The user copies or moves a mix of supported and unsupported items for
archiving.
• The user copies or moves emails stored in .pst files or on the desktop.
• The user copies or moves an item that was already archived.

Note: In all of the above cases, archiving does not take place, but no error
message is displayed to the user. The operation continues as a typical copy or
move operation, and the progress dialog box displays the status of the
operation.

The archiving process is largely transparent to the user:

• If archiving is successfully initiated, the progress dialog box displays a message

to indicate that the archiving request was sent.

NGDCORE210200-IGD-EN-01 Installation Guide 149

Chapter 6 Configuring Email Handling Options

• After the archiving request is sent, the rest of the process is handled by Email
Archiving. Any subsequent messages about the archiving process are sent
directly by Email Archiving to the user.
• Once the archiving process is complete, the copied or moved items are displayed
in their destination locations in Enterprise Connect.

Note: Until the archiving process is complete, the copied or moved items
are not displayed in Enterprise Connect. After they are archived, it might be
necessary to refresh the Enterprise Connect folder view to see the items in
their destination locations. In addition, moved items are only removed from
the source location after archiving is successfully completed.
• If a user archives an email by copying it, the email remains in its original location
in Outlook. If the Archiving Bridge is configured to append text to the email
subject, the appended text appears in the name of the email.
• If a user attempts an operation for which archiving is not supported, the
operation continues as a typical copy or move to Enterprise Connect. No error
message is displayed. The usual progress dialog box is displayed showing the
status of the copy or move operation.
For example, if a user drags several emails and a document to the Easy Access
pane, Enterprise Connect does not initiate an archiving request. Instead, the
items are copied or moved to the selected location in Enterprise Connect as if
archiving is not enabled.
• If a user attempts an operation for which archiving is supported, but Enterprise
Connect is unable to send the archiving request to the order mailbox, the
progress dialog box displays an error. The operation is canceled.

Note: You can edit a registry setting to prevent Enterprise Connect from
attempting to archive specific Outlook items. For more information, see
“Specifying Outlook Items for Which Archiving Is Not Attempted”
on page 152.

6.5.4 Configuring How Enterprise Connect Moves or Copies

Email Stubs into Content Server
If support for Email Archiving is enabled, you can configure the following registry
setting to specify how Enterprise Connect manages the process when users copy or
move email stubs from the Inbox to a folder in Content Server:

RetrieveEmailForStub (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Email

Archiving (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Email Archiving (on 64-bit systems)

150 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.5. Configuring Enterprise Connect to Work with Email Archiving for Microsoft Exchange

If this setting is 1 (the default), a copy of the full email is downloaded to the
Enterprise Connect client, and the email is then uploaded to the specified location in
Content Server. This process fully supports Enterprise Connect settings for splitting
attachments and Compound Emails. However, it can also increase the time required
to complete the transaction.

If this setting is 0, the full email is not downloaded to the client. The copy process is
handled entirely on the server. This can shorten processing time in some cases, but
also has the following implications:

• The email stub can only be moved or copied to the Content Server instance that
contains the Personal Email Volume which stores the corresponding email. It
cannot be moved or copied to a different Content Server instance.

• Enterprise Connect settings for splitting attachments do not apply. If the email
has attachments, they are always stored with the email.

• The copied emails cannot be stored as Compound Emails. They are always
stored as regular emails, even if the Compound Email setting is enabled.

• An upload directory must be specified for Content Server.

• If the Archiving Bridge is configured to append text to the email subject, the
appended text appears in the name of the copied email in Content Server.
However, the original subject is stored with the email, and displayed when the
email is opened.

For more information on Email Archiving, see “Configuring Enterprise Connect to

Work with Email Archiving for Microsoft Exchange” on page 145.

To configure email stubs to be moved or copied without downloading the

email to the client:

1. If an upload directory is not already set up for Content Server, do the following:

a. Create a folder for the upload directory.

For more information, see OpenText Content Server - Installation Guide
(LLESCOR200400-IGD). For more information on the required permission
settings for the folder, see KB13613834 (http://knowledge.opentext.com/
knowledge/cs.dll/Open/13613834).

b. In Content Server administration, click Configure Server Parameters.

c. Type the full path of the folder you created in the Upload Directory box,
and then click Save Changes.

2. On the Enterprise Connect clients, change the value of the

RetrieveEmailForStub registry setting to 0.

NGDCORE210200-IGD-EN-01 Installation Guide 151

Chapter 6 Configuring Email Handling Options

6.5.5 Specifying Outlook Items for Which Archiving Is Not

Attempted
If support for Email Archiving is enabled, in some cases users might attempt to
archive Outlook items whose message classes are specified in the Excluded message
classes setting for the Archiving Bridge. In this case, the items are not archived, and
the user is otherwise unable to copy or move them to Enterprise Connect.

To prevent this from happening, you can add Outlook message classes to a list that
Enterprise Connect explicitly excludes from archiving. For items with message
classes in this exclusion list, archiving is never attempted and the operation always
falls back to the usual Enterprise Connect copy or move operation.

To add item message classes to the archiving exclusion list for Enterprise Connect,
you must edit the following registry setting:

MessageClassFilters (Multi-string)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Email

Archiving (on 32-bit systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Email Archiving (on 64-bit systems)

This setting lists the Outlook message classes of items that Enterprise Connect does
not attempt to archive if a user moves or copies them to Enterprise Connect. By
default, it contains the IPM.Document* entry, which corresponds to all document
message classes.

The message classes you add to this setting should match the message classes
specified in the Excluded message classes setting in the Email Archiving Bridge >
Services > General area of the Archiving Bridge configuration. For more
information, see OpenText Email Archiving for Microsoft Exchange - Installation Guide
(EA160200-IGD).

Caution
Do not remove the IPM.Document* entry from this setting.

To edit this setting, add an Outlook message class to a new line in the setting. You
can determine an item’s message class in Outlook by displaying the Message Class
column in the Outlook view that shows the item.

You can add an asterisk (*) at the end of a line as a wildcard to represent one or
more trailing characters in the message class you specify. For example, IPM.
Document* specifies any message classes that begin with IPM.Document.

152 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.6. Configuring Double-click Actions for Compound Emails

For more information on Email Archiving, see “Configuring Enterprise Connect to

Work with Email Archiving for Microsoft Exchange” on page 145.

6.6 Configuring Double-click Actions for Compound

Emails
You can configure how Compound Emails open when users double-click them in
Enterprise Connect, in either Windows Explorer or Microsoft Outlook. Open
Compound Email’s message is the default setting, and you can use this option if
you want the Compound Email to open in Outlook when users double-click it. Use
the Open Compound Email’s sub-items setting if you want a separate web panel
that lists the email and the attachments to open when users double-click a
Compound Email. From the web panel, users can edit, open, or download the email
or the attachments, depending on their permissions. This panel offers the same
functionality as the Sub-Items tab in the Preview Pane. These settings apply to
Compound Emails that users browse to and to Compound Emails returned in search
result lists.

6.6.1 To Configure Double-click Actions for Compound

Emails
To configure double-click actions for Compound Emails:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Double-click Action area, click one of the following options in the When
double-clicking a Compound Email list:

• Open Compound Email’s message to open the selected email in Outlook.

This is the default value.
• Open Compound Email’s sub-items to launch a separate web panel.

3. Click Save Changes.

6.7 Configuring the Enterprise Connect Integration

with IBM Notes
You can do the following to configure the Enterprise Connect integration with IBM
Notes:

• Modify the Enterprise Connect labels that appear in the IBM Notes display.

• Enable the Attach Documents command.

• Specify the format to use when saving IBM Notes emails to Content Server.

NGDCORE210200-IGD-EN-01 Installation Guide 153

Chapter 6 Configuring Email Handling Options

6.7.1 Modifying IBM Notes Labels

You can add the following string settings to the registry to modify the default labels
for the IBM Notes integration:

LotusNotesCopyAttachmentsMenuLabel
String label of the Enterprise Connect copy attachments command that is
displayed on the IBM NotesAction menu.
LotusNotesCopyMoveMenuLabel
String label of the Enterprise Connect copy/move command that is displayed on
the IBM Notes Action menu.
LotusNotesOpenMenuLabel
String label of the Enterprise Connect open command that is displayed on the
IBM NotesAction menu.

If these registry settings do not exist, the default values for the labels are displayed,
according to the Enterprise Connect display language. If you add these keys, they
override the default values for the labels, in all languages. You must add the settings
to the following location:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

6.7.2 Enabling the Attach Documents Command in IBM Notes

The Enterprise Connect Attach Documents command lets users attach documents
from Enterprise Connect to IBM Notes emails. To enable the Attach Documents
command, you must make the following changes to the Mail<version>.ntf
template file in IBM Domino Designer:

• Add the (ECDeleteTempFiles) and (ECSelectDocuments) custom agents to the

template.
• Add the ECAttach.jpg image to the template.
• Insert the Attach Documents shared action into the appropriate mail forms in the
template.

The custom agents, image, and shared action are stored in the ECDesign.nsf file.
You can obtain a copy of this file in the <installation root>\OpenText\
Enterprise Connect folder when you install Enterprise Connect with the IBM
Notes Client integration selected.

Note: To ensure that users do not receive security alerts after you enable the
Attach Documents command, you must give the account that you use to edit
the Mail<version>.ntf template file permission to access the following from
user workstations:

154 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 6.7. Configuring the Enterprise Connect Integration with IBM Notes

• File system.
• Current Notes database.

• Environment variables.

• External programs.

To enable the Attach Documents command using IBM Domino Designer 9:

1. Install Enterprise Connect with the IBM Notes Client integration selected, and
obtain the ECDesign.nsf file located in the <installation root>\OpenText\
Enterprise Connect folder.

2. Start IBM Domino Designer.

3. Open the following files:

• mail9.ntf

• ECDesign.nsf

4. Do the following for each of the (ECDeleteTempFiles) and

(ECSelectDocuments) agents:

• Navigate to ECDesign > Code > Agents, right-click the agent, and then click
Copy.

• Navigate to Mail (R9) > Code, right-click Agents, and then click Paste.

5. Do the following for the ECAttach.jpg image:

• Navigate to ECDesign > Resources > Images, right-click ECAttach.jpg, and

then click Copy.

• Navigate to Mail (R9) > Resources, right-click Images, and then click Paste.

6. Do the following for the Attach Documents shared action:

• Navigate to ECDesign > Code > Shared Actions, right-click Attach

Documents, and then click Copy.

• Navigate to Mail (R9) > Code, right-click Shared Actions, and then click
Paste.

7. Do the following for each of the Message, Reply, and Reply with History and
Attachments forms:

• Navigate to Mail (R9) > Forms, right-click the form, and then click Open.

• On the Create menu, click Action > Insert Shared Action, click Attach
Documents, and then click Insert.

NGDCORE210200-IGD-EN-01 Installation Guide 155

Chapter 6 Configuring Email Handling Options

6.7.3 Specifying a Format for IBM Notes Emails

You can specify which email format is used when users save an email to Content
Server when they are working in IBM Notes. By default, DXL is used. Depending on
your requirements, you have the option of using EML.

6.7.3.1 To Specify a Format for IBM Notes Emails

To specify a format for IBM Notes emails:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Email Settings link.

2. In the IBM Notes area, select one of the following options in the When saving
an email from IBM Notes to Content Server, use this format list:

• DXL. This is the default setting.

• EML.

3. Click Save Changes.

156 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 7

Configuring Search Options

This chapter describes the following search options that you can configure for
Enterprise Connect:

• Search profiles.
• The number of search results displayed on a page.
• Whether search results include Shortcuts and Cross-References.
• Whether searches launched by the Advanced Search toolbar button specify the
current location in the Location box.
• Quick searches.
• Search result columns.
• The Score column.

7.1 Configuring Search Profiles

You can create search profiles to enable users to apply predefined search criteria
when they perform searches in the Enterprise Connect Easy Access pane. In the
Search Profile area, you can create, update, and delete search profiles. You can also
set the order in which search profiles are matched against the email subject.

The search profile consists of a location and search slice, as well as a name.
Optionally, you can include pattern-matching criteria that can extract search terms
that can in turn be used to form search criteria. You can also use prefixes and
suffixes to further refine the extracted search criteria.

Users can work with search profiles in several ways. In the Easy Access pane, users
can select a search profile from the Search Profile list, enter a search term in the
Search box, and then launch a search. Another way to use search profiles is to
generate search criteria by matching an email subject to a search profile and then
optionally adding a prefix or suffix to enhance the search. For example, consider a
situation where a user has an email in their Inbox that they would like to copy to
Enterprise Connect. However, they are not sure which folder to copy it to. If the user
clicks the email, Enterprise Connect will find a search profile that matches the
subject, extracts search criteria, and adds it to the Search box in the Easy Access
pane. If you are using a suffix or prefix, this is also added to the search criteria in the
Search box, with the extracted text. When the search is complete, the user can
review the search result list for a suitable location, and copy or move the email as
required. For more information about using search profiles in the Easy Access pane,
see OpenText Enterprise Connect - User Getting Started Guide (NGDCORE200400-
UGD).

NGDCORE210200-IGD-EN-01 Installation Guide 157

Chapter 7 Configuring Search Options

To set up search profiles, you may be able to use existing search slices, or you may
need to set up search slices in Content Server. For more information about working
with search slices, see section 1.11.13 “Creating Slices” in OpenText Content Server
Admin Online Help - Search Administration (LLESWBS-H-AGD). You should also be
comfortable working with regular expressions (regex). Your search profiles will be
unique to your organization, and there are many ways to set them up. The following
examples demonstrate some simple regular expressions.

Creating Regular Expressions

This example demonstrates how to set up a regular expression when there is a
constant string that identifies possible matches, followed by variable text that you
want to return. Assume that you have emails with the following subject lines:

• Reference Active 69582: Smith Contract Negotiation Meeting Notes

• Reference Archive 958: Jones Contract Termination Notes

You could create the following regular expressions:

• Reference\s?([a-z]+\s\d+) would return both examples, because it matches

the constant reference and the variables archive and active.
• Reference\s?(active+\s\d+) would only return the first example, because it
matches the constant reference and the variable active.

Note: Only the text that matches the part of the expression that resides inside
the parentheses is added to the Search box in the Easy Access Pane. If you do
not use parentheses in the regular expression, all of the matched text is added
to the Search box.

This example demonstrates a case where there are no constant strings used to
identify matches, and you are only using variable text only. For example, assume
that you have emails with the following subject lines:

• Reference 69582: Smith Contract Negotiation Meeting Notes

• Invoice 958: Jones Contract Termination Notes

You could create the following regular expressions:

• [a-z]\s?\d+ would return both examples, because it matches both reference and
invoice, as well as the numeric ID.
• Reference\s?\d+ would return only the first example, because it matches
reference.

Note: In this case, including parentheses around Reference\s?\d+ is

optional.

Working with Prefixes and Suffixes

Optionally, you can add a prefix or suffix to a search profile to further refine the
search. If specified, the prefix or suffix is added to the Search box with the extracted

158 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 7.1. Configuring Search Profiles

search term. When a user performs the search, the results reflect the extracted search
term as well as the prefix or suffix.

For example, assume that you have selected an email with the subject line
“Reference Active 69582: Smith Contract Negotiation Meeting Notes”. If you have a
search profile that consists of a regular expression of Active\s?(\d+:\s?[a-z]+),
and a prefix of Customer and a suffix of Notes, the Search box will be populated
with the search term Customer 69582:Smith Notes. By further refining the search
criteria in this way, the search results will be more precise.

7.1.1 To Configure Search Profiles

To configure search profiles:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Search Settings link.
2. In the Search Profiles area, do the following:

• In the Display Name box, enter the name of the search profile. This name
appears the search box in the Easy Access pane.

Tip: Make sure that the display name that you select describes the
search to help users understand what the search profile does. If you
have multiple search profiles, a descriptive name will help users
determine which search profile they should use.
• In the Location box, do one of the following to define where the search is
performed:

– Click Use current location to search the location selected by the user in
the Easy Access pane.
– Click Choose a specific location, and then in the Browse to a Location
dialog box, go to and then select the appropriate location.
• In the Slice box, define which slice will be used in the search.

• In the Actions column, specify the order of the search profiles by clicking the
Move Search Profile Up button or the Move Search Profile Down
button . Enterprise Connect matches the list of available search profiles to
the email subject in the order that you specify. This is also the order that
search profiles appear in the Search Profile box in the Easy Access pane.
3. Optional If you want to use pattern matching, do the following in the Search
Profiles area:

• In the Pattern Match box, define the pattern, in regular expression (regex)
form, that is used to extract a search term from the subject line of a selected
email.

Note: Regex values are not case-sensitive.

NGDCORE210200-IGD-EN-01 Installation Guide 159

Chapter 7 Configuring Search Options

• In the Search Prefix box, define the string that is added to the beginning of
the search term that was extracted using the pattern match values.
• In the Search Suffix box, define the string that is added to the end of the
search term that was extracted using the pattern match values.

4. Click the Add Search Profile button to add the search profile, and then click
Save Changes.

Tips

• To edit an existing search profile, make changes to the appropriate search

profile definitions, and then click Save Changes.
• To delete a search profile, click the Remove Search Profile button for the
appropriate search profile, and then click Save Changes.

7.2 Specifying the Number of Search Results on

Each Page
Using this setting, you can specify the number of search results that appear on each
page when a user performs a search using Enterprise Connect.

7.2.1 To Specify the Number of Search Results On Each Page

To specify the number of search results on each page:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Search Settings link.
2. In the Search Results area, select the appropriate number of search results to
display on each page in the Search Result Page Size list. The default value is 25.
3. Click Save Changes.

7.3 Specifying Quick Search Location Modifiers

To help users better define their Quick Searches, you can specify search location
modifiers. By default, no search location modifiers are applied to Quick Searches. If
you select the Exclude Sub-Folders option, Enterprise Connect only searches the
contents of the container that the user has selected, excluding any subfolders that
reside in the selected container. If you select the Follow Shortcuts option, any
folders that are referenced by shortcuts in the container that the user is searching
will be included in the Quick Search.

Note: Additional search location modifiers may be available, depending on

which modules have been installed.

Tip: OpenText recommends that you select only one of the available search
location modifiers at a time.

160 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 7.4. Specifying the Default Advanced Search Location

7.3.1 To Specify Quick Search Location Modifiers

To specify Quick Search location modifiers:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Search Settings link.

2. In the Search Results area, in the Include these location modifiers in Quick
Search area, do one of the following:

• Select the Exclude Sub-Folders check box if you want to exclude subfolders
from Quick Searches.
• Select the Follow Shortcuts check box if you want to include shortcuts to
folders in Quick Searches.

3. Click Save Changes.

7.4 Specifying the Default Advanced Search

Location
By default, when a user selects a folder and then launches an Advanced Search
using the Advanced Search button on the toolbar, the Location box will contain the
location specified by the user. However, you can change this behavior. By clearing
the Enable Advanced Search From Here check box, the Location box will not be
prepopulated with the currently selected location

Note: This setting only applies to advanced searches that users launch using
the Advanced Search button on the toolbar. It does not apply to advanced
searches launched using the Search a Repository command on the Enterprise
Connect menu or tab. In this case, users must always specify a location.

For example, you may want to change the default behavior if your users are working
with search templates. When users launch an Advanced Search, you might want the
location to be that specified by the template rather than the users’ current location.

7.4.1 To Specify the Default Advanced Search Location

To specify the default Advanced Search location:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Search Settings link.

2. In the Search Options area, do one of the following:

• Select the Enable Advanced Search From Here check box if you want
Enterprise Connect to populate the Location box in the Advanced Search
dialog box with the current location selected by the user. This is the default
setting.

NGDCORE210200-IGD-EN-01 Installation Guide 161

Chapter 7 Configuring Search Options

• Clear the Enable Advanced Search From Here check box if you do not want
the Location box to be populated with the current user location.

3. Click Save Changes.

7.5 Using Quick Search

The Enterprise Connect quick search uses the following settings for Content Server
searches:

• The mode is All Words.

• Results are sorted by relevance.
• Standard Content Server search operators are supported.

Depending on how the search bar settings are configured in Content Server,
Enterprise Connect quick search results might differ from those obtained in the Web
interface.

7.6 Setting Search Columns

By default, a search in Enterprise Connect returns the same columns as a Content
Server Web search, as defined by the user’s default Content Server Search Form.
This is either the system Search Form, which the Content Server administrator
configures, or a personal Search Form that the user has created and set to be their
default Search Form.

Enterprise Connect users can customize the column display for search results, by
showing or hiding search result columns in Outlook and Explorer. The column
selections persist across user sessions, and apply to all folders of the same subtype,
on a per-integration basis. For example, if a user removes a column from an Email
Folder search result view in Explorer, the column is not displayed for all subsequent
searches of Email Folders in Explorer. For more information, see section 2.3.3
“Specifying Columns in the List Pane” in OpenText Enterprise Connect - User Getting
Started Guide (NGDCORE200400-UGD).

Note: If a user customizes the column display of a search undertaken on two

or more different types of folders, the customized view is saved, and is applied
to all subsequent searches involving multiple folder types.

The following procedure gives an example of how to display the

OTEmailReceivedDate column in Enterprise Connect search results. It assumes that
the system Search Form is the default form for all users. This procedure is an
example only, and does not describe all the Search Form configuration options
available in Content Server. For more information about configuring columns to be
displayable in Content Server search results, see the section on configuring search
regions in the Content Server administration help. For more information about
displaying columns in Search Forms, see the section on retrieving information in the
Content Server user help.

162 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 7.6. Setting Search Columns

To display an email column in Enterprise Connect search results:

1. On the Content Server Administration page, click Search Administration, and

then click Open the System Object Volume.

2. Click Enterprise Data Source Folder.

3. Click the Enterprise Search Manager functions menu, and then click Properties
> Regions.

4. For the OTEmailReceivedDate column, do the following:

• In the Display Name box, type Received. This is the label that users see in
the column header.
• Select the Displayable check box. This makes the column available to be
added to the Search Form display.
• Select the Sortable check box. This enables users to sort on the column.

5. Click Update.

6. On the Content Server Administration page, click Search Administration, and

then click Edit the System Default Template or Edit the System Default
Search Form.

7. In the Results Display Style list, click Edit the Display Options.

8. In the Results Fields: Displayed area, in the Available box, double-click

Received. This moves the column to the Displayed box, which lists all the
columns that are displayed when the System Search Form is used.

9. Click Apply.

10. Click Update.

Note: This procedure causes the Received column to be displayed for all
Content Server search result lists in Enterprise Connect, for users whose
default Search Form is the system Search Form. If you do not want it displayed
for a folder type, perform a search on a folder of that type, and then remove the
Received column from the search results list. For example, if you perform a
search on a regular Content Server Folder in Outlook, and then remove the
Received column from the search results list, the column will never be
displayed again in regular Folder search results in Outlook.

NGDCORE210200-IGD-EN-01 Installation Guide 163

Chapter 7 Configuring Search Options

7.7 Displaying the Score Column in Search Results

By default, when users perform a search in Enterprise Connect, the Score column
will be visible in the search results. This column contains a value that indicates how
closely each search result matches the specified search criteria. You can choose to
hide this column if this information is not useful to your users.

7.7.1 To display the Score Column in Search Results

To display the Score column in search results:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Search Settings link.

2. In the Search Results area, do one of the following:

• Select the Show Score column in search result check box if you want users
to be able to see the Score column. This is the default setting.
• Clear the Show Score column in search result check box if you do not want
to show the Score column for search results.

3. Click Save Changes.

164 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 8

Configuring Copy and Move Options

This chapter describes the following copy and move options that you can configure
for Enterprise Connect:

• Metadata requirements when copying or moving items.

• Object types that support the Copy/Move context menu command.
• Object types for folders that are dragged into Enterprise Connect.
• The Send to > Desktop location command.
• File type filtering for files copied to Enterprise Connect.
• Mapping a custom subtype to a file extension.
• Whether Content Server shortcuts created by dragging include Shortcut in their
names.
• Briefcases that enable users to temporarily work on documents outside of
Enterprise Connect.
• Container options when saving items to Enterprise Connect.
• The Enterprise Connect Drag and Drop panel in Content Server.

8.1 Configuring When Users Are Required to Provide

Metadata
Metadata on items stored in Content Server can include the following:

• Properties such as the item name and description.

• Categories and their attributes.
• Classifications, such as Records Management Classifications.

You can use the Enterprise Connect module administration page in Content Server
to specify when metadata is required. If you specify Always for the Prompt for
metadata when content is added option, users must always provide metadata when
adding items. Otherwise, users are prompted for metadata when Content Server is
configured to require it, as in the following examples:

• A Category with one or more required attributes is applied to a Folder or other

object type that supports Categories. When users add an item to the Folder, they
are required to specify or confirm values for the required attributes before the
item is added.

NGDCORE210200-IGD-EN-01 Installation Guide 165

Chapter 8 Configuring Copy and Move Options

• One or more RM fields are made required for new documents. To do this, in the
Records Management workspace, go to Records Management Administration >
System Settings > RM Fields.
• A MIME type Category mapping is created for one or more document types.
When users add items that correspond to the MIME type, they are prompted to
specify attribute values for the mapped Category. For more information, see
“Enabling MIME Type Category Mappings” on page 168.

When users add multiple items to a Content Server folder by dragging them, they
can select the Apply to all items with similar types check box when specifying
Category attributes. If MIME type Category mapping is enabled, they can assign a
different set of attribute values to each MIME type being added. If MIME type
Category mapping is disabled, they can apply a different set of attribute values to
each object type being added, either documents, folders, or emails.

For more information, see “Configuring Content Capture Options” on page 166.

Notes

• The Prompt for metadata when content is added option only applies to
items that are added from outside Content Server, such as items that come
from the local desktop or from a different Content Server instance. It does
not apply to copy or move actions applied to items within a single Content
Server instance. If the metadata prompt is not required, users can also choose
to provide it by selecting the Prompt for Metadata check box when adding
items using the Enterprise Connect Open and Copy/Move to Enterprise
Connect dialog boxes. For more information, see OpenText Enterprise Connect
- User Getting Started Guide (NGDCORE200400-UGD)
• Some restrictions apply to name and category assignments for items that are
copied or moved from one folder to another within a single Content Server
instance.

8.1.1 Configuring Content Capture Options

The settings in this section enable you to specify when users are prompted to enter
metadata about items they add to Content Server.

Using the options in the Prompt for metadata when content is added list, you can
configure the settings so that users are only prompted to provide metadata if a
required attribute is missing or for every item they add to Content Server. You can
also specify that they are prompted to provide metadata even if required attributes
have already been defined, which gives users the opportunity to update attributes
before adding the item to Content Server.

If you have other Content Server modules such as Records Management installed in
your environment, by default, your users will always be prompted to provide
metadata when they copy or move items within an instance of Content Server.
However, you can specify that users are only prompted to provide metadata when
copying or moving items within an instance of Content Server when the source and

166 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.1. Configuring When Users Are Required to Provide Metadata

destinations have different category requirements. For example, consider an

environment with Enterprise Connect and Records Management installed. If you use
the Always setting, users will be prompted to provide metadata each time they copy
or move a Document within the instance of Content Server, regardless of the
metadata requirements of the source and destination. If you use the Never setting,
users will be prompted to provide metadata when the destination requires users to
provide no metadata, but the source has categories and attributes enabled. If the
metadata requirements of the source and destination are the same, users will not be
prompted for metadata.

Choose the options that suit your best practices for capturing metadata.

8.1.1.1 To Configure Content Capture Settings

To configure content capture settings:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Prompt Behavior area, do one of the following in the Prompt for
metadata when content is added list to specify when users should be prompted
to provide metadata for items that they add to Content Server:

• Click Only when required attributes are missing values to prompt users to
provide metadata only if the required attribute values have not been
provided.
• Click Always, even when there are no required attributes to prompt users
to provide metadata for each item they add to Content Server.
• Click Always, if there are required attributes to prompt users to provide
metadata even if the required attributes have already been provided.

3. In the Prompt Behavior area, do one of the following in the Prompt for
metadata from additional modules when content is moved/copied within
Content Server list to specify when users should be prompted to provide
metadata when other Content Server modules are installed in your
environment:

• Click Always if you want users to always be prompted to provide metadata

each time they copy or move items within Content Server. This is the default
setting.
• Click Never if you want users to only be prompted to provide metadata
when they copy or move items within Content Server when the source and
destination have different category requirements.

4. Click Save Changes.

NGDCORE210200-IGD-EN-01 Installation Guide 167

Chapter 8 Configuring Copy and Move Options

8.1.2 Enabling MIME Type Category Mappings

You can use theAdminister MIME Types and Categories Content Server
Administration page to map Categories to MIME types. For example, to ensure that
all PDF documents are assigned a Publishing Information Category, you can create a
Category with this name, and then map the category to the appropriate MIME type
for PDF documents, for example, application/pdf.

When an Enterprise Connect user adds an item with a mapped MIME type to
Content Server, the Add dialog box always appears for the item. This dialog box
gives the user the option to specify item metadata, including attribute values for the
item's mapped Category.

8.2 Configuring the Copy/Move Command

By default, the Copy/Move context menu command is available for all objects except
for the Favorites, your personal Workspace, and Enterprise folders. You can remove
this command from the context menu of other objects by adding their item type to
the Available list in the Copy/Move area. For example, if you wanted to make this
command unavailable for Folders, Tasks, and Discussions, you would move them
from the Selected list to the Available list.

Note: The Copy/Move context menu command is never available for virtual
items such as the Personal, Other Items, and Volumes nodes.

8.2.1 To Specify Where Users Can Access the Copy/Move

Command
To specify where users can access the Copy/Move command:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.
2. In the Copy/Move area, do the following:

• In the Available list, select the item types for which you want Copy/Move to
be available and click Add.
• In the Selected list, select the item types for which you do not want Copy/
Move to be available and click Remove.

Note: The following item types are excluded by default:

• Enterprise (141).
• My Workspace (142).
• Favorites (628).

Tip: Click Add All to make Copy/Move available for all item types. Click
Remove All make Copy/Move unavailable for all item types.

168 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.3. Configuring Object Types When Dragging Folders

3. Click Save Changes.

8.3 Configuring Object Types When Dragging

Folders
You may want to specify the type of object that is created when users drag certain
types of folders from their file system to Content Server. To do this, you specify that
folders with certain extensions in their names become either Email Folders or
Compound Documents when users drag them into Content Server. This feature is
not available in Microsoft Outlook.

By default, no values are provided. If you specify multiple extensions, use commas
to separate them.

For example, a user drags a folder called test.cd from their file system to Content
Server, and you have specified that folders with the CD extension should be treated
as a Compound Document. The CD extension is removed from the name of the
folder and a new Compound Document is created in the destination. All items
residing in the folder are included in the action, and users will be prompted to
provide metadata according to the settings you have specified. Subfolders that
reside in the main folder are not included in the action. If there already is an item
with the same name in the destination, the naming conflict resolution rules that you
have specified will be applied. If the folder contains a type of item that is not
permitted, then the action will be abandoned.

8.3.1 To Configure Object Types When Dragging Folders

To configure object types when dragging folders:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the File System Extension area, do the following:

• In the Folder extension for Compound Document box, specify the

extensions that you want to use to identify folders that should be treated as
Compound Documents, for example, CD. By default, the box is empty.
• In the Folder extension for Email Folder box, specify the extensions that
you want to use to identify folders that should be treated as Email Folders,
for example, EM. By default, the box is empty.

Note: If you are specifying multiple extensions, use commas to separate

the names. Do not leave spaces between the names.

3. Click Save Changes.

NGDCORE210200-IGD-EN-01 Installation Guide 169

Chapter 8 Configuring Copy and Move Options

8.4 Configuring the Send to Desktop location

Command
The Send to > Desktop location commands lets users download copies of selected
items, including folders and their contents, from Enterprise Connect to a folder on
the desktop. For more information, see section 2.2.6 “Downloading Items to the
Desktop” in OpenText Enterprise Connect - User Getting Started Guide
(NGDCORE200400-UGD).

You can do the following to configure the Send to > Desktop location command:

• Specify which subtypes can be downloaded to the desktop.

• Set a maximum file size for downloads to the desktop.
• Specify when the Send to > Desktop location results file is created.

8.4.1 Specifying Which Subtypes Can Be Sent to the Desktop

The Send To / Desktop Location option is only available for those subtypes that you
make available to users. If users select multiple items and one of those items does
not support the Send to Desktop Location feature, the Send to Desktop Location
option will not be available in the context menu.

By default Folders, Compound Documents, Documents, Projects, Collections,

Favorites, Email, and Email Folders subtypes can be sent to the desktop. The IDs for
these subtypes automatically appear in the Selected list. You can add or remove
subtypes as required. For more information about other subtype values, see section
7.2 “Node Type Number to Name Mappings” in OpenText Content Server Admin
Online Help - Content Server Administration (LLESWBA-H-AGD). For more
information about using the Send to Desktop feature, see OpenText Enterprise
Connect - User Getting Started Guide (NGDCORE200400-UGD).

Note: If users download Compound Emails to their desktops, they will appear
as a single email binary.

8.4.1.1 To Specify Which Subtypes Can Be Sent to the Desktop

To specify which subtypes can be sent to the desktop:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.

2. In the Send To / Desktop Location area, do the following:

• In the Available list, select the subtypes that you want users to be able to
send to their desktop and click Add.
• In the Selected list, select subtypes that you not want users to be able to
send to their desktop and click Remove.

170 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.4. Configuring the Send to Desktop location Command

Note: The following item types are selected by default:

• Collections (298).

• Compound Documents (136).

• Compound Emails (557).

• Documents (144).

• Email (749).

• Email Folders (751).

• Favorites (628).

• Folders (0).

• Projects (202).

Tip: Click Add All to enable users to send all subtypes to their desktop.
Click Remove All to prevent users from sending any subtypes to their
desktop.

3. Click Save Changes.

8.4.2 Setting a Maximum File Size for Downloads to the

Desktop
You can add the following registry setting to specify the maximum combined size, in
megabytes (MB), of items that users can download when they select the Send to >
Desktop location command:

MaximumDownloadToDesktopSize (DWORD)

You must add this setting to the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

By default, this setting is not present in the registry, and the default maximum is 250
MB. You must manually add this setting to the registry to specify a different
maximum. Specifying a value of 0 means that no maximum is set.

Download operations proceed until the maximum is reached. Any subsequent items
over the maximum are not downloaded.

NGDCORE210200-IGD-EN-01 Installation Guide 171

Chapter 8 Configuring Copy and Move Options

8.4.3 Specifying When the Download to Desktop XML Results

File is Created
You can edit the following registry setting to specify options for when the EC_
DownloadToDesktop_Results_<date and time of download>.xml results file is
created when users download documents using the Send to > Desktop location
command:

WriteDownloadToDesktopXmlReports (DWORD)

This setting is stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

You can specify one of the following values for this setting:

-1
The .xml results file is never created.
0
The .xml results file is only created if an error is reported. This is the default.
1
The .xml results file is always created.

For more information about the Download to Desktop results file, see section 2.2.6
“Downloading Items to the Desktop” in OpenText Enterprise Connect - User Getting
Started Guide (NGDCORE200400-UGD).

8.5 Filtering File Types Copied to Enterprise

Connect From the Local File System
By default, users can copy any type of file to a folder in Enterprise Connect from
their local file system. Optionally, you can configure a registry setting called
FilterWildcard to prevent users from copying specific types of items from their
local file system to an Enterprise Connect folder. This can be useful to filter out
unwanted files, such as the thumbs.db file that is automatically created by Windows
in folders that contain images.

This registry setting is not provided by default. You must create the following key in
the registry, and then add the setting to it:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\

FilterFilesAddedToEC (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\FilterFilesAddedToEC (on 64-bit systems)

172 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.6. Mapping Custom Subtypes to File Extensions

In the FilterFilesAddedToEC key, create the FilterWildcard (string) value to

define which file types to exclude. The string must contain a semicolon separated
value for each type that you want to exclude. Use * or ? if you want to specify a
wildcard search. For example, *.db would prevent users from copying files with
the .db extension, and init?.ini would prevent users from copying files such as
init1.ini and init2.ini.

Users do not receive a message to indicate that certain files were not copied. This
setting applies to all copy actions from the local file system to an Enterprise Connect
folder in Explorer and Outlook, including drag and drop.

Note: Users are not notified if the FilterWildcard setting filters items out of
copy or move operations. Only use this setting to filter out files and file types
that will never need to be stored in Content Server.

8.6 Mapping Custom Subtypes to File Extensions

Use this optional setting only if you have created custom subtypes and you want to
map specific file extensions to them.

The mappings that you specify only apply when users drag files to Enterprise
Connect. If you enable this feature, when a user drags an item with a specific file
extension to Enterprise Connect, the custom subtype that you mapped to that file
extension is applied to that item.

For example, assume that you have created a custom subtype with the value of
12345. In the File extensions for other subtypes box, you could specify that any
items with the docx file extension are saved with that custom subtype.

Use the <file extension>=<subtype number>format when specifying the mappings. For
this example, the setting would be docx=12345.

8.6.1 To Map a Custom Subtype to a File Extension

To map a custom subtype to a file extension:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.
2. In the File System Extension area, type the subtype that you want to map in the
File extensions for other subtypes box. Use the <file extension>=<subtype
number> format.

Tips

• For multiple mappings, place each mapping on a separate line.

• Any subtypes that you specify must be able to accept versions.
• If you provide an invalid mapping, it will be ignored.
• By default, the File extensions for other subtypes box is empty.

NGDCORE210200-IGD-EN-01 Installation Guide 173

Chapter 8 Configuring Copy and Move Options

3. Click Save Changes.

8.7 Controlling the Name of Content Server

Shortcuts Created by Dragging
Users can create a Content Server Shortcut to an item in Enterprise Connect by right-
clicking and dragging an item to another location in Enterprise Connect. By default,
the Shortcut is automatically given a name that consists of the prefix Shortcut
followed by the name of the item. The Include “Shortcut” prefix when creating
Content Server shortcuts using drag & drop setting allows you to specify if the
prefix is used. When you clear this check box, the Shortcut name will consist of the
name of the item. This setting only applies to Shortcuts created by dragging items
when working in Windows Explorer. If users have sufficient permissions, they can
rename the Shortcut after they have created it.

8.7.1 To Control the Name of Content Server Shortcuts

Created by Dragging
To control the name of Content Server Shortcuts created by dragging:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Content Server Shortcuts area, do one of the following:

• Select the Include ‘Shortcut’ prefix when creating Content Server shortcuts
using drag & drop check box to use the Shortcut prefix in Shortcut names.
This is the default setting.
• Clear the Include ‘Shortcut’ prefix when creating Content Server shortcuts
using drag & drop check box if you want to omit the Shortcut prefix from
Shortcut names.

3. Click Save Changes.

8.8 Working with Briefcases

A Briefcase is a working folder that Enterprise Connect creates on your file system. It
contains one or more documents or emails that you select from Enterprise Connect.
Briefcases provide a way to download documents from Enterprise Connect, work
with them on a computer that does not have Enterprise Connect installed, and then
return them to the same location in Enterprise Connect. For more information about
using briefcases, see section 2.12 “Working with Briefcases” in OpenText Enterprise
Connect - User Getting Started Guide (NGDCORE200400-UGD).

If OpenText™ Brava!™ is installed on Content Server, users can use Brava! to

annotate documents. The annotations are stored in annotation files that are
associated with the document. You can configure the Briefcase feature to support
downloading annotation files for items that have them. This allows users to view

174 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.8. Working with Briefcases

and edit the annotations when they open the Briefcase item in OpenText™ Brava!™
Desktop.

8.8.1 Adding Annotations to Briefcases

By default, when users create a new Briefcase, only the items they select are added
to the Briefcase. Any annotations for the selected items are not added. You may
prefer this option if your users do not use annotations and you do not want to create
subfolders in the Briefcase.

In cases where your users need to work with both the selected items and any
associated annotations, you can specify that annotations are added to the new
Briefcase. If you choose this option, a folder containing the item and any annotations
it may have is created for each item added to the Briefcase. The folder is created
even if the selected item has no annotations. The folder name is the same as the
name of the selected item.

For more information about working with annotations, see the documentation for
OpenText™ Brava!™.

Note: This check box is only available if the Brava module is installed.

8.8.1.1 To Add Annotations to Briefcases

To add annotations to Briefcases:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Annotations area, do one of the following:

• Select the Include Annotations when creating a Briefcase check box if you
want to include annotations for items that users add to their new Briefcase.
• Clear the Include Annotations when creating a Briefcase check box if you
do not want to include annotations when users create a Briefcase. This is the
default setting.

3. Click Save Changes.

NGDCORE210200-IGD-EN-01 Installation Guide 175

Chapter 8 Configuring Copy and Move Options

8.9 Specifying Types of Containers Available in

Enterprise Connect Save As
You can specify which types of containers users can choose from when they save
documents using the New list, which is available in places such as the Enterprise
Connect Save As dialog box and the Easy Access Pane. By default, Folders, Email
Folders, Projects, Compound Documents, and Business Workspaces are available.
You can remove options from this list or add additional subtypes as required. User
permissions may affect which types of containers users can select. In addition, how
your system is configured affects which containers are available. For example,
although Business Workspaces are available by default, users can only access them if
the appropriate modules have been installed and configured.

8.9.1 To Specify Types of Containers Available in Enterprise

Connect Save As
To specify types of containers available in Enterprise Connect Save As:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the New Container Menu area, make item types available by clicking the
appropriate items in the Available list and then clicking Add. Make item types
unavailable by clicking the appropriate items in the Selected list and clicking
Remove. The following subtypes are available by default:

• Folder (0)
• Compound Document (136)
• Project (202)
• Email Folder (751)
• Business Workspace (848)

Tip: Click Add All to make all items in the Available list available to
users. Click Remove All to make all items unavailable to users.

3. Click Save Changes.

176 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 8.10. Enabling the Drag and Drop Panel

8.10 Enabling the Drag and Drop Panel

If you enable the Show Enterprise Connect View button in the Content Server
web interface, users can click it to open the Drag and Drop panel. This feature is
available for Content Server Classic View and Smart View. The Drag and Drop
panel displays the items in the user’s current location in Content Server. Users can
drag items from Microsoft Outlook, IBM Notes, or Windows Explorer to the panel
and those items are then added to Content Server. Users can also drag items out of
the panel to other locations, access context menu actions that are available for each
item, and reorganize and choose columns.

Important
OpenText recommends that you use this feature as a replacement for
OpenText™ WebDAV drag and drop. If you have WebDAV installed, the
WebDAV functionality will still be available.

You can also specify the level of functionality available in the Drag and Drop panel.
Using the Compact View, users can only navigate the tree structure below the
selected item. In the Windows Explorer view, users can navigate the full Enterprise
Connect tree structure.

Note: The view that you specify will be available to Internet Explorer users
who launch the Enterprise Connect From Here command. It is also available
to users who launch the Drag and Drop panel using the Show Enterprise

Connect View button .

For both the Compact and Windows Explorer views, any rules that you have set for
collecting metadata, saving attachments, and handling conflicts or duplicate names
are applied to items that users add to Content Server.

By default, the Show Enterprise Connect View button is not available. When
enabled, the button is available for all container types except for Content Server
container types that Enterprise Connect considers to be document types, such as
Compound Emails. It is also not available for items that do not support browse
views, such as Search Results.

NGDCORE210200-IGD-EN-01 Installation Guide 177

Chapter 8 Configuring Copy and Move Options

8.10.1 To Enable the Drag and Drop Panel

To enable the Drag and Drop panel:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Advanced Settings link.

2. In the Enterprise Connect View area, select the Enable “ Enterprise Connect
View” in the Content Server browse view check box to make the Drag and
Drop panel available to users. By default, the check box is clear and the Drag
and Drop panel is not available.
3. In the View Type list, click one of the following:

• Click Use compact view to use a basic view.

• Click Use Windows Explorer to use a view with full Windows Explorer
functionality.

4. Click Save Changes.

178 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

Chapter 9
Configuring Offline Options

This chapter describes the offline options that you can configure for Enterprise
Connect:

• Subtypes that can be taken offline.

• Offline mode configurations, including the maximum size of the offline cache
and whether offline mode is enabled.
• Offline search.

9.1 Specifying Which Subtypes Can Be Taken Offline

You must specify which subtypes Enterprise Connect users can take offline. If users
right-click an item of a subtype that you have not made available for offline use, the
Download Offline Version option will not be available. If users select multiple
items and one of the items has been excluded from offline use, the download for
offline use option will not be available in the context menu.

By default Folders, Compound Documents, Documents, Projects, Collections,

Favorites, Email, and Email Folders subtypes can be downloaded for offline use. The
IDs for these subtypes automatically appear in the Selected list. You can add or
remove item types as required. For more information about other item type values,
see section 7.2 “Node Type Number to Name Mappings” in OpenText Content Server
Admin Online Help - Content Server Administration (LLESWBA-H-AGD).

9.1.1 To Specify Which Subtypes Can Be Taken Offline

To specify which subtypes can be taken offline:

1. In the Enterprise Connect Administration section of the Content Server

Administration page, click the Menu Settings link.
2. In the Download Offline area, do the following:

• In the Available list, select the subtypes that you want users to be able to
take offline and click Add.
• In the Selected list, select the subtypes that you not want users to be able to
take offline and click Remove.

Notes

• You cannot download Channels for offline use.

• To enable users to take Compound Emails offline, add subtype 557.
• The following item types are selected by default:

NGDCORE210200-IGD-EN-01 Installation Guide 179

Chapter 9 Configuring Offline Options

– Collections (298).
– Compound Documents (136).
– Documents (144).
– Email (749).
– Email Folders (751).
– Favorites (628).
– Folders (0).
– Projects (202).

Tip: Click Add All to enable users to take all item types offline. Click
Remove All to prevent users from taking any item types offline.
3. Click Save Changes.

9.2 Configuring Offline Mode

You can edit the following registry values to configure offline mode on the
Enterprise Connect client:

MaximumOfflineSize (DWORD)
This setting determines the maximum size, in megabytes (MB), of each user’s
offline document store on the client. If this setting is 0 (the default), users can
download an unlimited amount of offline content. Once the limit is reached,
users cannot download any additional offline documents or folders unless they
make space available by discarding previously downloaded offline documents.
OfflinePromptMode
This setting specifies what happens if Enterprise Connect detects that the
network connection or Content Server is unavailable while a user is working
online. You can set it to one of the following values:
0
If the connection to Content Server is unavailable, Enterprise Connect asks
the user if they want to work offline. If they say yes, Enterprise Connect
switches to offline mode. By default, Enterprise Connect will prompt the
user to switch back to online mode when it detects that the connection to
Content Server is available again. You can use the OnlinePromptMode
setting described in this section to change this default behavior.
1
If the connection to Content Server is unavailable, Enterprise Connect
remains in online mode. Enterprise Connect does not prompt the user to
switch to offline mode or display any message indicating that there is a
connectivity issue.
2
If the connection to Content Server is unavailable, Enterprise Connect
automatically switches to offline mode without prompting the user. By

180 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 9.2. Configuring Offline Mode

default, Enterprise Connect will prompt the user to switch back to online
mode when it detects that the connection to Content Server is available
again. You can use the OnlinePromptMode setting described in this section
to change this default behavior.
3 (default)
If the connection to Content Server is unavailable, Enterprise Connect
remains in online mode and displays a message indicating that the Content
Server repository is unavailable.

OfflineSupportEnabled (DWORD)
If this value is 1 (the default), offline support is enabled.
If this value is 0, offline support is disabled. The user can only work with
Enterprise Connect in online mode, and the following features are unavailable:

• The commands on the Offline submenu and its commands on the Enterprise
Connect menu, including Work Online, Work Offline, My Working
Documents List, and Offline sync.
• The Download Offline Version and Discard Offline Version context menu
commands.
• The Offline column in the List Pane.
• The Offline Synchronization option on the Options dialog box.

Note: You must restart the computer to apply changes to the

OfflineSupportEnabled registry setting.

OfflineSynchAfterSwitchingOnline (DWORD)
If this value is 0 (the default), an offline sync is not performed after a user
switches to online mode. New or edited documents are uploaded to the server
after Enterprise Connect goes online, but the offline content stored on the client
is not updated with the latest content from the online repository.
If this value is 1, an offline sync is performed after a user switches to online
mode. For more information about offline syncs, see section 6.5 “Synchronizing
Online and Offline Content” in OpenText Enterprise Connect - User Getting Started
Guide (NGDCORE200400-UGD).
OnlinePromptMode (DWORD)
You can edit this setting to control what happens when OfflinePromptMode is
set to 0 or 2, and Enterprise Connect detects that the connection to Content
Server is available again after Enterprise Connect has gone offline automatically.
You can set OnlinePromptMode to one of the following values:
0 (default)
Enterprise Connect prompts the user when attempting to go back online as
explained in the description of values 0 and 2 of the OfflinePromptMode
setting.
1
Enterprise Connect goes back online without prompting the user.

NGDCORE210200-IGD-EN-01 Installation Guide 181

Chapter 9 Configuring Offline Options

2
Enterprise Connect remains offline without prompting the user.

Note: This setting is only applicable if OfflinePromptMode is set to 0 or 2.

These settings are stored in the following location in the registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)

Notes

• The OfflineSynchAfterSwitchingOnline setting is stored in the registry in

HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect as well as
in HKEY_LOCAL_MACHINE. The HKEY_CURRENT_USER setting takes precedence
over HKEY_LOCAL_MACHINE. Users can modify the HKEY_CURRENT_USER
setting through the Offline Synchronization > Always Synchronize after
switching online check box in the Enterprise Connect Options dialog box.
• You can create registry settings for Office Editor that determine the location
of the document cache. This cache also stores Enterprise Connect offline
documents. For more information, see “Specifying the Location of the
Document Cache” on page 82.

9.3 Enabling Offline Search

Offline search uses the Windows Search feature to index and search offline
documents. In order to enable offline document searching, the correct Windows
Search components must be installed and enabled on the client. For more
information, see “Client and Integration Requirements” on page 22.

Offline searches are undertaken on the contents of offline documents, as well as on

the standard property fields indexed by Windows Search. Searches do not include
offline folder names. Attachments to emails are also searched. For more information,
see section 6.3.3 “Searching Offline Documents” in OpenText Enterprise Connect - User
Getting Started Guide (NGDCORE200400-UGD).

Any document format that can be indexed and searched on the local file system
using Windows Search can also be searched as an offline document. If Windows
Search does not support a specific document format, you might need to install third-
party add-ins to enable support for it.

The Treat similar words with diacritics as separate words setting in the Windows
Search Advanced Options dialog box controls whether diacritical marks such as
umlauts are considered when words are indexed and searched. For example, if this
setting is enabled, für and fur are considered to be different words. This setting is
not language-specific and applies to all offline documents.

182 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 9.3. Enabling Offline Search

Note: The Office Editor document cache is also used to store Enterprise
Connect offline documents. If you change the location of the document cache
to be a UNC path, indexing and searching of offline documents is not
supported. For more information, see “Specifying the Location of the
Document Cache” on page 82.

NGDCORE210200-IGD-EN-01 Installation Guide 183

Chapter 10
Registry Setting Reference

This chapter lists the client registry settings you can edit for Enterprise Connect
Framework and Office Editor.

Modifying the registry requires local administration permissions on the clients.

OpenText recommends that all changes to registry values be scheduled and
performed by the appropriate system or network administrator using your
organization's approved processes and tools. Individual users must not attempt to
modify the registry manually.

Caution
Errors made when modifying registry values can have a negative impact on
system performance and stability. For this reason, OpenText recommends
that you back up the registry before editing it, and that only qualified
personnel modify the registry in accordance with your organization's
accepted processes.

10.1 Registry Settings for Enterprise Connect

Framework
Most Enterprise Connect registry values are stored on a local-machine basis in the
following registry keys, or in a subkey under these keys:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect (on 32-bit

systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect (on 64-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Desktop\
Connectivity
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\Content Server
Desktop\Connectivity (on 64-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Browser Web
Extension\Applications\\EnterpriseConnect (on 64-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\Content Server
Browser Web Extension\Applications\\EnterpriseConnect (on 64-bit
systems)

Some registry settings are stored on a per-user basis. These settings are stored in the
following registry key, or in a subkey under this key:

HKEY_CURRENT_USER\SOFTWARE\Open Text\Enterprise Connect

NGDCORE210200-IGD-EN-01 Installation Guide 185

Chapter 10 Registry Setting Reference

For the specific location of each setting, consult the section that describes the setting
in detail. The following table provides links to detailed descriptions of each setting.

Note: You must start a new Windows session to apply registry setting changes.
In some cases, you might need to restart the client.

The following list describes the Enterprise Connect registry values you can modify,
and provides a cross-reference to a detailed description of each value.

ActionLeftMouseDragDefault
Specifies the default action when items are dragged to the Easy Access pane
with the left mouse button pressed. The default value is Copy. For more
information, see “Specifying Settings for the Easy Access Pane” on page 137.
ActionLeftMouseDragModifiable
Controls whether a user can modify the Outlook left mouse drag and drop
setting in the Easy Access pane Options dialog box. The default value of 1
means that the user can modify the setting. For more information, see
“Specifying Settings for the Easy Access Pane” on page 137.
AdobeAcrobatMenuLabel
The Enterprise Connect submenu label in Acrobat. Default value is Enterprise
Connect. For more information, see “Modifying Menu and Tree Labels”
on page 61.
AllowAutoAuthentication
Optional plug-in setting that indicates whether a user’s Windows login
credentials are used for authentication when automatic login is enabled for the
plug-in. For more information, see “Editing the Registry to Establish the
Connection” on page 29.
AuthorizationCookieNames
Optional setting that only applies if a third-party Web access management
system is used. If this setting is enabled, users are not required to enter
credentials after clicking Open, Edit, or Enterprise Connect from Here in the
Content Server Web interface. For more information, see “Editing the Registry to
Establish the Connection” on page 29.
DisableBrowserAuthentication
Specifies a list of URLs that Enterprise Connect or Office Editor should not
attempt to authenticate against if redirected to when connecting to Content
Server. For more information, see “Preventing Authentication When Content
Server Connection Attempts are Redirected” on page 45.
DisableLocalSave
If use of the Enterprise Connect Save As dialog box is forced, specifies whether
the Save Locally button is available or not. Default value is 0 (false). For more
information, see “Forcing the Use of the Enterprise Connect Open and Save As
Dialog Boxes” on page 109.

186 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.1. Registry Settings for Enterprise Connect Framework

DontSendEmailBody
Indicates if Enterprise Connect passes on the email body as metadata to be
stored in the Content Server database. Default value is 0 (the email body is
passed on to be stored in the Content Server database). For more information,
see “Enhancing Performance When Emails are Added to Content Server in
Outlook” on page 140.
DontSendEmailCustom
Indicates if Enterprise Connect passes on custom email properties to Content
Server. Default value is 0 (custom email properties are passed on to Content
Server). For more information, see “Enhancing Performance When Emails are
Added to Content Server in Outlook” on page 140.
DontStoreCredentialsLocally
Prevents Enterprise Connect from storing user credentials locally. Default value
is 0 (credentials are stored locally). For more information, see “Editing the
Registry to Prevent Enterprise Connect from Storing Credentials” on page 43.
DragAutoExpandMillisecondsDefault
Specifies how long, in milliseconds, it takes for a folder in the Easy Access Pane
to expand when a user hovers over it while dragging an item. The default value
is 5000 (5 seconds). For more information, see “Specifying Settings for the Easy
Access Pane” on page 137.
DragAutoExpandMillisecondsModifiable
Specifies whether the DragAutoExpandMillisecondsDefault setting can be
overridden or not. If the value is 1 (the default), it can be overridden. For more
information, see “Specifying Settings for the Easy Access Pane” on page 137.
EasyAccessMenu
The label for the Easy Access pane button that is displayed in the Outlook
ribbon. For more information, see “Modifying Language-Specific Labels”
on page 62.
EasyAccessPaneCaption
The label for the Easy Access pane title. For more information, see “Modifying
Language-Specific Labels” on page 62.
EnableDocumentCaching
Optional plug-in setting that indicates documents are stored in the document
cache. For more information, see “Editing the Registry to Establish the
Connection” on page 29.
EnterpriseConnectDisplayName
The Enterprise Connect root node label in the Tree Structure. This value is also
applied to the Enterprise Connect Copy/Move dialog box. Default value is
Enterprise Connect. For more information, see “Modifying Menu and Tree
Labels” on page 61.
ExtendedIntegrationExcludedApplications
If the Extended Integration option is installed, specifies which applications are
not supported for Extended Integration. For more information, see “Specifying
Which Applications Support Extended Integration” on page 112.

NGDCORE210200-IGD-EN-01 Installation Guide 187

Chapter 10 Registry Setting Reference

ExtendedIntegrationSupportedApplications
If the Extended Integration option is installed, specifies which applications
support native Open and Save dialog box integration with Enterprise Connect.
For more information, see “Specifying Which Applications Support Extended
Integration” on page 112.
FilterFilesAddedToEC
Prevents users from copying specific types of items from their local file system
to an Enterprise Connect folder. For more information, see “Filtering File Types
Copied to Enterprise Connect From the Local File System” on page 172.
ForceBrowserAuthentication
Causes Enterprise Connect to display a browser window that enables users to
authenticate separately with Content Server. For more information, see
“Requiring Users to Sign In with a Browser” on page 44.
FolderCacheTimeout
The value, in seconds, that determines how often Enterprise Connect updates its
cache of folder contents in the tree. Default value is 180 (three minutes). For
more information, see “Setting the Folder Cache Timeout Value” on page 76.
ForceEnterpriseConnectOpenDialog
Forces the use of the Enterprise Connect Open dialog box. Default value is 0
(false). For more information, see “Forcing the Use of the Enterprise Connect
Open and Save As Dialog Boxes” on page 109.
ForceEnterpriseConnectSaveAsDialog
Forces the use of the Enterprise Connect Save As dialog box. Default value is 0
(false). For more information, see “Forcing the Use of the Enterprise Connect
Open and Save As Dialog Boxes” on page 109.
HideAttachECDocument
Hides the Attach Item button in Outlook. Default value is 0 (false). For more
information, see “Hiding Options in Outlook” on page 135.
HideCopyAttachments
Hides the Copy Attachments button in Outlook. Default value is 0 (false). For
more information, see “Hiding Options in Outlook” on page 135.
HideCopyMessage
Hides the Copy Message button in Outlook. Default value is 0 (false). For more
information, see “Hiding Options in Outlook” on page 135.
HideCopyMove
Determines if the Enterprise Connect Copy/Move command is available on the
Enterprise Connect menu, and on the email and folder context menus in
Outlook. Default value is 0 (false). For more information, see “Hiding Options in
Outlook” on page 135.
HideLegacyTabInsertActions
Determines if the commands on the Enterprise Connect group on the Home and
Message tabs are also available on the Enterprise Connect tab in Outlook. The
default value of 1 means that these commands are only available on the Home

188 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.1. Registry Settings for Enterprise Connect Framework

and Message tabs. For more information, see “Hiding Options in Outlook”
on page 135.
HideQuickSteps
Hides the Quick Steps feature from Outlook. Default value is 0 (false). For more
information, see “Hiding Options in Outlook” on page 135.
HideSendAndSave
Hides the Send and Save button in Outlook. Default value is 0 (false). For more
information, see “Hiding Options in Outlook” on page 135.
HideSuggested
Hides the Suggested command in Outlook. Default value is 0 (false). For more
information, see “Hiding Options in Outlook” on page 135.
HttpFileTransferTimeout
Specifies how many seconds Enterprise Connect waits for a response to HTTP
requests that are file uploads. Default is 600. For more information, see “Setting
Timeouts for HTTP Requests” on page 51.
HttpRequestTimeout
Specifies how many seconds Enterprise Connect waits for a response to all
HTTP requests that are not file uploads. Default is 300. For more information,
see “Setting Timeouts for HTTP Requests” on page 51.
ListPaneItemLimitForNativeDialogs
This setting restricts the maximum number of items shown in an Enterprise
Connect folder in an Extended Integration Open or Save As dialog box. If this
setting is 1 or greater, Enterprise Connect restricts the maximum number of
items displayed in a folder to the value of the setting. If this setting is 0 or does
not exist (the default), Enterprise Connect places no restrictions on the number
of items shown in a folder. For more information, see “Limiting the Number of
Items Displayed in Extended Integration Open and Save As Dialog Boxes”
on page 114.
Locale
Specifies a language setting for Enterprise Connect different from the system’s
display language setting. For more information, see “Changing the Enterprise
Connect Language Setting” on page 79.
LotusNotesCopyAttachmentsMenuLabel
Specifies a label for the Enterprise Connect copy attachments command in IBM
Notes. For more information, see “Modifying IBM Notes Labels” on page 154.
LotusNotesCopyMoveMenuLabel
Specifies a label for the Enterprise Connect copy/move command in IBM Notes.
For more information, see “Modifying IBM Notes Labels” on page 154.
LotusNotesOpenMenuLabel
Specifies a label for the Enterprise Connect open command in IBM Notes. For
more information, see “Modifying IBM Notes Labels” on page 154.

NGDCORE210200-IGD-EN-01 Installation Guide 189

Chapter 10 Registry Setting Reference

MaximumDownloadToDesktopSize
The maximum allowable combined size, in megabytes (MB), of all items
downloaded in a single Download to Desktop action. The default value of 0
indicates no maximum. For more information, see “Setting a Maximum File Size
for Downloads to the Desktop” on page 171.

MaximumOfflineSize
The maximum size, in megabytes (MB), of the offline document store on the
client. The default value of 0 indicates no maximum. For more information, see
“Configuring Offline Mode” on page 180.

Mimetypes
Registry key that stores mappings between MIME types and file extensions. For
use when items are stored in Content Server without extensions and no
mapping between the MIME type and an extension exists on the client. For more
information, see “Mapping MIME Types to File Extensions” on page 115.

MenuLabel
The Enterprise Connect menu label in Explorer and Outlook. Default value is
Enterprise Connect. For more information, see “Modifying Menu and Tree
Labels” on page 61.

MessageClassFilters
Lists the Outlook message classes of item types that Enterprise Connect does not
attempt to archive if a user moves or copies them to Enterprise Connect. For
more information, see “Specifying Outlook Items for Which Archiving Is Not
Attempted” on page 152.

NavigationFolderContentsListViewOnSelectDefault
Controls whether the Show folder contents in list view on select check box in
the Easy Access pane Options dialog box is selected or cleared. The default
value of 1 means the check box is selected. For more information, see
“Specifying Settings for the Easy Access Pane” on page 137.

NavigationFolderContentsListViewOnSelectModifiable
Controls whether a user can modify the Show folder contents in list view on
select check box in the Easy Access pane Options dialog box. The default value
of 1 means that the user can modify the setting. For more information, see
“Specifying Settings for the Easy Access Pane” on page 137.

NavigationIncludeDocumentsFolderExpansionDefault
Controls whether the Include documents when browsing check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. For more information, see “Specifying Settings
for the Easy Access Pane” on page 137.

NavigationIncludeDocumentsFolderExpansionModifiable
Controls whether a user can modify the Include documents when browsing
check box in the Easy Access pane Options dialog box. The default value of 1
means that the user can modify the check box. For more information, see
“Specifying Settings for the Easy Access Pane” on page 137.

190 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.1. Registry Settings for Enterprise Connect Framework

NavigationIncludeDocumentsSearchResultsDefault
Controls whether the Include documents when searching check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. For more information, see “Specifying Settings
for the Easy Access Pane” on page 137.
NavigationIncludeDocumentsSearchResultsModifiable
Controls whether a user can modify the Include documents when searching
check box in the Easy Access pane Options dialog box. The default value of 1
means that the user can modify the check box. For more information, see
“Specifying Settings for the Easy Access Pane” on page 137.
OfficeRibbonKeyTip
The KeyTip for the Enterprise Connect tab in the Office ribbon. Default value is
C. For more information, see “Modifying Menu and Tree Labels” on page 61.

OfficeRibbonLabel
The Enterprise Connect tab label in the Office ribbon. Default value is
Enterprise Connect. For more information, see “Modifying Menu and Tree
Labels” on page 61 .
OfflinePromptMode
Indicates what happens if Enterprise Connect detects that the network
connection or the connection to Content Server is not working. Default value is 1
(true). For more information, see “Configuring Offline Mode” on page 180.
OfflineSupportEnabled
Indicates if Enterprise Connect supports offline mode on the client or not.
Default value is 1 (true). For more information, see “Configuring Offline Mode”
on page 180.
OfflineSynchAfterSwitchingOnline
Specifies whether an offline sync is performed after a user switches to online
mode. Default value is 0 (false). For more information, see “Configuring Offline
Mode” on page 180.
OnlinePromptMode
Indicates what happens when Enterprise Connect attempts to go back online
after the network connection is restored. You must add this setting to the
registry to be able to use it. For more information, see “Configuring Offline
Mode” on page 180.
OutlookEasyAccessPaneVisibleDefault
Controls whether the Easy Access pane is open by default when Outlook is first
started after Enterprise Connect is installed. The default value of 0 means that
the Easy Access pane is not open. For more information, see “Specifying Settings
for the Easy Access Pane” on page 137.
OutlookEasyAccessPaneVisibleModifiable
Controls whether the Easy Access Pane menu appears on the Enterprise
Connect tab in Outlook. The default value of 1 means that the menu is visible
and users can choose to display or hide the Easy Access pane and view and

NGDCORE210200-IGD-EN-01 Installation Guide 191

Chapter 10 Registry Setting Reference

modify options for the pane. For more information, see “Specifying Settings for
the Easy Access Pane” on page 137.
PluginIdentifier
Specifies the unique ID of the Content Server plug-in that supports Email
Archiving. For more information, see “Specifying the Content Server Plug-in for
Email Archiving” on page 148.
PreventDragAndDrop
Determines if users are prevented from copying or moving Outlook items and
folders into Enterprise Connect. Default value is 0 (false). For more information,
see “Hiding Options in Outlook” on page 135.
PreviewState
Determines if the Reading Pane is hidden or displayed by default when
Enterprise Connect is installed. Default value is 0 (the Reading Pane is not
displayed). For more information, see “Setting the Default Reading Pane
Display” on page 67.
RetrieveEmailForStub
Specifies how Enterprise Connect moves or copies email stubs into Content
Server. The default value of 1 means that a copy of the full email is downloaded
to the Enterprise Connect client, and the email is then uploaded to the specified
location in Content Server. For more information, see “Configuring How
Enterprise Connect Moves or Copies Email Stubs into Content Server”
on page 150.
ShowOnlyContentInPreview
Specifies whether the Reading Pane displays tabs for documents. For more
information, see “Displaying Tabs in the Reading Pane” on page 68.
StartupAutoNavigateToLastViewDefault
Controls whether the Auto expand to last tree view check box in the Easy
Access pane Options dialog box is selected or cleared. The default value of 1
means the check box is selected. For more information, see “Specifying Settings
for the Easy Access Pane” on page 137.
StartupAutoNavigateToLastViewModifiable
Controls whether a user can modify the Auto expand to last tree view check box
in the Easy Access pane Options dialog box. The default value of 1 means that
the user can modify the check box. For more information, see “Specifying
Settings for the Easy Access Pane” on page 137.
TreePaneItemLimit
Limits the number of folders that can appear beneath a folder in the Tree
Structure. Default value is 0 (no limit). For more information, see “Limiting the
Number of Folders Displayed in the Tree Structure” on page 77.
TrustedDomains
Specifies a list of one or more fully-qualified domain names to be automatically
verified, on a per-application basis, when a user performs an action that involves
the Content Server browser extension. For more information, see “Configuring
Domain Verification for Browser Extensions” on page 56.

192 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.1. Registry Settings for Enterprise Connect Framework

TrustedDomainsPromptBehavior
Determines what happens if an application is unable to verify a domain name
when a user performs an action that involves the Content Server browser
extension. For more information, see “Configuring Domain Verification for
Browser Extensions” on page 56.
UseNativeCertificateAuthentication
Optional plug-in setting that only applies if you are using SSL client certificates
and the authentication process for your certificates fails in Enterprise Connect
but succeeds in Internet Explorer. You can use this setting to cause the native
operating system processes to manage certificate handling rather than
Enterprise Connect. For more information, see “Editing the Registry to Establish
the Connection” on page 29.
UseNativeFolderIcons
Specifies if Enterprise Connect displays Content Server icons or native Outlook
icons in the Outlook Tree Structure. For more information, see “Configuring
Outlook to Use Native Folder Icons” on page 137.
UseOutlookToPreviewDocuments
Specifies if the Enterprise Connect Viewer or the Outlook viewer is used to
preview items in the Reading Pane in Outlook. Default value is 0 (the Enterprise
Connect Viewer is used). For more information, see “Using the Outlook Viewer
Instead of the Enterprise Connect Viewer” on page 134.
VisibilityOnStartupDefault (DWORD)
Controls the state of the Easy Access pane when Outlook starts. The default
PreviousState value means that the Easy Access pane is open or closed
depending on its state in the previous Outlook session. For more information,
see “Specifying Settings for the Easy Access Pane” on page 137.
VisibilityOnStartupModifiable (DWORD)
Controls whether a user can modify the Show Easy Access Pane on startup box
in the Easy Access pane Options dialog box. The default value of 1 means that
the user can modify the box. For more information, see “Specifying Settings for
the Easy Access Pane” on page 137.
WriteDownloadToDesktopXmlReports
Specifies options for when the EC_DownloadToDesktop_Results_<date and
time of download>.xml results file is created when users download documents
using the Download to Desktop command. Default is 0 (the file is only created
if an error is reported). For more information, see “Specifying When the
Download to Desktop XML Results File is Created” on page 172.

Note: You can also modify the DisplayName and BaseHREF registry values for
individual plug-ins. For more information, see “Editing the Registry to
Establish the Connection” on page 29.

The following registry settings in HKEY_LOCAL_MACHINE are for the internal use of
Enterprise Connect only, and must not be manually edited:

• AdobeEnabled

NGDCORE210200-IGD-EN-01 Installation Guide 193

Chapter 10 Registry Setting Reference

• Outlook\AutoSetOutlookAddinPolicy
• InstallPath
• All keys and settings in the Logging key

10.2 Registry Settings for Office Editor

Office Editor registry values are stored in one of the following registry keys:

• HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Preferences
• HKEY_CURRENT_USER\SOFTWARE\Open Text\OTEdit\Config
• HKEY_LOCAL_MACHINE\SOFTWARE\OTEdit\Preferences (on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OTEdit\Preferences (on 64-bit
systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Desktop\
Connectivity
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\Content Server
Desktop\Connectivity (on 64-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\OpenText\Content Server Browser Web
Extension\Applications\OfficeEditor (on 64-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\Content Server
Browser Web Extension\Applications\OfficeEditor (on 64-bit systems)

For the specific location of each setting, consult the section that describes the setting
in detail. The following table provides links to detailed descriptions of each setting.

Note: You must start a new Windows session to apply registry setting changes.
In some cases, you might need to restart the client.

The following list describes the Office Editor registry values you can modify, and
provides a cross-reference to a detailed description of each value.

BulkEditConfirmationMin
Specifies the minimum number of items that the user must select for editing or
opening as read-only in the My Working Documents List dialog box before a
warning prompt is displayed. For more information, see “Configuring the My
Working Documents List Dialog Box” on page 86.
BulkEditMaxLimit
Specifies the maximum number of items that a user can select at once for editing
in the My Working Documents List dialog box. For more information, see
“Configuring the My Working Documents List Dialog Box” on page 86.
CacheLocation
Specifies either an absolute or partial directory for the location of the document
cache. For more information, see “Specifying the Location of the Document
Cache” on page 82.

194 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.2. Registry Settings for Office Editor

CacheRootCSIDL
Specifies the base directory for the document cache. This must be a numeric
value corresponding to a CSIDL constant. For more information, see “Specifying
the Location of the Document Cache” on page 82.
DefaultFinalizeOnClose
If UploadDocumentSavesImmediately is set to 1, determines if documents with
pending changes are uploaded to the server when closed. For more information,
see “Configuring the Upload Mode for Edited Documents” on page 105.
DisableDesktopIconCreation
Specifies whether a shortcut called OpenText Office Editor is created on each
user’s desktop when Office Editor is run for the first time after being installed or
upgraded. Default value is 1 (true). For more information, see “Disable the
creation of the Office Editor desktop shortcut” on page 99.
DisableLocationLink
Specifies whether the Location column in the My Working Documents List
dialog box contains active links to Content Server. For more information, see
“Configuring the My Working Documents List Dialog Box” on page 86.
DocumentsMRUMaxSize
Specifies the maximum number of recently-edited items that can appear in the
My Working Documents List dialog box and in the document cache. For more
information, see “Configuring the My Working Documents List Dialog Box”
on page 86.
DontStoreCredentialsLocally
Prevents Office Editor from storing user credentials locally. Default value is 1
(credentials are not stored locally). For more information, see “Enabling Office
Editor to Store Credentials” on page 97.
EditOnDoubleClick
Specifies if double-clicking a document in the My Working Documents List
dialog box opens it for editing or as read-only. For more information, see
“Configuring Double-click Behavior in the My Working Documents List Dialog
Box” on page 98.
EditorBehavior
Registry key that stores list of applications whose associated documents are
opened as read-only. For more information, see “Removing the Ability to Edit
Specific File Types” on page 91.
EnableExcelQuerylinkRewriting
Specifies if Office Editor performs link rewriting for links between Excel
workbooks created using the Get Data > From File > From Workbook command
in Excel 2016 and later. For more information, see “Configuring Link Rewriting”
on page 104.
EnableLinkRewritingForLocalDocuments
Specifies if Office Editor performs link rewriting during document edits and
uploads. For more information, see “Configuring Link Rewriting” on page 104.

NGDCORE210200-IGD-EN-01 Installation Guide 195

Chapter 10 Registry Setting Reference

EnableMultiSessionDocumentCache
Specifies if the document cache supports multiple concurrent sessions. For more
information, see “Configuring the Document Cache Location to Support Citrix
Session Pools” on page 84.
FinalizeOnCloseModifiable
If UploadDocumentSavesImmediately is set to 1, determines whether the
Finalize on Close check box and the Document Options group are displayed on
the Office ribbon. For more information, see “Configuring the Upload Mode for
Edited Documents” on page 105.
ForceBrowserAuthentication
Causes Office Editor to display a browser window that enables users to
authenticate separately with Content Server. For more information, see
“Requiring Users to Sign In with a Browser” on page 44.
IgnoredProcesses
Specifies a comma-separated list of processes that Office Editor will ignore when
determining if a document has been modified and needs to be synced. For more
information, see “Specifying Processes To Ignore When Syncing Documents”
on page 90.
HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\OTEdit\Preferences (32–bit)

Locale
Specifies a language setting for Office Editor different from the system’s display
language setting. For more information, see “Changing the Office Editor
Language Setting” on page 80.
LockableApplications
Specifies whether applications support or do not support locking. For more
information, see “Specifying Locking and Non-locking Applications and File
Types” on page 93.
LockableTypes
Specifies whether file types are non-lockable or lockable. For more information,
see “Specifying Locking and Non-locking Applications and File Types”
on page 93.
LogFileLocation
Specifies the location of the log file on the client system. For more information,
see “Configuring Office Editor Logging” on page 87.
LogFileName
Specifies the name of the log file. For more information, see “Configuring Office
Editor Logging” on page 87.
LogLevel
Indicates the level of events that are included in the log. For more information,
see “Configuring Office Editor Logging” on page 87.
MaximumLogSize
Specifies maximum size of the log file, in bytes. For more information, see
“Configuring Office Editor Logging” on page 87.

196 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.3. Configuring Plug-in Definitions

MultiSessionDocumentCacheScanInterval
If is enabled, specifies how often Office Editor merges inactive My Working
Documents List collections from previous sessions with the currently active
session. For more information, see “Configuring the Document Cache Location
to Support Citrix Session Pools” on page 84.
NotificationBalloonInterval
Specifies how frequently, in minutes, the Documents Need Attention
notification is displayed in the notification area. The default value of 60 means
that the message is displayed once every 60 minutes. For more information, see
“Specifying the Frequency of the Notification Message” on page 88.
ShowFilterComboBox
Specifies whether the My Working Documents List dialog box displays a filter
list box that allows users to show only pending documents, recently edited
documents, or documents that are downloaded offline. Default value is 0 (false).
For more information, see “Configuring the My Working Documents List Dialog
Box” on page 86.
TrustedDomains
Specifies a list of one or more fully-qualified domain names to be automatically
verified, on a per-application basis, when a user performs an action that involves
the Content Server browser extension. For more information, see “Configuring
Domain Verification for Browser Extensions” on page 56.
TrustedDomainsPromptBehavior
Determines what happens if an application is unable to verify a domain name
when a user performs an action that involves the Content Server browser
extension. For more information, see “Configuring Domain Verification for
Browser Extensions” on page 56.
UploadDocumentSavesImmediately
Specifies the default upload mode for documents that users edit through Office
Editor or Enterprise Connect. Default value is 0 (pending document changes are
not immediately uploaded to the server). For more information, see
“Configuring the Upload Mode for Edited Documents” on page 105.

10.3 Configuring Plug-in Definitions

You can modify the registry to connect Enterprise Connect to additional plug-ins
that do not require client-side installations. To do this, you must create a new
registry key in the following location:

• HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\Solutions

(on 32-bit systems)
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise
Connect\Solutions (on 64-bit systems)

NGDCORE210200-IGD-EN-01 Installation Guide 197

Chapter 10 Registry Setting Reference

Caution
Errors made when modifying registry values can have a negative impact on
system performance and stability. For this reason, OpenText recommends
that the registry be backed up before it is edited, and that only qualified
personnel modify the registry in accordance with your organization's
accepted processes.

The name of this key represents the plug-in's unique ID. You can use any unique
alphanumeric string. Do not use other characters such as spaces or punctuation
characters, including question marks (?) or backslashes (\). Use the same name on
all clients.

Note: OpenText recommends using lowercase for the Unique ID.

You must also create the following registry values beneath the plug-in's unique ID
key:

BaseHREF (String)
The URL to the server component of the plug-in. For example: http://
contentserver/otcs/livelink.exe?func=ngd.ucroot

DisplayName (String)
The label that appears for the plug-in in the following locations:

• Root node in Tree Structure.

• Repository search command on the Enterprise Connect menu in Outlook
and Explorer.
• Help command that appears on the Enterprise Connect Help submenu in
Outlook and Explorer.

AllowAutoAuthentication (DWORD)
A setting that indicates whether a user’s Windows login credentials are used for
authentication when automatic login is enabled for the plug-in, for example by
using Windows Integrated Authentication (IWA).
If the value of the setting is 1, the Windows login credentials are used. If the
credentials do not succeed, the user is prompted to manually enter credentials.
If the value of this setting is 0, the user is prompted to manually enter
credentials the first time the user accesses the plug-in. Enterprise Connect then
stores the credentials for use in future sessions.
If this setting is missing, the default value of 1 is used.
This setting only applies if the plug-in is configured to support automatic login
using Windows login credentials.
IsHidden (DWORD)
An internal value that should always be set to the following: 0

198 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 10.3. Configuring Plug-in Definitions

ProgID (String)
An internal value that should always be set to the following: OpenText.
EnterpriseConnect.XmlPlugin

You can modify the BaseHREF and DisplayName values for existing plug-ins.

You can also use the Manage Plug-ins command on the Enterprise Connect menu
in Outlook or Explorer to add or edit the Unique ID registry key, along with the
associated DisplayName and BaseHREF registry values. Plug-in values created in this
way are stored in the registry in HKEY_CURRENT_USER and only apply to the user
who creates them. If a plug-in stored in HKEY_LOCAL_MACHINE uses the same
unique ID, it takes precedence over a plug-in defined through Manage Plug-ins. For
more information about the Manage Plug-ins command, see OpenText Enterprise
Connect - User Getting Started Guide (NGDCORE200400-UGD).

If you remove the Framework, the key and values that you created are removed
from the registry.

NGDCORE210200-IGD-EN-01 Installation Guide 199

Chapter 11
Troubleshooting

This chapter describes how to view Enterprise Connect log files, and suggests
resolutions for some possible issues.

11.1 Viewing the Log Files

Enterprise Connect offers a logging functionality that enables you to gather
information about issues that you might encounter with components of the client.
All outputs for each specified component are saved to a log file in a location that you
define using the Options command on the Enterprise Connect menu in Outlook or
Explorer. By default, the log level of each component is set to Error, and logging is
disabled. If logging is enabled, by default the log file is stored in the user's temp
folder, which for instance on Windows 7 is the Users\<user name>\AppData\Local
\Temp directory. For more information about using the logging function, see
OpenText Enterprise Connect - User Getting Started Guide (NGDCORE200400-UGD).

In addition, each time a user starts Outlook, Explorer, or an Office application such
as Word, Enterprise Connect automatically creates a file called startup.log in the
Documents and Settings\<current user>\Application Data\OpenText\
Enterprise Connect folder. This log file stores messages related to the operation of
Enterprise Connect, from startup until the user first expands the root node of the
Tree Structure.

To set log file options:

1. On the Enterprise Connect menu or tab in Outlook or Explorer, click Options.

2. In the Category list, click Advanced Settings.

3. Click Logging Options.

4. Select the Log Enabled check box.

5. Perform one or more of the actions in the following table, and then click Apply.

NGDCORE210200-IGD-EN-01 Installation Guide 201

Chapter 11 Troubleshooting

To Do this
Set a logging level for all components Click one of the following options in the
Apply to All list:

None
No log file is generated. This is the
default setting.
Error
Writes errors to the log file.
Warning
Writes errors and warnings to the log
file.
Information
Writes errors, warnings, and
informational messages to the log file.
Debug
Writes a detailed report of program
activity to the log file. Select this
option only if instructed to by your
administrator.

Specify a different log level for an Click the appropriate setting in the Log
individual component Level list next to the Component Name.
Increase the legibility of the log Select the Use Indentation in Log File
check box.

Specify a location for the log file Next to File Location, click Browse .
By default, the log is stored in the
temporary folder specified for your user
account, as represented by the %TEMP%
user environment variable.
Change the default log file name Type a different name in the File Name
box.
By default, the file name includes the
name of the process that generates the log,
as represented by the %PNAME% variable.

202 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 11.2. Enabling the Outlook Add-in

11.2 Enabling the Outlook Add-in

If Outlook closes unexpectedly, the next time Outlook starts it might prompt the
user to disable the Enterprise Connect add-in. The user should always enable the
add-in to ensure that Enterprise Connect remains available.

If the add-in is disabled, it must be re-enabled again from within Outlook. You can
do this by enabling enterprise connect (ucmsoaddin.dll or ucmsoaddin64.dll) on
the Disabled Items dialog box, which you can access by clicking File > Options >
Add-Ins, and then clicking Disabled Items in the Manage list.

11.3 Clearing the Client Cache

In some circumstances, you might need to clear the cache on the client systems. For
example, if you change the Content Server URL, you also need to clear the cache to
ensure the new server connection functions properly. You can clear the cache by
clicking the Reset Now button, which is available by clicking Advanced on the
Enterprise Connect Options dialog box in Outlook or Explorer. Clicking Reset Now
clears the contents of the Documents and Settings\<user name>\Application
Data\OpenText\Enterprise Connect folder, and removes the following items and
settings from the client:

• The user's search history and saved searches.

• Customized Reading Pane display options for specific folders.
• Customized column settings for specific folders.
• Stored plug-in credentials, such as Content Server user names and passwords.

After clearing the cache, you must begin a new Windows session to apply the
change.

To reset Enterprise Connect:

1. On the Enterprise Connect menu or tab in Outlook or Explorer, click Options.

2. In the Category list, click Advanced Settings.

3. Click Reset Now.

4. In the confirmation message, click Yes.

NGDCORE210200-IGD-EN-01 Installation Guide 203

Chapter 11 Troubleshooting

11.4 Resolving Content Server Connection Issues

If Enterprise Connect is unable to connect to Content Server, try the following:

• Verify that all registry values are correctly specified on the client system, as
described in “Connecting Enterprise Connect to Content Server” on page 29. In
particular, ensure that the URL is in the following format, with the ?func=ngd.
ucroot request handler at the end:
<http or https>://<server name>/<service name>/<livelink.exe or
llisapi.dll>?func=ngd.ucroot
• In the URL, specify the server name in fully-qualified format, for example
myserver.company.com.

• Verify that it is possible to use Internet Explorer to connect to Content Server

from the client. If Content Server is configured to use SSL, you might need to use
the browser to import the site certificate before you can connect using Enterprise
Connect.

11.5 Resolving Issues with Saving Office Documents

to Content Server
If a user edits a Content Server document in Office, and is subsequently unable to
save the updated document back to Content Server, in Content Server
Administration > Security Parameters > Cookie Authentication Information, try
changing the expiry setting for authentication cookies to Never Expire from the
default value of 30 minutes after last request.

11.6 Displaying the Enterprise Connect Menu in

Windows Explorer
You might need to enable the menu bar in order to see the Enterprise Connect menu
in Explorer. To enable the menu bar, do the following:

Windows 7
Click the Desktop folder, and then click Organize > Layout > Menu bar. You
can also access the Enterprise Connect menu commands by right-clicking the
Enterprise Connect folder in the Tree Structure.
Windows 8, Windows 8.1, and Windows 10
Click the Desktop folder, click the View tab, and then click Options > Change
folder and search options > View. Select the Always show menus check box,
and click OK.

204 OpenText™ Enterprise Connect and OpenText™ Office Editor NGDCORE210200-IGD-EN-01

 11.7. Enabling Macros in the Office Startup Folder

11.7 Enabling Macros in the Office Startup Folder

If macros stored in the Office Startup folder do not run properly, change the value
of the following registry entry from 0 to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Open Text\Enterprise Connect\

EnableMacroLaunchOnOfficeDocumentOpen (on 32-bit systems)

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise Connect\

EnableMacroLaunchOnOfficeDocumentOpen (on 64-bit systems)

NGDCORE210200-IGD-EN-01 Installation Guide 205