Aegis2.2x Installation Manual
6
With its own HASP key, each workstation is authorized to run Aegis2, and a workstation that is
restarted or taken offline will not affect the others on the system.
1.4
Installing Services on a Server
Occasionally a driver used by the Aegis2 software will have an independent service that aids in
communicating with external hardware. These can be installed on either a workstation or a server (this
can be a shared server). Much like the database, consideration needs to be given to the availability of the
service if it is installed on a workstation. If it is to be installed on a server, all workstations will need to be
configured to have network access, as well as the necessary permissions to access that server.
Additionally, a member of the IT staff will need to be present and have appropriate permissions to install
and configure the service, if necessary, on the server.
1.5
Data Execution Prevention (DEP)
It has been found that Windows Server OS’s often have
Data Execution Prevention
(DEP) defaulted to
Enabled
, which can cause problems with Aegis2 and it’s components. Disabling DEP will prevent these
issues, if the client does not have a problem with this option. You will need to disable DEP and restart the
server for this to take effect. If disabling DEP is not an acceptable option, then any .exe files in the Aegis2
folder will need to be added to the
Exceptions
list for DEP. Aegis2 should run without incident once
these exceptions have been added.
1.6
Running Aegis2 on Redundant Servers
If redundant servers with failover software (EMC, Marathon, etc.) are being utilized, it is the responsibility
of the integrator to know how Aegis2 works and how the failover software needs to be configured to work
with it. Aegis2 does not have any redundancy built into it and can only connect to and update one SQL
database at a time. The database needs to be mirrored for a true failover that avoids any down time.
If the
License Service
is installed in a redundant server environment, it needs to be done with the
awareness that the HASP key necessary for
Network License
mode can only be connected to one
server at a time. In order to failover to the second server, the HASP key will need to be physically moved
to it. We are not able to provide a duplicate HASP key for this purpose. Having the
License Service
installed in a third location can avoid this issue.
KapLogic does not support any Aegis2 software that is being installed and configured in this
environment.
1.7
Use of a Virtual Port Replicator with Aegis2
KapLogic supports connections from the server or workstation to hardware via a serial cable. If a virtual
port replicator, such as Lantronix, is being used, it is the responsibility of the integrator to know how this
feature is installed, configured, and interacts with Aegis2. KapLogic will provide in their driver manuals
what computer or software settings are needed for the driver to connect to the hardware.
