You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Enable Agent Auto Registration

Installing a DualShield fronend server is like instaling a DualShield agent, it requires Agent Auto Registration to be enabled. 

Install Frontend Server

Execute "DualShieldSetup64-xxx.yyyy-signed.exe" (where xxx is the version number and yyyy the build number) to start installation:

As of version 6.0.0, language translation is still in progress. For now, please select "English".




Please keep the installation path as suggested, unless the C drive does not exisits or for some other reasons. 


Select "Front-end Components" 


If you want to keep the legacy components, make sure that you select the following

  • Legacy SSO Server
  • Legacy Self-Service Server

First, the frontend server must have a different FQDN from the backend server. 

Secondly, if you are upgrading an old DualShield 5 frontend server to DualShield 6 by fresh installation, then you want to keep the FQDN the same as it currently is.

Thirdly, it is recommended that you provide a commercial SSL certificate for your DualShield frontend server as it is meant to be accessed by end-users from the Internet.


Change "dualshield.your-corporate-doamin.com" to the FQDN of your DualShield backend server, e.g. "dualback.deep.net"

Keep the rest of the fields as they are suggested, unless you have special reasons to change them.


The frontend server is not as resource demanding as the backend. The default values should be appropriate in most cases.






Wait for the DualShield server to be fully loaded

DualShield is a set of JAVA server applications. After the installation, upgrade or restart of the DualShield servers, The OS needs to initialise the JAVA virtual machine (JVM) and load the DualShield application into the JVM. This process can be slow and take a long time, depending on the speed and power of the machine. 


To wait for the DualShield server to be fully loaded and monitor the its initialisation progress, launch the Windows Task Manager and check the process called DualShield Server which is often a sub-process of Commons Daemon Service Runner, as shown below:

During the initialisation process, the CPU usage of the DualShield Server process will go up and down, and the Memory consumption will continue to increase.

When the CPU usage drops to zero or slightly above zero, and the memory consumption reaches close to 1.8GB for the backend or 550MB for the frontend, that's the indication that DualShield is fully loaded and ready for operation. 



  • No labels