Data Classification Suite

for Windows (On-premises)

5.1
Deployment Guide
Copyright Terms and Conditions

Copyright © Fortra, LLC and its group of companies. All trademarks and registered trademarks are the property of their respective
owners.
The content in this document is protected by the Copyright Laws of the United States of America and other countries worldwide.
The unauthorized use and/or duplication of this material without express and written permission from Fortra is strictly prohibited.
Excerpts and links may be used, provided that full and clear credit is given to Fortra with appropriate and specific direction to the
original content.
202409191029
Table of Contents

About this guide 6

Before you start 7

Prerequisites for the Data Classification Suite 8

About the Application Prerequisite Checker 11

Items validated by the Application Prerequisite Checker 11

Prerequisite Checker error dialog 12

Disable the Application Prerequisite Checker using an install property 12

Run the Application Prerequisite Checker outside of the Data Classification Suite
installer 12

Prerequisite Checker Logs 13

Deploy the TCPG Configuration file 14

Use the CONFIGURATIONFILE to synchronize to a TCPG location 15

Use the CONFIGLOCATION install property to provide a TCPG file during installation16

Manually create a registry key to set up synchronization to a TCPG location 16

Install DCS for Windows 18

Install DCS for Windows using the EXE file in a command line script 19

Install DCS using the MSI files 27

Install DCS for Windows on a single client machine 37

Upgrade DCS for Windows 38

About Titus Enterprise Services 42

Titus Client Services 42

Service Protocol and Default Port Numbers 42

Deployment Guide www.fortra.com page: 3

Table of Contents

Stop and start the Titus Service on the client machine 42

Set up client machines to forward Events to the DCS Analytics Collector 44

Use regedit to manually set the location of the DCS Analytics Collector machine 44

Verify the Administration Console ID 46

Expected behavior when using the Administration Console ID feature 46

About the Classification Selector 48

Classification selector overview 49

Ribbon Group 52

About the Main Ribbon group 52

About One Click Classification Ribbon group 52

About the Options Ribbon group 52

Favorites 54

Undoing Actions 56

Check Policies 57

Apply Portion Marking 58

Apply Portion Marking to Microsoft PowerPoint documents 60

Use Redaction in Microsoft Outlook 61

Determine if a Signed Trusted Label has already been applied 63

Apply Signed Trusted Labels 64

Prevent Save and Send during a service failure 65

Prevent Microsoft Outlook from sending emails 65

Logging information 66

Enable Windows Installer logging 66

Deployment Guide www.fortra.com page: 4

 Table of Contents

View log files for a Client application 66

Enter an annotation in a Client application log file 67

Debug Log locations on client machines 67

Contacting Fortra 69

Deployment Guide www.fortra.com page: 5

 About this guide /

About this guide

This guide is for Administrators who are deploying Data Classification software to users in
an organization.

It describes:

l how to install the Data Classification Suite

l the Titus Enterprise Services
l logging information
l how to verify that the Configuration consumed on the client machine, was created by
a trusted source.

Deployment Guide www.fortra.com page: 6

 Before you start /

Before you start

Before you start using DCS for Windows, ensure you have a Configuration that has been
published to your environment. If you do not have a Configuration, contact your
Administrator.

If you are upgrading DCS for Windows from a previous version, see Upgrade DCS for
Windows on page 38.

Deployment Guide www.fortra.com page: 7

 Prerequisites for the Data Classification Suite /

Prerequisites for the Data

Classification Suite
This section describes the supported software environments at the time of the product
release.

The minimum requirements for DCS for Windows are the same as the minimum
requirements for your operating system on which DCS for Windows is installed. Refer to the
Microsoft web site for those requirements.

NOTE: DCS for Windows supports issues related only to products that are currently
supported by Microsoft. If any issues related to unsupported Microsoft products are
found, DCS for Windows may not be able to address them. You might have to upgrade
to the latest supported Microsoft product and the latest DCS for Windows release.

TIP: A
Titus Client Application Prerequisite Checker is included as part of the installation
package to ensure that the prerequisites are in place and enabled on client machines.
For more information, see About the Application Prerequisite Checker on page 11.

Operating l Windows 10 (64-bit)

System
l Windows 11
Disk space 500 MB minimum
Microsoft Visual If you do not have Visual C++ installed, DCS will install Visual C++ 2017.
C++
Redistributable NOTE:
A Microsoft prerequisite in the Data Classification Suite installer may cause machines
to unexpectedly restart. This is caused by the Microsoft Visual Studio C++ 2017
redistributable. Windows 10 systems that have not previously installed this
redistributable may be affected. This issue has been reported to Microsoft, and they
are aware that the Microsoft Visual Studio C++ 2017 redistributable is not respecting
MSI reboot flags, causing machines to unexpectedly restart. To avoid unexpected
reboots on end user systems, Titus recommends that the Microsoft Visual Studio C++
2017 redistributable is deployed prior to the installation of Data Classification Suite.

Active Directory Data Classification Suite for Windows is supported on Active Directory on-premise only.
Active Directory on Azure is not supported.
Microsoft .NET .NET Framework V4.8 Redistributable Package or later. To download, go to the Microsoft
Framework web site.

Deployment Guide www.fortra.com page: 8

 Prerequisites for the Data Classification Suite /

Digital Titus signs its code to ensure the integrity of its software products. Code signing
Certificate certificates implement an integrity check that requires validation to a signing authority. In
closed environments, where there is no internet access, it is necessary to include these
root signing authority certificates and their corresponding revocation lists on each client
machine. Below is a list of the required certificates and revocation lists.

NOTE: The URLs below were valid at the time of publishing. They are maintained by the
Certificate Authority and may be changed without notice.

The following certificate authorities are used. Click their names to get the required files.

l DigiCert SHA2 Assured ID Code Signing CA

l DigiCert Assured ID Root CA

NOTE: All DigiCert's CA certificates are available here.

Microsoft The following prerequisites are required for Fortra Data Classification for Microsoft
Outlook (DCS Outlook only.
for Outlook
only)
NOTE: The installation will fail if a version of Microsoft Outlook is not found.

l Microsoft Outlook 2016 (32-bit and 64-bit)

l Microsoft Outlook 2019 (32-bit and 64-bit)
l Microsoft Outlook 2021 (64-bit)
l Microsoft Outlook from Microsoft 365 Enterprise

NOTE:
l Microsoft Office 2021 introduced a new user interface called Simplified
Ribbon in Outlook and is set to be the Default. In this view, COM Add-ins are
not visible. We recommend you use the Classic Ribbon View on a client for
full functionality. Contact Support for more information.
l Microsoft Office 2016 64-bit and Microsoft Office 2019 64-bit are supported
but have not been tested.

Email Server Microsoft Exchange

(DCS for
Outlook)

Deployment Guide www.fortra.com page: 9

 Prerequisites for the Data Classification Suite /

Microsoft Office The following prerequisites are required for Fortra Data Classification for Microsoft Office
only.
(DCS for Office
l Microsoft Office 2016 (32-bit and 64-bit)
l Microsoft Office 2019 (32-bit and 64-bit)
l Microsoft Office 2021 (64-bit)
l Microsoft Office from Microsoft 365 Enterprise

NOTE:
l If you are using Microsoft Office 365, OnSave Policies for Data Classification
for Office run every time an “Auto-Save” sync occurs. We recommend
minimizing or eliminating your Policies for that Event.
l There are additional Microsoft .NET Framework and Primary InterOp
Assembly requirements. If these components are not installed, the DCS for
Windows software will not appear when the user launches the Microsoft
Office application.

Supported The Upload button in the Ribbon Group can be used to upload and apply Policies to the
Cloud Storage following cloud storage solutions:
Providers
l Dropbox for Business
l Box Starter
l Box Business
l Box Enterprise

NOTE: DCS for Office and DCS for Desktop can work with any Cloud storage services
which integrate with Windows as a mapped folder. Box Starter and Box Business are
supported but not tested. If you encounter any issues, contact Support.

TCPG See Deploy the TCPG Configuration file

Configuration
file

Deployment Guide www.fortra.com page: 10

 About the Application Prerequisite Checker / Items validated by the Application Prerequisite Checker

About the Application Prerequisite

Checker
The Application Prerequisite Checker ensures that the prerequisites for the Data
Classification Suite for Windows are in place and enabled on client machines.

An information dialog appears when one of the prerequisites for the Data Classification
Suite for Windows is missing or fails to start. The Prerequisite Checker also generates an
MSI log file containing the results.

When performing a client install using the TitusClassificationSetup.exe file the Application
Prerequisite Checker is run automatically. When using a software distribution tool, the
TITUS_PEP_PrerequisiteChecker.msi file must be run according to the order listed in Install
DCS using the MSI files on page 27.

You can run the TITUS_PEP_PrerequisiteChecker.msi file before installing Titus software to
ensure the prerequisites are all in place.

Before running Application Prerequisite Checker:

l review Prerequisites for the Data Classification Suite on page 8 in this document
l ensure your %temp% folder does not contain any Titus logs:
C:\Users\user.name\AppData\Local\Temp\*.log and C:\ProgramData\TITUS\*.log

Items validated by the Application Prerequisite

Checker
The following prerequisites are validated for the Data Classification Suite for Windows:

1. Checks system information including Windows version, bitness, etc.

2. Verifies that the PREREQ_SKIP property was not used; if used, stops checking and
creates a log entry
3. Checks that the .NET Framework version is equal or greater to 4.8
4. Checks if a Windows update is running; if so, the check fails
5. Checks for a pending system restart (either due to a Windows update or because
another installer has set the restart flag)

Deployment Guide www.fortra.com page: 11

 About the Application Prerequisite Checker / Prerequisite Checker error dialog

6. Checks that the user running the installer can create a Registry Key ‘TestKey’ and
write a sub key ‘test’, with a value of ‘test’; that the value of that sub key can be read;
and that the Registry Key ‘TestKey’ can be deleted at the following registry areas:
HKLM\SOFTWARE\Policies and HKLM\SOFTWARE

If any of these checks fail, the Prerequisite Checker displays a dialog and/or writes to the
MSI log file located in %temp%. For example:

C:\Users\user.name\AppData\Local\Temp\Titus_Classification_20160713113543_000_
PrerequisiteCheckerInstall.log

Prerequisite Checker error dialog

The following is an example of an error dialog that appears when one of the prerequisites
for Data Classification Suite is missing or fails to start.

Disable the Application Prerequisite Checker using an

install property
We recommend using the Prerequisite Checker to identify potential issues prior to deploying
the Data Classification Suite. It can, however, be disabled.

To disable the Prerequisite Checker, run the MSI.

TITUSClassificationSetup.exe PREREQ_SKIP=yes

Run the Application Prerequisite Checker outside of

the Data Classification Suite installer
The Prerequisite Checker can run outside the Data Classification Suite installer using the
following elevated command prompt:

Deployment Guide www.fortra.com page: 12

 About the Application Prerequisite Checker / Prerequisite Checker Logs

Msiexec.exe /I TITUS_PEP_PrerequisiteChecker.msi

A log file is created in %temp%, for example:

C:\Users\<user>\AppData\Local\Temp\<MSIb01a0.LOG>

If the prerequisite check is successful, install the Prerequisite Checker before installing the
Data Classification Suite using the following elevated command prompt:

Msiexec.exe /x TITUS_PEP_PrerequisiteChecker.msi

Prerequisite Checker Logs

For more information about the Prerequisite Checker results, view the MSI log file in the
%temp% folder, for example:

C:\Users\user.name\AppData\Local\Temp\Titus_Classification_20160713113543_000_
PrerequisiteCheckerInstall.log

Log sample - PREREQ_SKIP property set to ‘yes’

The following sample log is from a prerequisite check performed when an Install Property
was used to skip the process. The prerequisite check ended.

Titus Prerequisite Checker: Prerequisite Scan Start

Titus Prerequisite Checker: OS: Windows 10, Edition: Enterprise, Service pack: None, Version:
10.0.10240.0, Product type: 1
Titus Prerequisite Checker: The OS has bitness of: AMD64
Titus Prerequisite Checker: Skip Property set ..... exiting!
Titus Prerequisite Checker: Prerequisite Scan End

Deployment Guide www.fortra.com page: 13

 Deploy the TCPG Configuration file /

Deploy the TCPG Configuration file

We recommend that a Configuration be deployed to users during the Data Classification
Suite installation. See Before you start on page 7 for more information about how to
prepare for a deployment.

You can also install the Data Classification Suite without a Configuration. You can provide
the Configuration later by manually copying the TCPG file to the following location on your
client machine: %ProgramData%\TITUS\, and name the file “Titus.new.tcpg”.

We support the following Install Properties that can be used to deploy the Configuration file.

Install Property Description

CONFIGURATIONFILE Delivers a TCPG file and sets up synchronization to a specified
location to check for an updated version. Place this file on a
web server or file share.

Creates a registry key named ConfigFileURI used by the client

after installation to check for updates to the TCPG file.

The time interval between these checks is defined in the

System Settings tab of the Data Classification Administration
Console or DCSSystem Settings in the Policy Manager
(depending on what tool you used to create your Policies and
Configuration). By default, a sync is performed every 60
minutes.
CONFIGLOCATION Installs a TCPG file to the client machines during Data
Classification Suite installation.

The installer downloads the TCPG to the following location:

%ProgramData%\TITUS\Titus.new.tcpg

Deployment Guide www.fortra.com page: 14

 Deploy the TCPG Configuration file / Use the CONFIGURATIONFILE to synchronize to a TCPG location

Use the CONFIGURATIONFILE to synchronize to a

TCPG location
When the CONFIGURATIONFILE Install Property is used, the location of a TCPG file is set up
so that the client environment is prepared for sync operations.

The first sync interval after installation is performed immediately and then every 15
minutes. This interval changes to the value defined in the Administration Console or Policy
Manager once the TCPG is consumed.

This install property creates a registry string to specify the contents of the ConfigFileURI.
The Client Service then returns to this location to check for updates according to the sync
options specified in the Administration Console or Policy Manager.

NOTE:
l The Data Classification Suite sync task downloads the most recent TCPG file
from FileServer/HTTP/HTTPS. The client service will not download if the file
specified in ConfigFileURI is older or the same as what’s listed in
Titus.local.TCPG file. In this case, you must force a download. To do that, delete
your current Titus.local.TCPG and restart the Data Classification Suite.
l Registry keys created on installation are removed when the software is
uninstalled.

To use the CONFIGURATIONFILE Install Property to distribute the TCPG, copy the TCPG to a
file share or web server.

l The following registry key is created. The location and name of the configuration file
being deployed is also required:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TITUS\ServiceLocation\ConfigFileURI
l The machine account must have READ access to the TCPG file. All computers can
be given READ Access using the group name “Domain Computers”. See
https://technet.microsoft.com/en-ca/library/cc756898%28v=ws.10%29.aspx for
additional information.
l Do not name the TCPG file "TITUS.new.tcpg"; it will, however, be renamed to
TITUS.new.tcpg once it is copied to the %ProgramData%\Titus folder.
l The name of the File Server containing the TCPG can be an explicit IP address.
l When the TCPG file is accessed via fileshare, only fully qualified network paths are
supported, and a UNC path must be specified. Mapped drives are not supported
because they are user-specific and the Configuration is retrieved by the system user.

Deployment Guide www.fortra.com page: 15

 Deploy the TCPG Configuration file / Use the CONFIGLOCATION install property to provide a TCPG file during installation

l When the TCPG file is accessed via http or https, you must adjust Internet
Information Services Manager (IIS) to support the TCPG MIME type on the website.
See the following link for more information:
http://technet.microsoft.com/en-us/library/cc725608(v=ws.10).aspx

Use the CONFIGLOCATION install property to provide

a TCPG file during installation
The installer downloads the TCPG to the following location:

%ProgramData%\TITUS\TITUS.new.tcpg

When using this method, the TCPG file that is distributed at installation is always used or
until it is manually replaced by a new TCPG or a sync process is set up.

You can copy the TCPG to a file share or web server or it can be a local file. You can place
the TCPG file in any location accessible by the installer. It is delivered only once during
install.

NOTE: Using the CONFIGLOCATION and CONFIGURATIONFILE Install Properties is not

supported.

Manually create a registry key to set up

synchronization to a TCPG location
You can set up synchronization to a TCPG after a client has been installed. You can create
this REG key on a client machine using one of the various enterprise configuration
management solutions such as Group Policy Object (GPO) or Microsoft System Center
Configuration Manager. You can also use a Registry script (.Reg file) specify the location
manually.

NOTE: The Registry entry is not deleted on client machines when DCS for Windows is
uninstalled.

1. Open the Registry Editor and navigate to the following location:

HKEY_LOCAL_MACHINE\Software\Policies\TITUS\ServiceLocation.

Deployment Guide www.fortra.com page: 16

 Deploy the TCPG Configuration file / Manually create a registry key to set up synchronization to a TCPG location

2. Add a new String Value named ConfigFileURI.

3. Enter the value of the ConfigFileURI as either a fully qualified UNC path including the
filename, for example: \\FileServer\Path\TITUS.new.tcpg, or a URL specifying the
web location (http or https).
NOTE: Async occurs if the file specified in ConfigFileURI is newer that the file in
\ProgramData\TITUS.

Deployment Guide www.fortra.com page: 17

 Install DCS for Windows /

Install DCS for Windows

IMPORTANT: When you install DCS for Windows, a UserSetting file is generated. This
UserSetting file is not compatible with versions prior to 2022.0. Therefore, if a user is
reverted to a version of TCS earlier than 2022.0, the UserSettings file must be deleted.
The UserSettings file is located in C:\Users\<username>\AppData\Roaming\Titus.

The following methods are supported to install the DCS for Windows.

Method When to use

Running the EXE Use the EXE file when creating a script to deploy the Data
(Bootstrapper) file in a Classification Suite. Use a software deployment tool such as
script that is run in a Microsoft System Center Configuration Management (SCCM).
Command Line
Titus recommends this method when deploying to the entire
organization once testing has been completed.

See Install DCS for Windows using the EXE file in a command
line script on page 19 for more information.
Using the MSI files Use MSI when distributing the Data Classification Suite using
a configuration management technology such as Microsoft
System Center Configuration Management (SCCM)

Titus recommends this method when deploying to the entire

organization once testing has been completed.

See Install DCS using the MSI files on page 27 for more
information.
Running the EXE Titus recommends this method when testing the software for
(Bootstrapper) on a a larger deployment or installing the software for a small
single Client Machine group of users.

See Install DCS for Windows on a single client machine on

page 37 for more information.

Deployment Guide www.fortra.com page: 18

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Install DCS for Windows using the EXE file in a

command line script
TitusClassificationSetup.exe performs the necessary prerequisite checks and will install
when using a command line. The RedistSuite folder is required in addition to the
TitusClassificationSetup.exe file and must be in the same location during the installation.
The RedistSuite folder contains the prerequisites and Services that are automatically
installed when the TitusClassificationSetup.exe file is run.

The Administration can create a script to run the EXE. The Install properties for the EXE are
included in the table below.

When using a local system account to deploy the Data Classification Suite with SCCM or
PSEXEC, the error code 1073741819 may be returned. The following settings will help avoid
this error:

For PSEXEC use: -s -i

For SCCM use the following setting: "Allow users to view and interact with the program
installation."

NOTE: EXE files cannot be run using Group Policy Object (GPO).

Supported installation properties

The TitusClassificationSetup.exe file can be run with the following install properties.

These install properties are optional but can be used to configure the software installation.

NOTE: The install properties are case-sensitive and will fail if not entered as listed in the
table below.

Deployment Guide www.fortra.com page: 19

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
INSTALLCLIENT_TMC By default,DCS for Outlook, DCS for Office, and DCS for
Desktop are installed when the
INSTALLCLIENT_TCO TITUSClassificationSetup.exe file is run.

INSTALLCLIENT_TCD In the command line, specify which client application you

want to install when using the Data Classification Suite
using the .exe file. For example:

TITUSClassificationSetup.exe /quiet INSTALLCLIENT_

TMC=1 INSTALLCLIENT_TCO=1 INSTALLCLIENT_TCD=0

In the above example, DCS for Desktop is not installed.

“/quiet” installs the client applications without displaying the
install screens to the user.INSTALLCLIENT_TMC:
Determines if DCS for Outlook will be installed. Set to 1 to
install it.

INSTALLCLIENT_TCO: Determines if DCS for Office will be

installed. Set to 1 to install it.

INSTALLCLIENT_TCD: Determines if DCS for Desktop will be

installed. Set to 1 to install it.

NOTE: If one client application is identified in a command

line, the other client applications must also be included
and explicitly enabled or disabled.

Deployment Guide www.fortra.com page: 20

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
TITUS_SKIP On systems where Office version is not detected
automatically, use the following command:
TITUS_
FOUNDPRODUCTPLATFOR For Office 32-bit:
M
TitusClassificationSetup.exe TITUS_SKIP=yes TITUS_
FOUNDPRODUCTPLATFORM=x86 /quiet

For Office 64-bit:

TitusClassificationSetup.exe TITUS_SKIP=yes TITUS_

FOUNDPRODUCTPLATFORM=x64 /quiet

NOTE: TITUS_SKIP=yes does not check the bitness for

Office and sets it using TITUS_
FOUNDPRODUCTPLATFORM=x64 or x86.

NOTE: If any Components are not required, set its value

to 0 for example: INSTALLCLIENT_TCD=0
INSTALLCLIENT_TMC=1 INSTALLCLIENT_TCO=1

Deployment Guide www.fortra.com page: 21

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
CONFIGURATIONFILE To create a registry key named ConfigFileURI which is used
by the client after installation to check for updates to the
TCPG file. The time interval between these checks is
defined in the System Settings tab of the Data Classification
Administration Console. By default a sync is performed
every 60 minutes.

For example:

TitusClassificationSetup.exe /quiet
CONFIGURATIONFILE=Local or UNC or http Path to
Titus.new.tcpg

The following is an example using a UNC:

CONFIGURATIONFILE=\\<machine name>\<share path to

TCPG file>\TitusConfig.tcpg

NOTE:
The machine account must have READ access to the
TCPG file. All computers can be given READ Access
using the group name “Domain Computers”. The
following link describes the default behavior of the
“Domain Computers” group which contains all
computers that are not domain controllers:
https://docs.microsoft.com/en-
us/windows/security/identity-protection/access-
control/active-directory-security-groups
For more information on how to grant READ access see:
https://technet.microsoft.com/en-us/library/cc754344
(v=ws.11).aspx

Deployment Guide www.fortra.com page: 22

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
CONFIGLOCATION To specify the name and location of a Configuration file
(TCPG) which the installer will copy to the client during
install. This Configuration will be used immediately on first
start of the client application if no other Configuration has
been delivered by a synchronization cycle – see
CONFIGURATIONFILE above. The CONFIGLOCATION and
CONFIGURATIONFILE cannot be used together.

For example:

TitusClassificationSetup.exe /quiet
CONFIGLOCATION=Local or UNC Path to Titus.new.tcpg

CONFIGLOCATION=\\<machine name>\<share path to

TCPG file>\Titus.new.tcpg

CONFIGLOCATION=\\sample.co.local\titusconfig\Titus.new
.tcpg

NOTE: Titus.new.tcpg can be another file name if

preferred, for example TITUS.config.tcpg.

Network Mapped drives are not supported during install for

the configuration file. Use UNC path if required.

The following is an example using a UNC path:

CONFIGLOCATION=\\<machine name>\<share path to

TCPG file>\TITUS.new.tcpg

CONFIGLOCATION=\\sample.co.local\titusconfig\TITUS.ne
w.tcpg

Deployment Guide www.fortra.com page: 23

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
NOTE:
The machine account must have READ access to the
TCPG file. All computers can be given READ Access
using the group name “Domain Computers”. The
following link describes the default behavior of the
“Domain Computers” group which contains all
computers that are not domain controllers:
https://docs.microsoft.com/en-
us/windows/security/identity-protection/access-
control/active-directory-security-groups
For more information on how to grant READ access see:
https://technet.microsoft.com/en-us/library/cc754344
(v=ws.11).aspx

NOTE: This
Install Property was previously named
SDFLOCATION. SDFLOCATION is no longer supported.

PREREQ_SKIP Skips the Titus Client Application Prerequisite Checker, Use

the following property value:

PREREQ_SKIP=yes

By default, this Install Property is set to NO and the Checker

is run.
COLLECTORLOCATION Sets the machine name for the Fortra's Data Classification
Suite (DCS) Analytics Collector (On-premises).

For more information, see Set up client machines to forward

Events to the DCS Analytics Collector on page 44.

For example:

COLLECTORLOCATION=<http://machine name:port where

Fortra's Data Classification Suite (DCS) Analytics Collector
(On-premises)is installed>

COLLECTORLOCATION= http://Tlog.titus.local:34390
EVENT_LOG_FILE_SIZE To set the maximum size of the event source log file in MBs.
The maximum size that is permitted is 4GB. For example:

EVENT_LOG_FILE_SIZE=20

By default the maximum size is set at 30MB.

Deployment Guide www.fortra.com page: 24

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
DISABLE_ Disables the Titus Health Monitor. Use:
HEALTHMONITOR
DISABLE_HEALTHMONITOR=TRUE

By default, this Install Property is set to FALSE and the

Health Monitor is installed.
HEALTHMONITOR_ Sets the Health Monitor interval in seconds. If the Titus
INTERVAL Service on the Client Machine stops, the Titus Health
Monitor Service restarts it. For example:

HEALTHMONITOR_INTERVAL=30

The default is 20 seconds.

RESTART_EXPLORER Automatically restarts Windows Explorer after Fortra Data
Classification for Desktop is installed. You must restart
Windows Explorer before Fortra Data Classification for
Desktop is enabled. For example:

RESTART_EXPLORER=1

By default, the Install Property is set to 0 and a Windows

Explorer does not restart.
TITUS_EPOENABLED To create the registry keys required to generate McAfee
event logs for the Data Classification Suite client
applications. These registry keys identify the Titus Client
Applications to the ePO server.

TITUS_EPOENABLED =1

By default the Install Property is set to 0 and the ePO

registry keys are not created.

Deployment Guide www.fortra.com page: 25

 Install DCS for Windows / Install DCS for Windows using the EXE file in a command line script

Property Description
PACKAGE_VALIDATION Sets a registry key to ensure that Client machines only trust
Configurations from the specified Administration Console
(s) . Multiple values can be provided.

The registry key is created under

HKLM\SOFTWARE\Policies\TITUS\Services with a value of
AdministrationConsoleIDs enter:

PACKAGE_VALIDATION=<the GUID>

The unique Administration Console ID appears on the

bottom right corner of the Overview page of the Titus
Administration Console. This GUID string is used to identify
each installed Administration Console.

NOTE: ThisInstall Property is not mandatory. If a value is

not provided, Configurations from any Administration
Console machines are accepted.

USETCPSERVICEBINDING Uses TCP bindings instead of Named Pipes bindings for the
Titus Enterprise Client Service. Include this parameter with a
value of “1”.

The default value is 0.

For example:
USETCPSERVICEBINDING="1"
To specify the location of The location of the log files is specified as:
install log files
/log "PATH\LogFile”

Deployment Guide www.fortra.com page: 26

 / Install DCS using the MSI files

Install DCS using the MSI files

Use the Microsoft Installer (MSI) files when distributing the Data Classification Suite using a
configuration management technology such as Microsoft System Center Configuration
Management (SCCM). This allows you to deploy the Titus software without any interaction
from users on client machines. These MSI files are located in the RedistServerAC folder.

If one the following required Install Properties is not included when using the MSI files, the
installation fails:

OUTLOOK_BITNESS=x86 or OFFICE_BITNESS=x86

OUTLOOK_BITNESS=x64 or OFFICE_BITNESS=x64

NOTE: MSIs are complete installers with configurable variables. If the bitness of
Microsoft Office or Outlook matches the bitness of your OS, then you only need to
install one MSI. If the bitnesses of MSO and OS do not match, then run both MSIs. If you
are using the 64-bit Operating System MSI and a 32-bit version of Microsoft Office, you
must include OUTLOOK_BITNESS=x86 OFFICE_BITNESS=x86 in the 64-bit MSI
parameters as well as the 32-bit MSI.

By default, the version of the MSI determines if the Data Classification Suite is installed to
the 32 or 64-bit version of Microsoft Outlook/Microsoft Office. If the incorrect version is
specified or the MSI for the wrong bitness is used without this Install Property, the
installation fails.

MSIExec
Microsoft provides the MSIExec application to process MSI files with a list of Install
Properties to deploy software. IT Administrators deploying the Data Classification Suite can
use the quiet switch to ensure the Installation user interface is not displayed to the end
users.

Typical command lines

There are separate Data Classification Suite MSI files for 32-bit and 64-bit operating
systems which require MSIs. The MSI properties are fully documented in the following
section. The following example illustrates the command lines that you must run to install on
a 32-bit and 64-bit operating systems of Microsoft Office:

msiexec.exe /i TITUS_Classification_Setup_x64.msi INSTALLCLIENT_

TMC=0 INSTALLCLIENT_TCO=0 INSTALLCLIENT_TCD=1 OUTLOOK_BITNESS=x86

Deployment Guide www.fortra.com page: 27

 / Install DCS using the MSI files

OFFICE_BITNESS=x86 /quiet
msiexec.exe /i TITUS_Classification_Setup_x86.msi INSTALLCLIENT_
TMC=1 INSTALLCLIENT_TCO=1 INSTALLCLIENT_TCD=0 OUTLOOK_BITNESS=x86
OFFICE_BITNESS=x86 /quiet

The first line installs Fortra's DCS for Desktop (On-premises) on a 64-bit system.

The second line installs Fortra's DCS for Office (On-premises) and Fortra's DCS for Outlook
(On-premises) on a 32-bit system.

When deploying through SCCM, use system targeting to ensure that the correct deployment
package is applied to the correct bitness level of the system.

Instead of running the TitusClassificationSetup.exe file, open the RedistSuite folder. Install
the required files in the order specified in Install MSI by bitness on page 28. The files you
install depend upon the bitness of the operating system (32-bit or 64-bit), Microsoft Office,
and Microsoft Outlook.

Install MSI by bitness

You can install the Data Classification Suite manually or by using an enterprise
Configuration management solution such as Group Policy Object (GPO) or Microsoft
System Center Configuration Manager. Instead of running the TITUSClassificationSetup.exe
file, open the RedistSuite folder, and install the required files according to the tables. The
files you install depend upon the bitness of the operating system (32-bit or 64-bit), Microsoft
Office, and Microsoft Outlook.

To install a client application, you must use the MSI Properties.

For information about MSIExec syntax, see Install DCS using the MSI files on page 27.

NOTE: You must install the files in the order listed, from top to bottom and left to right.

64-bit Operating System, 64-bit Microsoft Office and Microsoft Outlook

Install Installation file DCS for DCS for DCS for

Order OutlookInstall OfficeInstall Desktop Install
Properties Properties Properties
1 vcredist_x64.exe
2 vcredist_x86.exe

Deployment Guide www.fortra.com page: 28

 / Install DCS using the MSI files

Install Installation file DCS for DCS for DCS for

Order OutlookInstall OfficeInstall Desktop Install
Properties Properties Properties
3 TITUS_PEP_
PrerequisiteChecker.m
si
4 TITUS_Classification_ INSTALLCLIEN INSTALLCLIEN INSTALLCLIEN
Setup_x64.msi T_TMC=1 T_TCO=1 T_TCD=1

OUTLOOK_ OFFICE_
BITNESS=x64 BITNESS=x64

64-bit Operating System, 32-bit Microsoft Office and Microsoft Outlook

Install Installation file DCS for DCS for DCS for

order OutlookInstall OfficeInstall Desktop Install
Properties Properties Properties
1 vcredist_x86.exe
2 vcredist_x64.exe
3 TITUS_PEP_
PrerequisiteChecker.m
si
4 TITUS_Classification_ INSTALLCLIEN INSTALLCLIEN INSTALLCLIEN
Setup_x64.msi T_TMC=0 T_TCO=0 T_TCD=1

OUTLOOK_ OFFICE_
BITNESS=x86 BITNESS=x86
5 TITUS_Classification_ INSTALLCLIEN INSTALLCLIEN INSTALLCLIEN
Setup_x86.msi T_TMC=1 T_TCO=1 T_TCD=0

OUTLOOK_ OFFICE_
BITNESS=x86 BITNESS=x86

32-bit Operating System, 32-bit Microsoft Office and Microsoft Outlook

Install Installation file DCS for DCS for DCS for

Order OutlookInstall OfficeInstall Desktop Install
Properties Properties Properties
1 vcredist_x86.exe

Deployment Guide www.fortra.com page: 29

 / Install DCS using the MSI files

Install Installation file DCS for DCS for DCS for

Order OutlookInstall OfficeInstall Desktop Install
Properties Properties Properties
2 TITUS_PEP_
PrerequisiteChecker.m
si
3 TITUS_Classification_ INSTALLCLIEN INSTALLCLIEN INSTALLCLIEN
Setup_x86.msi T_TMC=1 T_TCO=1 T_TCD=1

OUTLOOK_ OFFICE_
BITNESS=x86 BITNESS=x86

Supported install properties

Property Description
INSTALLCLIENT_TMC Determines if DCS for Outlook will be installed. Set to 1 to install
it. This must be used in conjunction with OUTLOOK_BITNESS
property: Use

INSTALLCLIENT_TMC=1
INSTALLCLIENT_TCO Determines if DCS for Office will be installed. Set to 1 to install
it. This must be used in conjunction with OFFICE_BITNESS
property: Use

INSTALLCLIENT_TCO=1
INSTALLCLIENT_TCD Determines if DCS for Desktop will be installed. Set to 1 to
install it. This should be used only on the MSI which matches the
bitness of the operating system.

INSTALLCLIENT_TCD=1

Deployment Guide www.fortra.com page: 30

 / Install DCS using the MSI files

Property Description
CONFIGURATIONFILE To create a registry key named ConfigFileURI which is used by
the client after installation to check for updates to the TCPG file.
The time interval between these checks is defined in the System
Settings tab of the Data Classification Administration Console.
By default a sync is performed every 60 minutes.

For example:

TitusClassificationSetup.exe /quiet CONFIGURATIONFILE=Local

or UNC or http Path to Titus.new.tcpg

The following is an example using a UNC:

CONFIGURATIONFILE=\\<machine name>\<share path to TCPG

file>\TitusConfig.tcpg

NOTE:
The machine account must have READ access to the TCPG
file. All computers can be given READ Access using the
group name “Domain Computers”. The following link
describes the default behavior of the “Domain Computers”
group which contains all computers that are not domain
controllers: https://docs.microsoft.com/en-
us/windows/security/identity-protection/access-
control/active-directory-security-groups
For more information on how to grant READ access see:
https://technet.microsoft.com/en-us/library/cc754344
(v=ws.11).aspx

Deployment Guide www.fortra.com page: 31

 / Install DCS using the MSI files

Property Description
CONFIGLOCATION To specify the name and location of a Configuration file (TCPG)
which the installer will copy to the client during install. This
Configuration will be used immediately on first start of the client
application if no other Configuration has been delivered by a
synchronization cycle – see CONFIGURATIONFILE above. The
CONFIGLOCATION and CONFIGURATIONFILE cannot be used
together.

For example:

TitusClassificationSetup.exe /quiet CONFIGLOCATION=Local or

UNC Path to Titus.new.tcpg

CONFIGLOCATION=\\<machine name>\<share path to TCPG

file>\Titus.new.tcpg

CONFIGLOCATION=\\sample.co.local\titusconfig\Titus.new.tcp
g

NOTE: Titus.new.tcpgcan be another file name if preferred,

for example TITUS.config.tcpg.

Network Mapped drives are not supported during install for the
configuration file. Use UNC path if required.

The following is an example using a UNC path:

CONFIGLOCATION=\\<machine name>\<share path to TCPG

file>\TITUS.new.tcpg

CONFIGLOCATION=\\sample.co.local\titusconfig\TITUS.new.tc
pg

Deployment Guide www.fortra.com page: 32

 / Install DCS using the MSI files

Property Description
NOTE:
The machine account must have READ access to the TCPG
file. All computers can be given READ Access using the
group name “Domain Computers”. The following link
describes the default behavior of the “Domain Computers”
group which contains all computers that are not domain
controllers: https://docs.microsoft.com/en-
us/windows/security/identity-protection/access-
control/active-directory-security-groups
For more information on how to grant READ access see:
https://technet.microsoft.com/en-us/library/cc754344
(v=ws.11).aspx

NOTE: This
Install Property was previously named
SDFLOCATION. SDFLOCATION is no longer supported.

PACKAGE_ Allows you to create a registry key named

VALIDATION AdministrationConsoleIDs when the Data Classification Suite is
installed. This registry key is used to ensure that the Client
Service can consume the Titus.new.tcpg generated on the
specified server.

The ServerIdsForAllowedConfigs registry key is located in:

(32 bits OS) HKEY_LOCAL_

MACHINE\SOFTWARE\TITUS\Services

(64 bits OS) HKEY_LOCAL_

MACHINE\SOFTWARE\WOW6432Node\TITUS\Services

For example:

PACKAGE_VALIDATION=<ServerID>

PACKAGE_VALIDATION=012345

Multiple Server IDs can be concatenated using semi-colon ";" as

the separator.

Deployment Guide www.fortra.com page: 33

 / Install DCS using the MSI files

Property Description
COLLECTORLOCATIO Allows you to set the machine name for the Reporting Collector
N Service.

For more information, see Set up client machines to forward

Events to the DCS Analytics Collector on page 44.

For example:

COLLECTORLOCATION=<http://machine name:port where Titus

Collector is installed>

COLLECTORLOCATION= http://Tlog.titus.local:34390
OUTLOOK_BITNESS Allows you to specify whether DCS for Outlook will be installed
to a 32 or 64-bit version of Microsoft Outlook. For example for a
32-bit version of Microsoft Outlook:

OUTLOOK_BITNESS=X86

By default, the version of the MSI determines if the Data

Classification Suite is installed to the 32 or 64-bit version of
Microsoft Outlook. If the incorrect version is specified or the MSI
for the wrong bitness is used without this Install Property, the
installation fails.
OFFICE_BITNESS Allows you to specify whether DCS for Office will be installed to
an 86 or 32-bit version of Microsoft Office. For example:

OFFICE_BITNESS=X86

By default, the version of the MSI determines if the DCS for

Windows is installed to the 32 or 64-bit version of Microsoft
Office. If the incorrect version is specified or the MSI for the
wrong bitness is used without this switch, the installation fails.
SERVICESLOGLEVEL Allows you to set the services logging to DEBUG, WARN, INFO, or
ERROR enter: enter:

SERVICESLOGLEVEL=DEBUG

By default, the logging level is WARN.

Deployment Guide www.fortra.com page: 34

 / Install DCS using the MSI files

Property Description
EVENT_LOG_FILE_ Allows you to set the maximum size of the event source log file
SIZE in MBs. The maximum size that is permitted is 4GB. For
example:

EVENT_LOG_FILE_SIZE=20

By default the maximum size is set at 30MB.

CLOSE_OFFICE_APPS Allows you to check for open Microsoft Office applications and
close them prior to install and uninstall. For example:

CLOSE_OFFICE_APPS=1

By default, this Install Property is set to 0 and any open

Microsoft Office applications remain open.
TITUS_DISABLE_ Allows you to stop Microsoft Outlook messages from being sent
SEND_OUTLOOK during install and uninstall. For example:

TITUS_DISABLE_SEND_OUTLOOK=0

By default, this Install Property is set to 1 and messages can be

sent during install and uninstall.
TITUS_DISABLE_ Stop Microsoft Office documents from being saved prior to
SAVE_OFFICE install and uninstall. For example:

TITUS_DISABLE_SAVE_OFFICE =0

By default, this Install Property is set to 1 and Microsoft Office

documents are saved prior to install and uninstall.
RESTART_EXPLORER Automatically restart Windows Explorer after DCS for Desktop is
installed. You must restart Windows Explorer before DCS for
Desktop is enabled. For example:

RESTART_EXPLORER=1

By default, the Install Property is set to 0 and a Windows

Explorer restart is not performed.
HEALTHMONITOR_ Set the Health Monitor interval in seconds. If the Titus Service
INTERVAL on the Client Machine stops, the Health Monitor Service restarts
it. For example:

HEALTHMONITOR_INTERVAL=30

The default is 20 seconds.

Deployment Guide www.fortra.com page: 35

 / Install DCS using the MSI files

Additional MSI files

TITUS_PEP_ Do not run this MSI if you do not want to use the Titus
PrerequisiteChecker.msi Prerequisite Checker.

Deployment Guide www.fortra.com page: 36

 / Install DCS for Windows on a single client machine

Install DCS for Windows on a single client machine

Use these instructions when testing the software for a larger deployment or installing the
software for a small group of users. You require Administrator privileges to install this
product.

You can install Data Classification manually or using an enterprise configuration

management solution such as Group Policy Object (GPO) or Microsoft System Center
Configuration Manager. For more information, see Install DCS for Windows using the EXE
file in a command line script on page 19.

Titus recommends that you assess your Configuration in a test environment before
targeting the Titus Configuration to all machines.

NOTE: When deploying in closed environments with no internet access, the digital
certificates, used to ensure authenticity of the Titus files, must exist on the systems
where the Titus software is installed. For more information, refer to the Knowledge Base
in the Titus Support Portal and search for “Root CA Certificate”.

Close Microsoft Outlook and all open Office applications.

Extract the installation package before running the TITUSAdminConsoleSetup.exe or the

TitusClassificationSetup.exe.

1. Double-click TitusClassificationSetup.exe.
The RedistSuite folder must be in the same location as the installation file so that
the prerequisites and Services can also be installed.
The Fortra Classification Setup Welcome window appears.
2. Select the client applications you want to install and click Next.
The File Explorer Restart window appears if you have selected the Fortra Data
Classification for Desktop checkbox.
3. Select Yes to automatically restart File Explorer.
If you do not select Yes, you must reboot your system before you can use Fortra
Data Classification for Desktop on your machine.
The License Agreement window appears.
4. Read and accept the license agreement.
5. Click Install.
The Setup Progress window appears.

Deployment Guide www.fortra.com page: 37

 / Upgrade DCS for Windows

If you did not install all client applications, you can add them later by running the MSI
corresponding to the application you want to install. See Install DCS using the MSI
files on page 27 for more information.
6. When the installation is complete, click Close.
7. In some instances, systems must be restarted to complete an installation. If you are
prompted, restart your system.

Upgrade DCS for Windows

IMPORTANT:
If you are upgrading DCS from:
l Titus Classification Suite prior to 2021.4, you must uninstall that version before
installing this version. You can select an existing database; the database will be
migrated as part of the installation.
l Titus Classification Suite 2021.4 or later, you can do an in-place upgrade (that is,
you do not need to uninstall the previous version before installing this version)

We strongly recommend that the Data Classification Suite 2023.0 uses Configurations
published by Titus Administration Console or Policy Manager, and you export your
Configuration before upgrading. The exported Configuration files (TCFs) can be used to
restore the previous version if necessary. See Export your current Configuration on page 39.

NOTE: TCFs are not supported in Policy Manager. TCFs published with previous versions
of the Titus Administration Console are not compatible with new versions. You cannot
use a TCF to migrate a Configuration from one version of the Titus Administration
Console to the other.

IMPORTANT: Older TCS for Windows clients (4.9 SP1 to 2021.2) can use existing
Configurations published from Titus Administration Console 2022.0. Once changes are
made to the existing Configuration, the behavior of the older clients cannot be
predicted.

WARNING:
Titus strongly recommends that you back up your database before upgrading. This
database can be used to restore the previous version if necessary.

Deployment Guide www.fortra.com page: 38

 / Upgrade DCS for Windows

NOTE: The Data Classification Administration Console installer attempts to upgrade the
database as part of the installation. A SQL utility (SQLCmd.exe) is used to back up the
database. If the utility is not found on the system where Administration Console is
installed, the backup is not created. However, the database is upgraded and the
installation completes as expected.

Export your current Configuration

Export your Configurations to let the Administrator store a copy of the Configuration to the
specified location. These configuration files can be imported into the current version of the
Administration Console if necessary.

NOTE:
l Custom Adapter settings and System Settings are not preserved when a
Configuration is exported. These settings must be reconfigured if you import
your TCF into a new Titus Administration Console instance or an instance with a
new database.
l Configurations (TCFs) can only be imported into the same version of the
Administration Console from which they were exported.

1. Select the Configuration tab and select the Configuration you want to export.
2. Click Export.
3. Enter a filename for the Configuration and then click OK.

The Configuration is saved to the Administrator’s machine as a TCF.

4. Back up your Administration Console SQL database.

5. Restore the Administration Console SQL database using a new name, or restore it
into a new SQL Server instance.
6. If you are using Titus Classification Suite version 4.5 or newer, note the location of
the Reporting Collector.

Deploy the Administration Console

1. Install the Administration Console. Select the following options:
l Use the Connect to an existing SQL Server instance option to connect to the
Administration Console database in the new SQL Server instance.
l Select Select this checkbox and Next to migrate the current database to the
latest version.

Deployment Guide www.fortra.com page: 39

 / Upgrade DCS for Windows

WARNING: Selecting this option upgrades the tables in the Administration

Console database. Once the database has been upgraded, it cannot be
used by previous versions of the Administration Console.

2. Open the Administration Console website. Your Configurations appear in the

Configurations tab. Review your Schema and Policies to ensure that they appear as
expected.

Publish and distribute Configurations

You must publish your Configuration to a location that can be accessed by Data
Classification Suite 2023.0 clients.

We recommend that you distribute these Configurations from a new location or use a
different name to avoid replacing Configurations previously published.

NOTE: TitusAdministration Consoles version 4.7 and above publish Configurations as

TCPG files rather than SDF files.

Upgraded switches
NOTE: Ifyou did not use CONFIGFILEURI to locate your Configurations, your TCPG will be
deleted from "C:\ProgramData\TITUS" and be replaced by a blank TCPG file upon
installation.

Data Classification Suite install switches were upgraded in version 4.7. If you are upgrading
from Titus Classification Suite version 4.6 or earlier, and you are using an existing
installation script, the script may need to be modified to use the new switches.

1. Install Data Classification.

2. Configure the client to locate the Configuration at the location specified in Publish
and distribute Configurations on page 40.
3. Repeat the steps until all users have been upgraded to version 2023.0.

Deployment Guide www.fortra.com page: 40

 / Upgrade DCS for Windows

TIP:
l You can deploy the Data Classification Suite to a single client machine to ensure
that your Configuration was upgraded successfully.
l Some Data Classification Suite settings, such as the location of the Reporting
Collector, are stored in registry entries. Note the values in the following registry
key, as you may need to reconfigure these settings after upgrading:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TITUS\ServiceLocation
l If you are upgrading from Titus Classification Suite version 4.6 or earlier, some
prerequisites no longer apply. The following features and applications can be
removed from the client machine after Data Classification Suite is installed:
l MSMQ
l MSDTC
l SQL Compact Edition

Deployment Guide www.fortra.com page: 41

 About Titus Enterprise Services / Titus Client Services

About Titus Enterprise Services

Titus Services enterprise-grade software services operate in a service-oriented architecture.
All common capabilities from applications are centralized within these services.

Titus Client Services

The Titus Client installation includes the Service listed in the table below.

Service Role
Titus.Enterprise.Client Evaluates client requests from Fortra-enabled
applications and services.
Titus Enterprise. Health Verifies the status of the Titus Enterprise Client service
Monitor Service

Service Protocol and Default Port Numbers

Titus Services are implemented using Microsoft’s Windows Communication Foundation
(WCF) framework. The Data Classification Suite communicates with a Windows Service
installed on each client.

Service Protocol Default Service Location

AuditLogServicePort NetNamedPipeBinding net.pipe://localhost/AuditLogService
MetadataServicePort NetNamedPipeBinding net.pipe://localhost/MetadataService
PolicyServicePort NetNamedPipeBinding net.pipe://localhost/PolicyService
SettingsServicePort NetNamedPipeBinding net.pipe://localhost/DataService

Stop and start the Titus Service on the client machine

If the Titus Service on the client machine stops for any reason, the Data Classification
Enterprise Health Monitor Service restarts it after approximately 20 seconds (default value).

However, if the service must be stopped and started immediately, please use this procedure
to restart the Titus Enterprise Client Service on the client machine.

Deployment Guide www.fortra.com page: 42

 About Titus Enterprise Services / Stop and start the Titus Service on the client machine

1. On the client machine, open the Services program.

2. Restart the Titus Enterprise Client Service.

Deployment Guide www.fortra.com page: 43

 Set up client machines to forward Events to the DCS Analytics Collector / Use regedit to manually set the location of the

Set up client machines to forward

Events to the DCS Analytics
Collector
Data Classification Suite audit events are routed from the desktop components to the
DCS Analytics Collector based on a registry string value AuditCollectorLocation in the key
HKEY_LOCAL_MACHINE\Software\Policies\TITUS\ServiceLocation.

When the client applications are installed on user systems, this registry value is set by the
COLLECTORLOCATION parameter of the installer MSI. It can also be set manually after
installation.

This registry value can be created on a client machine using an enterprise configuration
management solution such as Group Policy Object (GPO) or Microsoft System Center
Configuration Manager. A Registry script (.Reg file) can also be used to specify the location.

For more information on the DCS Analytics Collector, contact Support for the Fortra's Data
Classification Suite (DCS) Analytics Collector (On-premises)User Guide.

Use regedit to manually set the location of the

DCS Analytics Collector machine
Use regedit to manually set the location of the DCS Analytics Collector machine

Set the location of the DCS Analytics Collector on a single machine by editing the Registry
Settings on the machine.

1. Open the Registry Editor and navigate to the following key:

HKEY_LOCAL_MACHINE\Software\Policies\TITUS\ServiceLocation
2. Add a new String Value named AuditCollectorLocation.

The AuditCollectorLocation Value must identify the DCS Analytics Collector machine URL.
You can enter it in one of the following formats:

l http://<machine name>:<port>
l http://<fully qualified domain and machine name (FQDN)>:<port>
l http://<IP Address>:<port>

Deployment Guide www.fortra.com page: 44

 Set up client machines to forward Events to the DCS Analytics Collector / Use regedit to manually set the location of the

NOTE:
l By default, the DCS Analytics Collector API uses port number 34390.
l If you update this location while the Data Classification desktop software is
running, restart the Titus Enterprise Client Service for the change to take effect.
l The Registry entry is not deleted on client machines when the Data Classification
Suite Analytics Collector is uninstalled.

Deployment Guide www.fortra.com page: 45

 Verify the Administration Console ID / Expected behavior when using the Administration Console ID feature

Verify the Administration Console

ID
An Administration Console ID verifies that the Configuration consumed on the client
machine was created by a trusted source. This extra layer of security ensures that a
malicious user cannot easily change a Configuration.

1. Open the Registry Editor and navigate to: HKEY_LOCAL_

MACHINE\Software\Policies\TITUS\Services
2. Add a new String Value named AdministrationConsoleIDs.

The Value for this string (the unique Administration Console ID) can be found on the bottom
right corner of the Overview page of the Administration Console you want to trust.

NOTE: Multiple AdministrationConsoleIDs, separated by a semicolon, are supported.

This Registry Key can be created on a client machine using an enterprise configuration
management solution such as Group Policy Object (GPO) or Microsoft System Center
Configuration Manager.

Expected behavior when using the Administration

Console ID feature
Scenario Result
The AdministrationConsoleID Registry Key exists and is The Configuration is
populated by a valid Administration Console ID consumed.
(matching Titus.new.tcpg)
The AdministrationConsoleID Registry Key exists and is The Configuration is
blank consumed.

OR

The registry key does not exist

Deployment Guide www.fortra.com page: 46

 Verify the Administration Console ID / Expected behavior when using the Administration Console ID feature

Scenario Result
The AdministrationConsoleID Registry Key exists, and is The Configuration is NOT
populated by an invalid Administration Console ID or by consumed and an empty
random text Titus.tcpg is created.

Titus.New.TCPG remains in
C:\ProgramData\TITUS

Deployment Guide www.fortra.com page: 47

 About the Classification Selector /

About the Classification Selector

The Classification selector lets users view or modify the metadata that applies to an item,
as configured in the Schema and applicable Schema View. The fields that appear in the
Classification selector vary depending on how your Schema is configured. For more
information, see About the Schema View.

NOTE: TheClassification selector can also contain One Click Classification buttons. For
more information, see One Click Settings.

Once you have created a Classification Schema has been created, a user can select
Classifications:

l by choosing Select from the Advanced dropdown below the Data Classification logo
or the Advanced button in the Task Pane
l by clicking the logo itself
l from the One Click Classification in the ribbon
l by right-clicking an email attachment in Microsoft Outlook and chooses Select
(Microsoft Outlook 2016+ only)
l by sending an email or attachment with Fields that are set to Required and not
making a selection previously. This can also occur if the Data Classification for
Microsoft Outlook has been configured to "Force Select on Save".

If the user does not select a classification, the default or first item in the classification
Schema is applied to the content.

Use the ALT key to navigate to the Settings and Favorites options in the Classification
selector.

Deployment Guide www.fortra.com page: 48

 About the Classification Selector / Classification selector overview

Classification selector overview

Item Description
1 - Title Text The Title Text defines the Ribbon Group and Classification selector title.
The default title is, “TITUS" and is configured using the Metadata
Selection Dialog Title option in the Application Settings section of the
Configuration.

The Subject of the email message or the name of the document or file
appears beside the Classification selector Title.
2- The Classification selector Text is a short instructional message that
Classification appears at the top of the Classification selector, and is defined using
selector Text the Metadata Selection Dialog Preamble option in the Application
Settings section of the Configuration.

Default text: Please select Classification level(s)

3 - Field Names The Field Name describes the items that can be selected or the
information required to classify the content. The Values appear below
the Field Name and can be selected to label and define the
classification level of the content.
NOTE: Ifa Value does not have Display Text, that Value shows as
blank in the Field Name area. If multiple Values do not have Display
Text, those Values are displayed by their Value parameter in the
Field Name area. See Add a Value to a Text Field.

Deployment Guide www.fortra.com page: 49

 About the Classification Selector / Classification selector overview

Item Description
4 - Options icon Users can show/hide field and value descriptions, Favorites, and Help.
The Options icon is configurable. By default, it is Settings.

l Show full descriptions - This feature enables the user to show or

hide the Field and Value descriptions in the Classification
selector. These definitions help the user in selecting the correct
options. When Show full descriptions is enabled, the
Classification selector includes the Field and Value descriptions
(as shown in Department in the above screenshot). When the
Show full descriptions feature is disabled, no Field or Value
descriptions appear. By default, Show full descriptions is
disabled.
l Favorites - Users can create or apply a Favorite Classification
label. See Favorites on page 54.
l Help - Users can access custom online help. See the Data
Classification Suite Administration Console User Guide or Policy
Manager online help for more information.
5 - Preview bar Users can see a summary of the currently selected Classification and
other schema field values. The color coincides with the Classification
as configured in the Field Appearance Style in the Administration
Console or Policy Manager. The Preview bar does not display date or
time values.

If you are using the Administration Console, the Preview bar is enabled
by default for both the Classification Selector and the clients (DCS for
Outlook, DCS for Office, and DCS for Desktop). Contact Support for
more information.

NOTE: If
you are using Policy Manager, you can enable/disable and
configure the Preview bar using Application Settings in the
Configuration. If you are using the Administration Console, you can
use registry keys. See Fortra's Data Classification Suite (DCS)
Administration Console (On-premises) Deployment Guide.

Deployment Guide www.fortra.com page: 50

 About the Classification Selector / Classification selector overview

Item Description
6 - Logo Users can see a company logo or any image. You can configure a logo
in Policy Manager only.

Classification Information bar

When you open a message or file/document, a Classification Information bar appears. This
bar shows the same information as set in the Preview bar.

NOTE: Ifyou are using Policy Manager, you can enable/disable and configure the
Classification Information bar using Application Settings in the Configuration. If you are
using the Administration Console, you can use registry keys. See Fortra's Data
Classification Suite (DCS) Administration Console (On-premises) Deployment Guide.

For example, from an email message:

From a file/document:

You can change the color, resize, and close/reopen the Classification Information bar.

To change color of the bar, simply click a Classification. The color coincides with the
Classification as configured in the Field Appearance Style in the Administration Console or
Policy Manager.

To resize the bar:

1. Click the drop-down arrow in the top-right-hand corner of the Classification

Information bar.
2. Click Resize.
A double-sided arrow appears allowing you to change the size of the bar. You can
only change the bar's length.

Deployment Guide www.fortra.com page: 51

 Ribbon Group / About the Main Ribbon group

Ribbon Group
The Ribbon group is comprised of three separate groupings that can be individually enabled
or disabled; the Main, One Click Classification, and Options Ribbon group.

About the Main Ribbon group

The Main Ribbon group contains the logo dropdown button that allows a user to access the
Select and About Dialogs. When enabled, Redaction (Fortra Data Classification for
Microsoft Outlook for Outlook only) and access to the Help URL are also available. Favorites
are displayed and can be selected from the dropdown menu. You can enable or disable
logging from the Main Ribbon group.

NOTE: Youcan use a custom logo or no logo instead of the Data Classification logo in
the Ribbon. This is configurable in the Policy Manager only.

You can configure the Main Ribbon group to display the default or selected classification or
to allow the user to select a value from the dropdown menu.

About One Click Classification Ribbon group

The One Click Classification Ribbon group provides users with access to the Classification
option via color coded buttons in the ribbon. This Ribbon group can also be configured to
include an Advanced and a Help link.

The One Click Classification buttons enable users to classify content with one click of the
mouse.

You can access the About Dialog from the One Click Classification Ribbon group using the
down arrow in the bottom right corner.

NOTE: When determining the layout, the length of each Field is determined by the longest
Value.

About the Options Ribbon group

Deployment Guide www.fortra.com page: 52

 Ribbon Group / About the Options Ribbon group

Enable the Options Ribbon group in order for the Portion Marking, Check Policy, and Upload
(to the Cloud) buttons to appear in the Client Application. You can select the Enable Check
Policy Button in Ribbon setting in Application Settings > Check Policy Settings.

NOTE: You cannot configure Portion Marking or Check Policy in Policy Manager.

You can customize the name of this Ribbon group, and you can access the About Dialog
from the Options Ribbon group using the down arrow in the bottom right corner.

Use the Check Policy button to check for Policy violations. See Check Policies on page 57.
For more information on Portion Marking, see Apply Portion Marking on page 58.

Deployment Guide www.fortra.com page: 53

 Favorites /

Favorites
Favorites enable users to select a combination of Classification options in the Classification
Selector Dialog and group them together as one option. Once defined, a Favorite can be
accessed from the Classification Selector Dialog, the Favorites menu below the Data
Classification logo, or the Favorites Task Pane (when enabled).

NOTE:
l You can use a custom logo or no logo instead of the Data Classification logo in
the Ribbon and Classification Selector Dialog. NOTE: This is configurable in the
Policy Manager only.
l The contents of a Favorite cannot include a comma or semi-colon as text
delimiter. Acceptable delimiters include; Space, Dash (-), Forward Slash (/),
Underscore (_), and Period (.).
l You can perform actions in the Favorites dialog using shortcut keys. You must
have the Favorites dialog open first. For example, to add a Favorite, use CTRL +
A; to manage Favorites, use CTRL + M.

Because Favorites are stored in the UserSettings file found under your roaming profile
(C:\Users\<username>\AppData\Roaming\Titus), they are retained if you upgrade your
version of DCS. Therefore, you do not have to reconfigure your Favorites in the new version.

Keep in the mind the following:

l You can create a Favorite without fields requiring mandatory values. When a user
applies a Favorite that contains a missing required field, the Classification Selector
Dialog will be shown so the user can select an appropriate value for the missing
field.
NOTE: The Classification Selector Dialog may not immediately appear when you
apply a Favorite from the Ribbon or Task Pane.

l If applying a Favorite causes an alert or warning because of an upgrade, downgrade,

change, or missing field, the Classification Selector Dialog will be shown allowing
you to fix the cause of the alert or warning.
l If a Favorite contains a value that is no longer in the Schema, that value will not be
used.

To create a favorite:

Deployment Guide www.fortra.com page: 54

 Favorites /

1. Click the Settings or User Options icon.

2. Click Favorites > Add to Favorites.
3. Enter a name for the Favorite and other required values.
4. Click OK.

To rename a favorite:

1. Click the Settings or User Options icon.

2. Click Favorites > Manage Favorites.
3. Select a favorite.
4. Click Rename and enter the new name.
5. Click OK.

To reorder your favorites:

1. Click the Settings or User Options icon.

2. Click Favorites > Manage Favorites.
3. Select a favorite and click the up and down arrows to change the order.
4. Click OK.

To delete a favorite:

1. Click the Settings or User Options icon.

2. Click Favorites > Manage Favorites.
3. Select a favorite.
4. Click Delete.
5. Click OK.

Deployment Guide www.fortra.com page: 55

 Undoing Actions /

Undoing Actions
If you have applied a Policy that has one or more of the following Actions to your document,
you can undo the Actions.

l Apply Advanced Header/Footer

l Apply HTML Header/Footer
l Apply Watermark
l Apply Document Markings

For more information on these Actions, see the Titus Administration Console User Guide or
the Data Classification Suite for Windows Policy Authoring Guide.

To undo these Actions, either:

l Press Ctrl + Z
l Click the Undo button
l Click the dropdown arrow next to the Undo button, and select Apply Document
Markings.
NOTE:To undo Apply Advanced Header/Footer, Apply HTML Header/Footer, or
Apply Watermark, select Apply Document Markings.

IMPORTANT:
l If your Document Marking was applied because of a Classification change,
undoing Document Markings does not undo the change to your Classification.
l When you undo Document Markings, the headers, footers, and watermarks
configured in the Apply Document Markings action are removed from the
document at the same time.
l Click the Redo button or click Ctrl + Y to bring back the Documents Markings you
just removed.
l You can undo these Actions to Microsoft Word documents only.

NOTE: Forinformation on undoing Redactions, see Use Redaction in Microsoft Outlook

on page 61.

Deployment Guide www.fortra.com page: 56

 Check Policies /

Check Policies
The Check Policy button appears in the Options Ribbon Group to allow you to check for
Policy violators to your email or document. If configured, a Policy Validation dialog box
appears allowing you to perform any remediation steps.

Deployment Guide www.fortra.com page: 57

 Apply Portion Marking /

Apply Portion Marking

Use the Portion Marking feature to classify a portion of an email message or document.
This allows users to label specific portions of an email clearly and with a high level of
granularity.

Portion Marking works differently depending on the application in which you are using it,
and the version of that application.

When a Portion Mark with a higher classification than the entire document is applied, the
document classification is only upgraded when the Portion Mark is created.

You can define a Portion Mark at individual or multiple paragraphs, a table, image, at the
bullet or at the comment level in PowerPoint. Portion Marks appear at the beginning of the
selected paragraph and not at the position the cursor is placed. You can select multiple
paragraphs. Each selected paragraph is individually classified at the beginning of the
paragraph during one Portion Marking action. If multiple paragraphs are selected and do not
appear consecutively, the Portion Mark is added only to the paragraph where the cursor was
last placed.

The following example shows how to use Portion Marking in Microsoft Word in the Military
edition of DCS for Windows. Currently, Portion Marking is not supported for Microsoft Excel.

1. Place your cursor to the required location. The Portion Mark will be inserted before,
after, or before and after the paragraph.
2. Click the Add Portion Mark symbol in the Ribbon at the top of the pane.

The Titus Portion Marking window appears.

3. Using the dropdown menu, select a Classification for the Portion Mark.

Deployment Guide www.fortra.com page: 58

 Apply Portion Marking /

4. Click OK.
The Portion Mark appears in your document. If an Alternate Label has been defined
for this Value, it appears in your text.

Delete the Portion Marking

1. Place your cursor inside the brackets.
2. Right-click and select Delete Portion Mark.
3. Click Yes to confirm that you want to delete the Portion Mark.

Edit the Portion Marking

1. Place your cursor inside the brackets.
2. Right-click and select Edit Portion Mark.
3. Make the necessary changes.
4. Click OK.

Deployment Guide www.fortra.com page: 59

 Apply Portion Marking / Apply Portion Marking to Microsoft PowerPoint documents

Apply Portion Marking to Microsoft PowerPoint

documents
1. Place your cursor where you would like the Portion Mark to be applied.
2. Select Add Portion Mark.
3. Use the drop down menu to select the values you want to apply for the Portion Mark.
4. Click OK to apply this Portion Mark.

The Portion Mark appears in your slide or notes. If an Alternate Label has been
defined for this Value, it appears as well.
NOTE: To delete the Portion Mark, place your cursor inside the brackets. Then click the
Portion Mark symbol in the Titus Ribbon Group, and select Delete Portion Mark.Click
Yes to confirm that you want to delete the Portion Mark.

Edit the Portion Marking in Microsoft PowerPoint documents

1. Place your cursor inside the brackets. Then click on the Portion Mark symbol in the
Titus Ribbon Group.
2. Select Edit Portion Mark in the drop down menu.
The Portion Marking window appears.
3. Use the drop down menu to select the values you want to apply for this Portion Mark.
4. Click OK when you have made the required changes.

Deployment Guide www.fortra.com page: 60

 Use Redaction in Microsoft Outlook /

Use Redaction in Microsoft Outlook

The Do it Yourself Redaction feature allows you to perform the following actions:

l Redact text from the message body.

l Redact in Line images from the message body.
In Line graphics are replaced by a black shape when redacted. Images that are not
set as “Inline with Text” in the message body are removed from the email message
when redacted.
l Redact a hyperlink from the message body. The entire hyperlink is redacted. A
portion of the hyperlink cannot be redacted.

To Redact content:

1. Select the content in the email message that cannot be shared with the message
recipients.
2. Click the Redact button.

The selected information will be replaced by a black rectangle.

The redaction size is dependent on the font size or graphic size that is selected for
redaction.

In-line graphics are replaced by a black shape when redacted. Redacted images that are not
set as “In Line with Text” in the message body are removed from the email message.

If you want to include the redacted image shape in the email message you must set the
image to be “In Line with Text”.

Redaction can be undone using the Undo function in Microsoft Outlook. The Undo
procedure must be performed twice. The first Undo procedure displays the redacted text as
stars (*). The second Undo procedure displays the original text. Once the message is Saved
or Sent, redaction cannot be undone. The user must return to the original un-redacted
message to retrieve the content.

If the selected content contains advanced formatting properties it may not be possible to
redact the entire the selection in one redaction procedure. If a portion of the selected
content is not redacted by the original operation re-select the content and perform the
redaction again.

If the selected content contains advanced formatting properties it may not be possible to
redact the entire the selection in one redaction procedure. If a portion of the selected

Deployment Guide www.fortra.com page: 61

 Use Redaction in Microsoft Outlook /

content is not redacted by the original operation re-select the content and perform the
redaction again.

Deployment Guide www.fortra.com page: 62

 Determine if a Signed Trusted Label has already been applied /

Determine if a Signed Trusted Label

has already been applied
1. Click the Advanced button on the Ribbon. The following menu appears.

2. Select Signed Trusted Labels.

If there is no trusted label applied, the following appears:

If there is a signed trust label applied, the following appears:

Deployment Guide www.fortra.com page: 63

 Determine if a Signed Trusted Label has already been applied / Apply Signed Trusted Labels

If there is an invalid signed trust label applied, the following appears:

NOTE:The exact text displayed for each of these scenarios can be customized,
and may be different in your system.

3. Click Close.

Apply Signed Trusted Labels

1. Click the Advanced button on the ribbon.
2. Select Apply Signed Trusted Labels. A dialog box opens saying that you must close
the document to apply a signed label.
3. Close the document.
4. Click Yes to proceed.

If the label is applied successfully, appears in the ribbon of the document.

Deployment Guide www.fortra.com page: 64

 Prevent Save and Send during a service failure / Prevent Microsoft Outlook from sending emails

Prevent Save and Send during a

service failure
You can create Registry Key settings to notify users that the Data Classification Suite is not
working due to a Service failure. By default, the Health Monitor Service status is checked
every 20 seconds. For more information on the Health Monitor Service Setting, see Fortra's
Data Classification Suite (DCS) Administration Console (On-premises) User Guide.

Prevent Microsoft Outlook from sending emails

To prevent Microsoft Outlook from sending emails when the Health Service is down or in a
faulted state, open the Registry and go to HKEY_LOCAL_
MACHINE\SOFTWARE\Policies\Titus\Message Classification for Microsoft Outlook.
Change the value of AllowUnrestrictedMicrosoftOutlookFunctionality to 0.

The default text is: "This operation has been prevented because the Titus Service is not
responding"

If you want to change this message:

1. Create the following Registry Key as a string type:

MicrosoftOutlookFunctionalityRestrictedMessage.
2. Add the customized message as the value.
You can customize the text only for this message. You cannot edit the font, size,
color, and background.

Deployment Guide www.fortra.com page: 65

 Logging information / Enable Windows Installer logging

Logging information
The installer and running software create various log files that you can use to troubleshoot
issues. This section describes the types and location of the various logs available.

Enable Windows Installer logging

To enable Windows Installer logging, open the registry and create the following path and
keys:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging
Value: voicewarmupx

Client Install Debug Log location

The location of Installer logs varies based on the method used to install the DCS for
Windows software.

Installation Method Log Location

By ePO %windir%\temp\
Running TitusClassificationSetup.exe %temp%\titusclassification*.log
Running the individual MSI’s %temp%\msi*.log

Logfile filename patterns for various installation files are:

Installation File Log File Name

TitusClassificationSetup.exe Fortra_Data_Classification_<year month day time>.log
Titus_PEP_ Fortra_Data_Classification_<year month day time>_xxx_
PrerequisiteChecker.msi PrerequisiteCheckerInstall.log
All other Titus msi’s Fortra_Data_Classification_<year month day time>_xxx_
Classification_setup_xXX.log

View log files for a Client application

Use DCS for Office or DCS for Outlook

Deployment Guide www.fortra.com page: 66

 Logging information / Enter an annotation in a Client application log file

1. From the ribbon, click , and click About.

NOTE:The Ribbon Group or the One Click Ribbon Group must be enabled so the
About Dialog is accessible. The Ribbon Group is enabled by default.

2. Press Alt + L if the View Log button is disabled.

Use DCS for Desktop

1. Right-click a file and select About.
2. Press Alt + L if the View Log button is disabled.

Enter an annotation in a Client application log file

The Annotation is added into the client application DebugLog file to indicate a specific point
in the log. This is used when you are tracking an event and want to locate it later.

This annotation feature is available only for DCS for Outlook and DCS for Office.

1. From the ribbon, click , and click About.

NOTE:The Ribbon Group or the One Click Ribbon Group must be enabled so the
About Dialog is accessible. The Ribbon Group is enabled by default.

2. Press Alt + A.
3. In the Add Annotation to Log field, enter the annotation.
4. Click Annotate.

Debug Log locations on client machines

Log names File name Location
Titus Services Enterprise.Client.log C:\ProgramData\TITUS
Debug Log

Deployment Guide www.fortra.com page: 67

 Logging information / Debug Log locations on client machines

DCS for Message Classification C:\Users\<username>\AppData\Local\Titus

OutlookDebug for Microsoft
Log Outlook.htm
DCS for Office Document C:\Users\<username>\AppData\Local\Titus
Debug Log Classification for
Word.htm

Document
Classification for
PowerPoint.htm

Document
Classification for
Excel.htm
DCS for Classification for C:\Users\<username>\AppData\Local\Titus
Desktop Log Desktop.htm
Location

Deployment Guide www.fortra.com page: 68

 Contacting Fortra /

Contacting Fortra
Please contact Fortra for questions or to receive information about Data Classification Suite
for Windows (On-premises).

For additional resources, or to contact Technical Support, visit our website at

https://dataclassification.fortra.com/ or support.fortra.com. You can email Support at
[email protected].

Gather and organize as much information as possible about the problem including job/error
logs, screen shots or anything else to document the issue.

Deployment Guide www.fortra.com page: 69