Getting Started Dell Data Security Implementation Services
Preparation Checklist - Upgrade/Migration
This checklist applies only to Security Management Server.
NOTE:
Update Security Management Server Virtual from the Basic Configuration menu in your Dell Server Terminal. For more information, see Security Management Server Virtual Quick Start and Installation Guide.
Use the following checklist to ensure you have met all prerequisites before beginning to upgrade Encryption or Endpoint Security Suite Enterprise.
Servers meet required software specifications?
| Windows Server 2012 R2 (Standard or Datacenter), Windows Server 2016 (Standard or Datacenter), Windows Server 2019 (Standard or Datacenter), or Windows Server 2022 (Standard or Datacenter) is installed. Alternatively, a virtualized environment can be installed.
NOTE:Updating to Dell Server v11.0 or higher requires Windows Server 2019 or higher.
|
| Windows Installer 4.0 or later is installed. |
| .NET Framework 4.6.1 is installed. |
| Microsoft SQL Native Client 2012 is installed, if using SQL Server 2012 or SQL Server 2016. If available, SQL Native Client 2014 may be used. NOTE:SQL Express is not supported with
Security Management Server.
|
| Windows Firewall is disabled or configured to allow (inbound) ports 8000, 8050, 8081, 8443, 8888, 61613. |
| Connectivity is available between Security Management Server and Active Directory (AD) over ports 88, 135, 389, 443, 636, 3268, 3269, 49125+ (RPC) (inbound to AD). |
| UAC is disabled before installation on Windows Server 2012 R2 when installing in C:\Program Files. The server must be rebooted for this change to take effect. (see Windows Control Panel > User Accounts).
|
Service accounts successfully created?
| Service account with read-only access to AD (LDAP) - basic user/domain user account is sufficient. |
| Service account must have local administrator rights to the Security Management Server application servers. |
| To use Windows authentication for the database, a domain services account with system administrator rights. The user account must be in the format DOMAIN\Username and have the SQL Server permissions Default Schema: dbo and Database Role Membership: dbo_owner, public. |
| To use SQL authentication, the SQL account used must have system administrator rights on the SQL Server. The user account must have the SQL Server permissions Default Schema: dbo and Database Role Membership: dbo_owner, public. |
Database and all necessary files are backed up?
| The entire existing installation is backed up to an alternate location. The backup should include the SQL database, secretKeyStore, and configuration files. |
| Ensure that these most critical files, which store information necessary to connect to the database, are backed up: <Installation folder>\Enterprise Edition\Compatibility Server\conf\server_config.xml <Installation folder>\Enterprise Edition\Compatibility Server\conf\secretKeyStore <Installation folder>\Enterprise Edition\Compatibility Server\conf\gkresource.xml |
Installation key and license file are available?
| The license key is included in the original email with CFT credentials - see Example Customer Notification Email. This key is also included in the download of the application from http://www.dell.com/support and https://ddpe.credant.com. |
| The license file is an XML file located on the CFT site under in the Client Licenses folder. |
NOTE:
If you purchased your licenses on-the-box, no license file is necessary. The entitlement is automatically downloaded from Dell upon activation of any new Encryption or Endpoint Security Suite Enterprise client.
New and existing Dell Data Security software is downloaded?
Download from Dell Data Security file transfer site (CFT).
| Software is located at https://ddpe.credant.com in the SoftwareDownloads folder. |
| If you purchased Encryption Enterprise or Endpoint Security Suite Enterprise on-the-box (OTB), the software is optionally fulfilled using Dell Digital Delivery. Alternatively, the software can be downloaded from www.dell.com/support or ddpe.credant.com respectively. |
Have enough endpoint licenses?
Prior to upgrading, ensure that you have enough client licenses to cover all of the endpoints in your environment. If your installations currently exceed your license count, contact your Dell Sales Representative prior to upgrading or migrating. Dell Data Security performs license validation, and activations is prevented if no licenses are available.
| I have enough licenses to cover my environment. |
Are DNS records documented?
| Validate that DNS records are documented and staged for update if hardware has been changed. |
Plan for SSL Certificates?
| We have an internal Certificate Authority (CA) that can be used to sign certificates and is trusted by all workstations in the environment or we plan to purchase a signed certificate using a public Certificate Authority, such as VeriSign or Entrust. If using a public Certificate Authority, inform the Dell Client Services Engineer. The Certificate contains the Entire Chain of Trust (Root and Intermediate) with Public and Private Key Signatures. |
| Subject Alternate Names (SANs) on Certificate Request match all DNS aliases given to every server being used for Dell Enterprise Server installation. Does not apply to Wildcard or Self Signed certificate requests. |
| Certificate is generated to a .pfx format. |
Change Control requirements identified and communicated to Dell?
| Submit any specific Change Control requirements for the installation of Encryption or Endpoint Security Suite Enterprise to Dell Client Services prior to the installation engagement. These requirements may include changes to the application server(s), database, and client workstations. |
Test Hardware prepared?
| Prepare at least three computers with your corporate computer image to be used for testing. Dell recommends that you not use productions computers for testing. Production computers should be used during a production pilot after encryption policies have been defined and tested using the Test Plan provided by Dell. |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\