
Enterprise Server Installation and Migration Guide 53
d
At the
Test Configuration
window, the results of the Test Connection Settings, Compatibility Test, and the Database
Migrated Test display.
You may get a failed test result for the Database Migrated T
est, which is correct – this database has not been migrated
yet. You cannot migrate this database until the two other tests, Test Connection Settings and Compatibility Test, have a
result of Passed.
Click
Finish
.
e
From the top menu, select
Configuration
>
Save
. If prompted, confirm the save.
7
Migrate Database.
a
If you have not yet backed up your existing Dell database,
do so now
.
a
From the top menu, select
Actions
>
Migrate Database
. The Configuration Wizard launches.
b
At the
Migrate Enterprise Database
window, a warning displays. Confirm that you have either backed up the entire
database or confirm that a backup does not need to be made of your existing database. Click
Next
.
c
At the
Migrate Enterprise Database
window, read the information and click
Next
.
At the
Migrating Database
window, informational messages display the status of the migration.
When complete, check for errors.
NOTE: An error message identified by , signifies that a database task has failed and corrective action needs to be
taken before the database can be properly migrated. Click Finish, correct the database errors, and reinitiate
the instructions in this section.
d
Click
Finish
.
e
From the top menu, select
Configuration
>
Save
. If prompted, confirm the save.
8
Configure Certificates.
The first time you run the Dell Server Configuration T
ool for initial Dell Enterprise Server setup, certificates must be configured
for the Dell Compatibility Server, Dell Core Server, and Message Security.
You have a choice of which type of certificates t
o use – self-signed or signed:
–
Self-signed
certificates are signed by their own creator. Self-signed certificates are appropriate for pilots, POCs, etc. For
a production environment, Dell recommends public CA-signed or domain-signed certificates.
–
Signed
(public CA-signed or domain-signed) certificates are signed by a public CA or a domain. In the case of certificates
that are signed by a public certificate authority (CA), the certificate of the signing CA will, usually, already exist in the
Microsoft certificate store and therefore, the chain of trust will be automatically established. For domain CA-signed
certificates, if the workstation has been joined to the domain, the signing CA certificate from the domain will have been
added to the workstation’s Microsoft certificate store, thereby also creating a chain of trust.
The components that are affected by certificat
e configuration:
– Java Services (for instance, Dell Device Server, Dell Console
Web Services, and so on)
– .NET Applications (Dell Core Server)
– Validation of smart cards used for Preboot
Authentication (Dell Security Server)
– Importing of private encryption keys to be used for signing policy bundles being sent to
Dell Manager. Dell Manager
performs SSL validation for remotely-managed Enterprise Edition clients with Hardware Crypto Accelerators,
self-encrypting drives, or BitLocker Manager.
– Client Workstations:
• Workstations running the web browser version of th
e Silverlight Console
• Workstations running Dell Data Protection | BitLocker Manager
• Workstations running Dell Data Protection | Enterprise Edition
(Windows clients)
Information regarding which type of certificates to use:
Preboot Authentication using smart cards requires SSL validation with the Dell Security Server. Dell Manager performs SSL
validation when connecting to the Dell Core Server. The Silverlight Console also performs SSL validation. For these types of
connections, the signing CA will need to be in the keystore (either the Java keystore or the Microsoft keystore, depending on
which Dell Server component is being discussed). If self-signed certificates are chosen, the following options are available:
Commentaires sur ces manuels