Procedure

1. Select Typical.
   
   Click Custom to install the Database Server, Application Server, Web Server, and Assistant Server on a different host.
2. Specify the SecureCloud Web service and console settings in the Website Configuration screen, and then click Next.
   

   Note To secure the Web Service and Web Console connections, SecureCloud requires an HTTPS connection. The SecureCloud runtime agent and Configuration Tool must be able to verify the certificate trust.

   • Host header—assigned FQDN of the target Windows server
     Ensure that the SSL certificate is issued to this host header. If this field is left empty, the full computer name of the target Windows server is used.
   • IP address—select listening IP from the drop-down list
   • Connection port—accept the default or type the connection ports for Central Management Console, SecureCloud Management Console, and Web Service API.
3. Provide the SecureCloud service account.
   Setup requires a Windows account (local or domain user) to run SecureCloud services. If you created new user, the information you specify here is for that user.

   
4. Specify the database connection information.
   

   • Database name—SecureCloud database name.
   • SQL Server name—SQL Server name or IP address and instance name.
   • Failover Partner—mirroring SQL Server

     Note You can skip this field if there is no mirror database available.

   • SQL Server User name and Password—use to access the SQL server and SecureCloud database
     If you have created a dedicated SQL Server user, use that account here.
   • Database encryption backup key
     Next to Key file, click Browse and find the backup key file. Provide its passphrase in the Passphrase box.
     • Initialize key encryption for DB and backup key to file—for fresh install
     • Use an existing key encryption for DB from file—for installing a second SecureCloud server component while there is already an existing database
5. Specify the Reporting Services URL.
   
   • Report Server Web Service URL—type/copy the URL. Check your Reporting Manager URL here.
     Setup displays the following screen when connectivity is verified:

     
   • Report template folder—specify a name to store the report templates. If empty, setup uses the default value (/Home).
   • Archive path—default is C:\inetpub\SecureCloud Management Server\archive\Reports. Setup cannot accept network path. However, UNC path is valid.
6. Specify the account information that will be used to access the SecureCloud Central Management console.

   Note This step only appears if you set assistant server configuration when executing the installation package from a command prompt.

   Type the information needed to logon to the console.

   

   Email and Password—credentials used to log on to the SecureCloud Central Management console.

   

   Tip Access the console locally from the host through the Windows Start shortcut.

7. Specify the assistant server settings.
   Verify that the default settings are correct, and modify them if necessary.
   
   • Web Service HTTP port—port that will access the web service.
   • Python Executable Directory—location of the Python executable file. Click Verify Modules to confirm that all required modules have been properly installed.
8. Click Finish to close the Installation Wizard.
   

   Note Learn about the latest features, known issues, and basic product information by launching the SecureCloud KMS readme after finishing setup.