Dell Dp Endpt Security Suite Enterprise Data Endpoint Advanced Installation Guide V1.7.1 User Manual Install En Us

User Manual: Dell dell-dp-endpt-security-suite-enterprise - Endpoint Security Suite Enterprise Advanced Installation Guide v1.7.1

Open the PDF directly: View PDF PDF.
Page Count: 168 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Dell Data Security
Endpoint Security Suite Enterprise Advanced Installation
Guide v1.7.1
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2018 Dell Inc. All rights reserved.Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may
be trademarks of their respective owners.
Registered trademarks and trademarks used in the Dell Encryption, Endpoint Security Suite Pro, Endpoint Security Suite Enterprise, and
Data Guardian suite of documents: DellTM and the Dell logo, Dell PrecisionTM, OptiPlexTM, ControlVaultTM, LatitudeTM, XPS®, and KACETM
are trademarks of Dell Inc. Cylance®, CylancePROTECT, and the Cylance logo are registered trademarks of Cylance, Inc. in the U.S. and
other countries. McAfee® and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. in the US and other countries.
Intel®, Pentium®, Intel Core Inside Duo®, Itanium®, and Xeon® are registered trademarks of Intel Corporation in the U.S. and other
countries. Adobe®, Acrobat®, and Flash® are registered trademarks of Adobe Systems Incorporated. Authen Tec® and Eikon® are
registered trademarks of Authen Tec. AMD® is a registered trademark of Advanced Micro Devices, Inc. Microsoft®, Windows®, and
Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista®, MSN®, ActiveX®, Active Directory®, Access®, ActiveSync®,
BitLocker®, BitLocker To Go®, Excel®, Hyper-V®, Silverlight®, Outlook®, PowerPoint®, OneDrive®, SQL Server®, and Visual C++® are
either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. VMware® is a registered
trademark or trademark of VMware, Inc. in the United States or other countries. Box® is a registered trademark of Box. DropboxSM is a
service mark of Dropbox, Inc. GoogleTM, AndroidTM, GoogleTM ChromeTM, GmailTM, YouTube®, and GoogleTM Play are either trademarks or
registered trademarks of Google Inc. in the United States and other countries. Apple®, Aperture®, App StoreSM, Apple Remote
DesktopTM, Apple TV®, Boot CampTM, FileVaultTM, iCloud®SM, iPad®, iPhone®, iPhoto®, iTunes Music Store®, Macintosh®, Safari®,
and Siri® are either servicemarks, trademarks, or registered trademarks of Apple, Inc. in the United States and/or other countries. GO ID®,
RSA®, and SecurID® are registered trademarks of Dell EMC. EnCaseTM and Guidance Software® are either trademarks or registered
trademarks of Guidance Software. Entrust® is a registered trademark of Entrust®, Inc. in the United States and other countries.
InstallShield® is a registered trademark of Flexera Software in the United States, China, European Community, Hong Kong, Japan, Taiwan,
and United Kingdom. Micron® and RealSSD® are registered trademarks of Micron Technology, Inc. in the United States and other
countries. Mozilla® Firefox® is a registered trademark of Mozilla Foundation in the United States and/or other countries. iOS® is a
trademark or registered trademark of Cisco Systems, Inc. in the United States and certain other countries and is used under license.
Oracle® and Java® are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.
SAMSUNGTM is a trademark of SAMSUNG in the United States or other countries. Seagate® is a registered trademark of Seagate
Technology LLC in the United States and/or other countries. Travelstar® is a registered trademark of HGST, Inc. in the United States and
other countries. UNIX® is a registered trademark of The Open Group. VALIDITYTM is a trademark of Validity Sensors, Inc. in the United
States and other countries. VeriSign® and other related marks are the trademarks or registered trademarks of VeriSign, Inc. or its aliates
or subsidiaries in the U.S. and other countries and licensed to Symantec Corporation. KVM on IP® is a registered trademark of Video
Products. Yahoo!® is a registered trademark of Yahoo! Inc. This product uses parts of the 7-Zip program. The source code can be found at
7-zip.org. Licensing is under the GNU LGPL license + unRAR restrictions (7-zip.org/license.txt).
Endpoint Security Suite Enterprise Advanced Installation Guide
2018 - 01
Rev. A01
Contents
1 Introduction....................................................................................................................................................7
Before You Begin................................................................................................................................................................ 7
Using This Guide................................................................................................................................................................ 8
Contact Dell ProSupport...................................................................................................................................................8
2 Requirements............................................................................................................................................... 10
All Clients........................................................................................................................................................................... 10
All Clients - Prerequisites........................................................................................................................................... 10
All Clients - Hardware..................................................................................................................................................11
All Clients - Localization..............................................................................................................................................11
Encryption Client............................................................................................................................................................... 11
Encryption Client Prerequisites.................................................................................................................................12
Encryption Client Hardware.......................................................................................................................................12
Encryption Client Operating Systems...................................................................................................................... 12
Encryption Client Operating Systems with Deferred Activation...........................................................................12
Encryption External Media Operating Systems...................................................................................................... 13
Full Disk Encryption.......................................................................................................................................................... 13
Full Disk Encryption Client Prerequisites..................................................................................................................14
Full Disk Encryption Client Hardware....................................................................................................................... 14
Full Disk Encryption Client Operating Systems.......................................................................................................15
Server Encryption Client..................................................................................................................................................15
Server Encryption Client Hardware..........................................................................................................................16
Server Encryption Client Operating Systems..........................................................................................................16
Encryption External Media Operating Systems...................................................................................................... 17
Advanced Threat Prevention Client............................................................................................................................... 18
Advanced Threat Prevention Operating Systems.................................................................................................. 18
Advanced Threat Prevention Ports.......................................................................................................................... 18
BIOS Image Integrity Verication..............................................................................................................................19
Advanced Threat Prevention Compatibility.............................................................................................................19
Client Firewall and Web Protection Clients....................................................................................................................21
Client Firewall and Web Protection Client Operating Systems............................................................................. 21
Client Firewall and Web Protection Client Ports.................................................................................................... 22
SED Client.........................................................................................................................................................................22
OPAL Drivers.............................................................................................................................................................. 23
SED Client Hardware................................................................................................................................................. 23
Authentication Options with SED Client................................................................................................................. 24
SED Client International KeyboardsSED Client LocalizationSED Client Operating Systems............................ 25
Advanced Authentication Client.....................................................................................................................................26
Advanced Authentication Client Hardware.............................................................................................................26
Advanced Authentication Client Operating Systems.............................................................................................27
BitLocker Manager Client................................................................................................................................................27
BitLocker Manager Client Hardware....................................................................................................................... 28
BitLocker Manager Client Operating Systems....................................................................................................... 28
Dell Data Security Endpoint Security Suite Enterprise
Contents
3
3 Registry Settings......................................................................................................................................... 29
Encryption Client Registry Settings...............................................................................................................................29
Full Disk Encryption Client Registry Settings............................................................................................................... 33
Advanced Threat Prevention Client Registry Settings................................................................................................34
SED Client Registry Settings..........................................................................................................................................35
BitLocker Manager Client Registry Settings.................................................................................................................37
4 Install Using the Master Installer..................................................................................................................39
Install Interactively Using the Master Installer..............................................................................................................39
Install by Command Line Using the Master Installer....................................................................................................42
5 Uninstall Using the Endpoint Security Suite Enterprise Master Installer...................................................... 45
Uninstall the Endpoint Security Suite Enterprise Master Installer............................................................................. 45
Command Line Uninstallation................................................................................................................................... 45
6 Install Using the Child Installers................................................................................................................... 46
Install Drivers.....................................................................................................................................................................47
Install Encryption Client...................................................................................................................................................47
Command Line Installation........................................................................................................................................ 47
Install Full Disk Encryption Client................................................................................................................................... 49
Command Line Installation........................................................................................................................................49
Install Server Encryption Client......................................................................................................................................50
Install Server Encryption Interactively......................................................................................................................51
Install Server Encryption Using the Command Line.............................................................................................. 54
Activate Server Encryption.......................................................................................................................................56
Install Advanced Threat Prevention Client....................................................................................................................59
Command Line Installation........................................................................................................................................59
Install Web Protection and Firewall................................................................................................................................60
Command Line Installation........................................................................................................................................60
Install SED Management and Advanced Authentication Clients................................................................................62
Command Line Installation........................................................................................................................................63
Install BitLocker Manager Client.................................................................................................................................... 63
Command Line Installation........................................................................................................................................64
7 Uninstall Using the Child Installers............................................................................................................... 65
Uninstall Web Protection and Firewall........................................................................................................................... 66
Command Line Uninstallation...................................................................................................................................66
Uninstall Advanced Threat Prevention..........................................................................................................................66
Command Line Uninstallation...................................................................................................................................66
Uninstall SED and Advanced Authentication Clients...................................................................................................66
Process........................................................................................................................................................................66
Deactivate the PBA................................................................................................................................................... 67
Uninstall SED Client and Advanced Authentication Clients.................................................................................. 67
Uninstall Encryption and Server Encryption Client...................................................................................................... 67
Process........................................................................................................................................................................68
Command Line Uninstallation................................................................................................................................... 68
4Dell Data Security Endpoint Security Suite Enterprise
Contents
Uninstall BitLocker Manager Client................................................................................................................................70
Command Line Uninstallation................................................................................................................................... 70
8 Uninstall Using the Dell Data Security Uninstaller.........................................................................................71
Uninstall Endpoint Security Suite Enterprise.................................................................................................................71
9 Commonly Used Scenarios.......................................................................................................................... 76
Encryption Client, Advanced Threat Prevention, and Advanced Authentication.....................................................77
SED Client (including Advanced Authentication) and Encryption External Media.................................................. 78
BitLocker Manager and Encryption External Media.................................................................................................... 78
BitLocker Manager and Advanced Threat Prevention................................................................................................ 79
10 Provision a Tenant for Advanced Threat Prevention................................................................................... 80
Provision a Tenant............................................................................................................................................................80
11 Congure Advanced Threat Prevention Agent Auto Update........................................................................ 84
12 Pre-Installation Conguration for SED UEFI, and BitLocker Manager.........................................................85
Initialize the TPM............................................................................................................................................................. 85
Pre-Installation Conguration for UEFI Computers.....................................................................................................85
Enable Network Connectivity During UEFI Preboot Authentication...................................................................85
Disable Legacy Option ROMs...................................................................................................................................86
Pre-Installation Conguration to Set Up a BitLocker PBA Partition..........................................................................86
13 Set GPO on Domain Controller to Enable Entitlements...............................................................................87
14 Extract the Child Installers from the Endpoint Security Suite Enterprise Master Installer.......................... 90
15 Congure Key Server for Uninstallation of Encryption Client Activated Against Security Management
Server............................................................................................................................................................. 91
Services Panel - Add Domain Account User.................................................................................................................91
Key Server Cong File - Add User for Security Management Server Communication.......................................... 92
Sample Conguration File......................................................................................................................................... 93
Services Panel - Restart Key Server Service............................................................................................................... 93
Remote Management Console - Add Forensic Administrator....................................................................................93
16 Use the Administrative Download Utility (CMGAd).................................................................................... 95
Use the Administrative Download Utility in Forensic Mode........................................................................................95
Use the Administrative Download Utility in Admin Mode............................................................................................97
17 Congure Server Encryption...................................................................................................................... 99
Enable Server Encryption............................................................................................................................................... 99
Customize Activation Logon Dialog...............................................................................................................................99
Set Encryption External Media Policies.......................................................................................................................100
Suspend an Encrypted Server Instance...................................................................................................................... 100
18 Congure Deferred Activation...................................................................................................................102
Deferred Activation Customization.............................................................................................................................. 102
Dell Data Security Endpoint Security Suite Enterprise
Contents
5
Install the Encryption Client with Deferred Activation...............................................................................................103
Activate the Encryption Client with Deferred Activation.......................................................................................... 103
Troubleshoot Deferred Activation.................................................................................................................................104
Troubleshoot Activation...........................................................................................................................................104
19 Troubleshooting........................................................................................................................................ 106
All Clients - Troubleshooting..........................................................................................................................................106
All Clients - Protection Status.......................................................................................................................................106
Encryption and Server Encryption Client Troubleshooting....................................................................................... 106
Upgrade to the Windows 10 Creators Update......................................................................................................106
Activation on a Server Operating System............................................................................................................. 107
(Optional) Create an Encryption Removal Agent Log File................................................................................... 110
Find TSS Version.......................................................................................................................................................110
Encryption External Media and PCS Interactions................................................................................................. 110
Use WSScan..............................................................................................................................................................110
Use WSProbe............................................................................................................................................................ 114
Check Encryption Removal Agent Status..............................................................................................................115
Advanced Threat Prevention Client Troubleshooting................................................................................................. 116
Find the Product Code with Windows PowerShell...............................................................................................116
Advanced Threat Prevention Provisioning and Agent Communication..............................................................117
BIOS Image Integrity Verication Process............................................................................................................. 119
SED Client Troubleshooting...........................................................................................................................................120
Use the Initial Access Code Policy......................................................................................................................... 120
Create a PBA Log File for Troubleshooting............................................................................................................ 121
Dell ControlVault Drivers................................................................................................................................................122
Update Dell ControlVault Drivers and Firmware................................................................................................... 122
UEFI Computers............................................................................................................................................................. 136
Troubleshoot Network Connection........................................................................................................................ 136
TPM and BitLocker........................................................................................................................................................ 136
TPM and BitLocker Error Codes............................................................................................................................ 136
20 Glossary................................................................................................................................................... 167
6Dell Data Security Endpoint Security Suite Enterprise
Contents
Introduction
This guide details how to install and congure Advanced Threat Prevention, the Encryption client, SED management client, Advanced
Authentication, and BitLocker Manager.
All policy information and their descriptions are found in the AdminHelp.
Before You Begin
1 Install the Security Management Server/Security Management Server Virtual before deploying clients. Locate the correct guide as
shown below, follow the instructions, and then return to this guide.
Dell Security Management Server Installation and Migration Guide
Dell Security Management Server Virtual Quick Start Guide and Installation Guide
Verify that polices are set as desired. Browse through the AdminHelp, available from the ? at the far right of the screen. The
AdminHelp is page-level help designed to help you set and modify policy and understand your options with your Security
Management Server/Security Management Server Virtual.
1
Dell Data Security Endpoint Security Suite Enterprise
Introduction
7
2Provision a Tenant for Advanced Threat Prevention. A tenant must be provisioned in the Dell Server before Advanced Threat
Prevention enforcement of policies becomes active.
3 Thoroughly read the Requirements chapter of this document.
4 Deploy clients to end users.
Using This Guide
Use this guide in the following order.
See Requirements for client prerequisites, computer hardware and software information, limitations, and special registry modications
needed for features.
If needed, see Pre-Installation Conguration for SED UEFI, and BitLocker.
If your clients will be entitled using Dell Digital Delivery (DDD), see Set GPO on Domain Controller to Enable Entitlements.
If installing clients using the Endpoint Security Suite Enterprise master installer, see:
Install Interactively Using the Master Installer
or
Install by Command Line Using the Master Installer
If installing clients using the child installers, the child installer executable les must be extracted from the master installer. See Extract
the Child Installers from the Master Installer, then return here.
Install Child Installers by Command line:
Install Drivers - Download the appropriate drivers and rmware based on your authentication hardware.
Install Encryption Client - use these instructions to install the Encryption client, which is the component that enforces security
policy, whether a computer is connected to the network, disconnected from the network, lost, or stolen.
Install Advanced Threat Prevention Client - use these instructions to install the Advanced Threat Prevention client, which is
next-generation antivirus protection that uses algorithmic science and machine learning to identify, classify, and prevent both
known and unknown cyberthreats from executing or harming endpoints.
Install Web Protection and Firewall - use these instructions to install the optional Web Protection and Firewall features. The
Client Firewall is a stateful rewall that checks all incoming and outgoing trac against its list of rules. Web Protection monitors
web browsing and downloads to identify threats and enforce action set by policy when a threat is detected, based on ratings for
websites.
Install SED Management and Advanced Authentication Clients - use these instructions to install encryption software for SEDs.
Although SEDs provide their own encryption, they lack a platform to manage their encryption and policies. With SED
management, all policies, storage, and retrieval of encryption keys are available from a single console, reducing the risk that
computers are unprotected in the event of loss or unauthorized access.
The Advanced Authentication client manages multiple authentication methods, including PBA for SEDs, Single Sign-on (SSO),
and user credentials such as ngerprints and passwords. In addition, it provides Advanced Authentication capabilities to access
websites and applications.
Install BitLocker Manager Client - use these instructions to install the BitLocker Manager client, designed to improve the
security of BitLocker deployments and to simplify and reduce the cost of ownership.
NOTE:
Most child installers can be installed interactively, but installations are not described in this guide. However, the
Advanced Threat Prevention client child installer can be installed by command line only.
See Commonly Used Scenarios for scripts of our most commonly used scenarios.
Contact Dell ProSupport
Call 877-459-7304, extension 4310039 for 24x7 phone support for your Dell product.
8Dell Data Security Endpoint Security Suite Enterprise
Introduction
Additionally, online support for Dell products is available at dell.com/support. Online support includes drivers, manuals, technical advisories,
FAQs, and emerging issues.
Be sure to help us quickly connect you to the right technical expert by having your Service Tag or Express Service Code available when you
call.
For phone numbers outside of the United States, check Dell ProSupport International Phone Numbers.
Dell Data Security Endpoint Security Suite Enterprise
Introduction
9
Requirements
All Clients
These requirements apply to all clients. Requirements listed in other sections apply to specic clients.
IT best practices should be followed during deployment. This includes, but is not limited to, controlled test environments for initial tests,
and staggered deployments to users.
The user account performing the installation/upgrade/uninstallation must be a local or domain administrator user, which can be
temporarily assigned by a deployment tool such as Microsoft SMS or Dell KACE. A non-administrator user that has elevated privileges is
not supported.
Back up all important data before beginning installation/uninstallation.
Do not make changes to the computer, including inserting or removing external (USB) drives during installation.
Ensure that outbound port 443 is available to communicate with the Security Management Server/Security Management Server
Virtual if your master installer clients will be entitled using Dell Digital Delivery (DDD). The entitlement functionality will not work if port
443 is blocked (for any reason). DDD is not used if installing using the child installers.
Be sure to periodically check www.dell.com/support for the most current documentation and Technical Advisories.
NOTE: The Dell Data Security line of products does not support Windows Insider Preview releases.
All Clients - Prerequisites
The master installer installs the following prerequisites if not already installed on the computer. When using the child installer, you must
install this component before installing the Encryption client.
Prerequisite
Visual C++ 2012 Update 4 or later Redistributable Package (x86 and x64)
Visual C++ 2015 Update 3 or later Redistributable Package (x86 and x64)
Visual C++ 2015 requires Windows Update KB2999226 if installed on Windows 7.
Microsoft .Net Framework 4.5.2 (or later) is required for the Endpoint Security Suite Enterprise master installer and child installer clients.
The installer does not install the Microsoft .Net Framework component.
To verify the version of Microsoft .Net installed, follow these instructions on the computer targeted for installation: http://
msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx. To install Microsoft .Net Framework 4.5.2, go to https://
www.microsoft.com/en-us/download/details.aspx?id=42643.
Drivers and rmware for ControlVault, ngerprint readers and smart cards (as shown below) are not included in the Endpoint Security
Suite Enterprise master installer or child installer executable les. The drivers and rmware must be kept up-to-date, and can be
downloaded from http://www.dell.com/support and selecting your computer model. Download the appropriate drivers and rmware
based on your authentication hardware.
• ControlVault
NEXT Biometrics Fingerprint Driver
Validity Fingerprint Reader 495 Driver
O2Micro Smart Card Driver
2
10 Dell Data Security Endpoint Security Suite Enterprise
Requirements
If installing on non-Dell hardware, download updated drivers and rmware from that vendor's website. Installation instructions for
ControlVault drivers are provided in Update Dell ControlVault Drivers and Firmware.
All Clients - Hardware
The following table details the minimum supported computer hardware.
Hardware
Intel Pentium or AMD Processor
500 MB available disk space
2 GB RAM
NOTE: Additional free disk space is required to encrypt the les on the endpoint. This size varies based on policies and size of
drive.
All Clients - Localization
The Encryption, Advanced Threat Prevention, and BitLocker Manager clients are Multilingual User Interface (MUI) compliant and are
localized in the following languages. Full Disk Encryption is only supported with English operating systems. Advanced Threat Prevention
data displayed in the Remote Management Console is English only.
Language Support
EN - English JA - Japanese
ES - Spanish KO - Korean
FR - French PT-BR - Portuguese, Brazilian
IT - Italian PT-PT - Portuguese, Portugal (Iberian)
DE - German
Encryption Client
The client computer must have network connectivity to activate.
To reduce initial encryption time, run the Windows Disk Cleanup Wizard to remove temporary les and any other unnecessary data.
Turn o sleep mode during the initial encryption sweep to prevent an unattended computer from going to sleep. Encryption cannot
occur on a sleeping computer (nor can decryption).
The Encryption client does not support dual boot congurations since it is possible to encrypt system les of the other operating
system, which would interfere with its operation.
The Encryption client now supports Audit Mode. Audit Mode allows administrators to deploy the Encryption client as part of the
corporate image, rather than using a third-party SCCM or similar solutions to deploy the Encryption client. For instructions about how
to install the Encryption client in a corporate image, see http://www.dell.com/support/article/us/en/19/SLN304039.
The Encryption client has been tested and is compatible with McAfee, the Symantec client, Kaspersky, and MalwareBytes. Hard-coded
exclusions are in place in for these anti-virus providers to prevent incompatibilities between anti-virus scanning and encryption. The
Encryption client has also been tested with the Microsoft Enhanced Mitigation Experience Toolkit.
If your organization uses an anti-virus provider that is not listed, see http://www.dell.com/support/article/us/en/19/SLN288353/ or
Contact Dell ProSupport for help.
The TPM is used for sealing the GPK. Therefore, if running the Encryption client, clear the TPM in the BIOS before installing a new
operating system on the client computer.
Dell Data Security Endpoint Security Suite Enterprise
Requirements
11
Operating system re-install is not supported. To re-install the operating system, perform a backup of the target computer, wipe the
computer, install the operating system, then recover the encrypted data following established recovery procedures.
Encryption Client Prerequisites
Encryption Client Hardware
The following table details supported hardware.
Optional Embedded Hardware
TPM 1.2 or 2.0
Encryption Client Operating Systems
The following table details supported operating systems.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional, Ultimate
Windows Embedded Standard 7 with Application Compatibility template (hardware encryption is not supported)
Windows 8: Enterprise, Pro
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows Embedded 8.1 Industry Enterprise (hardware encryption is not supported)
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
VMware Workstation 5.5 and higher
NOTE:
When using UEFI mode, the Secure Hibernation policy is not supported.
Encryption Client Operating Systems with Deferred Activation
Deferred activation allows the Active Directory user account used during activation to be independent of the account used to login to
the endpoint. Instead of the network provider capturing the authentication information, the user instead manually species the Active
Directory-based account when prompted. Once the credentials are entered, the authentication information is securely sent to the Dell
Server which validates it against the congured Active Directory domains. For more information, see http://www.dell.com/support/
article/us/en/19/sln306341.
The following table details supported operating systems with deferred activation.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Home Basic, Home Premium, Enterprise, Professional, Ultimate
Windows Embedded Standard 7 with Application Compatibility template (hardware encryption is not supported)
Windows 8: Home Basic, Home Premium, Enterprise, Pro
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows Embedded 8.1 Industry Enterprise (hardware encryption is not supported)
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
12 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Windows Operating Systems (32- and 64-bit)
VMware Workstation 5.5 and higher
Encryption External Media Operating Systems
The following table details the operating systems supported when accessing media protected by Encryption External Media.
NOTE:
External media must have approximately 55MB available plus open space on the media that is equal to the largest le to be
encrypted to host Encryption External Media.
Windows Operating Systems Supported to Access Encryption External Media-Protected Media (32- and 64-bit)
Windows 7 SP0-SP1: Home Basic, Home Premium, Enterprise, Professional, Ultimate
Windows Embedded Standard 7 with Application Compatibility template (hardware encryption is not supported)
Windows 8: Home Basic, Home Premium, Enterprise, Pro
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows Embedded 8.1 Industry Enterprise (hardware encryption is not supported)
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
Mac Operating Systems Supported to Access Encryption External Media-Protected Media (64-bit kernels)
Mac OS X El Capitan 10.11.6
macOS Sierra 10.12.6
macOS High Sierra 10.13.2 - 10.13.3
Full Disk Encryption
Full Disk Encryption requires activation against a Dell Server running v9.8.2 or later.
Full Disk Encryption requires UEFI boot mode.
The client computer must have network connectivity or access code to activate.
A wired connection is required for the PBA to communicate with the Dell Server.
A SED can not be present on the target computer.
Full Disk Encryption is not supported with the Encryption client in this release. Do not install Full Disk Encryption on a computer on
which the Encryption client is installed.
Full Disk Encryption is not supported with BitLocker or BitLocker Manager. Do not install Full Disk Encryption on a computer on which
BitLocker or BitLocker Manager is installed.
Any NVMe drive that is being leveraged for PBA – The BIOS’ SATA operation must be set to RAID ON, as Dell’s PBA management does
not support AHCI on NVMe drives.
Any NVMe drive that is being leveraged for PBA – The BIOS's boot mode must be UEFI and Legacy option ROMs must be disabled.
Any non-NVMe drive that is being leveraged for PBA – The BIOS’ SATA operation must be set to AHCI, as Dell’s PBA management
does not support RAID with non-NVMe drives.
RAID ON is not supported because access to read and write RAID-related data (at a sector that is not available on a locked non-
NVMe drive) is not accessible at start-up, and cannot wait to read this data until after the user is logged on.
The operating system will crash when switched from RAID ON > AHCI if the AHCI controller drivers are not pre-installed. For
instructions on how to switch from RAID > AHCI (or vice versa), see http://www.dell.com/support/article/us/en/19/SLN306460.
Dell recommends Intel Rapid Storage Technology Driver version 15.2.0.0 or later, with NVMe drives.
Turn o sleep mode during the initial encryption sweep to prevent an unattended computer from going to sleep. Encryption cannot
occur on a sleeping computer (nor can decryption).
Dell Data Security Endpoint Security Suite Enterprise
Requirements
13
The Full Disk Encryption client does not support dual boot congurations since it is possible to encrypt system les of the other
operating system, which would interfere with its operation.
Operating system re-install is not supported. To re-install the operating system, perform a backup of the target computer, wipe the
computer, install the operating system, then recover the encrypted data following established recovery procedures.
In-place operating system upgrade is not supported with Full Disk Encryption installed. Uninstall and decrypt the Full Disk Encryption
client, upgrade to the new operating system, and then re-install the Full Disk Encryption client.
NOTE: Full Disk Encryption must be congured with Encryption Algorithms set to AES 256 and Encryption Mode set to CBC.
Full Disk Encryption Client Prerequisites
Microsoft .Net Framework 4.5.2 (or later) is required for the master installer and child installer clients. The installer does not install the
Microsoft .Net Framework component.
To verify the version of Microsoft .Net installed, follow these instructions on the computer targeted for installation: http://
msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx. To install Microsoft .Net Framework 4.5.2, go to https://
www.microsoft.com/en-us/download/details.aspx?id=42643.
Full Disk Encryption Client Hardware
The following table details supported hardware.
Optional Embedded Hardware
TPM 1.2 or 2.0
Dell Computer Models Supported with UEFI
The following table details Dell computer models supported with UEFI.
Dell Computer Models - UEFI Support
Latitude 5280
Latitude 5480
Latitude 5580
Latitude 7370
Latitude 7380
Latitude E5250
Latitude E5270
Latitude E5285
Latitude E5289 2-in-1
Latitude E5450
Latitude E5470
Latitude E5550
Latitude E5570
Latitude E6440
Latitude E6540
Latitude E7240
Latitude E7250
Latitude E7270
Latitude E7280
Latitude E7350
Latitude 7389 2-in-1
Precision M3510
Precision M3520
Precision M4800
Precision M5510
Precision M5520
Precision M6800
Precision M7510
Precision M7520
Precision M7710
Precision M7720
Precision D5720 All-in-One
Precision T1700
Precision T3420
Precision T3620
Precision T5810
Precision T7810
Precision T7910
XPS 13 9333
XPS 13 9350
XPS 15 9550
Optiplex 3040 Micro, Mini
Tower, Small Form Factor
Optiplex 3046
OptiPlex 3050 All-In-One
OptiPlex 3050 Tower, Small
Form Factor, Micro
Optiplex 5040 Mini Tower,
Small Form Factor
OptiPlex 5050 Tower, Small
Form Factor, Micro
OptiPlex 7020
Optiplex 7040 Micro, Mini
Tower, Small Form Factor
OptiPlex 7050 Tower, Small
Form Factor, Micro
Optiplex 3240 All-In-One
Optiplex 5055 Ryzen CPU
OptiPlex 5250 All-In-One
Precision 5820 Tower
Optiplex 7010
Optiplex 7440 All-In-One
OptiPlex 7450 All-In-One
Precision 7820 Tower
Venue Pro 11 (Models
5175/5179)
Venue Pro 11 (Model 7139)
14 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Dell Computer Models - UEFI Support
Latitude E7440
Latitude E7450
Latitude E7470
Latitude E7480
Latitude 12 Rugged Extreme
(model 7414)
Latitude 12 Rugged Tablet
(Model 7202)
Latitude 7212 Rugged
Extreme Tablet
Latitude 14 Rugged Extreme
(model 7414)
Latitude 14 Rugged (model
5414)
XPS 15 9560 Precision 7920 Rack
Optiplex 9010
Optiplex 9020 Micro, Mini
Tower, Small Form Factor
Optiplex 9020 All-in-One
Optiplex 9030 All-in-One
Optiplex XE2
Full Disk Encryption Client Operating Systems
The following table details supported operating systems.
Windows Operating Systems (64-bit)
Windows 10: Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
Server Encryption Client
Server Encryption is intended for use on computers running in server mode, particularly le servers.
Server Encryption is compatible only with Encryption Enterprise and Endpoint Security Suite Enterprise.
Server Encryption provides the following:
Software encryption
Removable storage encryption
Port control
NOTE:
The server must support port controls.
Server Port Control System policies aect removable media on protected servers, for example, by controlling access and usage
of the server's USB ports by USB devices. USB port policy applies to external USB ports. Internal USB port functionality is not
aected by USB port policy. If USB port policy is disabled, the client USB keyboard and mouse will not work and the user will
not be able to use the computer unless a Remote Desktop Connection is set up before the policy is applied.
Server Encryption is for use on:
File servers with local drives
Virtual Machine (VM) guests running a Server operating system or non-Server operating system as a simple le server
Supported congurations:
Servers equipped with RAID 5 or 10 drives; RAID 0 (striping) and RAID 1 (mirroring) are supported independent of each other.
Servers equipped with Multi TB RAID drives
Servers equipped with drives that can be changed out without shutting down the computer
Dell Data Security Endpoint Security Suite Enterprise
Requirements
15
Server Encryption has been tested and is compatible with McAfee VirusScan, Symantec clients, Kaspersky Anti-Virus, and
MalwareBytes Anti-Malware. Hard-coded exclusions are in place for these anti-virus providers to prevent incompatibilities between
anti-virus scanning and encryption. If your organization uses an anti-virus provider that is not listed, see KB article SLN298707 or
contact Dell ProSupport for help.
Not Supported
Server Encryption is not for use on:
Dell Servers or servers running databases for Dell Server
Server Encryption is not compatible with Encryption Personal or Advanced Authentication.
Server Encryption is not supported with SED Management or BitLocker Manager client.
Server Encryption is not supported on servers that are part of distributed le systems (DFS).
Migration to or from Server Encryption is not supported. Upgrades from Encryption External Media to Server Encryption require that
the previous product or products be uninstalled completely before installing Server Encryption.
VM hosts (A VM Host typically contains multiple VM guests.)
Domain Controllers
Exchange Servers
Servers hosting databases (SQL, Sybase, SharePoint, Oracle, MySQL, Exchange, etc.)
Servers using any of the following technologies:
Resilient le systems
Fluid le systems
Microsoft storage spaces
SAN/NAS network storage solutions
iSCSI connected devices
Deduplication software
Hardware deduplication
Split RAIDs (multiple volumes across a single RAID)
SED drives (RAIDs and NON-RAID)
Auto-logon (Windows OS 7, 8/8.1) for kiosks
Microsoft Storage Server 2012
Server Encryption does not support dual boot congurations since it is possible to encrypt system les of the other operating system,
which would interfere with its operation.
In-place operating system upgrade is not supported with Server Encryption. To upgrade your operating system, uninstall and decrypt
Server Encryption, upgrade to the new operating system, and then re-install Server Encryption.
Additionally, operating system re-installs are not supported. If you want to re-install the operating system, perform a backup of the
target computer, wipe the computer, install the operating system, then recover the encrypted data by following recovery procedures.
For more information about recovering encrypted data, refer to the Recovery Guide.
Server Encryption Client Hardware
Minimum hardware requirements must meet the minimum specications of the operating system.
Server Encryption Client Operating Systems
The following table details supported operating systems.
16 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Home, Enterprise, Professional, Ultimate
Windows 8.0: Enterprise, Pro
Windows 8.1 - Windows 8.1 Update 1: Enterprise Edition, Pro Edition
Windows 10: Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators Update/
Redstone 3)
Supported Server Operating Systems
Windows Server 2008 R2 SP1: Standard Edition, Datacenter Edition, Enterprise Edition, Webserver Edition
Windows Server 2012: Standard Edition, Essentials Edition, Datacenter Edition (Server Core is not supported)
Windows Server 2012 R2: Standard Edition, Essentials Edition, Datacenter Edition(Server Core is not supported)
Windows Server 2016: Standard Edition, Essentials Edition, Datacenter Edition (Server Core is not supported)
Operating Systems Supported with UEFI Mode
Windows 8: Enterprise, Pro
Windows 8.1 - Windows 8.1 Update 1: Enterprise Edition, Pro Edition
Windows 10: Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators Update/
Redstone 3)
NOTE:
On a supported UEFI computer, after selecting Restart from the main menu, the computer restarts and then displays one of two
possible logon screens. The logon screen that appears is determined by dierences in computer platform architecture.
Encryption External Media Operating Systems
The following table details the operating systems supported when accessing media protected by Encryption External Media.
NOTE:
External media must have approximately 55MB available plus open space on the media that is equal to the largest le to be encrypted
to host Encryption External Media.
NOTE:
Windows XP is supported when using Encryption External Media Explorer only.
Windows Operating Systems Supported to Access Encryption External Media-Protected Media (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional, Ultimate, Home Premium
Windows 8: Enterprise, Pro, Consumer
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows 10: Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators Update/
Redstone 3)
Supported Server Operating Systems
Windows Server 2012 R2
Dell Data Security Endpoint Security Suite Enterprise
Requirements
17
Mac Operating Systems Supported to Access Encryption External Media-Protected Media (64-bit kernels)
OS X El Capitan 10.11.6
macOS Sierra 10.12.6
macOS High Sierra 10.13.2 - 10.13.3
Advanced Threat Prevention Client
To complete Advanced Threat Prevention installation when the Security Management Server/Security Management Server Virtual
managing the client is running in Connected Mode (default), the computer must have network connectivity. However, network
connectivity is
not
required for Advanced Threat Prevention installation when the managing Dell Server is running in Disconnected
Mode.
To provision a tenant for Advanced Threat Prevention, the Dell Server must have Internet connectivity.
NOTE: Internet connectivity is not required when the Dell Server is running in Disconnected Mode.
The optional Client Firewall and Web Protection features should
not
be installed on client computers that are managed by Security
Management Server/Security Management Server Virtual running in Disconnected Mode.
Other vendors' antivirus, antimalware, and antispyware applications may conict with the Advanced Threat Prevention client. If
possible, uninstall these applications. Conicting software does not include Windows Defender. Firewall applications are allowed.
If uninstalling other antivirus, antimalware, and antispyware applications is not possible, you must add exclusions to Advanced Threat
Prevention in the Dell Server and also to the other applications. For instructions on how to add exclusions to Advanced Threat
Prevention in the Dell Server, see http://www.dell.com/support/article/us/en/04/SLN300970. For a list of exclusions to add to the
other antivirus applications, see http://www.dell.com/support/article/us/en/19/SLN301134.
Advanced Threat Prevention Operating Systems
The following table details supported operating systems.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional, Ultimate
Windows 8: Enterprise, Pro
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
Windows Server 2008 R2
Windows Server 2012 R2
Windows Server 2016
Advanced Threat Prevention Ports
The Advanced Threat Prevention agents are managed by and report to the management console SaaS platform. Port 443 (https) is
used for communication and must be open on the rewall in order for the agents to communicate with the console. The console is
hosted by Amazon Web Services and does not have any xed IPs. If port 443 is blocked for any reason, updates cannot be downloaded,
so computers may not have the most current protection. Ensure that client computers can access the URLs, as follows.
Use Application
Protocol
Transport
Protocol
Port
Number
Destination Direction
All Communication HTTPS TCP 443 Allow all https trac to *.cylance.com Outbound
For detailed information regarding the URLs being used, refer to: http://www.dell.com/support/article/us/en/19/SLN303898
18 Dell Data Security Endpoint Security Suite Enterprise
Requirements
BIOS Image Integrity Verication
If the Enable BIOS Assurance policy is selected in the Remote Management Console, the Cylance tenant validates a BIOS hash on end user
systems to ensure that the BIOS has not been modied from the Dell factory version, which is a possible attack vector. If a threat is
detected, a notication is passed to the Dell Server and the IT administrator is alerted in the Remote Management Console. For an
overview of the process, see BIOS Image Integrity Verication Process.
NOTE: A custom factory image cannot be used with this feature, as the BIOS has been modied.
Dell Computer Models supported with BIOS Image Integrity Verication
Latitude 3470
Latitude 3570
Latitude 7275
Latitude 7370
Latitude E5270
Latitude E5470
Latitude E5570
Latitude E7270
Latitude E7470
Latitude Rugged 5414
Latitude Rugged 7214 Extreme
Latitude Rugged 7414
OptiPlex 3040
OptiPlex 3240
OptiPlex 5040
OptiPlex 7040
OptiPlex 7440
Precision Mobile Workstation 3510
Precision Mobile Workstation 5510
Precision Workstation 3620
Precision Workstation 7510
Precision Workstation 7710
Precision Workstation T3420
Venue 10 Pro 5056
Venue Pro 5855
Venue XPS 12 9250
XPS 13 9350
XPS 9550
Advanced Threat Prevention Compatibility
The following table details Advanced Threat Prevention's compatibility with Windows, Mac, and Linux.
n/a - Technology does not apply to this platform.
Blank eld - Policy is not supported with Endpoint Security Suite Enterprise.
Features Policies Windows macOS Linux
File Actions
Auto Quarantine (Unsafe) x x x
Auto Quarantine
(Abnormal) x x x
Auto Upload x x x
Policy Safe List x x x
Memory Actions
Memory Protection x x x
Exploitation
Dell Data Security Endpoint Security Suite Enterprise
Requirements
19
Features Policies Windows macOS Linux
Stack Pivot x x x
Stack Protect x x x
Overwrite Code x n/a
RAM Scraping x n/a
Malicious Payload x
Process Injection
Remote Allocation of
Memory
x x n/a
Remote Mapping of
Memory
x x n/a
Remote Write to Memory x x n/a
Remote Write PE to
Memory x n/a n/a
Remote Overwrite Code x n/a
Remote Unmap of
Memory
x n/a
Remote Thread Creation x x
Remote APC Scheduled x n/a n/a
DYLD Injection x x
Escalation
LSASS Read x n/a n/a
Zero Allocate x x
Protection Settings
Execution Control x x x
Prevent service shutdown
from device
x x
Kill unsafe running
processes and their sub
processes
x x x
Background Threat
Detection
x x x
Watch for New Files x x x
Maximum archive le size
to scan
x x x
Exclude Specic Folders x x x
Copy File Samples x
Application Control
Change Window x x
Folder Exclusions x
20 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Features Policies Windows macOS Linux
Agent Settings
Enable auto-upload of log
les
x x x
Enable Desktop
Notications
x
Script Control
Active Script x
Powershell x
Oce Macros x n/a
Block Powershell console
usage
x
Approve scripts in these
folders (and subfolders)
x
Logging Level x
Self Protection Level x
Auto Update x
Run a Detection (from
Agent UI)
x
Delete Quarantined (Agent
UI and Console UI)
x
Disconnected Mode x x
Detailed Threat Data x
Certicate Safe List x x n/a
Copy malware samples x x x
Proxy Settings x x x
Manual Policy Check
(Agent UI)
x x
Client Firewall and Web Protection Clients
To successfully install Client Firewall and Web Protection, the computer must have network connectivity.
Uninstall other vendors' anti-virus, anti-malware, anti-spyware, and rewall applications before installing the Client Firewall and Web
Protection clients to prevent installation failures. Conicting software does not include Windows Defender and Endpoint Security Suite
Enterprise.
The Web Protection feature is supported with Internet Explorer only.
Client Firewall and Web Protection Client Operating Systems
The following table details supported operating systems.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional, Ultimate
Windows 8: Enterprise, Pro
Dell Data Security Endpoint Security Suite Enterprise
Requirements
21
Windows Operating Systems (32- and 64-bit)
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1703 (Creators
Update/Redstone 2)
Client Firewall and Web Protection Client Ports
To ensure that Client Firewall and Web Protection clients receive the most current Client Firewall and Web Protection updates, ports
443 and 80 must be available for the client to communicate with the various destination servers. If the ports are blocked for any reason,
anti-virus signature updates (DAT les) cannot be downloaded, so computers may not have the most current protection. Ensure that
client computers can access the URLs, as follows.
Use Application
Protocol
Transport
Protocol
Port Number Destination Direction Notes
Reputation
Service
SSL TCP 443 tunnel.web.trustedsource.org Outbound
Reputation
Service Feedback
SSL TCP 443 gtifeedback.trustedsource.or
g
Outbound
URL Reputation
Database Update
HTTP TCP 80 list.smartlter.com Outbound
URL Reputation
Lookup
SSL TCP 443 tunnel.web.trustedsource.org Outbound
SED Client
The computer must have a wired network connection to successfully install SED management.
IPv6 is not supported.
Be prepared to shut down and restart the computer after you apply policies and are ready to begin enforcing them.
Computers equipped with self-encrypting drives cannot be used with HCA cards. Incompatibilities exist that prevent the provisioning of
the HCA. Dell does not sell computers with self-encrypting drives that support the HCA module. This unsupported conguration would
be an after-market conguration.
If the computer targeted for encryption is equipped with a self-encrypting drive, ensure that the Active Directory option, User Must
Change Password at Next Logon, is disabled. Preboot Authentication does not support this Active Directory option.
Dell recommends that you do not change the authentication method after the PBA has been activated. If you must switch to a dierent
authentication method, you must either:
Remove all the users from the PBA.
or
Deactivate the PBA, change the authentication method, and then re-activate the PBA.
IMPORTANT:
Due to the nature of RAID and SEDs, SED management does not support RAID. The issue with RAID=On with SEDs is that RAID
requires access to the disk to read and write RAID-related data at a high sector not available on a locked SED from start and cannot
wait to read this data until after the user is logged on. Change the SATA operation in the BIOS from RAID=On to AHCI to resolve
the issue. If the operating system does not have the AHCI controller drivers pre-installed, the operating system will blue screen
when switched from RAID=On to AHCI.
Conguration of self-encrypting drives for Dell’s SED management dier between NVMe and non-NVMe (SATA) drives, as follows.
Any NVMe drive that is being leveraged as an SED – The BIOS’ SATA operation must be set to RAID ON, as Dell’s SED
management does not support AHCI on NVMe drives.
22 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Any NVMe drive that is being leveraged as an SED – The BIOS's boot mode must be UEFI and Legacy option ROMs must be
disabled.
Any non-NVMe drive that is being leveraged as an SED – The BIOS’ SATA operation must be set to AHCI, as Dell’s SED
management does not support RAID with non-NVMe drives.
RAID ON is not supported because access to read and write RAID-related data (at a sector that is not available on a locked non-
NVMe drive) is not accessible at start-up, and cannot wait to read this data until after the user is logged on.
The operating system will crash when switched from RAID ON > AHCI if the AHCI controller drivers are not pre-installed. For
instructions on how to switch from RAID > AHCI (or vice versa), see http://www.dell.com/support/article/us/en/19/
SLN306460.
Supported OPAL compliant SEDs require updated Intel Rapid Storage Technology Drivers, located at http://www.dell.com/support/
home/us/en/19/product-support/product/dell-dp-endpt-security-suite-enterprise/drivers. Dell recommends Intel Rapid Storage
Technology Driver version 15.2.0.0 or later, with NVMe drives.
SED Management is not supported with Server Encryption or Advanced Threat Prevention on a server OS.
OPAL Drivers
Supported OPAL compliant SEDs require updated Intel Rapid Storage Technology Drivers, located at http://www.dell.com/support.
SED Client Hardware
OPAL Compliant SEDs
For the most up-to-date list of Opal compliant SEDs supported with the SED management, refer to this KB article: http://
www.dell.com/support/article/us/en/19/SLN296720.
Dell Computer Models Supported with UEFI
The following table details Dell computer models supported with UEFI.
Dell Computer Models - UEFI Support
Latitude 5280
Latitude 5480
Latitude 5580
Latitude 7370
Latitude 7380
Latitude E5250
Latitude E5270
Latitude E5285
Latitude E5289 2-in-1
Latitude E5450
Latitude E5470
Latitude E5550
Latitude E5570
Latitude E6440
Latitude E6540
Latitude E7240
Latitude E7250
Latitude E7270
Latitude E7280
Latitude E7350
Latitude 7389 2-in-1
Latitude E7440
Precision M3510
Precision M3520
Precision M4800
Precision M5510
Precision M5520
Precision M6800
Precision M7510
Precision M7520
Precision M7710
Precision M7720
Precision D5720 All-in-One
Precision T1700
Precision T3420
Precision T3620
Precision T5810
Precision T7810
Precision T7910
XPS 13 9333
XPS 13 9350
XPS 15 9550
XPS 15 9560
Optiplex 3040 Micro, Mini
Tower, Small Form Factor
Optiplex 3046
OptiPlex 3050 All-In-One
OptiPlex 3050 Tower, Small
Form Factor, Micro
Optiplex 5040 Mini Tower,
Small Form Factor
OptiPlex 5050 Tower, Small
Form Factor, Micro
OptiPlex 7020
Optiplex 7040 Micro, Mini
Tower, Small Form Factor
OptiPlex 7050 Tower, Small
Form Factor, Micro
Optiplex 3240 All-In-One
Optiplex 5055 Ryzen CPU
OptiPlex 5250 All-In-One
Precision 5820 Tower
Optiplex 7010
Optiplex 7440 All-In-One
OptiPlex 7450 All-In-One
Precision 7820 Tower
Precision 7920 Rack
Venue Pro 11 (Models
5175/5179)
Venue Pro 11 (Model 7139)
Dell Data Security Endpoint Security Suite Enterprise
Requirements
23
Dell Computer Models - UEFI Support
Latitude E7450
Latitude E7470
Latitude E7480
Latitude 12 Rugged Extreme
(model 7414)
Latitude 12 Rugged Tablet
(Model 7202)
Latitude 7212 Rugged
Extreme Tablet
Latitude 14 Rugged Extreme
(model 7414)
Latitude 14 Rugged (model
5414)
Optiplex 9010
Optiplex 9020 Micro, Mini
Tower, Small Form Factor
Optiplex 9020 All-in-One
Optiplex 9030 All-in-One
Optiplex XE2
NOTE:
Authentication features are supported with UEFI mode on these computers running Windows 8, Windows 8.1, and Windows 10 with
qualied Opal Compliant SEDs. Other computers running Windows 7, Windows 8, Windows 8.1, and Windows 10 support Legacy
Boot mode.
For a list of docking stations and adapters supported with the SED client, see http://www.dell.com/support/article/us/en/19/
sln296720/.
Authentication Options with SED Client
Specic hardware is required, to use smart cards and to authenticate on UEFI computers. Conguration is required to use smart cards
with Preboot Authentication. The following tables show authentication options available by operating system, when hardware and
conguration requirements are met.
Non-UEFI
PBA
Password Fingerprin
t
Contacted
Smart
card
SIPR Card
Windows 7 SP0-
SP1
X1X1 2
Windows 8 X1X1 2
Windows 8.1 X1X1 2
Windows 10 X1X1 2
1. Available when authentication drivers are downloaded from
support.dell.com.
2. Available with a supported OPAL SED.
24 Dell Data Security Endpoint Security Suite Enterprise
Requirements
UEFI
PBA - on supported Dell computers
Password Fingerprin
t
Contacted
Smart
card
SIPR Card
Windows 7
Windows 8 X1X1
Windows 8.1 X1X1
Windows 10 X1X1
1. Available with a supported OPAL SED on supported UEFI computers.
SED Client International Keyboards
The following table lists international keyboards supported with Preboot Authentication on UEFI and non-UEFI computers.
International Keyboard Support - UEFI
DE-CH - Swiss German
DE-FR - Swiss French
International Keyboard Support - Non-UEFI
AR - Arabic (using Latin letters)
DE-CH - Swiss German
DE-FR - Swiss French
SED Client Localization
The SED and Advanced Authentication clients are Multilingual User Interface (MUI) compliant and are localized the following languages.
UEFI Mode and Preboot Authentication are supported in the following languages except Russian, Traditional Chinese, or Simplied Chinese.
Language Support
EN - English KO - Korean
FR - French ZH-CN - Chinese, Simplied
IT - Italian ZH-TW - Chinese, Traditional/Taiwan
DE - German PT-BR - Portuguese, Brazilian
ES - Spanish PT-PT - Portuguese, Portugal (Iberian)
Dell Data Security Endpoint Security Suite Enterprise
Requirements
25
Language Support
JA - Japanese RU - Russian
SED Client Operating Systems
The following table details the supported operating systems.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional (supported with Legacy Boot mode but not UEFI)
NOTE:
Legacy Boot mode is supported on Windows 7. UEFI is not supported on Windows 7.
NVMe self-encrypting drives are not supported with Windows 7.
Windows 8: Enterprise, Pro,
Windows 8.1: Enterprise Edition, Pro Edition
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
Advanced Authentication Client
Advanced Authentication features are available only when Preboot Authentication is enabled. When using Advanced Authentication,
users will be securing access to the computer using advanced authentication credentials that are managed and enrolled using
Advanced Authentication. Advanced Authentication will be the primary manager of the authentication credentials for Windows Sign-in,
including Windows password, ngerprint, and smart cards. Picture password, PIN, and ngerprint credentials enrolled using the
Microsoft Operating System will not be recognized at Windows Sign-in.
To continue using the Microsoft Operating System to manage user credentials, do not install Advanced Authentication or uninstall it.
An SED does not require a TPM to provide Advanced Authentication or encryption.
NOTE: PBA authentication methods cannot be changed between Password and SmartCard when the user account exists
within the PBA.
Advanced Authentication Client Hardware
The following table details supported authentication hardware.
Fingerprint and Smart Card Readers
Validity VFS495 in Secure Mode
ControlVault Swipe Reader
UPEK TCS1 FIPS 201 Secure Reader 1.6.3.379
Authentec Eikon and Eikon To Go USB Readers
Contactless Cards
Contactless Cards using Contactless Card Readers built-in to specied Dell laptops
26 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Smart Cards
PKCS #11 Smart Cards using the ActivIdentity client
NOTE:
The ActivIdentity client is not pre-loaded and must be installed separately.
CSP Cards
Common Access Cards (CACs)
Class B/SIPR Net Cards
The following table details Dell computer models supported with SIPR Net cards.
Dell Computer Models - Class B/SIPR Net Card Support
Latitude E6440
Latitude E6540
Precision M2800
Precision M4800
Precision M6800
Latitude 14 Rugged Extreme
Latitude 12 Rugged Extreme
Latitude 14 Rugged
Advanced Authentication Client Operating Systems
Windows Operating Systems
The following table details supported operating systems.
Windows Operating Systems (32- and 64-bit)
Windows 7 SP0-SP1: Enterprise, Professional, Ultimate
Windows 8: Enterprise, Pro
Windows 8.1 Update 0-1: Enterprise Edition, Pro Edition
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
NOTE: UEFI mode is not supported on Windows 7.
BitLocker Manager Client
Consider reviewing Microsoft BitLocker requirements if BitLocker is not yet deployed in your environment,
Ensure that the PBA partition is already set up. If BitLocker Manager is installed before the PBA partition is set up, BitLocker cannot be
enabled and BitLocker Manager will not be operational. See Pre-Installation Conguration to Set Up a BitLocker PBA Partition.
A Security Management Server/Security Management Server Virtual is required to use BitLocker Manager.
Ensure a signing certicate is available within the database. For more information, see http://www.dell.com/support/article/us/en/19/
sln307028.
The keyboard, mouse, and video components must be directly connected to the computer. Do not use a KVM switch to manage
peripherals as the KVM switch can interfere with the computer's ability to properly identify hardware.
Turn on and enable the TPM. BitLocker Manager will take ownership of the TPM and will not require a reboot. However, if a TPM
ownership already exists, BitLocker Manager will begin the encryption setup process (no restart is required). The point is that the TPM
must be "owned" and enabled.
The BitLocker Manager client will use the approved AES FIPS validated algorithms if FIPS mode is enabled for the GPO security setting
"System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" on the device and you manage that device
via our product. We do not force this mode as default for BitLocker-encrypted clients because Microsoft now suggests customers not
use their FIPS validated encryption due to numerous issues with application compatibility, recovery, and media encryption: http://
blogs.technet.com.
BitLocker Manager is not supported with Server Encryption or Advanced Threat Prevention on a server OS.
Dell Data Security Endpoint Security Suite Enterprise
Requirements
27
BitLocker Manager Client Hardware
The following table details supported hardware.
Optional Embedded Hardware
TPM 1.2 or 2.0
BitLocker Manager Client Operating Systems
The following table details supported operating systems.
Windows Operating Systems
Windows 7 SP0-SP1: Enterprise, Ultimate (32- and 64-bit)
Windows 8: Enterprise (64-bit)
Windows 8.1: Enterprise Edition, Pro Edition (64-bit)
Windows 10: Home, Education, Enterprise, Pro Version 1607 (Anniversary Update/Redstone 1) through Version 1709 (Fall Creators
Update/Redstone 3)
Windows Server 2008 R2: Standard Edition, Enterprise Edition (64-bit)
Windows Server 2012 R2: Standard Edition, Enterprise Edition (64-bit)
Windows Server 2016
Windows updates KB3133977 and KB3125574 must not be installed if installing BitLocker Manager on Windows 7.
28 Dell Data Security Endpoint Security Suite Enterprise
Requirements
Registry Settings
This section details all Dell ProSupport approved registry settings for local client computers, regardless of the reason for the registry
setting. If a registry setting overlaps two products, it will be listed in each category.
These registry changes should be done by Administrators only and may not be appropriate or work in all scenarios.
Encryption Client Registry Settings
If a self-signed certicate is used on the Dell Security Management Server for Windows, certicate trust validation must remain
disabled on the client computer (trust validation is disabled by default with Security Management Server for Windows). Before enabling
trust validation on the client computer, the following requirements must be met.
A certicate signed by a root authority, such as EnTrust or Verisign, must be imported into Security Management Server/Security
Management Server Virtual.
The full chain of trust of the certicate must be stored in the Microsoft keystore on the client computer.
To enable trust validation for the Encryption client, change the value of the following registry entry to 0 on the client computer.
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield]
"IgnoreCertErrors"=DWORD:00000000
0 = Fail if a certicate error is encountered
1= Ignores errors
To use smart cards with Windows Authentication, the following registry value must be set on the client computer.
[HKLM\SOFTWARE\DigitalPersona\Policies\Default\SmartCards]
"MSSmartcardSupport"=DWORD:1
To create an Encryption Removal Agent log le, create the following registry entry on the computer targeted for decryption. See
(Optional) Create an Encryption Removal Agent Log File.
[HKLM\Software\Credant\DecryptionAgent]
"LogVerbosity"=DWORD:2
0: no logging
1: logs errors that prevent the Service from running
2: logs errors that prevent complete data decryption (recommended level)
3: logs information about all decrypting volumes and les
5: logs debugging information
By default, during installation, the system tray icon is displayed. Use the following registry setting to hide the system tray icon for all
managed users on a computer after the original installation. Create or modify the registry setting as follows:
[HKLM\Software\CREDANT\CMGShield]
"HIDESYSTRAYICON"=DWORD:1
3
Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
29
By default, all temporary les in the c:\windows\temp directory are automatically deleted during installation. Deletion of temporary les
speeds initial encryption and occurs before the initial encryption sweep.
However, if your organization uses a third-party application that requires the le structure within the \temp directory to be preserved,
you should prevent this deletion.
To disable temporary le deletion, create or modify the registry setting as follows:
[HKLM\SOFTWARE\CREDANT\CMGShield]
"DeleteTempFiles"=REG_DWORD:0
Not deleting temporary les increases initial encryption time.
The Encryption client displays the length of each policy update delay prompt for ve minutes each time. If the user does not respond to
the prompt, the next delay begins. The nal delay prompt includes a countdown and progress bar, and it displays until the user
responds, or the nal delay expires and the required logo/reboot occurs.
You can change the behavior of the user prompt to begin or delay encryption, to prevent encryption processing following no user
response to the prompt. To do this, set the registry the following registry value:
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield]
"SnoozeBeforeSweep"=DWORD:1
Any non-zero value will change the default behavior to snooze. With no user interaction, encryption processing will be delayed up to the
number of congurable allowed delays. Encryption processing begins when the nal delay expires.
Calculate the maximum possible delay as follows (a maximum delay would involve the user never responding to a delay prompt, each of
which displays for 5 minutes):
(NUMBER OF POLICY UPDATE DELAYS ALLOWED × LENGTH OF EACH POLICY UPDATE DELAY) + (5 MINUTES × [NUMBER OF
POLICY UPDATE DELAYS ALLOWED - 1])
Use the following registry setting to have the Encryption client poll the Security Management Server/Security Management Server
Virtual for a forced policy update. Create or modify the registry setting as follows:
[HKLM\SOFTWARE\Credant\CMGShield\Notify]
"PingProxy"=DWORD value:1
The registry setting will automatically disappear when done.
Use the following registry settings to either allow the Encryption client to send an optimized inventory to the Security Management
Server/Security Management Server Virtual, send a full inventory to the Security Management Server/Security Management Server
Virtual, or to send a full inventory for all activated users to the Security Management Server/Security Management Server Virtual.
Send Optimized Inventory to Security Management Server/Security Management Server Virtual:
Create or modify the registry setting as follows:
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield]
"OnlySendInvChanges"=REG_DWORD:1
If no entry is present, optimized inventory is sent to the Security Management Server/Security Management Server Virtual.
Send Full Inventory to Security Management Server/Security Management Server Virtual:
Create or modify the registry setting as follows:
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield]
30 Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
"OnlySendInvChanges"=REG_DWORD:0
If no entry is present, optimized inventory is sent to the Security Management Server/Security Management Server Virtual.
Send Full Inventory for All Activated Users
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield]
"RefreshInventory"=REG_DWORD:1
This entry is deleted from the registry as soon as it is processed. The value is saved in the vault, so even if the computer is rebooted
before the inventory upload takes place, the Encryption client still honors this request the next successful inventory upload.
This entry supersedes the OnlySendInvChanges registry value.
Slotted Activation is a feature that allows you to spread activations of clients over a set time period in order to ease Security
Management Server/Security Management Server Virtual load during a mass deployment. Activations are delayed based on
algorithmically generated time slots to provide a smooth distribution of activation times.
For users requiring activation through VPN, a slotted activation conguration for the client may be required, to delay initial activation for
long enough to allow time for the VPN client to establish a network connection.
These registry entries require a restart of the computer for the updates to take eect.
Slotted Activation
To enable or disable this feature, create a DWORD with the name SlottedActivation under the following parent key:
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\]
Activation Slot
To enable or disable this feature, create a subkey with the name ActivationSlot under the following parent key:
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\]
Activation Slot - a string that denes the period within which the Dell Encryption client will attempt to activate with the Security
Management Server/Security Management Server Virtual. These values are dened in seconds, and the syntax is dened by
<lowervalue>,<uppervalue>. An example would be 120,300. This means that the Encryption client will attempt to activate at a
random time between 2 minutes and 5 minutes after user login.
Calendar Repeat
To enable or disable this feature, create a subkey with the name CalRepeat under the following parent key:
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\ActivationSlot]
CalRepeat - A DWORD that denes the time period in seconds that the activation slot interval occurs. Use this setting to
override the time period in seconds that the activation slot interval occurs. 25200 seconds are available for slotting activations
during a seven-hour period. The default setting is 86400 seconds, which represents a daily repeat. The suggested decimal value
is 600, which represents 10 minutes.
Slot Interval
To enable or disable this feature, create a subkey with the name SlotInterval under the following parent key:
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\ActivationSlot]
Slot Interval - A string value that denes the intervals between slot activations. The suggested setting is 45,120. This represents
activation time being randomly assigned between 45 and 120 seconds.
Missed Threshold
To enable or disable this feature, create a subkey with the name MissThreshold under the following parent key:
Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
31
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\ActivationSlot]
MissThreshold - a DWORD value that contains a positive integer that denes the number of attempts to activate before a log
o is required. If the MissThreshold is reached, activation attempts will cease until the next login for the unactivated user. The
count for MissThreshold is always reset on logo.
The following registry keys collect slotted activation user data:
[HKCU/Software/CREDANT/ActivationSlot] (per-user data)
Deferred time to attempt the slotted activation, which is set when the user logs onto the network for the rst time after slotted
activation is enabled. The activation slot is recalculated for each activation attempt.
[HKCU/Software/CREDANT/SlotAttemptCount] (per-user data)
Number of failed or missed attempts, when the time slot arrives and activation is attempted but fails. When this number
reaches the value set in ACTIVATION_SLOT_MISSTHRESHOLD, the computer attempts one immediate activation upon
connecting to the network.
To detect unmanaged users on the client computer, set the following registry value on the client computer:
[HKLM\SOFTWARE\Credant\CMGShield\ManagedUsers\]
"UnmanagedUserDetected"=DWORD value:1
Detect unmanaged users on this computer=1
Do not detect unmanaged users on this computer=0
To enable silent automatic reactivation in the rare case that a user becomes deactivated, the following registry value must be set on the
client computer.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CMGShield]
"AutoReactivation"=DWORD:00000001
0=Disabled (default)
1=Enabled
System Data Encryption (SDE) is enforced based on the policy value for SDE Encryption Rules. Additional directories are protected by
default when the SDE Encryption Enabled policy is Selected. For more information, search "SDE Encryption Rules" in AdminHelp. When
the Encryption client is processing a policy update that includes an active SDE policy, the current user prole directory is encrypted by
default with the SDUser key (a User key) rather than the SDE key (a Device key). The SDUser key is also used to encrypt les or
folders that are copied (not moved) into a user directory that is not a encrypted with SDE.
To disable the SDUser key and use the SDE key to encrypt these user directories, create the following registry entry on the computer:
[HKEY_LOCAL_MACHINE\SOFTWARE\Credant\CMGShield]
"EnableSDUserKeyUsage"=DWORD:00000000
If this registry key is not present or is set to anything other than 0, the SDUser key will be used to encrypt these user directories.
For more information about SDUser, see www.dell.com/support/article/us/en/19/SLN304916
Setting the registry entry, EnableNGMetadata, if issues occur related with Microsoft updates on computers with Common key-
encrypted data or with encrypting, decrypting, or unzipping large numbers of les within a folder.
Set the EnableNGMetadata registry entry in the following location:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CmgShieldFFE]
32 Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
"EnableNGMetadata" = DWORD:1
0=Disabled (default)
1=Enabled
The non-domain activation feature can be enabled by contacting Dell ProSupport and requesting instructions.
Full Disk Encryption Client Registry Settings
This section details all Dell ProSupport approved registry settings for local client computers, regardless of the reason for the registry
setting. If a registry setting overlaps two products, it will be listed in each category.
These registry changes should be done by Administrators only and may not be appropriate or work in all scenarios.
To set the retry interval when the Security Management Server/Security Management Server Virtual is unavailable to communicate
with the Full Disk Encryption client, add the following registry value.
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
"CommErrorSleepSecs"=DWORD:300
This value is the number of seconds the Full Disk Encryption client waits to attempt to contact the Security Management Server/
Security Management Server Virtual if it is unavailable to communicate with the Full Disk Encryption client. The default is 300 seconds
(5 minutes).
If a self-signed certicate is used on the Security Management Server/Security Management Server Virtual for Full Disk Encryption
management, SSL/TLS trust validation must remain disabled on the client computer (SSL/TLS trust validation is disabled by default
with Full Disk Encryption management). Before enabling SSL/TLS trust validation on the client computer, the following requirements
must be met.
A certicate signed by a root authority, such as EnTrust or Verisign, must be imported into Security Management Server/Security
Management Server Virtual.
The full chain of trust of the certicate must be stored in the Microsoft keystore on the client computer.
To enable SSL/TLS trust validation for Full Disk Encryption management, change the value of the following registry entry to 0 on
the client computer.
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
"DisableSSLCertTrust"=DWORD:0
0 = Enabled
1 = Disabled
To determine if the PBA is activated, ensure that the following value is set:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters]
"PBAIsActivated"=DWORD (32-bit):1
A value of 1 means that the PBA is activated. A value of 0 means the PBA is not activated.
NOTE: Manually deleting this key can create unintended results for users syncing with the PBA resulting in the need for
manual recovery.
The Security Server host may be changed from the original installation location if needed. The host information is read by the client
computer every time a policy poll occurs. Change the following registry value on the client computer:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent]
"ServerHost"=REG_SZ:<newname>.<organization>.com
Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
33
The Security Server port may be changed from the original installation location if needed. This value is read by the client computer
every time a policy poll occurs. Change the following registry value on the client computer:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent]
ServerPort=REG_SZ:8888
(With Preboot Authentication only) If you do not want the Advanced Authentication client to change the services associated with
smart cards and biometric devices to a startup type of "automatic", disable the service startup feature. Disabling this feature also
suppresses warnings associated with the required services not running.
When disabled, Advanced Authentication will not attempt to start these services:
SCardSvr - Manages access to smart cards read by the computer. If this service is stopped, this computer will be unable to read
smart cards. If this service is disabled, any services that explicitly depend on it will fail to start.
SCPolicySvc - Allows the system to be congured to lock the user desktop upon smart card removal.
WbioSrvc - The Windows biometric service gives client applications the ability to capture, compare, manipulate, and store biometric
data without gaining direct access to any biometric hardware or samples. The service is hosted in a privileged SVCHOST process.
By default, if the registry key does not exist or the value is set to 0, this feature is enabled.
[HKLM\SOFTWARE\DELL\Dell Data Protection]
SmartCardServiceCheck=REG_DWORD:0
0 = Enabled
1 = Disabled
To suppress all Toaster notications from the Encryption Management Agent, the following registry value must be set on the client
computer.
[HKEY_LOCAL_MACHINE\SOFTWARE\Dell\Dell Data Protection]
"PbaToastersAllowClose" =DWORD:1
0=Enabled (default)
1=Disabled
Advanced Threat Prevention Client Registry Settings
To have the Advanced Threat Prevention plugin monitor HKLM\SOFTWARE\Dell\Dell Data Protection for changes to the LogVerbosity
value, and update the client log level accordingly, set the following value.
[HKLM\SOFTWARE\Dell\Dell Data Protection]
"LogVerbosity"=dword:<see below>
Dump: 0
Fatal: 1
Error 3
Warning 5
Info 10
Verbose 12
34 Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
Trace 14
Debug 15
The registry value is checked when the ATP service starts or whenever the value changes. If the registry value does not exist, there will
be no change to the logging level.
Use this registry setting for testing/debugging only, as this registry setting controls log verbosity for other components, including the
Encryption client and Encryption Management Agent.
Compatibility Mode allows applications to run on the client computer while Memory Protection or Memory Protection and Script
Control policies are enabled. Enabling compatibility mode requires adding a registry value on the client computer.
To enable compatibility mode, follow these steps:
a In the Remote Management Console, disable the Memory Protection Enabled policy. If the Script Control policy is enabled, disable
it.
b Add the CompatibilityMode registry value.
1 Using the Registry Editor on the client computer, go to HKEY_LOCAL_MACHINE\SOFTWARE\Cylance\Desktop.
2 Right-click Desktop, click Permissions, then take ownership and grant yourself Full Control.
3 Right-click Desktop, then select New > Binary Value.
4 For the name, type CompatibilityMode.
5Open the registry setting and change the value to 01.
6 Click OK, then close Registry Editor.
To add the registry value with a command, you can use one of the following command line options to run on the client computer:
(For one computer) Psexec:
psexec -s reg add HKEY_LOCAL_MACHINE\SOFTWARE\Cylance\Desktop /v CompatibilityMode /t
REG_BINARY /d 01
(For multiple computers) Invoke-Command cmdlet:
$servers = "testComp1","testComp2","textComp3"
$credential = Get-Credential -Credential {UserName}\administrator
Invoke-Command -ComputerName $servers -Credential $credential -ScriptBlock {New-Item -
Path HKCU:\Software\Cylance\Desktop -Name CompatibilityMode -Type REG_BINARY -Value 01}
c In the Remote Management Console, re-enable the Memory Protection Enabled policy. If the Script Control policy was previously
enabled, re-enable it.
SED Client Registry Settings
To set the retry interval when the Security Management Server/Security Management Server Virtual is unavailable to communicate
with the SED client, add the following registry value.
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
"CommErrorSleepSecs"=DWORD:300
This value is the number of seconds the SED client waits to attempt to contact the Security Management Server/Security
Management Server Virtual if it is unavailable to communicate with the SED client. The default is 300 seconds (5 minutes).
If a self-signed certicate is used on the Security Management Server/Security Management Server Virtual for SED management,
SSL/TLS trust validation must remain disabled on the client computer (SSL/TLS trust validation is disabled by default with SED
management). Before enabling SSL/TLS trust validation on the client computer, the following requirements must be met.
A certicate signed by a root authority, such as EnTrust or Verisign, must be imported into Security Management Server/Security
Management Server Virtual.
Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
35
The full chain of trust of the certicate must be stored in the Microsoft keystore on the client computer.
To enable SSL/TLS trust validation for SED management, change the value of the following registry entry to 0 on the client
computer.
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
"DisableSSLCertTrust"=DWORD:0
0 = Enabled
1 = Disabled
To use smart cards with Windows Authentication, the following registry value must be set on the client computer.
[HKLM\SOFTWARE\DigitalPersona\Policies\Default\SmartCards]
"MSSmartcardSupport"=DWORD:1
To use smart cards with Preboot Authentication, the following registry value must be set on the client computer. Also set the
Authentication Method policy to Smart Card in the Remote Management Console, and commit the change.
[HKLM\SOFTWARE\DigitalPersona\Policies\Default\SmartCards]
"MSSmartcardSupport"=DWORD:1
To determine if the PBA is activated, ensure that the following value is set:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters]
"PBAIsActivated"=DWORD (32-bit):1
A value of 1 means that the PBA is activated. A value of 0 means the PBA is not activated.
To set the interval at which the SED client will attempt to contact the Security Management Server/Security Management Server
Virtual when it is unavailable to communicate with the SED client, set the following value on the client computer:
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
"CommErrorSleepSecs"=DWORD Value:300
This value is the number of seconds the SED client waits to attempt to contact the Security Management Server/Security
Management Server Virtual if it is unavailable to communicate with the SED client. The default is 300 seconds (5 minutes).
The Security Server host may be changed from the original installation location if needed. The host information is read by the client
computer every time a policy poll occurs. Change the following registry value on the client computer:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent]
"ServerHost"=REG_SZ:<newname>.<organization>.com
The Security Server port may be changed from the original installation location if needed. This value is read by the client computer
every time a policy poll occurs. Change the following registry value on the client computer:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent]
ServerPort=REG_SZ:8888
The Security Server URL may be changed from the original install location if needed. This value is read by the client computer every
time a policy poll occurs. Change the following registry value on the client computer:
[HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent]
"ServerUrl"=REG_SZ:https://<newname>.<organization>.com:8888/agent
36 Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
(With Preboot Authentication only) If you do not want the Advanced Authentication client to change the services associated with
smart cards and biometric devices to a startup type of "automatic", disable the service startup feature. Disabling this feature also
suppresses warnings associated with the required services not running.
When disabled, Advanced Authentication will not attempt to start these services:
SCardSvr - Manages access to smart cards read by the computer. If this service is stopped, this computer will be unable to read
smart cards. If this service is disabled, any services that explicitly depend on it will fail to start.
SCPolicySvc - Allows the system to be congured to lock the user desktop upon smart card removal.
WbioSrvc - The Windows biometric service gives client applications the ability to capture, compare, manipulate, and store biometric
data without gaining direct access to any biometric hardware or samples. The service is hosted in a privileged SVCHOST process.
By default, if the registry key does not exist or the value is set to 0, this feature is enabled.
[HKLM\SOFTWARE\DELL\Dell Data Protection]
SmartCardServiceCheck=REG_DWORD:0
0 = Enabled
1 = Disabled
To use smart cards with Windows Authentication, the following registry value must be set on the client computer.
[HKLM\SOFTWARE\DigitalPersona\Policies\Default\SmartCards]
"MSSmartcardSupport"=DWORD:1
To use smart cards with SED Preboot Authentication, the following registry value must be set on the client computer that is equipped
with an SED.
[HKLM\SOFTWARE\DigitalPersona\Policies\Default\SmartCards]
"MSSmartcardSupport"=DWORD:1
Set the Authentication Method policy to Smart Card in the Remote Management Console, and commit the change.
To suppress all Toaster notications from the Encryption Management Agent, the following registry value must be set on the client
computer.
[HKEY_LOCAL_MACHINE\SOFTWARE\Dell\Dell Data Protection]
"PbaToastersAllowClose" =DWORD:1
0=Enabled (default)
1=Disabled
BitLocker Manager Client Registry Settings
If a self-signed certicate is used on the Security Management Server/Security Management Server Virtual for BitLocker Manager,
SSL/TLS trust validation must remain disabled on the client computer (SSL/TLS trust validation is disabled by default with BitLocker
Manager). Before enabling SSL/TLS trust validation on the client computer, the following requirements must be met.
A certicate signed by a root authority, such as EnTrust or Verisign, must be imported into Security Management Server/Security
Management Server Virtual .
The full chain of trust of the certicate must be stored in the Microsoft keystore on the client computer.
To enable SSL/TLS trust validation for BitLocker Manager, change the value of the following registry entry to 0 on the client
computer.
[HKLM\System\CurrentControlSet\Services\DellMgmtAgent\Parameters]
Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
37
"DisableSSLCertTrust"=DWORD:0
0 = Enabled
1 = Disabled
38 Dell Data Security Endpoint Security Suite Enterprise
Registry Settings
Install Using the Master Installer
Command line switches and parameters are case-sensitive.
To install using non-default ports, use the child installers instead of the master installer.
Endpoint Security Suite Enterprise master installer log les are located at C:\ProgramData\Dell\Dell Data Protection\Installer.
Instruct users to see the following document and help les for application assistance:
See the Dell Encrypt Help to learn how to use the feature of the Encryption client. Access the help from <Install dir>:\Program Files
\Dell\Dell Data Protection\Encryption\Help.
See the Encryption External Media Help to learn how the features of Encryption External Media. Access the help from <Install dir>:
\Program Files\Dell\Dell Data Protection\Encryption\EMS.
See the Endpoint Security Suite Enterprise Help to learn how to use the features of Advanced Authentication and Advanced Threat
Prevention. Access the help from <Install dir>:\Program Files\Dell\Dell Data Protection\Client Security Framework\Help.
Users should update their policies by right-clicking the Dell Encryption icon in the system tray and selecting Check for Policy Updates
after installation completes.
The master installer installs the entire suite of products. There are two methods to install using the master installer. Choose one of the
following.
Install Interactively Using the Master Installer
or
Install by Command Line Using the Master Installer
Install Interactively Using the Master Installer
The Endpoint Security Suite Enterprise master installer can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-Pro_Ent-1.x.x.xxx.zip.
Use these instructions to install Dell Endpoint Security Suite Enterprise interactively using the Endpoint Security Suite Enterprise
master installer. This method can be used to install the suite of products on one computer at a time.
1 Locate DDSSuite.exe in the Dell installation media. Copy it to the local computer.
2 Double-click DDSSuite.exe to launch the installer. This may take several minutes.
3 Click Next in the Welcome dialog.
4 Read the license agreement, accept the terms, and click Next.
5 In the Enterprise Server Name eld, enter the fully qualied host name of the Security Management Server/Security Management
Server Virtual that will manage the target user, such as server.organization.com.
In the Device Server URL eld, enter the URL of the Device Server (Security Server) with which the client will communicate.
The format is https://server.organization.com:8443/xapi/ (including trailing forward slash).
Click Next.
4
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
39
6 Click Next to install the product in the default location of C:\Program Files\Dell\Dell Data Protection\. Dell recommends installing in
the default location only, as problems may arise when installing in other locations.
7 Select the components to be installed.
Security Framework installs the underlying security framework and Advanced Authentication, the advanced authentication client that
manages multiple authentication methods, including PBA and credentials such as ngerprints and passwords.
Advanced Authentication installs the les and services required for Advanced Authentication.
Encryption installs the Encryption client, the component that enforces security policy, whether a computer is connected to the
network, disconnected from the network, lost, or stolen.
Threat Protection installs the Threat Protection clients, which are malware and antivirus protection to scan for viruses, spyware, and
unwanted programs, client rewall to monitor communication between the computer and resources on the network and the Internet,
and web ltering to display safety ratings or block access to websites during online browsing.
BitLocker Manager installs the BitLocker Manager client, designed to enhance the security of BitLocker deployments by simplifying
and reducing the cost of ownership through centralized management of BitLocker encryption policies.
Advanced Threat Prevention installs the Advanced Threat Prevention client, which is next-generation antivirus protection that uses
algorithmic science and machine learning to identify, classify, and prevent both known and unknown cyberthreats from executing or
harming endpoints.
Web Protection and Firewall installs the optional features, Web Protection and Firewall. The Client Firewall checks all incoming and
outgoing trac against its list of rules. Web Protection monitors web browsing and downloads to identify threats and enforce action
set by policy when a threat is detected, based on ratings for websites.
NOTE: If the installer detects a Windows version later than Creators Update (Redstone 2), the Client Firewall and Web
Protection option does not display.
Click Next when your selections are complete.
40 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
8 Click Install to begin the installation. Installation will take several minutes.
9 Select Yes, I want to restart my computer now and click Finish.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
41
Installation is complete.
Install by Command Line Using the Master Installer
The switches must be specied rst in a command line installation. Other parameters go inside an argument that is passed to the /v
switch.
Switches
The following table describes the switches that can be used with the Endpoint Security Suite Enterprise master installer.
Switch Description
-y -gm2 Pre-extraction of Endpoint Security Suite Enterprise master installer. The -y and -gm2 switches must be
used together.
Do not separate the switches.
/S Silent installation
/z Pass variables to the .msi inside the DDSSuite.exe
Parameters
The following table describes the parameters that can be used with the Endpoint Security Suite Enterprise master installer. The
Endpoint Security Suite Enterprise master installer cannot exclude individual components but can receive commands to specify which
components should be installed.
42 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
Parameter Description
SUPPRESSREBOOT Suppresses the automatic reboot after the installation completes. Can be used in SILENT mode.
SERVER Species the URL of the Security Management Server/Security Management Server Virtual.
InstallPath Species the path for the installation. Can be used in SILENT mode.
FEATURES Species the components that can be installed in SILENT mode.
ATP = Advanced Threat Prevention
only
on a server OS; Advanced Threat Prevention
and
Encryption on a
workstation OS
DE-ATP = Advanced Threat Prevention and Encryption on a server OS. Use
only
for installation on a server
OS. This is the default installation on a server OS if the FEATURES parameter is not specied.
DE = Drive Encryption (Encryption client)
only
Use
only
for installation on a server OS.
BLM = BitLocker Manager
SED = SED Management (EMAgent/Manager, PBA/GPE Drivers)(Available only when installed on a
workstation OS)
ATP-WEBFIREWALL = Client Firewall and Web Protection on a workstation OS
DE-ATP-WEBFIREWALL = Client Firewall and Web Protection on a server OS
NOTE: For upgrades from Encryption Enterprise or from pre-v1.4 Endpoint Security Suite Enterprise,
ATP-WEBFIREWALL or DE-ATP-WEBFIREWALL
must
be specied in order to install Client Firewall
and Web Protection. Do not specify ATP-WEBFIREWALL or DE-ATP-WEBFIREWALL when installing
a client to be managed by Dell Security Management Server/Security Management Server Virtual
running in Disconnected Mode.
BLM_ONLY=1 Must be used when using FEATURES=BLM in the command line to exclude the SED Management plugin.
Example Command Line
Command line parameters are case-sensitive.
(On a workstation OS) This example installs all components using the Endpoint Security Suite Enterprise master installer on standard
ports, silently, in the default location of C:\Program Files\Dell\Dell Data Protection\, and congures it to use the specied Security
Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com\""
(On a workstation OS) This example installs Advanced Threat Prevention and Encryption
only
using the Endpoint Security Suite
Enterprise master installer on standard ports, silently, in the default location of C:\Program Files\Dell\Dell Data Protection\, and
congures it to use the specied Security Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=ATP\""
(On a workstation OS) This example installs Advanced Threat Prevention, Encryption, and SED Management using the Endpoint
Security Suite Enterprise master installer on standard ports, silently, with a suppressed reboot, in the default location of C:\Program
Files\Dell\Dell Data Protection\, and congures it to use the specied Security Management Server/Security Management Server
Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=ATP-SED,
SUPPRESSREBOOT=1\""
(On a workstation OS) This example installs Advanced Threat Prevention, Encryption, Web Protection, and Client Firewall using the
Endpoint Security Suite Enterprise master installer on standard ports, silently, in the default location of C:\Program Files\Dell\Dell Data
Protection\, and congures it to use the specied Security Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=ATP-WEBFIREWALL\""
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
43
(On a server OS) This example installs Advanced Threat Prevention and Encryption
only
using the Endpoint Security Suite Enterprise
master installer on standard ports, silently, in the default location of C:\Program Files\Dell\Dell Data Protection\, and congures it to
use the specied Security Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=DE-ATP\""
(On a server OS) This example installs Advanced Threat Prevention, Encryption, Web Protection, and Client Firewall using the Endpoint
Security Suite Enterprise master installer on standard ports, silently, in the default location of C:\Program Files\Dell\Dell Data
Protection\
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=DE-ATP-WEBFIREWALL\""
(On a server OS) This example installs Advanced Threat Prevention
only
using the Endpoint Security Suite Enterprise master installer
on standard ports, silently, in the default location of C:\Program Files\Dell\Dell Data Protection\, and congures it to use the specied
Security Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=ATP\""
(On a server OS) This example installs Encryption
only
using the Endpoint Security Suite Enterprise master installer on standard ports,
silently, in the default location of C:\Program Files\Dell\Dell Data Protection\, and congures it to use the specied Security
Management Server/Security Management Server Virtual.
"DDSSuite.exe" -y -gm2 /S /z"\"SERVER=server.organization.com, FEATURES=DE\""
44 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Master Installer
Uninstall Using the Endpoint Security Suite
Enterprise Master Installer
Each component must be uninstalled separately, followed by uninstallation of the Endpoint Security Suite Enterprise master installer.
The clients must be uninstalled in a specic order to prevent uninstallation failures.
Follow the instructions in Extract the Child Installers from the Master Installer to obtain child installers.
Ensure that the same version of Endpoint Security Suite Enterprise master installer (and thereby clients) is used for uninstallation as
installation.
This chapter refers you to other chapters that contain detailed instructions of how to uninstall the child installers. This chapter explains
the last step only, uninstalling the master installer.
Uninstall the clients in the following order.
aUninstall Encryption Client.
bUninstall Advanced Threat Prevention.
cUninstall SED and Advanced Authentication Clients (this uninstalls the Dell Encryption Management Agent, which cannot be
uninstalled until Advanced Threat Prevention is uninstalled).
dUninstall BitLocker Manager Client
The Driver package does not need to be uninstalled.
Proceed to Uninstall the Master Installer.
Uninstall the Endpoint Security Suite Enterprise
Master Installer
Now that all of the individual clients have been uninstalled, the master installer can be uninstalled.
Command Line Uninstallation
The following example silently uninstalls the Endpoint Security Suite Enterprise master installer.
"DDSSuite.exe" -y -gm2 /S /x
Reboot the computer when nished.
5
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Endpoint Security Suite Enterprise Master Installer
45
Install Using the Child Installers
To install each client individually, the child executable les must rst be extracted from the Endpoint Security Suite Enterprise master
installer, as shown in Extract the Child Installers from the Master Installer.
Command examples included in this section assume the commands are run from C:\extracted.
Command line switches and parameters are case-sensitive.
Be sure to enclose a value that contains one or more special characters, such as a blank space in the command line, in escaped
quotation marks.
Use these installers to install the clients using a scripted installation, batch les, or any other push technology available to your
organization.
The reboot has been suppressed in the command line examples. However, an eventual reboot is required. Encryption cannot begin until
the computer has rebooted.
Log les - Windows creates unique child installer installation log les for the logged in user at %temp%, located at C:\Users
\<UserName>\AppData\Local\Temp.
If you decide to add separate a log le when you run the installer, ensure that the log le has a unique name, as child installer log les do
not append. The standard .msi command can be used be create a log le by using /l*v C:\<any directory>\<any log le name>.log.
All child installers use the same basic .msi switches and display options, except where noted, for command line installations. The
switches must be specied rst. The /v switch is required and takes an argument. Other parameters go inside an argument that is
passed to the /v switch.
Display options can be specied at the end of the argument passed to the /v switch to achieve the expected behavior. Do not use
both /q and /qn in the same command line. Only use ! and - after /qb.
Switch Meaning
/v Pass variables to the .msi inside the setup.exe. The content must always be enclosed in
plain-text quotes.
/s Silent mode
/x Uninstall mode
/a Administrative install (will copy all les inside the .msi)
NOTE:
With /v, the Microsoft default options are available. For a list of options, see https://msdn.microsoft.com/en-us/library/windows/
desktop/aa367988(v=vs.85).aspx.
Option Meaning
/q No Progress dialog, restarts itself after process completion
/qb Progress dialog with Cancel button, prompts for restart
/qb- Progress dialog with Cancel button, restarts itself after process completion
/qb! Progress dialog without Cancel button, prompts for restart
6
46 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Option Meaning
/qb!- Progress dialog without Cancel button, restarts itself after process completion
/qn No user interface
/norestart Suppress reboot
Instruct users to see the following document and help les for application assistance:
See the Dell Encrypt Help to learn how to use the feature of the Encryption client. Access the help from <Install dir>:\Program Files
\Dell\Dell Data Protection\Encryption\Help.
See the Encryption External Media Help to learn how the features of Encryption External Media. Access the help from <Install dir>:
\Program Files\Dell\Dell Data Protection\Encryption\EMS.
See the Endpoint Security Suite Enterprise Help to learn how to use the features of Advanced Authentication and Advanced Threat
Prevention. Access the help from <Install dir>:\Program Files\Dell\Dell Data Protection\Client Security Framework\Help.
Install Drivers
Drivers and rmware for ControlVault, ngerprint readers and smart cards are not included in the Endpoint Security Suite Enterprise
master installer or child installer executable les. The drivers and rmware must be kept up-to-date, and can be downloaded from
http://www.dell.com/support and selecting your computer model. Download the appropriate drivers and rmware based on your
authentication hardware.
• ControlVault
NEXT Biometrics Fingerprint Driver
Validity Fingerprint Reader 495 Driver
O2Micro Smart Card Driver
If installing on non-Dell hardware, download updated drivers and rmware from that vendor's website.
Install Encryption Client
Review Encryption Client Requirements if your organization is using a certicate signed by a root authority, such as EnTrust or Verisign.
A registry setting change is needed on the client computer to enable certicate validation.
Users should update their policies by right-clicking the Dell Data Security icon in the system tray and selecting Check for Policy
Updates after installation completes.
The Encryption client installer can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-1.x.x.xxx.zip and then Extract the Child
Installers from the Master Installer. After extraction, locate the le at C:\extracted\Encryption.
Command Line Installation
The following table details the parameters available for the installation.
Parameters
SERVERHOSTNAME=<ServerName> (FQDN of the Dell Server for re-activation)
POLICYPROXYHOSTNAME=<RGKName> (FQDN of the default Policy Proxy)
MANAGEDDOMAIN=<MyDomain> (Domain to be used for the device)
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
47
Parameters
DEVICESERVERURL=<DeviceServerName/SecurityServerName> (URL used for activation; usually includes server name, port, and
xapi)
GKPORT=<NewGKPort> (Gatekeeper port)
MACHINEID=<MachineName> (Computer name)
RECOVERYID=<RecoveryID> (Recovery ID)
REBOOT=ReallySuppress (Null allows for automatic reboots, ReallySuppress disables reboot)
HIDEOVERLAYICONS=1 (0 enables overlay icons, 1 disables overlay icons)
HIDESYSTRAYICON=1 (0 enables the systray icon, 1 disables the systray icon)
EME=1 (Install Encryption External Media mode)
For a list of basic .msi switches and display options that can be used in command lines, refer to Install Using the Child Installers.
The following table details additional optional parameters related with activation.
Parameters
SLOTTEDACTIVATON=1 (0 disables delayed/scheduled activations, 1 enables delayed/scheduled activations)
SLOTINTERVAL=45,120 (Schedules activations through x,x notation where the rst value is the lower limit of the schedule and the
second value is the upper limit - in seconds)
CALREPEAT=600 (MUST match or exceed the upper limit set in SLOTINTERVAL. Number of seconds the Encryption client waits
before generating an activation attempt based on SLOTINTERVAL.)
Example Command Line
The following example installs the client with default parameters (Encryption client, Encrypt for Sharing, no dialogue, no progress bar,
automatic restart, installed in the default location of C:\Program Files\Dell\Dell Data Protection).
DDPE_XXbit_setup.exe /s /v"SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/ /qn"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" /qn REBOOT="ReallySuppress"
SERVERHOSTNAME="server.organization.com" POLICYPROXYHOSTNAME="rgk.organization.com"
MANAGEDDOMAIN="ORGANIZATION" DEVICESERVERURL="https://server.organization.com:8443/xapi/"
The following example installs the Encryption client and Encrypt for Sharing, hides the Data Security Console system tray icon, hides
the overlay icons, no dialogue, no progress bar, suppresses restart, installed in the default location of C:\Program Files\Dell\Dell Data
Protection.
DDPE_XXbit_setup.exe /s /v"SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/ HIDESYSTRAYICON=1 HIDEOVERLAYICONS=1
REBOOT=ReallySuppress /qn"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" /qn REBOOT="ReallySuppress"
SERVERHOSTNAME="server.organization.com" POLICYPROXYHOSTNAME="rgk.organization.com"
MANAGEDDOMAIN="ORGANIZATION" DEVICESERVERURL="https://server.organization.com:8443/xapi/"
HIDESYSTRAYICON="1" HIDEOVERLAYICONS="1"
48 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Example Command Line to Install in Deferred Activation Mode
The following example installs the client with Deferred Activation in the default location of C:\Program Files\Dell\Dell Data Protection)
DDPE_XXbit_setup.exe /s /v"OPTIN=1 SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com DEVICESERVERURL=https://server.organization.com:8443/
xapi/ MANAGEDDOMAIN=ORGANIZATION"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" OPTIN="1"
SERVERHOSTNAME="server.organization.com" POLICYPROXYHOSTNAME="rgk.organization.com"
DEVICESERVERURL="https://server.organization.com:8443/xapi/" MANAGEDDOMAIN="ORGANIZATION"
The following example installs the client with Deferred Activation and with default parameters (Encryption client, Encrypt for Sharing,
no dialogue, no progress bar, no restart, no Encryption overlay icons, installed in the default location of C:\Program Files\Dell\Dell Data
Protection).
DDPE_XXbit_setup.exe /s /v"SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/ OPTIN=1 HIDEOVERLAYICONS=1 REBOOT=ReallySuppress /qn"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" /qn REBOOT="ReallySuppress" OPTIN="1"
SERVERHOSTNAME="server.organization.com" POLICYPROXYHOSTNAME="rgk.organization.com"
MANAGEDDOMAIN="ORGANIZATION" DEVICESERVERURL="https://server.organization.com:8443/xapi/"
HIDEOVERLAYICONS="1"
NOTE:
Some older clients may require escape characters of \" around the values of parameters. For example:
DDPE_XXbit_setup.exe /v"CMG_DECRYPT=\"1\" CMGSILENTMODE=\"1\" DA_SERVER=
\"server.organization.com\" DA_PORT=\"8050\" SVCPN=\"administrator@organization.com\"
DA_RUNAS=\"domain\username\" DA_RUNASPWD=\"password\" /qn"
Install Full Disk Encryption Client
Review Full Disk Encryption Client Requirements if your organization is using a certicate signed by a root authority, such as EnTrust or
Verisign. A registry setting change is needed on the client computer to enable SSL/TLS trust validation.
Users log in to the PBA using their Windows credentials.
NOTE: Full Disk Encryption is only supported in UEFI boot mode.
Command Line Installation
The following table details the parameters available for the installation.
Parameters
CM_EDITION=1 <remote management>
INSTALLDIR=<change the installation destination>
SERVERHOST=<securityserver.organization.com>
SERVERPORT=8888
SECURITYSERVERHOST=<securityserver.organization.com>
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
49
Parameters
SECURITYSERVERPORT=8443
ARPSYSTEMCOMPONENT=1 <no entry in the Control Panel Programs list>
FEATURE=FDE
For a list of basic .msi switches and display options that can be used in command lines, refer to Install Using the Child Installers.
Example Command Line
Prerequisite installation
\Encryption Management Agent
The following example installs remotely managed Full Disk Encryption (silent installation, no reboot, no entry in the Control Panel
Programs list, installed in the default location of C:\Program Files\Dell\Dell Data Protection).
EMAgent_64bit_setup.exe /s /v"CM_EDITION=1 FEATURE=FDE SERVERHOST=server.organization.com
SERVERPORT=8888 SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443
ARPSYSTEMCOMPONENT=1 /norestart /qn"
Then:
\Advanced Authentication\<x64>
The following example installs Advanced Authentication (silent installation, no reboot)
setup.exe /s /v"/norestart /qn ARPSYSTEMCOMPONENT=1"
Install Server Encryption Client
There are two methods available to install Server Encryption. Choose one of the following methods:
Install Server Encryption Interactively
NOTE:
Server Encryption can be installed interactively only on computers running server operating systems. Installation on computers
running non-server operating systems must be performed by command line, with the SERVERMODE=1 parameter specied.
Install Server Encryption Using the Command Line
Virtual User Account
As part of the installation, a virtual server user account is created for the exclusive use of Server Encryption. Password and DPAPI
authentication are disabled so that only the virtual server user can access encryption keys on the computer.
Before You Begin
The user account performing the installation must be a local or domain user with administrator-level permissions.
To override the requirement that a domain administrator activate Server Encryption, or to run Server Encryption on non-domain or
multi-domain servers, set the ssos.domainadmin.verify property to false in the application.properties le. The le is stored in the
following le paths, based on the Dell Server you are using:
Security Management Server - <installation folder>/Security Server/conf/application.properties
Security Management Server Virtual - /opt/dell/server/security-server/conf/application.properties
The server must support port controls.
Server Port Control System policies aect removable media on protected servers, for example, by controlling access and usage of the
server's USB ports by USB devices.USB port policy applies to external USB ports. Internal USB port functionality is not aected by
50 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
USB port policy. If USB port policy is disabled, the client USB keyboard and mouse will not work and the user will not be able to use the
computer unless a Remote Desktop Connection is set up before the policy is applied.
To successfully activate Server Encryption, the computer must have network connectivity.
When the Trusted Platform Module (TPM) is available, it is used for sealing the GPK on Dell hardware. If a TPM is not available, Server
Encryption uses Microsoft's Data Protection API (DPAPI) to protect the General Purpose Key.
NOTE:
When installing a new operating system on a Dell computer with TPM that is running Server Encryption, clear the TPM in the BIOS.
See https://technet.microsoft.com/en-us/library/cc749022%28v=ws.10%29.aspx#BKMK_S2 for instructions.
NOTE: Encryption is not supported on servers that are part of distributed le systems (DFS).
Extract the Child Installer
Server Encryption requires only one of the installers in the master installer. To install Server Encryption, you must rst extract the
Encryption client's child installer, DDPE_xxbit_setup.exe, from the master installer. See Extract the Child Installers from the Master
Installer.
Install Server Encryption Interactively
Use these instructions to install Server Encryption interactively. This installer includes the components you need for software
encryption.
1 Locate DDPE_XXbit_setup.exe in the C:\extracted\Encryption folder. Copy it to the local computer.
2 If you are installing Server Encryption on a server, double-click the DDPE_XXbit_setup.exe le to launch the installer.
NOTE:
When Server Encryption is installed on a computer that is running a server operating system such as Windows Server 2012 R2,
the installer installs encryption in Server mode by default.
3 In the Welcome dialog, click Next.
4 In the License Agreement screen, read the license agreement, agree to the terms, and click Next.
5 Click Next to install Server Encryption in the default location.
NOTE:
Dell recommends installing in the default location. Installing in a location other than the default location-whether in a dierent
directory, on the D drive, or on a USB drive-is not recommended.
6 Click Next to skip the Management Type dialog.
7 In the Security Management Server Name eld, enter the fully qualied host name of the Dell Security Management Server or
Security Management Server Virtual that will manage the target user (example, server.organization.com).
8 Enter the domain name in the Managed Domain eld (example, organization), and click Next.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
51
9 Click Next to skip the auto-populated Dell Policy Proxy Information dialog.
10 Click Next to skip the auto-populated Dell Device Server Information dialog.
52 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
11 Click Install to begin the installation.
Installation may take several minutes.
12 In the Conguration Completed dialog, click Finish.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
53
Installation is complete.
NOTE:
The log le for the installation is located in the account's %temp% directory, located at C:\Users\<user name>\AppData\Local
\Temp. To locate the installer's log le, look for a le name that begins with MSI and ends with a .log extension. The le should
have a date/time stamp matching the time when you ran the installer.
NOTE:
As part of the installation, a virtual server user account is created for the exclusive use of Server Encryption. Password and
DPAPI authentication are disabled so that only the virtual server user can access encryption keys on the computer.
13 Restart the computer.
IMPORTANT: Choose Snooze Reboot only if you need time to save your work and close any open applications.
Install Server Encryption Using the Command Line
Server Encryption Client - locate the installer at C:\extracted\Encryption
Use DDPE_xxbit_setup.exe to install or upgrade using a scripted installation, using batch les, or any other push technology available
to your organization.
Switches
The following table details the switches available for the installation.
54 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Switch Meaning
/v Pass variables to the .msi inside the DDPE_XXbit_setup.exe
/a Administrative installation
/s Silent mode
Parameters
The following table details the parameters available for the installation.
Component Log File Command Line Parameters
All /l*v [fullpath][lename].log * SERVERHOSTNAME=<Management Server Name>
SERVERMODE=1
POLICYPROXYHOSTNAME=<RGK Name>
MANAGEDDOMAIN=<My Domain>
DEVICESERVERURL=<Activation Server Name>
GKPORT=<New GK Port>
MACHINEID=<Machine Name>
RECOVERYID=<Recovery ID>
REBOOT=ReallySuppress
HIDEOVERLAYICONS=1
HIDESYSTRAYICON=1
EME=1
NOTE:
Although the reboot can be suppressed, an eventual reboot is required. Encryption cannot begin until the computer has rebooted.
Options
The following table details the display options that can be specied at the end of the argument passed to the /v switch.
Option Meaning
/q No Progress dialog, restarts itself after process completion
/qb Progress dialog with Cancel button, prompts for restart
/qb- Progress dialog with Cancel button, restarts itself after process completion
/qb! Progress dialog without Cancel button, prompts for restart
/qb!- Progress dialog without Cancel button, restarts itself after process completion
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
55
Option Meaning
/qn No user interface
NOTE:
Do not use both /q and /qn in the same command line. Only use ! and - after /qb.
The command line parameter, SERVERMODE=1, is honored only during new installations. The parameter is ignored for uninstallations.
Installing in a location other than the default location, whether in a dierent directory, on a drive other than C:, or on a USB drive is not
recommended. Dell recommends installing in the default location.
Enclose a value that contains one or more special characters, such as a blank space, in escaped quotation marks.
The Dell Activation Server URL (DEVICESERVERURL) is case sensitive.
Example Command Line Installation
The following example installs the Server Encryption client with default parameters (Server Encryption client, silent installation, Encrypt
for Sharing, no dialogue, no progress bar, automatic restart, installed in the default location of C:\Program Files\Dell\Dell Data
Protection).
DDPE_XXbit_setup.exe /s /v"SERVERMODE=1 SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/qn"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" /qn REBOOT="ReallySuppress"
SERVERMODE="1" SERVERHOSTNAME="server.organization.com"
POLICYPROXYHOSTNAME="rgk.organization.com" MANAGEDDOMAIN="ORGANIZATION"
DEVICESERVERURL="https://server.organization.com:8443/xapi/"
The following example installs the Server Encryption client with a log le and default parameters (Server Encryption client, silent
installation, Encrypt for Sharing, no dialogue, no progress bar, no restart, installed in the default location of C:\Program Files\Dell\Dell
Data Protection\Encryption) and species a custom log le name ending with a number (DDP_ssos-090.log) that should be
incremented if the command line is run more than once on the same server.
DDPE_XXbit_setup.exe /s /v"SERVERMODE=1 SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/ /l*v DDP_ssos-090.log /norestart/qn"
MSI Command:
msiexec.exe /i "Dell Data Protection Encryption.msi" /qn SERVERMODE="1"
SERVERHOSTNAME="server.organization.com" POLICYPROXYHOSTNAME="rgk.organization.com"
MANAGEDDOMAIN="ORGANIZATION" DEVICESERVERURL="https://server.organization.com:8443/xapi/" /l*v
DDP_ssos-090.log /norestart/qn"
To specify a log location other than the default location where the executable is located, provide the complete path in the command.
For example, /l*v C:\Logs\DDP_ssos-090.log will create install logs in a C:\Logs folder.
Restart the computer
After installation, restart the computer. The computer must be restarted as soon as possible.
IMPORTANT:
Choose Snooze Reboot only if you need time to save your work and close any open applications.
Activate Server Encryption
The server must be connected to your organization's network.
56 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Ensure that the computer name of the server is the endpoint name you want to display in the Remote Management Console.
A live, interactive user with domain administrator credentials must log on to the server at least once for the purpose of the initial
activation. The logged on user can be of any type - domain or non-domain, remote-desktop-connected or interactive user at the server,
but activation requires domain administrator credentials.
Following the restart after installation, the Activation dialog displays. The administrator must enter domain administrator credentials with
a user name in User Principal Name (UPN) format. The Server Encryption client does not activate automatically.
During initial activation, a virtual server user account is created. After initial activation, the computer is restarted so that device
activation can begin.
During the Authentication and Device Activation phase, the computer is assigned a unique Machine ID, encryption keys are created and
bundled, and a relationship is established between the encryption key bundle and the virtual server user. The encryption key bundle
associates the encryption keys and policies with the new virtual server user to create an unbreakable relationship between the
encrypted data, the specic computer, and the virtual server user. After device activation, the virtual server user appears in the Remote
Management Console as SERVER-USER@<fully qualied server name>. For more information about activation, see Activation on a
Server Operating System.
NOTE:
If you rename the server after activation, its display name will not change in the Remote Management Console. However, if the Server
Encryption client activates again after the server name is changed, the new server name would appear in the Remote Management
Console.
An Activation dialog displays once after each restart to prompt the user to activate Server Encryption. To complete activation, follow these
steps:
1 Log on to the server either at the server or through Remote Desktop Connection.
2 Enter the username of a Domain Administrator in UPN format and password and click Activate. This is the same Activation dialog that
appears each time an unactivated system is restarted.
The Dell Server issues an encryption key for the Machine ID, creates the virtual server user account, creates an encryption key for
the user account, bundles the encryption keys, and creates the relationship between the encryption bundle and the virtual server user
account.
3 Click Close.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
57
After activation, encryption begins.
4 After the encryption sweep has nished, restart the computer to process any les that were previously in use. This is an important
step for security purposes.
NOTE:
If the Secure Windows Credentials policy is set to True, Server Encryption encrypts the \Windows\system32\cong les, which
includes Windows credentials. The les in \Windows\system32\cong are encrypted even if the SDE Encryption Enabled policy
is Not Selected. By default, the Secure Windows Credentials policy is Selected.
NOTE:
After restarting the computer, authentication to the Common key material always requires the protected server's Machine key.
The Dell Server returns an unlock key to access the encryption keys and policies in the vault. (The keys and policies are for the
server, not for the user). Without the server's Machine key, the Common le encryption key cannot be unlocked, and the
computer cannot receive policy updates.
Conrm Activation
From the local console, open the About dialog to conrm that Server Encryption is installed, authenticated, and in Server mode. If the
Shield ID is red, encryption has not yet been activated.
The Virtual Server User
In the Remote Management Console, a protected server can be found under its machine name. In addition, each protected server has
its own virtual server user account. Each account has a unique static username and unique machine name.
The virtual server user account is only used by Server Encryption and is otherwise transparent to the operation of the protected server.
The virtual server user is associated with the encryption key bundle and the policy proxy.
58 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
After activation, the virtual server user account is the user account that is activated and associated with the server.
After the virtual server user account is activated, all server logon/logo notications are ignored. Instead, during startup, the computer
automatically authenticates with the virtual server user, and then downloads the Machine key from the Dell Data Security Server.
Install Advanced Threat Prevention Client
The installers must be run in a specic order. Failure to install the components in the proper order will result in installation failure. Run
the installers in the following order:
1(On a workstation OS only) \Advanced Authentication - Advanced Threat Prevention needs the Dell Encryption Management Agent
component.
(On a server OS only) Dell Encryption Management Agent component, as shown in Command Line Installation.
2(On a workstation OS only) \Advanced Authentication\<x64/x86> - On a workstation OS, Advanced Authentication and
Authentication must be installed together; Authentication is not available on a server OS and does not need to be installed.
3 Advanced Threat Prevention Client, as shown in Command Line Installation.
The Advanced Threat Prevention client installer can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-1.x.x.xxx.zip and then Extract the Child
Installers from the Master Installer. After extraction, locate the le at C:\extracted\Advanced Threat Prevention\WinXXR\ and C:
\extracted\Advanced Threat Prevention\WinNtAll\.
The SED and Advanced Authentication client installers can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-1.x.x.xxx.zip and then Extract the Child
Installers from the Master Installer. After extraction, locate the le at C:\extracted\Encryption Management Agent and C:
\extracted\Advanced Authentication\<x64/x86>.
NOTE: The SED and Advanced Authentication clients can be installed only on a workstation OS and not on a server OS.
Command Line Installation
Basic .msi commands are available for the installation.
The following table details the parameters available for the installation.
Parameters
CM_EDITION=1 <remote management>
INSTALLDIR=<change the installation destination>
SERVERHOST=<securityserver.organization.com>
SERVERPORT=8888
SECURITYSERVERHOST=<securityserver.organization.com>
SECURITYSERVERPORT=8443
ARPSYSTEMCOMPONENT=1 <no entry in the Control Panel Programs list>
REBOOT=ReallySuppress <suppresses the reboot>
FEATURE=BASIC <
required
on a server OS; may also be used (optionally) on a workstation OS; prevents SED Management client
and BitLocker Manager installation>
For a list of basic .msi switches and display options that can be used in command lines, refer to Install Using the Child Installers.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
59
Example Command Lines
The following example installs the basic Dell Encryption Management Agent component, without the SED Management client or
BitLocker Manager (silent installation, no reboot, no entry in the Control Panel Programs list, installed in the default location of C:
\Program Files\Dell\Dell Data Protection).
EMAgent_XXbit_setup.exe /s /v"FEATURE=BASIC CM_EDITION=1 SERVERHOST=server.organization.com
SERVERPORT=8888 SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443
ARPSYSTEMCOMPONENT=1 /norestart /qn"
The following example installs Advanced Threat Prevention (silent installation, no reboot, installation log le and installation folder in the
specied locations)
MSIEXEC.EXE /I "ATP_CSF_Plugins_x64.msi" /qn REBOOT="ReallySuppress" APPFOLDER="C:\Program
Files\Dell\Dell Data Protection\Advanced Threat Prevention\Plugins"
ARPSYSTEMCOMPONENT="1" /l*v "C:\ProgramData\Dell\Dell Data Protection\Installer Logs
\ATP_Plugins_x64.msi.log"
and
ATP_AgentSetup.exe" -y -gm2 /S EXTRACT_INSTALLERS /v"/qb!"
NOTE: These components must be installed by command line only. Double-clicking to install this component installs a non-Dell,
non-managed version of the product, which is not supported. If this is accidentally done, simply go to Add/Remove Programs
and uninstall that version.
Example Script
The following example installs Advanced Threat Prevention, without the SED Management client or BitLocker Manager (silent installation,
no reboot, no entry in the Control Panel Programs list, no desktop icon, installed in the default location of C:\Program Files\Dell\Dell Data
Protection).
:: Installing Encryption Management Agent
".\Encryption Management Agent\EMAgent_64bit_setup.exe" /s /v" FEATURE=BASIC CM_EDITION=1 SERVERHOST=%SERVER%
SERVERPORT=8888 SECURITYSERVERHOST=%SERVER% SECURITYSERVERPORT=8443 ARPSYSTEMCOMPONENT=1 /
norestart /qn"
:: Installing ATP Plugins
".\Advanced Threat Prevention\Win64R\ATP_CSF_Plugins_x64.msi" /qn REBOOT=ReallySuppress APPFOLDER="C:\Program Files\Dell
\Dell Data Protection\Advanced Threat Prevention\Plugins" ARPSYSTEMCOMPONENT=1 /l*v "C:\ProgramData\Dell\Dell Data
Protection\Installer Logs\ATP_CSF_Plugins_x64.msi.log"
:: Installing Advanced Threat Prevention
".\Advanced Threat Prevention\WinNtAll\ATP_AgentSetup.exe" -y -gm2 /S EXTRACT_INSTALLERS /v"/qb!"
Install Web Protection and Firewall
The installers must be run in a specic order. Failure to install the components in the proper order will result in installation failure. Run
the installers in the following order:
NOTE: If you attempt to install the optional Web Protection Client Firewall features on a Windows 10 Fall Creators Update
(Redstone 3) or later, an incompatibility warning displays.
1 Web Protection and Firewall, as shown in Command Line Installation.
Command Line Installation
The following table details the parameters available for the EnsMgmtSdkInstaller.exe le.
60 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Parameters Description
LoadCert Load the certicate at the specied directory.
The following table details the parameters available for the EPsetup.exe le.
Parameters Description
ADDLOCAL="fw,wc" Identies the modules to install:
fw=Client Firewall
wc=Web Protection
override "hips" Do not install Host Intrusion Prevention
INSTALLDIR Non-default installation location
nocontentupdate Tells the installer not to update content les automatically as part of the installation process.
Dell recommends scheduling an update as soon as installation has completed.
nopreservesettings Do not save settings.
The following table details the parameters available for the DellThreatProtection.msi le.
Parameters Description
Reboot=ReallySuppress Suppresses the reboot.
ARP 0=No entry in Add/Remove Programs
1=Entry in Add/Remove Programs
The following table details the parameters available for the EnsMgmtSdkInstaller.exe le.
Parameters Description
InstallSDK Installs the SDK at the specied location.
RemoveRightClick Removes the right-click menu option for end users.
RemoveMcTray Removes the system tray.
Example Command Line
\Threat Protection\SDK
The following command line loads the certicate default parameters.
"Threat Protection\SDK\EnsMgmtSdkInstaller.exe" -LoadCert >"C:\ProgramData\Dell\Dell Data
Protection\Installer Logs\McAfeeSDKInstallerBeforeEndPoint.log"
Then:
\Threat Protection\EndPointSecurity
The following example installs the Web Protection and Client Firewall with default parameters (silent mode, install Client Firewall, and
Web Protection, override the Host Intrusion Prevention, no content update, no settings saved).
"Threat Protection\EndPointSecurity\EPsetup.exe" ADDLOCAL="fw,wc" /override"hips" /
nocontentupdate /nopreservesettings /qn
Then:
\Threat Protection\ThreatProtection\WinXXR
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
61
The following example installs the client with default parameters (suppress the reboot, no dialogue, no progress bar, no entry in the
Control Panel Programs list).
"Threat Protection\ThreatProtection\WinXXR\DellThreatProtection.msi" /qn REBOOT=ReallySuppress
ARPSYSTEMCOMPONENT=1
\Threat Protection\SDK
The following example installs the SDK.
"Threat Protection\SDK\EnsMgmtSdkInstaller.exe" "C:\Program Files\Dell\Dell Data Protection
\Threat Prevention\DellAVAgent.exe" -InstallSDK -RemoveRightClick -RemoveMcTray >"C:
\ProgramData\Dell\Dell Data Protection\Installer Logs\McAfeeSDKInstallerAfterEndPoint.log"
To upgrade, use the following workow:
\Threat Protection\EndPointSecurity
The following installs the Web Protection and Client Firewall with default parameters (silent mode, install Client Firewall and Web
Protection, override Host Intrusion Prevention, no content update, no settings saved).
EPSetup.exe ADDLOCAL="fw,wc" /override"hips" /nocontentupdate /nopreservesettings /l"C:
\ProgramData\Dell\Dell Data Protection\Installer Logs\McAfee" /qn
Then:
\Threat Protection\ThreatProtection\WinXXR
The following example installs the client with default parameters (suppress the reboot, no dialogue, no progress bar, no entry in the
Control Panel Programs list).
DellThreatProtection.msi /qn REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 /l*v "<C:\ProgramData
\Dell\Dell Data Protection\Installer Logs\Dell> Data Protection - Threat Protection.msi.log"
Then:
\Threat Protection\SDK
The following command line loads the certicate default parameters.
"Threat Protection\SDK\EnsMgmtSdkInstaller.exe" -LoadCert >"C:\ProgramData\Dell\Dell Data
Protection\Installer Logs\McAfeeSDKInstallerBeforeEndPoint.log"
Then:
\Threat Protection\SDK
The following example installs the SDK.
EnsMgmtSdkInstaller.exe "C:\Program Files\Dell\Dell Data Protection\Threat Prevention
\DellAVAgent.exe" -InstallSDK -RemoveRightClick -RemoveMcTray > "C:\ProgramData\Dell\Dell Data
Protection\Installer Logs\McAfeeSDKInstallerAfterEndPoint.log"
Install SED Management and Advanced
Authentication Clients
The SED client is required for Advanced Authentication in v8.x.
Review SED Client Requirements if your organization is using a certicate signed by a root authority, such as EnTrust or Verisign. A
registry setting change is needed on the client computer to enable SSL/TLS trust validation.
Users log in to the PBA using their Windows credentials.
62 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
The SED and Advanced Authentication client installers can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-1.x.x.xxx.zip and then Extract the Child
Installers from the Master Installer. After extraction, locate the le at C:\extracted\Encryption Management Agent and C:
\extracted\Advanced Authentication\<x64/x86>.
Command Line Installation
The following table details the parameters available for the installation.
Parameters
CM_EDITION=1 <remote management>
INSTALLDIR=<change the installation destination>
SERVERHOST=<securityserver.organization.com>
SERVERPORT=8888
SECURITYSERVERHOST=<securityserver.organization.com>
SECURITYSERVERPORT=8443
ARPSYSTEMCOMPONENT=1 <no entry in the Control Panel Programs list>
For a list of basic .msi switches and display options that can be used in command lines, refer to Install Using the Child Installers.
Example Command Line
\Encryption Management Agent
The following example installs remotely managed SED (silent installation, no reboot, no entry in the Control Panel Programs list, installed
in the default location of C:\Program Files\Dell\Dell Data Protection).
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 ARPSYSTEMCOMPONENT=1 /
norestart /qn"
Then:
\Advanced Authentication\<x64/x86>
The following example installs Advanced Authentication (silent installation, no reboot)
setup.exe /s /v"/norestart /qn ARPSYSTEMCOMPONENT=1"
Install BitLocker Manager Client
Review BitLocker Manager Client Requirements if your organization is using a certicate signed by a root authority, such as EnTrust or
Verisign. A registry setting change is needed on the client computer to enable SSL/TLS trust validation.
The BitLocker Manager client installers can be located at:
From Your Dell FTP Account - Locate the installation bundle at Endpoint-Security-Suite-1.x.x.xxx.zip and then Extract the Child
Installers from the Master Installer. After extraction, locate the le at C:\extracted\Encryption Management Agent.
Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
63
Command Line Installation
The following table details the parameters available for the installation.
Parameters
CM_EDITION=1 <remote management>
INSTALLDIR=<change the installation destination>
SERVERHOST=<securityserver.organization.com>
SERVERPORT=8888
SECURITYSERVERHOST=<securityserver.organization.com>
SECURITYSERVERPORT=8443
FEATURE=BLM <install BitLocker Manager only>
FEATURE=BLM,SED <install BitLocker Manager with SED>
ARPSYSTEMCOMPONENT=1 <no entry in the Control Panel Programs list>
For a list of basic .msi switches and display options that can be used in command lines, refer to Install Using the Child Installers.
Example Command Line
The following example installs BitLocker Manager only (silent installation, no reboot, no entry in the Control Panel Programs list, installed
in the default location of C:\Program Files\Dell\Dell Data Protection)
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 FEATURE=BLM /norestart /qn"
The following example installs BitLocker Manager with SED (silent installation, no reboot, no entry in the Control Panel Programs list,
installed in the default location of C:\Program Files\Dell\Dell Data Protection)
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 FEATURE=BLM,SED /
norestart /qn"
64 Dell Data Security Endpoint Security Suite Enterprise
Install Using the Child Installers
Uninstall Using the Child Installers
To uninstall each client individually, the child executable les must rst be extracted from the Endpoint Security Suite Enterprise master
installer, as shown in Extract the Child Installers from the Master Installer Alternatively, run an administrative installation to extract
the .msi.
Ensure that the same versions of client are used for uninstallation as installation.
Command line switches and parameters are case-sensitive.
Be sure to enclose a value that contains one or more special characters, such as a blank space in the command line, in escaped
quotation marks. Command line parameters are case-sensitive.
Use these installers to uninstall the clients using a scripted installation, batch les, or any other push technology available to your
organization.
Log les - Windows creates unique child installer uninstallation log les for the logged in user at %temp%, located at C:\Users
\<UserName>\AppData\Local\Temp.
If you decide to add separate a log le when you run the installer, ensure that the log le has a unique name, as child installer log les do
not append. The standard .msi command can be used be create a log le by using /l C:\<any directory>\<any log le name>.log. Dell
does not recommend using "/l*v" (verbose logging) in a command line uninstallation, as the username/password is recorded in the log
le.
All child installers use the same basic .msi switches and display options, except where noted, for command line uninstallations. The
switches must be specied rst. The /v switch is required and takes an argument. Other parameters go inside an argument that is
passed to the /v switch.
Display options can be specied at the end of the argument passed to the /v switch to achieve the expected behavior. Do not use
both /q and /qn in the same command line. Only use ! and - after /qb.
Switch Meaning
/v Pass variables to the .msi inside the setup.exe. The content must always be enclosed in
plain-text quotes.
/s Silent mode
/x Uninstall mode
/a Administrative install (will copy all les inside the .msi)
NOTE:
With /v, the Microsoft default options are available. For a list of options, see https://msdn.microsoft.com/en-us/library/windows/
desktop/aa367988(v=vs.85).aspx.
Option Meaning
/q No Progress dialog, restarts itself after process completion
/qb Progress dialog with Cancel button, prompts for restart
/qb- Progress dialog with Cancel button, restarts itself after process completion
/qb! Progress dialog without Cancel button, prompts for restart
7
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
65
Option Meaning
/qb!- Progress dialog without Cancel button, restarts itself after process completion
/qn No user interface
Uninstall Web Protection and Firewall
If Web Protection and Firewall are not installed, proceed to Uninstall Encryption Client.
Command Line Uninstallation
Once extracted from the Endpoint Security Suite Enterprise master installer, the Web Protection and Firewall client installer can be
located at C:\extracted\Threat Protection\ThreatProtection\WinXXR\DellThreatProtection.msi.
Go to Add/Remove Programs in the Control Panel and uninstall the following components in this order.
McAfee Endpoint Security Firewall
McAfee Endpoint Security Web Control
McAfee Agent
• Then:
The following example uninstalls Web Protection and Firewall .
MSIEXEC.EXE /x "DellThreatProtection.msi"
Uninstall Advanced Threat Prevention
Command Line Uninstallation
The following example uninstalls the Advanced Threat Prevention client.
This command must be run from an administrative
command prompt.
wmic path win32_product WHERE (CAPTION LIKE "%%CYLANCE%%") call uninstall
Shut down and restart the computer, then uninstall the Dell Encryption Management Agent component.
IMPORTANT: If you installed both SED and Advanced Authentication clients or activated Preboot Authentication, follow the
uninstallation instructions in Uninstall SED and Advanced Authentication Clients.
The following example uninstalls only the Dell Encryption Management Agent component and not SED and Advanced Authentication
clients.
EMAgent_XXbit_setup.exe /x /s /v" /qn"
Uninstall SED and Advanced Authentication Clients
Network connection to the Security Management Server/Security Management Server Virtual is required for PBA deactivation.
Process
Deactivate the PBA, which removes all PBA data from the computer and unlocks the SED keys.
Uninstall the SED client.
66 Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
Uninstall the Advanced Authentication client.
Deactivate the PBA
1 As a Dell administrator, log in to the Remote Management Console.
2 In the left pane, click Protect & Manage > Endpoints.
3 Select the appropriate Endpoint Type.
4 Select Show >Visible, Hidden, or All.
5 If you know the Hostname of the computer, enter it in the Hostname eld (wildcards are supported). You may leave the eld blank to
display all computers. Click Search.
If you do not know the Hostname, scroll through the list to locate the computer.
A computer or list of computers displays based on your search lter.
6 Select the Details icon of the desired computer.
7 Click Security Policies on the top menu.
8 Select Self-Encrypting Drives.from the Policy Category drop-down menu.
9 Expand the SED Administration area and change the Enable SED Management and Activate PBA policies from True to False.
10 Click Save.
11 In the left pane, click Actions > Commit Policies.
12 Click Apply Changes.
Wait for the policy to propagate from the Security Management Server/Security Management Server Virtual to the computer
targeted for deactivation.
Uninstall the SED and Authentication clients after the PBA is deactivated.
Uninstall SED Client and Advanced Authentication Clients
Command Line Uninstallation
Once extracted from the master installer, the SED client installer can be located at C:\extracted\Advanced Authentication\<x64/x86>
\setup.exe.
The following example silently uninstalls the Advanced Authentication client.
setup.exe /x /s /v" /qn"
Shut down and restart the computer when nished.
Once extracted from the master installer, the SED client installer can be located at C:\extracted\Encryption Management Agent
\EMAgent_XXbit_setup.exe.
The following example silently uninstalls the SED client.
EMAgent_XXbit_setup.exe /x /s /v" /qn"
Shut down and restart the computer when nished.
Uninstall Encryption and Server Encryption Client
To reduce decryption time, run the Windows Disk Cleanup Wizard to remove temporary les and other unneeded data.
Plan to decrypt overnight, if possible.
Turn o sleep mode to prevent an unattended computer from going to sleep. Decryption cannot occur on a sleeping computer.
Shut down all processes and applications to minimize decryption failures because of locked les.
Once the uninstall is complete and decryption is in progress, disable all network connectivity. Otherwise, new policies may be acquired
that re-enable encryption.
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
67
Follow your existing process for decrypting data, such as issuing a policy update.
Windows Encryption clients update the Security Management Server/Security Management Server Virtual to change the status to
Unprotected at the beginning of a Encryption client uninstall process. However, in the event that the client cannot contact the Security
Management Server/Security Management Server Virtual, regardless of the reason, the status cannot be updated. In this case, you will
need to manually Remove Endpoint in the Remote Management Console. If your organization uses this workow for compliance
purposes, Dell recommends that you verify that Unprotected has been set as expected, either in the Remote Management Console or
Compliance Reporter.
Process
Before beginning the uninstall process, see (Optional) Create an Encryption Removal Agent Log File. This log le is useful for
troubleshooting an uninstall/decryption operation. If you do not intend to decrypt les during the uninstall process, you do not need to
create an Encryption Removal Agent log le.
The Key Server (and Security Management Server) must be congured prior to uninstallation if using the Encryption Removal Agent's
Download Keys from Server option. See Congure Key Server for Uninstallation of Encryption Client Activated Against Security
Management Server for instructions. No prior action is needed if the client to uninstall is activated against a Security Management
Server Virtual, as Security Management Server Virtual does not use the Key Server.
You must use the Dell Administrative Utility (CMGAd) prior launching the Encryption Removal Agent if using the Encryption Removal
Agent's Import Keys from a le option. This utility is used to obtain the encryption key bundle. See Use the Administrative Download
Utility (CMGAd) for instructions. The utility can be located in the Dell installation media.
Run WSScan to ensure that all data is decrypted after uninstallation is complete, but before restarting the computer. See Use WSScan
for instructions.
Periodically Check Encryption Removal Agent Status. Data decryption is still in process if the Encryption Removal Agent Service still
exists in the Services panel.
Command Line Uninstallation
Once extracted from the Endpoint Security Suite Enterprise master installer, the Encryption client installer can be located at C:
\extracted\Encryption\DDPE_XXbit_setup.exe.
The following table details the parameters available for the uninstallation.
Parameter Selection
CMG_DECRYPT Property for selecting the type of Encryption Removal Agent
installation:
3 - Use LSARecovery bundle
2 - Use previously downloaded forensics key material
1 - Download keys from the Dell Server
0 - Do not install Encryption Removal Agent
CMGSILENTMODE Property for silent uninstallation:
1 - Silent
0 - Not Silent
Required Properties
DA_SERVER FQHN for the Security Management Server hosting the negotiate
session.
DA_PORT Port on the Security Management Server for request (default is
8050).
68 Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
Parameter Selection
SVCPN Username in UPN format that the Key Server Service is logged
on as on the Security Management Server.
DA_RUNAS Username in SAM compatible format under whose context the
key fetch request will be made. This user must be in the Key
Server list in the Security Management Server.
DA_RUNASPWD Password for the runas user.
FORENSIC_ADMIN The Forensic Administrator account on the Dell Server, which can
be used for forensic requests for uninstalls or keys.
FORENSIC_ADMIN_PWD The password for the Forensic Administrator account.
Optional Properties
SVCLOGONUN Username in UPN format for Encryption Removal Agent Service
log on as parameter.
SVCLOGONPWD Password for log on as user.
The following example silently uninstalls the Encryption client and downloads the encryption keys from the Security Management
Server.
DDPE_XXbit_setup.exe /s /x /v"CMG_DECRYPT=1 CMGSILENTMODE=1 DA_SERVER=server.organization.com
DA_PORT=8050 SVCPN=administrator@organization.com DA_RUNAS=domain\username
DA_RUNASPWD=password /qn"
MSI Command:
msiexec.exe /s /x "Dell Data Protection Encryption.msi" /qn REBOOT="ReallySuppress"
CMG_DECRYPT="1" CMGSILENTMODE="1" DA_SERVER="server.organization.com" DA_PORT="8050"
SVCPN="administrator@domain.com" DA_RUNAS="domain\username" DA_RUNASPWD="password" /qn
Reboot the computer when nished.
The following example silently uninstalls the Encryption client and downloads the encryptions keys using a Forensic Administrator
account.
DDPE_XXbit_setup.exe /s /x /v"CMG_DECRYPT=1 CMGSILENTMODE=1
FORENSIC_ADMIN=forensicadmin@organization.com FORENSIC_ADMIN_PWD=tempchangeit /qn"
MSI Command:
msiexec.exe /s /x "Dell Data Protection Encryption.msi" /qn CMG_DECRYPT=1 CMGSILENTMODE=1
FORENSIC_ADMIN=forensicadmin@organization.com FORENSIC_ADMIN_PWD=tempchangeit
REBOOT=REALLYSUPPRESS
Reboot the computer when nished.
IMPORTANT:
Dell recommends the following actions when using a Forensic Administrator password on the command line:
1 Create a Forensic Administrator account in the Remote Management Console for the purpose of performing the silent
uninstallation.
2 Use a temporary password for that account that is unique to that account and time period.
3 After the silent uninstallation has been completed, remove the temporary account from the list of administrators or change its
password.
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
69
NOTE:
Some older clients may require escape characters of \" around the values of parameters. For example:
DDPE_XXbit_setup.exe /x /v"CMG_DECRYPT=\"1\" CMGSILENTMODE=\"1\" DA_SERVER=
\"server.organization.com\" DA_PORT=\"8050\" SVCPN=\"administrator@organization.com\"
DA_RUNAS=\"domain\username\" DA_RUNASPWD=\"password\" /qn"
Uninstall BitLocker Manager Client
Command Line Uninstallation
Once extracted from the Endpoint Security Suite Enterprise master installer, the BitLocker client installer can be located at C:
\extracted\Encryption Management Agent\EMAgent_XXbit_setup.exe.
The following example silently uninstalls the BitLocker Manager client.
EMAgent_XXbit_setup.exe /x /s /v" /qn"
Reboot the computer when nished.
70 Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Child Installers
Uninstall Using the Dell Data Security Uninstaller
Uninstall Endpoint Security Suite Enterprise
Dell provides the Data Security Uninstaller as a master uninstaller. This utility gathers the currently installed products and removes them in
the appropriate order.
This Data Security Uninstaller is available in the following location: C:\Program Files (x86)\Dell\Dell Data Protection
For more information or to use command line interface (CLI), see http://www.dell.com/support/article/us/en/19/sln307791.
Logs are generated in C:\ProgramData\Dell\Dell Data Protection\ for all of the components that are removed.
To run the utility, open the containing folder, right-click the DataSecurityUninstaller.exe, and run it as administrator.
Click Next.
8
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Dell Data Security Uninstaller
71
Optionally de-select any application from removal and then select Next.
NOTE: Required dependencies will automatically be checked or un-checked.
72 Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Dell Data Security Uninstaller
To remove applications without installing the Encryption Removal Agent, choose Do not install Encryption Removal Agent and select
Next.
Select Encryption Removal Agent - Download Keys from Server.
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Dell Data Security Uninstaller
73
Enter the fully qualied credentials of a Forensic Administrator and select Next.
Select Remove to begin the uninstall.
Click Finish to complete removal and reboot the computer. Reboot machine after clicking nished is selected by default.
74 Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Dell Data Security Uninstaller
Uninstallation and removal is complete.
Dell Data Security Endpoint Security Suite Enterprise
Uninstall Using the Dell Data Security Uninstaller
75
Commonly Used Scenarios
To install each client individually, the child executable les must rst be extracted from the Endpoint Security Suite Enterprise master
installer, as shown in Extract the Child Installers from the Master Installer.
The SED client is required for Advanced Authentication in v8.x, which is why it is part of the command line in the following examples.
The Advanced Threat Prevention child installer component should be installed by command line only. Double-clicking to install this
component installs a non-Dell, non-managed version of the product, which is not supported. If this is accidentally done, simply go to
Add/Remove Programs and uninstall that version.
Command line switches and parameters are case-sensitive.
Be sure to enclose a value that contains one or more special characters, such as a blank space in the command line, in escaped
quotation marks.
Use these installers to install the clients using a scripted installation, batch les, or any other push technology available to your
organization.
The reboot has been suppressed in the command line examples. However, an eventual reboot is required. Encryption cannot begin until
the computer has rebooted.
Log les - Windows creates unique child installer installation log les for the logged in user at %temp%, located at C:\Users
\<UserName>\AppData\Local\Temp.
If you decide to add separate a log le when you run the installer, ensure that the log le has a unique name, as child installer log les do
not append. The standard .msi command can be used be create a log le by using /l*v C:\<any directory>\<any log le name>.log.
All child installers use the same basic .msi switches and display options, except where noted, for command line installations. The
switches must be specied rst. The /v switch is required and takes an argument. Other parameters go inside an argument that is
passed to the /v switch.
Display options can be specied at the end of the argument passed to the /v switch to achieve the expected behavior. Do not use
both /q and /qn in the same command line. Only use ! and - after /qb.
Switch Meaning
/v Pass variables to the .msi inside the *.exe
/s Silent mode
/i Install mode
Option Meaning
/q No Progress dialog, restarts itself after process completion
/qb Progress dialog with Cancel button, prompts for restart
/qb- Progress dialog with Cancel button, restarts itself after process completion
/qb! Progress dialog without Cancel button, prompts for restart
/qb!- Progress dialog without Cancel button, restarts itself after process completion
/qn No user interface
9
76 Dell Data Security Endpoint Security Suite Enterprise
Commonly Used Scenarios
Instruct users to see the following document and help les for application assistance:
See the Dell Encrypt Help to learn how to use the feature of the Encryption client. Access the help from <Install dir>:\Program Files
\Dell\Dell Data Protection\Encryption\Help.
See the Encryption External Media Help to learn how the features of Encryption External Media. Access the help from <Install dir>:
\Program Files\Dell\Dell Data Protection\Encryption\EMS
See the Endpoint Security Suite Enterprise Help to learn how to use the features of Advanced Authentication and Advanced Threat
Prevention. Access the help from <Install dir>:\Program Files\Dell\Dell Data Protection\Advanced Threat Prevention\Help.
Encryption Client, Advanced Threat Prevention, and
Advanced Authentication
The following example installs remotely managed SED (silent installation, no reboot, no entry in the Control Panel Programs list, installed
in the default location of C:\Program Files\Dell\Dell Data Protection). This component installs the Dell Encryption Management Agent
that is required by Advanced Threat Prevention.
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 ARPSYSTEMCOMPONENT=1 /
norestart /qn"
Then:
The following example installs Advanced Authentication (silent installation, no reboot, installed in the default location of C:\Program
Files\Dell\Dell Data Protection\Authentication).
setup.exe /s /v"/norestart /qn ARPSYSTEMCOMPONENT=1"
Then:
The following example installs Advanced Threat Prevention (silent installation, no reboot, installation log le and installation folder in the
specied locations)
MSIEXEC.EXE /I "ATP_CSF_Plugins_x64.msi" /qn REBOOT="ReallySuppress" APPFOLDER="C:\Program
Files\Dell\Dell Data Protection\Advanced Threat Prevention\Plugins"
ARPSYSTEMCOMPONENT="1" /l*v "C:\ProgramData\Dell\Dell Data Protection\Installer Logs
\AdvancedThreatProtectionPlugins.msi.log"
and
ATP_AgentSetup.exe" -y -gm2 /S EXTRACT_INSTALLERS /v"/qb!"
The following example installs the Encryption client with default parameters (Encryption client and Encrypt for Sharing, no dialogue, no
progress bar, no restart, installed in the default location of C:\Program Files\Dell\Dell Data Protection).
DDPE_XXbit_setup.exe /s /v"SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://
server.organization.com:8443/xapi/ /norestart /qn"
The following examples install the
optional
features, Web Protection and Firewall.
\Threat Protection\SDK
The following command line loads the certicate default parameters.
EnsMgmtSdkInstaller.exe -LoadCert >"C:\ProgramData\Dell\Dell Data Protection\Installer Logs
\McAfeeSDKInstallerBeforeEndPoint.log"
NOTE:
This installer cannot be skipped if upgrading.
Then:
\Threat Protection\EndPointSecurity
Dell Data Security Endpoint Security Suite Enterprise
Commonly Used Scenarios
77
The following example installs the the optional features, Web Protection and Firewall with default parameters (silent mode, install Threat
Protection, Client Firewall, and Web Protection, override the Host Intrusion Prevention, no content update, no settings saved).
"Threat Protection\EndPointSecurity\EPsetup.exe" ADDLOCAL="fw,wc" /override"hips" /
nocontentupdate /nopreservesettings /qn
Then:
\Threat Protection\ThreatProtection\WinXXR
The following example installs the client with default parameters (suppress the reboot, no dialogue, no progress bar, no entry in the
Control Panel Programs list).
"DellThreatProtection.msi" /qn REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1
\Threat Protection\SDK
The following example installs the SDK.
EnsMgmtSdkInstaller.exe "C:\Program Files\Dell\Dell Data Protection\Threat Protection
\DellAVAgent.exe" -InstallSDK -RemoveRightClick -RemoveMcTray >"C:\ProgramData\Dell\Dell Data
Protection\Installer Logs\McAfeeSDKInstallerAfterEndPoint.log"
SED Client (including Advanced Authentication) and
Encryption External Media
The following example installs remotely managed SED (silent installation, no reboot, no entry in the Control Panel Programs list, installed
in the default location of C:\Program Files\Dell\Dell Data Protection).
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 ARPSYSTEMCOMPONENT=1 /
norestart /qn"
Then:
The following example installs Advanced Authentication (silent installation, no reboot, installed in the default location of C:\Program
Files\Dell\Dell Data Protection\Authentication).
setup.exe /s /v"/norestart /qn ARPSYSTEMCOMPONENT=1"
Then:
The following example installs Encryption External Media only (silent installation, no reboot, installed in the default location of C:
\Program Files\Dell\Dell Data Protection).
DDPE_XXbit_setup.exe /s /v"EME=1 SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com DEVICESERVERURL=https://server.organization.com:8443/
xapi/ MANAGEDDOMAIN=ORGANIZATION /norestart /qn"
BitLocker Manager and Encryption External Media
The following example installs BitLocker Manager (silent installation, no reboot, no entry in the Control Panel Programs list, installed in
the default location of C:\Program Files\Dell\Dell Data Protection).
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 FEATURE=BLM /norestart /qn"
Then:
The following example installs Encryption External Media only (silent installation, no reboot, installed in the default location of C:
\Program Files\Dell\Dell Data Protection).
DDPE_XXbit_setup.exe /s /v"EME=1 SERVERHOSTNAME=server.organization.com
POLICYPROXYHOSTNAME=rgk.organization.com DEVICESERVERURL=https://server.organization.com:8443/
xapi/ MANAGEDDOMAIN=ORGANIZATION /norestart /qn"
78 Dell Data Security Endpoint Security Suite Enterprise
Commonly Used Scenarios
BitLocker Manager and Advanced Threat Prevention
The following example installs BitLocker Manager (silent installation, no reboot, no entry in the Control Panel Programs list, installed in
the default location of C:\Program Files\Dell\Dell Data Protection).This component installs the Dell Encryption Management Agent that
is required by Advanced Threat Prevention.
EMAgent_XXbit_setup.exe /s /v"CM_EDITION=1 SERVERHOST=server.organization.com SERVERPORT=8888
SECURITYSERVERHOST=server.organization.com SECURITYSERVERPORT=8443 FEATURE=BLM /norestart /qn"
Then:
The following example installs Advanced Threat Prevention (silent installation, no reboot, installation log le and installation folder in the
specied locations)
MSIEXEC.EXE /I "ATP_CSF_Plugins_x64.msi" /qn REBOOT="ReallySuppress"
ARPSYSTEMCOMPONENT="1" /l*v "C:\ProgramData\Dell\Dell Data Protection\Installer Logs\ATP.log"
APPFOLDER="C:\Program Files\Dell\Dell Data Protection\Advanced Threat Prevention"
Dell Data Security Endpoint Security Suite Enterprise
Commonly Used Scenarios
79
Provision a Tenant for Advanced Threat
Prevention
If your organization is using Advanced Threat Prevention, a tenant must be provisioned in the Dell Server before Advanced Threat
Prevention enforcement of policies becomes active.
Prerequisites
Must be performed by an administrator with the System Administrator role.
Must have connectivity to the Internet to provision on the Dell Server.
Must have connectivity to the Internet on the client to display the Advanced Threat Prevention online service integration in the Remote
Management Console.
Provisioning is based o of a token that is generated from a certicate during provisioning.
Advanced Threat Prevention licenses must be present in the Dell Server.
Provision a Tenant
1 Log in to the Remote Management Console and navigate to Services Management.
2 Click Set Up Advanced Threat Protection Service. Import your Advanced Threat Prevention licenses if failure occurs at this point.
10
80 Dell Data Security Endpoint Security Suite Enterprise
Provision a Tenant for Advanced Threat Prevention
3 The guided set up begins once the licenses are imported. Click Next to begin.
4 Read and agree to the EULA (the check box is o by default) and click Next.
Dell Data Security Endpoint Security Suite Enterprise
Provision a Tenant for Advanced Threat Prevention
81
5 Provide identifying credentials to the Dell Server for provisioning of the Tenant. Click Next. Provisioning an existing Tenant that is
Cylance-branded is not supported.
6 Download the Certicate. This is required to recover if there is a disaster scenarios with the Dell Server. This Certicate is not
automatically backed up. Back up the Certicate to a safe location on a dierent computer. Check the box to conrm that you backed
up the Certicate and click Next.
82 Dell Data Security Endpoint Security Suite Enterprise
Provision a Tenant for Advanced Threat Prevention
7 Set up is complete. Click OK.
Dell Data Security Endpoint Security Suite Enterprise
Provision a Tenant for Advanced Threat Prevention
83
Congure Advanced Threat Prevention Agent
Auto Update
In the Dell Server Remote Management Console, you can enroll to receive Advanced Threat Prevention agent auto updates. Enrolling to
receive agent auto updates allows clients to automatically download and apply updates from the Advanced Threat Prevention service.
Updates are released monthly.
NOTE:
Agent auto updates are supported with Dell Server v9.4.1 or later.
Receive agent auto updates
To enroll to receive agent auto updates:
1 In the left pane of the Remote Management Console, click Management > Services Management.
2 On the Advanced Threats tab, under Agent Auto Update, click the On button then click the Save Preferences button.
It may take a few moments for the information to populate and for auto updates to display.
Stop receiving agent auto updates
To stop receiving agent auto updates:
1 In the left pane of the Remote Management Console, click Management > Services Management.
2 On the Advanced Threats tab, under Agent Auto Update, click the O button then click the Save Preferences button.
11
84 Dell Data Security Endpoint Security Suite Enterprise
Congure Advanced Threat Prevention Agent Auto Update
Pre-Installation Conguration for SED UEFI, and
BitLocker Manager
Initialize the TPM
You must be a member of the local Administrators group, or equivalent.
The computer must be equipped with a compatible BIOS and a TPM.
Follow the instructions located at http://technet.microsoft.com/en-us/library/cc753140.aspx.
Pre-Installation Conguration for UEFI Computers
Enable Network Connectivity During UEFI Preboot
Authentication
In order for preboot authentication to succeed on a computer with UEFI rmware, the PBA must have network connectivity. By default,
computers with UEFI rmware do not have network connectivity until the operating system is loaded, which occurs after PBA mode.
The following procedure enables network connectivity during PBA for UEFI-enabled computers. Because the conguration steps vary from
one UEFI computer model to the next, the following procedure is only an example.
1 Boot into the UEFI rmware conguration.
2 Press F2 continuously during boot until you see a message in the upper right screen similar to "preparing one-time boot menu."
3 Enter the BIOS administrator password, if prompted.
NOTE:
Typically, you will not see this prompt if this is a new computer since the BIOS password has not yet been
congured.
4 Select System Conguration.
5 Select Integrated NIC.
6 Select the Enable UEFI Network Stack check box.
7 Select either Enabled or Enabled w/PXE.
8 Select Apply
12
Dell Data Security Endpoint Security Suite Enterprise
Pre-Installation Conguration for SED UEFI, and BitLocker Manager
85
NOTE:
Computers without UEFI rmware do not require conguration.
Disable Legacy Option ROMs
Ensure that the Enable Legacy Option ROMs setting is disabled in the BIOS.
1 Restart the computer.
2 As it is restarting, press F12 repeatedly to bring up the UEFI computer's boot settings.
3 Press the down arrow, highlight the BIOS Settings option, and press Enter.
4 Select Settings > General > Advanced Boot Options.
5 Clear the Enable Legacy Option ROMs check box and click Apply.
Pre-Installation Conguration to Set Up a BitLocker
PBA Partition
You must create the PBA partition before installing BitLocker Manager.
Turn on and activate the TPM before installing BitLocker Manager. BitLocker Manager will take ownership of the TPM (a reboot will
not be required). However, if the TPM's ownership already exists, BitLocker Manager will begin the encryption setup process. The point
is that the TPM must be "owned".
You may need to partition the disk manually. See Microsoft's description of the BitLocker Drive Preparation Tool for further information.
Use the BdeHdCfg.exe command to create the PBA partition. The default parameter indicates that the command line tool will follow
the same process as the BitLocker Setup Wizard.
BdeHdCfg -target default
TIP:
For more options available for the BdeHdCfg command, see Microsoft's BdeHdCfg.exe Parameter Reference.
86 Dell Data Security Endpoint Security Suite Enterprise
Pre-Installation Conguration for SED UEFI, and BitLocker Manager
Set GPO on Domain Controller to Enable
Entitlements
If your clients will be entitled from Dell Digital Delivery (DDD), follow these instructions to set the GPO on the domain controller to
enable entitlements (this may not be the same server running the Security Management Server/Security Management Server Virtual).
The workstation must be a member of the OU where the GPO is applied.
NOTE:
Ensure that outbound port 443 is available to communicate with the Security Management Server/Security Management Server
Virtual. If port 443 is blocked (for any reason), the entitlement functionality will not work.
1On the Domain Controller to manage the clients, click Start > Administrative Tools > Group Policy Management.
2 Right-click the OU where the policy should be applied and select Create a GPO in this domain, and Link it here....
3 Enter a name for the new GPO, select (none) for Source Starter GPO, and click OK.
4 Right-click the GPO that was created and select Edit.
5 The Group Policy Management Editor loads. Access Computer Conguration > Preferences > Windows Settings > Registry.
13
Dell Data Security Endpoint Security Suite Enterprise
Set GPO on Domain Controller to Enable Entitlements
87
6 Right-click the Registry and select New > Registry Item. Complete the following.
Action: Create
Hive: HKEY_LOCAL_MACHINE
Key Path: SOFTWARE\Dell\Dell Data Protection
Value name: Server
Value type: REG_SZ
Value data: <IP address of the Security Management Server/Security Management Server Virtual>
7 Click OK.
88 Dell Data Security Endpoint Security Suite Enterprise
Set GPO on Domain Controller to Enable Entitlements
8 Log out and then back into the workstation, or run gpupdate /force to apply the group policy.
Dell Data Security Endpoint Security Suite Enterprise
Set GPO on Domain Controller to Enable Entitlements
89
Extract the Child Installers from the Endpoint
Security Suite Enterprise Master Installer
To install each client individually, extract the child executable les from the installer.
The master installer is not a master uninstaller. Each client must be uninstalled individually, followed by uninstallation of the master
installer. Use this process to extract the clients from the master installer so that they can be used for uninstallation.
1 From the Dell installation media, copy the DDSSuite.exe le to the local computer.
2 Open a command prompt in the same location as the DDSSuite.exe le and enter:
DDSSuite.exe /z"\"EXTRACT_INSTALLERS=C:\extracted\""
The extraction path cannot exceed 63 characters.
Before you begin installation, ensure that all prerequisites have been met and all required software has been installed for each child
installer that you plan to install. Refer to Requirements for details.
The extracted child installers are located at C:\extracted\.
14
90 Dell Data Security Endpoint Security Suite Enterprise
Extract the Child Installers from the Endpoint Security Suite Enterprise Master Installer
Congure Key Server for Uninstallation of
Encryption Client Activated Against Security
Management Server
This section explains how to congure components for use with Kerberos Authentication/Authorization when using an Security
Management Server. The Security Management Server Virtual does not use the Key Server.
The Key Server is a Service that listens for clients to connect on a socket. Once a client connects, a secure connection is negotiated,
authenticated, and encrypted using Kerberos APIs (if a secure connection cannot be negotiated, the client is disconnected).
The Key Server then checks with the Security Server (formerly the Device Server) to see if the user running the client is allowed to
access keys. This access is granted on the Remote Management Console via individual domains.
If Kerberos Authentication/Authorization is to be used, then the server that contains the Key Server component will need to be part of
the aected domain.
Because the Security Management Server Virtual does not use the Key Server, typical uninstallation is aected. When an Encryption
client that is activated against a Security Management Server Virtual is uninstalled, standard forensic key retrieval through the Security
Server is used, instead of the Key Server's Kerberos method. See Command Line Uninstallation for more information.
Services Panel - Add Domain Account User
1 On the Security Management Server, navigate to the Services panel (Start > Run... > services.msc > OK).
2 Right-click Key Server and select Properties.
3 Select the Log On tab and select the This account: option.
In the This account: eld, add the domain account user. This domain user must have at least local administrator rights to the Key
Server folder (must be able to write to the Key Server cong le, as well as the ability to write to the log.txt le).
Enter and conrm the password for the domain user.
Click OK.
15
Dell Data Security Endpoint Security Suite Enterprise
Congure Key Server for Uninstallation of Encryption Client Activated Against Security Management Server
91
4 Restart the Key Server Service (leave the Services panel open for further operation).
5 Navigate to <Key Server install dir> log.txt to verify that the Service started properly.
Key Server Cong File - Add User for Security
Management Server Communication
1 Navigate to <Key Server install dir>.
2 Open Credant.KeyServer.exe.cong with a text editor.
3 Go to <add key="user" value="superadmin" /> and change the "superadmin" value to the name of the appropriate user (you may also
leave as "superadmin").
The "superadmin" format can be any method that can authenticate to the Security Management Server. The SAM account name,
UPN, or domain\username is acceptable. Any method that can authenticate to the Security Management Server is acceptable
because validation is required for that user account for authorization against Active Directory.
For example, in a multi-domain environment, only entering a SAM account name such as "jdoe" will likely fail because the Security
Management Server will not be able to authenticate "jdoe" because it cannot nd "jdoe". In a multi-domain environment, the UPN is
recommended, although the domain\username format is acceptable. In a single domain environment, the SAM account name is
acceptable.
4 Go to <add key="epw" value="<encrypted value of the password>" /> and change "epw" to "password". Then change "<encrypted
value of the password>" to the password of the user from Step 3. This password is re-encrypted when the Security Management
Server restarts.
If using "superadmin" in Step 3, and the superadmin password is not "changeit", it must be changed here. Save and close the le.
92 Dell Data Security Endpoint Security Suite Enterprise
Congure Key Server for Uninstallation of Encryption Client Activated Against Security Management Server
Sample Conguration File
<?xml version="1.0" encoding="utf-8" ?>
<conguration>
<appSettings>
<add key="port" value="8050" /> [TCP port the Key Server will listen to. Default is 8050.]
<add key="maxConnections" value="2000" /> [number of active socket connections the Key Server will allow]
<add key="url" value="https://keyserver.domain.com:8443/xapi/" /> [Security Server (formerly Device Server) URL (the format is
8081/xapi for a pre-v7.7 Security Management Server)]
<add key="verifyCerticate" value="false" /> [true veries certs/set to false to not verify or if using self-signed certs]
<add key="user" value="superadmin" /> [User name used to communicate with the Security Server. This user must have the administrator
role selected in the Remote Management Console. The "superadmin" format can be any method that can authenticate to the Security
Management Server. The SAM account name, UPN, or domain\username is acceptable. Any method that can authenticate to the Security
Management Server is acceptable because validation is required for that user account for authorization against Active Directory. For
example, in a multi-domain environment, only entering a SAM account name such as "jdoe" will likely fail because the Security Management
Server will not be able to authenticate "jdoe" because it cannot nd "jdoe". In a multi-domain environment, the UPN is recommended,
although the domain\username format is acceptable. In a single domain environment, the SAM account name is acceptable.]
<add key="cacheExpiration" value="30" /> [How often (in seconds) the Service should check to see who is allowed to ask for keys.
The Service keeps a cache and keeps track of how old it is. Once the cache is older than the value, it gets a new list. When a user
connects, the Key Server needs to download authorized users from the Security Server. If there is no cache of these users, or the list has
not been downloaded in the last "x" seconds, it will be downloaded again. There is no polling, but this value congures how stale the list can
become before it is refreshed when it is needed.]
<add key="epw" value="encrypted value of the password" /> [Password used to communicate with the Security Server. If the
superadmin password has been changed, it must be changed here.]
</appSettings>
</conguration>
Services Panel - Restart Key Server Service
1 Go back to the Services panel (Start > Run... > services.msc > OK).
2 Restart the Key Server Service.
3 Navigate to <Key Server install dir> log.txt to verify that the Service started properly.
4 Close the Services panel.
Remote Management Console - Add Forensic
Administrator
1 If needed, log on to the Remote Management Console.
2 Click Populations > Domains.
3 Select the appropriate Domain.
4 Click the Key Server tab.
Dell Data Security Endpoint Security Suite Enterprise
Congure Key Server for Uninstallation of Encryption Client Activated Against Security Management Server
93
5 In the Account eld, add the user that will be performing the administrator activities. The format is DOMAIN\UserName. Click Add
Account.
6 Click Users in the left menu. In the search box, search for the username added in Step 5. Click Search.
7 Once the correct user is located, click the Admin tab.
8 Select Forensic Administrator and click Update.
The components are now congured for Kerberos Authentication/Authorization.
94 Dell Data Security Endpoint Security Suite Enterprise
Congure Key Server for Uninstallation of Encryption Client Activated Against Security Management Server
Use the Administrative Download Utility
(CMGAd)
This utility allows the download of a key material bundle for use on a computer that is not connected to an Security Management
Server/Security Management Server Virtual.
This utility uses one of the following methods to download a key bundle, depending on the command line parameter passed to the
application:
Forensic Mode - Used if -f is passed on the command line or if no command line parameter is used.
Admin Mode - Used if -a is passed on the command line.
Log les can be located at C:\ProgramData\CmgAdmin.log
Use the Administrative Download Utility in Forensic
Mode
1 Double-click cmgad.exe to launch the utility or open a command prompt where CMGAd is located and type cmgad.exe -f (or
cmgad.exe).
2 Enter the following information (some elds may be pre-populated).
Device Server URL: Fully qualied Security Server (Device Server) URL. The format is https://securityserver.domain.com:8443/xapi/.
Dell Admin: Name of the administrator with forensic administrator credentials (enabled in the Remote Management Console), such as
jdoe
Password: Forensic administrator password
MCID: Machine ID, such as machineID.domain.com
DCID: First eight digits of the 16-digit Shield ID
TIP:
Usually, specifying either the MCID or DCID are sucient. However, if both are known, it is helpful to enter both. Each parameter
contains dierent information about the client and client computer.
Click Next.
16
Dell Data Security Endpoint Security Suite Enterprise
Use the Administrative Download Utility (CMGAd)
95
3 In the Passphrase: eld, type a passphrase to protect the download le. The passphrase must be at least eight characters long, and
contain at least one alphabetic and one numeric character. Conrm the passphrase.
Either accept the default name and location of where the le will be saved to or click ... to select a dierent location.
Click Next.
A message displays, indicating that the key material was successfully unlocked. Files are now accessible.
4 Click Finish when complete.
96 Dell Data Security Endpoint Security Suite Enterprise
Use the Administrative Download Utility (CMGAd)
Use the Administrative Download Utility in Admin
Mode
The Security Management Server Virtual does not use the Key Server, so Admin mode cannot be used to obtain a key bundle from a
Security Management Server Virtual. Use Forensic mode to obtain the key bundle if the client is activated against a Security Management
Server Virtual.
1 Open a command prompt where CMGAd is located and type cmgad.exe -a.
2 Enter the following information (some elds may be pre-populated).
Server: Fully qualied hostname of the Key Server, such as keyserver.domain.com
Port Number: The default port is 8050
Server Account: The domain user the Key Server is running as. The format is domain\username. The domain user running the utility
must be authorized to perform the download from the Key Server
MCID: Machine ID, such as machineID.domain.com
DCID: First eight digits of the 16-digit Shield ID
TIP:
Usually, specifying either the MCID or DCID are sucient. However, if both are known, it is helpful to enter both. Each parameter
contains dierent information about the client and client computer.
Click Next.
3 In the Passphrase: eld, type a passphrase to protect the download le. The passphrase must be at least eight characters long, and
contain at least one alphabetic and one numeric character.
Conrm the passphrase.
Either accept the default name and location of where the le will be saved or click ... to select a dierent location.
Dell Data Security Endpoint Security Suite Enterprise
Use the Administrative Download Utility (CMGAd)
97
Click Next.
A message displays, indicating that the key material was successfully unlocked. Files are now accessible.
4 Click Finish when complete.
98 Dell Data Security Endpoint Security Suite Enterprise
Use the Administrative Download Utility (CMGAd)
Congure Server Encryption
Enable Server Encryption
NOTE:
Server Encryption converts User encryption to Common encryption.
1Log in as a Dell Administrator on the Dell Remote Management Console.
2 Select Endpoint Group (or Endpoint), search for the endpoint or endpoint group you want to enable, select Security Policies, and
then select the Server Encryption policy category.
3 Set the following policies:
Server Encryption - Select to enable Server Encryption and related policies.
SDE Encryption Enabled - Select to turn on SDE encryption.
Encryption Enabled - Select to turn on Common encryption.
Secure Windows Credentials - This policy is Selected by default.
When the Secure Windows Credentials policy is Selected (the default), all les in the \Windows\system32\cong les folder are
encrypted, including Windows credentials. To prevent Windows credentials from being encrypted, set the Secure Windows
Credentials policy to Not Selected. Encryption of Windows credentials occurs independently of the SDE Encryption Enabled
policy setting.
4 Save and commit the policies.
Customize Activation Logon Dialog
The Activation Logon dialog displays:
When an unmanaged user logs on.
When the user selects Activate Dell Encryption from the Encryption icon's menu, located in the system tray.
17
Dell Data Security Endpoint Security Suite Enterprise
Congure Server Encryption
99
Set Encryption External Media Policies
The
originating encrypting computer
is the computer that originally encrypts a removable device. When the originating computer is a
protected server
- a server with Server Encryption installed and activated - and the protected server rst detects the presence of a
removable device, the user is prompted to encrypt the removable device.
Encryption External Media policies control removable media access to the server, authentication, encryption, and more.
Port Control policies aect removable media on protected servers, for example, by controlling access and usage of the Server's USB
ports by USB devices.
The policies for removable media encryption can be found in the Remote Management Console under the Server Encryption technology
group.
Server Encryption and External Media
When the protected server's EMS Encrypt External Media policy is Selected, external media is encrypted. Server Encryption links the
device to the protected server with the Machine key and to the user, with the User Roaming key of the removable device's owner/user. All
les added to the removable device will then be encrypted with those same keys, regardless of the computer it is connected to.
NOTE:
Server Encryption converts User encryption to Common encryption, except on removable devices. On removable devices, encryption
is performed with the User roaming key associated with the computer.
When the user does not agree to encrypt the removable device, the user's access to the device can be set to blocked when used on the
protected server, Read only while used on the protected server, or Full access. The protected server's policies determine the level of access
on an unprotected removable device.
Policy updates occur when the removable device is re-inserted into the originating protected server.
Authentication and External Media
The protected server's policies determine authentication functionality.
After a removable device has been encrypted, only its owner/user can access the removable device on the protected server. Other users
will not be able to access the encrypted les on the removable media.
Local automatic authentication allows the protected removable media to be automatically authenticated when inserted in the protected
server when the owner of that media is logged in. When automatic authentication is disabled, the owner/user must authenticate to access
the protected removable device.
When a removable device's originating encrypting computer is a protected server, the owner/user must always log in to the removable
device when using it on non-originating computers, regardless of the Encryption External Media policy settings dened on the other
computers.
Refer to AdminHelp for information on Server Encryption Port Control and Encryption External Media policies.
Suspend an Encrypted Server Instance
Suspending an encrypted server prevents access to its encrypted data after a restart. The virtual server user cannot be suspended.
Instead, the Server Encryption Machine key is suspended.
NOTE:
Suspending the server endpoint does not immediately suspend the server. The suspension takes place the next time the key is
requested, typically the next time the server is restarted.
100 Dell Data Security Endpoint Security Suite Enterprise
Congure Server Encryption
IMPORTANT:
Use with care. Suspending an encrypted server instance could result in instability, depending on policy settings and whether the
protected server is suspended while disconnected from the network.
Prerequisites
Help Desk Administrator rights, assigned in the Remote Management Console, are required to suspend an endpoint.
The administrator must be logged in to the Remote Management Console.
In the left pane of the Remote Management Console, click Populations > Endpoints.
Search or select a Hostname, then click the Details & Actions tab.
Under Server Device Control, click Suspend then Yes.
NOTE:
Click the Reinstate button to allow Server Encryption to access encrypted data on the server after it restarts.
Dell Data Security Endpoint Security Suite Enterprise
Congure Server Encryption
101
Congure Deferred Activation
The Encryption client with Deferred Activation diers from the Encryption client activation in two ways:
Device-based Encryption policies
The Encryption client policies are user-based; the Encryption client with Deferred Activation's encryption policies are device-based. User
encryption is converted to Common encryption. This dierence allows the user to bring a personal device to use within the organization's
domain, while the organization maintains its security by centrally managing encryption policies.
Activation
With the Encryption client, activation is automatic. When Endpoint Security Suite Enterprise with Deferred Activation is installed, automatic
activation is disabled. Instead, the user chooses whether to activate encryption, and when to activate it.
IMPORTANT:
Before a user permanently leaves the organization and while his email address is still active, the user must run the Encryption Removal
Agent and uninstall the Encryption client from his personal computer.
Deferred Activation Customization
These client-side tasks allow Deferred Activation customization.
Add a disclaimer to the Activation Logon dialog box
Disable automatic re-activation (optional)
Add a disclaimer to the Activation Logon dialog box
The Activation Logon dialog displays at these times:
When an unmanaged user logs on.
When the user decides to activate encryption and selects Activate Encryption from the system tray Encryption icon menu.
18
102 Dell Data Security Endpoint Security Suite Enterprise
Congure Deferred Activation
Install the Encryption Client with Deferred Activation
To install the Encryption client with Deferred Activation, install the Encryption client with the OPTIN=1 parameter. For more information
about client installation with the OPTIN=1 parameter, see Install Encryption Client.
Activate the Encryption Client with Deferred
Activation
Activation associates a domain user with a local user account and a specic computer.
Multiple users can activate on the same computer, provided they use unique local accounts and have unique domain email addresses.
A user can activate the Encryption client only once per domain account.
Before you activate the Encryption client:
Log in to the local account that you use the most often. The data associated with this account is the data that will be encrypted.
Connect to your organization's network.
1 Log on to the workstation or server.
2 Enter the domain email address and password and click Activate.
NOTE:
Non-domain or personal email addresses cannot be used for activation.
3 Click Close.
Dell Data Security Endpoint Security Suite Enterprise
Congure Deferred Activation
103
The Dell Server combines the encryption key bundle with the user's credentials and with the computer's unique ID (machine ID),
creating an unbreakable relationship between the key bundle, the specic computer, and the user.
4 Restart the computer to begin the encryption sweep.
NOTE:
The Local Management Console, accessible from the system tray icon, shows the policies sent by the Server, not the eective
policy.
Troubleshoot Deferred Activation
Troubleshoot Activation
Problem: Cannot access certain les and folders
Inability to access certain les and folders is a symptom of being logged in with a dierent account than the one under which the user
activated.
The Activation Logon dialog automatically displays even though the user has previously activated.
Possible Solution
Log out and log back in with the credentials of the activated account and try to access the les again.
In the rare event that the Encryption client cannot authenticate the user, the Activation Logon dialog prompts the user for credentials to
authenticate and access encryption keys. To use the automatic re-activation feature, the AutoReactivation and AutoPromptForActivation
registry keys must BOTH be enabled. Although the feature is enabled by default, it can be manually disabled. For more information, see
Disable Automatic Re-activation.
Error Message: Server Authentication Failed
The Server was not able to authenticate the email address and password.
Possible Solutions
Use the email address associated with the organization. Personal email addresses cannot be used for activation.
Re-enter the email address and password and ensure there are no typographical errors.
Ask the administrator to verify that the email account is active and is not locked.
Ask the administrator to reset the user's domain password.
Error Message: Network connection error
The Encryption client could not communicate with the Dell Server.
Possible Solutions
Connect directly to the organization's network and try to activate again.
If VPN access is required to connect to the network, check the VPN connection and try again.
Check the Dell Server URL to ensure it matches the URL provided by the administrator.
The URL and other data that the user entered into the installer are stored in the registry. Check the accuracy of the data under [HKLM
\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield] and [HKLM\SOFTWARE\Microsoft\Windows NT
\CurrentVersion\Winlogon\CMGShield\Servlet]
Disconnect and reconnect:
Disconnect the computer from the network.
104 Dell Data Security Endpoint Security Suite Enterprise
Congure Deferred Activation
Reconnect to the network.
Restart the computer.
Try to connect to the network again.
Error Message: Legacy Server Not Supported
Encryption cannot be activated against a legacy server; the Dell Server must be v9.1 or higher.
Possible Solution
Check the Dell Server URL to ensure it matches the URL provided by the administrator.
The URL and other data that the user entered into the installer are stored in the registry.
Check the accuracy of the data under [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield] and [HKLM
\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\Servlet]
Error Message: Domain User Already Activated
A second user has logged on to the local computer and tried to activate against a domain account that has already been activated.
A user can activate the Encryption client only once per domain account.
Possible Solution
Decrypt and uninstall the Encryption client while logged in as the second activated user.
Error Message: Server Error General
An error has occurred on the Server.
Possible Solution
The administrator should check the Server logs to ensure services are running.
The user should try to activate later.
Tools
CMGAd
Use the CMGAd utility prior to launching the Encryption Removal Agent to obtain the encryption key bundle. The CMGAd utility and its
instructions are located in the Dell installation media (Dell-Oine-Admin-XXbit)
Log Files
In C:\ProgramData\Dell\Dell Data Protection\Encryption, look for the log le called CmgSysTray.
Search for the phrase "Manual activation result".
The error code is on the same line, followed by " status = "; the status indicates what went wrong.
Dell Data Security Endpoint Security Suite Enterprise
Congure Deferred Activation
105
Troubleshooting
All Clients - Troubleshooting
Endpoint Security Suite Enterprise master installer log les are located at C:\ProgramData\Dell\Dell Data Protection\Installer.
Windows creates unique child installer installation log les for the logged in user at %temp%, located at C:\Users\<UserName>
\AppData\Local\Temp.
Windows creates log les for client prerequisites, such as Visual C++, for the logged in user at %temp%, located at C:\Users
\<UserName>\AppData\Local\Temp. For example, C:\Users\<UserName>\AppData\Local\Temp
\dd_vcredist_amd64_20160109003943.log
Follow the instructions at http://msdn.microsoft.com to verify the version of Microsoft .Net that is installed on the computer targeted
for installation.
Go to https://www.microsoft.com/en-us/download/details.aspx?id=30653to download the full version of Microsoft .Net Framework
4.5.2 or later.
See this document if the computer targeted for installation has (or has had in the past) Dell Access installed. DDP|A is not compatible
with this suite of products.
All Clients - Protection Status
A new method for deriving a device's protected status has been implemented in the Dell Security Management Server v9.8.2. Previously,
the Endpoint Protected Status area in the management console's Dashboard would only denote the state of Encryption per device.
Protected status is now denoted if any of the following criteria have been met:
Advanced Threat Prevention is installed and enabled.
Web Protection or Client Firewall is installed and either Web Protection or Client Firewall's policy is enabled.
Dell Data Guardian is installed and enabled.
Self-Encrypting Drive Management is installed, enabled, and the Pre-Boot Authentication (PBA) is enabled.
BitLocker Manager is installed, enabled, and encryption has completed.
Dell Encryption (Mac) is installed and enabled, and policy-based encryption has been enforced.
Dell Encryption (Windows) is installed, enabled, Policy-Based Encryption has been set for the endpoint, and device sweeps are
completed.
Encryption and Server Encryption Client
Troubleshooting
Upgrade to the Windows 10 Creators Update
To upgrade to the Windows 10 Fall Creators Update version, follow the instructions in the following article: http://www.dell.com/support/
article/us/en/19/SLN298382.
19
106 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
Activation on a Server Operating System
When Encryption is installed on a server operating system, activation requires two phases of activation: initial activation and device
activation.
Troubleshooting Initial Activation
Initial activation fails when:
A valid UPN cannot be constructed using the supplied credentials.
The credentials are not found in the enterprise vault.
The credentials used to activate are not the Domain Administrator's credentials.
Error Message: Unknown user name or bad password
The user name or password does not match.
Possible Solution: Try to log in again, ensuring that you type the user name and password exactly.
Error Message: Activation failed because the user account does not have domain admin rights.
The credentials used to activate do not have domain administrator rights, or the administrator's username was not in UPN format.
Possible Solution: In the Activation dialog, enter credentials for a domain Administrator and ensure that they are in UPN format.
Error Messages: A connection with the server could not be established.
or
The operation timed out.
Server Encryption could not communicate with port 8449 over HTTPS to the Dell Server.
Possible Solutions
Connect directly to your network and try to activate again.
If connected by VPN, try connecting directly to the network and try again to activate.
Check the Dell Server URL to ensure it matches the URL supplied by the administrator. The URL and other data that the user entered
into the installer are stored in the registry. Check the accuracy of the data under [HKLM\SOFTWARE\Microsoft\Windows NT
\CurrentVersion\Winlogon\CMGShield] and [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield
\Servlet].
Disconnect the server from the network. Restart the server and reconnect to the network.
Error Message: Activation failed because the Server is unable to support this request.
Possible Solutions
Server Encryption cannot be activated against a legacy server; the Dell Server version must be version 9.1 or higher. If necessary,
upgrade your Dell Server to version 9.1 or higher.
Check the Dell Server URL to ensure it matches the URL supplied by the administrator. The URL and other data that the user entered
into the installer are stored in the registry.
Check the accuracy of the data under [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield] and [HKLM
\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield\Servlet].
Initial Activation Process
The following diagram illustrates a successful initial activation.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
107
The initial activation process of Server Encryption requires a live user to access the server. The user can be of any type: domain or non-
domain, remote-desktop-connected or interactive user, but the user must have access to Domain Administrator credentials.
The Activation dialog box displays when one of the two following things happens:
A new (unmanaged) user logs on to the computer.
When a new user right-clicks the Encryption client icon in the system tray and selects Activate Dell Encryption.
The initial activation process is as follows:
1 The user logs in.
2 Detecting a new (unmanaged) user, the Activate dialog displays. The user clicks Cancel.
3 The user opens the Server Encryption's About box to conrm that it is running in Server mode.
4 The user right-clicks the Encryption client icon in the system tray and selects Activate Dell Encryption.
5 The user enters Domain Administrator credentials in the Activate dialog.
NOTE:
The requirement for Domain Administrator credentials is a safety measure that prevents Server Encryption from being rolled out
to other server environments that do not support it. To disable the requirement for Domain Administrator credentials, see Before
You Begin.
6 Dell Server checks for the credentials in the enterprise vault (Active Directory or equivalent) to verify that the credentials are Domain
Administrator credentials.
7 A UPN is constructed using the credentials.
8 With the UPN, the Dell Server creates a new user account for the virtual server user, and stores the credentials in the Dell Server's
vault.
The virtual server user account is for the exclusive use of the Encryption client. It will be used to authenticate with the server, to
handle Common encryption keys, and to receive policy updates.
NOTE:
Password and DPAPI authentication are disabled for this account so that only the virtual server user can access encryption keys
on the computer. This account does not correspond to any other user account on the computer or on the domain.
9 When activation is successful, the user restarts the computer, which kicks o the second part of activation, Authentication and
Device Activation.
Troubleshooting Authentication and Device Activation
Device activation fails when:
The initial activation failed.
The connection to the server could not be established.
The trust certicate could not be validated.
108 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
After activation, when the computer is restarted, Server Encryption automatically logs in as the virtual server user, requesting the Machine
key from the Security Management Server. This takes place even before any user can log in.
Open the About dialog to conrm that Server Encryption is authenticated and in Server mode.
If the Encryption client ID is red, encryption has not yet been activated.
In the Remote Management Console, the version of a server with Server Encryption installed is listed as Shield for Server.
If the Machine key retrieval fails due to a network failure, Server Encryption registers for network notications with the operating
system.
If the Machine key retrieval fails:
The virtual server user logon is still successful.
Set up the Retry Interval Upon network Failure policy to make key retrieval attempts on a timed interval.
Refer to AdminHelp, available in the Remote Management Console, for details on the Retry Interval Upon network Failure policy.
Authentication and Device Activation Process
The following diagram illustrates successful authentication and device activation.
1 When restarted after a successful initial activation, a computer with Server Encryption automatically authenticates using the virtual
server user account and runs the Encryption client in Server mode.
2 The computer checks its device activation status with the Dell Server:
If the computer has not previously device-activated, the Dell Server assigns the computer an MCID, a DCID, and a trust
certicate, and stores all of the information in the Dell Server's vault.
If the computer had previously been device-activated, the Dell Server veries the trust certicate.
3 After the Dell Server assigns the trust certicate to the server, the server can access its encryption keys.
4 Device activation is successful.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
109
NOTE:
When running in Server mode, the Encryption client must have access to the same certicate as was used for device activation
to access the encryption keys.
(Optional) Create an Encryption Removal Agent Log File
Before beginning the uninstall process, you can optionally create an Encryption Removal Agent log le. This log le is useful for
troubleshooting an uninstall/decryption operation. If you do not intend to decrypt les during the uninstall process, you do not need to
create this log le.
The Encryption Removal Agent log le is not created until after the Encryption Removal Agent Service runs, which does not happen
until the computer is restarted. Once the client is successfully uninstalled and the computer is fully decrypted, the log le is
permanently deleted.
The log le path is C:\ProgramData\Dell\Dell Data Protection\Encryption.
Create the following registry entry on the computer targeted for decryption.
[HKLM\Software\Credant\DecryptionAgent]
"LogVerbosity"=DWORD:2
0: no logging
1: logs errors that prevent the Service from running
2: logs errors that prevent complete data decryption (recommended level)
3: logs information about all decrypting volumes and les
5: logs debugging information
Find TSS Version
TSS is a component that interfaces with the TPM. To nd the TSS version, go to (default location) C:\Program Files\Dell\Dell Data
Protection\Drivers\TSS\bin > tcsd_win32.exe. Right-click the le and select Properties. Verify the le version on the Details tab.
Encryption External Media and PCS Interactions
To Ensure Media is Not Read-Only and the Port is Not Blocked
The Encryption External Media Access to unShielded Media policy interacts with Port Control System - Storage Class: External Drive
Control policy. If you intend to set the Encryption External Media Access to unShielded Media policy to Full Access, ensure that the Storage
Class: External Drive Control policy is also set to Full Access to ensure that the media is not set to read-only and the port is not blocked.
To Encrypt Data Written to CD/DVD
Set Windows Media Encryption = On.
Set EMS Exclude CD/DVD Encryption = not selected.
Set Subclass Storage: Optical Drive Control = UDF Only.
Use WSScan
WSScan allows you to ensure that all data is decrypted when uninstalling the Encryption client as well as view encryption status and
identify unencrypted les that should be encrypted.
110 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
Administrator privileges are required to run this utility.
Run WSScan
1 From the Dell installation media, copy WSScan.exe to the Windows computer to scan.
2 Launch a command line at the location above and enter wsscan.exe at the command prompt. WSScan launches.
3 Click Advanced.
4 Select the type of drive to scan from the drop-down menu: All Drives, Fixed Drives, Removable Drives, or CDROMs/ DVDROMs.
5 Select the desired Encryption Report Type from the drop-down menu: Encrypted FIles, Unencrypted FIles, All FIles, or Unencrypted
FIles in Violation:
Encrypted FIles - To ensure that all data is decrypted when uninstalling the Encryption client. Follow your existing process for
decrypting data, such as issuing a decryption policy update. After decrypting data, but before performing a restart in preparation
for uninstall, run WSScan to ensure that all data is decrypted.
Unencrypted FIles - To identify les that are not encrypted, with an indication of whether the les should be encrypted (Y/N).
All FIles - To list all encrypted and unencrypted les, with an indication of whether the les should be encrypted (Y/N).
Unencrypted FIles in Violation - To identify les that are not encrypted that should be encrypted.
6 Click Search.
OR
1 Click Advanced to toggle the view to Simple to scan a particular folder.
2 Go to Scan Settings and enter the folder path in the Search Path eld. If this eld is used, the selection in the drop-down box is
ignored.
3 If you do not want to write WSScan output to a le, clear the Output to File check box.
4 Change the default path and lename in Path, if desired.
5 Select Add to Existing File if you do not want to overwrite any existing WSScan output les.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
111
6 Choose the output format:
Select Report Format for a report style list of scanned output. This is the default format.
Select Value Delimited File for output that can be imported into a spreadsheet application. The default delimiter is "|", although it
can be changed to up to 9 alphanumeric, space, or keyboard punctuation characters.
Select the Quoted Values option to enclose each value in double quotation marks.
Select Fixed Width File for non-delimited output containing a continuous line of xed-length information about each encrypted le.
7 Click Search.
Click Stop Searching to stop your search. Click Clear to clear displayed messages.
WSScan Command Line Usage
WSScan [-ta] [-tf] [-tr] [-tc] [drive] [-s] [-o<filepath>] [-a] [-f<format specifier>] [-r] [-
u[a][-|v]] [-d<delimeter>] [-q] [-e] [-x<exclusion directory>] [-y<sleep time>]
112 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
Switch Meaning
Drive Drive to scan. If not specied, the default is all local xed hard drives. Can be a mapped network
drive.
-ta Scan all drives
-tf Scan xed drives (default)
-tr Scan removable drives
-tc Scan CDROMs/DVDROMs
-s Silent operation
-o Output le path
-a Append to output le. The default behavior truncates the output le.
-f Report format specier (Report, Fixed, Delimited)
-r Run WSScan without administrator privileges. Some les may not be visible if this mode is used.
-u Include unencrypted les in output le.
This switch is sensitive to order: "u" must be rst, "a" must be second (or omitted), "-" or "v" must
be last.
-u- Only include unencrypted les in output le
-ua Report unencrypted les also, but use all user policies to display the "should" eld.
-ua- Report unencrypted les only, but use all user policies to display the "should" eld.
-uv Report unencrypted les that violate policy only (Is=No / Should=Y)
-uav Report unencrypted les that violate policy only (Is=No / Should=Y), using all user policies.
-d Species what to use as a value separator for delimited output
-q Species the values that should be in enclosed in quotes for delimited output
-e Include extended encryption elds in delimited output
-x Exclude directory from scan. Multiple exclusions are allowed.
-y Sleep time (in milliseconds) between directories. This switch results in slower scans, but potentially
a more responsive CPU.
WSScan Output
WSScan information about encrypted les contains the following information.
Example Output:
[2015-07-28 07:52:33] SysData.7vdlxrsb._SDENCR_: "c:\temp\Dell - test.log" is still AES256 encrypted
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
113
Output Meaning
Date/time stamp The date and time the le was scanned.
Encryption type The type of encryption used to encrypt the le.
SysData: SDE Encryption Key.
User: User Encryption Key.
Common: Common Encryption Key.
WSScan does not report les encrypted using Encrypt for Sharing.
KCID The Key Computer ID.
As shown in the example above, "7vdlxrsb"
If you are scanning a mapped network drive, the scanning report does not return a KCID.
UCID The User ID.
As shown in the example above, "_SDENCR_"
The UCID is shared by all the users of that computer.
File The path of the encrypted le.
As shown in the example above, "c:\temp\Dell - test.log"
Algorithm The encryption algorithm being used to encrypt the le.
As shown in the example above, "is still AES256 encrypted"
RIJNDAEL 128
RIJNDAEL 256
AES 128
AES 256
3DES
Use WSProbe
The Probing Utility is for use with all versions of the Encryption client, with the exception of Encryption External Media policies. Use the
Probing Utility to:
Scan or schedule scanning of an encrypted computer. The Probing Utility observes your Workstation Scan Priority policy.
Temporarily disable or re-enable the current user Application Data Encryption List.
Add or remove process names on the privileged list.
Troubleshoot as instructed by Dell ProSupport.
Approaches to Data Encryption
If you specify policies to encrypt data on Windows devices, you can use any of the following approaches:
The rst approach is to accept the default behavior of the client. If you specify folders in Common Encrypted Folders or User
Encrypted Folders, or set Encrypt "My Documents", Encrypt Outlook Personal Folders, Encrypt Temporary Files, Encrypt Temporary
Internet Files, or Encrypt Windows Paging File to selected, aected les are encrypted either when they are created, or (after being
114 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
created by an unmanaged user) when a managed user logs on. The client also scans folders specied in or related to these policies for
possible encryption/decryption when a folder is renamed, or when the client receives changes to these policies.
You can also set Scan Workstation on Logon to Selected. If Scan Workstation on Logon is Selected, when a user logs on, the client
compares how les in currently- and previously-encrypted folders are encrypted to the user policies, and makes any necessary changes.
To encrypt les that meet your encryption criteria but were created prior to your encryption policies going into eect, but do not want
the performance impact of frequent scanning, you can use this utility to scan or schedule scanning of the computer.
Prerequisites
The Windows device you want to work with must be encrypted.
The user you want to work with must be logged on.
Use the Probing Utility
WSProbe.exe is located in the installation media.
Syntax
wsprobe [path]
wsprobe [-h]
wsprobe [-f path]
wsprobe [-u n] [-x process_names] [-i process_names]
Parameters
Parameter To
path Optionally specify a particular path on the device that you want to scan for possible encryption/
decryption. If you do not specify a path, this utility scans all folders related to your encryption
policies.
-h View command line Help.
-f Troubleshoot as instructed by Dell ProSupport
-u Temporarily disable or re-enable the user Application Data Encryption List. This list is only eective
if Encryption Enabled is selected for the current user. Specify 0 to disable or 1 to re-enable. The
current policy in force for the user is reinstated at the next logon.
-x Add process names to the privileged list. The computer and installer process names on this list,
plus those you add using this parameter or HKLM\Software\CREDANT\CMGShield
\EUWPrivilegedList, are ignored if specied in the Application Data Encryption List. Separate
process names with commas. If your list includes one or more spaces, enclose the list in double
quotes.
-i Remove process names previously added to the privileged list (you cannot remove hard-coded
process names). Separate process names with commas. If your list includes one or more spaces,
enclose the list in double quotes.
Check Encryption Removal Agent Status
The Encryption Removal Agent displays its status in the description area of the Services panel (Start > Run... > services.msc > OK) as
follows. Periodically refresh the Service (highlight the Service > right-click > Refresh) to update its status.
Waiting for SDE Deactivation - The Encryption client is still installed, is still congured, or both. Decryption does not start until the
Encryption client is uninstalled.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
115
Initial sweep - The Service is making an initial sweep, calculating the number of encrypted les and bytes. The initial sweep occurs one
time.
Decryption sweep - The Service is decrypting les and possibly requesting to decrypt locked les.
Decrypt on Reboot (partial) - The decryption sweep is complete and some locked les (but not all) are to be decrypted on the next
restart.
Decrypt on Reboot - The decryption sweep is complete and all locked les are to be decrypted on the next restart.
All les could not be decrypted - The decryption sweep is complete, but all les could not be decrypted. This status means one of the
following occurred:
The locked les could not be scheduled for decryption because they were too big, or an error occurred while making the request to
unlock them.
An input/output error occurred while decrypting les.
The les could not be decrypted by policy.
The les are marked as should be encrypted.
An error occurred during the decryption sweep.
In all cases, a log le is created (if logging is congured) when LogVerbosity=2 (or higher) is set. To troubleshoot, set the log
verbosity to 2 and restart the Encryption Removal Agent Service to force another decryption sweep. See (Optional) Create an
Encryption Removal Agent Log File for instructions.
Complete - The decryption sweep is complete. The Service, the executable, the driver, and the driver executable are all scheduled for
deletion on the next restart.
Advanced Threat Prevention Client Troubleshooting
Find the Product Code with Windows PowerShell
You can easily identify the product code, if the product code changes in the future, using this method.
Get-WmiObject Win32_Product | Where-Object {$_.Name -like '*Cylance*'} | FT
IdentifyingNumber, Name, LocalPackage
The output will result with the full path and .msi le name (the converted hex name of the le).
116 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
Advanced Threat Prevention Provisioning and Agent
Communication
The following diagrams illustrate the Advanced Threat Prevention service provisioning process.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
117
The following diagram illustrates the Advanced Threat Prevention agent communication process.
118 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
BIOS Image Integrity Verication Process
The following diagram illustrates the BIOS image integrity verication process. For a list of Dell computer models supported with BIOS
image integrity verication, see Requirements - BIOS Image Integrity Verication.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
119
SED Client Troubleshooting
Use the Initial Access Code Policy
This policy is used to log on to a computer when network access is unavailable. Meaning, access to the Security Management Server/
Security Management Server Virtual and AD are both unavailable. Only use the Initial Access Code policy if absolutely necessary. Dell
does not recommend this method to log in. Using the Initial Access Code policy does not provide the same level of security as the usual
method of logging in using username, domain, and password.
120 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
In addition to being a less secure method of logging in, if an end user is activated using the Initial Access Code, then there is no record
on the Security Management Server/Security Management Server Virtual of that user activating on this computer. In turn, there is no
way to generate a Response Code from the Security Management Server/Security Management Server Virtual for the end user if they
fail password and self help questions.
The Initial Access Code can only be used one time, immediately after activation. After an end user has logged in, the Initial Access Code
will not be available again. The rst domain login that occurs after the Initial Access Code is entered will be cached, and the Initial
Access Code entry eld will not be displayed again.
The Initial Access Code will only display under the following circumstances:
A user has never activated inside the PBA.
The client has no connectivity to the network or Security Management Server/Security Management Server Virtual.
Use Initial Access Code
1 Set a value for the Initial Access Code policy in the Remote Management Console.
2 Save and commit the policy.
3 Start the local computer.
4 Enter the Initial Access Code when the Access Code screen displays.
5 Click the blue arrow.
6 Click OK when the Legal Notice screen displays.
7 Log in to Windows with the user credentials for this computer. These credentials must be part of the domain.
8 After logging in, open the Data Security Console and verify that the PBA user was successfully created.
Click Log in the top menu and look for the message Created PBA user for <domain\username>, which indicates the process was
successful.
9 Shut down and restart the computer.
10 At the login screen, enter the username, domain, and password that was previously used to log in to Windows.
You must match the username format that was used when creating the PBA user. Thus, if you used the format domain/username,
you must enter domain/username for the Username.
11 (Credant Manager only) Respond to the Question and Answer prompts.
Click the blue arrow.
12 Click Login when the Legal Notice screen displays.
Windows now launches and the computer can be used as usual.
Create a PBA Log File for Troubleshooting
There may be cases when a PBA log le is needed for troubleshooting PBA issues, such as:
You are unable to see the network connection icon, yet you know there is network connectivity. The log le contains DHCP
information to resolve the issue.
You are unable to see the Security Management Server/Security Management Server Virtual connection icon. The log le contains
information to help diagnose Security Management Server/Security Management Server Virtual connectivity issues.
Authentication fails even when entering correct credentials. The log le used with the Security Management Server/Security
Management Server Virtual Server logs can help diagnose the issue.
Capture Logs When Booting Into the PBA (Legacy PBA)
1 Create a folder on a USB drive and name it \CredantSED, at the root level of the USB drive.
2 Create a le named actions.txt and place it in the \CredantSED folder.
3 In actions.txt, add the line:
get logs
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
121
4 Save and close the le.
Do not insert the USB drive when the computer is powered down. If the USB drive is already inserted during the shutdown state,
remove the USB drive.
5 Power on the computer and log in to the PBA. Insert the USB drive into the computer that the logs are to be collected from during
this step.
6 After inserting the USB drive, wait for 5-10 seconds, then remove the drive.
A credpbaenv.tgz le is created in the \CredantSED folder that contains the needed log les.
Capture Logs When Booting Into the PBA (UEFI PBA)
1 Create a le called PBAErr.log at the root level of the USB drive.
2 Insert the USB drive before powering on the computer.
3 Remove the USB drive after reproducing the issue requiring the logs.
The PBAErr.log le will be updated and written in real-time.
Dell ControlVault Drivers
Update Dell ControlVault Drivers and Firmware
Dell ControlVault drivers and rmware that are installed on Dell computers at the factory are outdated and should be updated by
following this procedure, in this order.
If an error message is received during client installation prompting you to exit the installer to update Dell ControlVault drivers, the
message may be safely dismissed to continue with the installation of the client. The Dell ControlVault drivers (and rmware) can be
updated after the client installation is complete.
Download Latest Drivers
1 Go to support.dell.com.
122 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
2 Select your computer model.
3 Select Drivers & Downloads.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
123
4 Select the Operating System of the target computer.
5 Expand the Security category.
124 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
6 Download and save the Dell ControlVault Drivers.
7 Download and save the Dell ControlVault Firmware.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
125
8 Copy the drivers and rmware to the target computers, if needed.
Install Dell ControlVault Driver
1 Navigate to the folder which you downloaded the driver installation le.
2 Double-click the Dell ControlVault driver to launch the self-extracting executable le.
TIP:
Be sure to install the driver rst. The lename of the driver at the time of this document creation is
ControlVault_Setup_2MYJC_A37_ZPE.exe.
3 Click Continue to begin.
126 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
4 Click Ok to unzip the driver les in the default location of C:\Dell\Drivers\<New Folder>.
5 Click Yes to allow the creation of a new folder.
6 Click Ok when the successfully unzipped message displays.
7 The folder which contains the les should display after extraction. If not, navigate to the folder to which you extracted the les. In this
case, the folder is JW22F.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
127
8 Double-click CVHCI64.MSI to launch the driver installer. [this example is CVHCI64.MSI in this example (CVHCI for a 32-bit
computer)].
9 Click Next at the Welcome screen.
10 Click Next to install the drivers in the default location of C:\Program Files\Broadcom Corporation\Broadcom USH Host Components\.
128 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
11 Select the Complete option and click Next.
12 Click Install to begin the installation of the drivers.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
129
13 Optionally check the box to display the installer log le. Click Finish to exit the wizard.
Verify Driver Installation
The Device Manager will have a Dell ControlVault device (and other devices) depending on the operating system and hardware
conguration.
Install Dell ControlVault Firmware
130 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
1 Navigate to the folder which you downloaded the rmware installation le.
2 Double-click the Dell ControlVault rmware to launch the self-extracting executable le.
3 Click Continue to begin.
4 Click Ok to unzip the driver les in the default location of C:\Dell\Drivers\<New Folder>.
5 Click Yes to allow the creation of a new folder.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
131
6 Click Ok when the successfully unzipped message displays.
7 The folder which contains the les should display after extraction. If not, navigate to the folder to which you extracted the les. Select
the rmware folder.
8 Double-click ushupgrade.exe to launch the rmware installer.
9 Click Start to begin the rmware upgrade.
132 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
IMPORTANT:
You may be asked to enter the admin password if upgrading from an older version of rmware. Enter Broadcom as the
password and click Enter if presented with this dialog.
Several status messages display.
Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
133
134 Dell Data Security Endpoint Security Suite Enterprise
Troubleshooting
10 Click Restart to complete the