Manually Install The Deep Security Agent - Deep Security
Manually Install The Deep Security Agent - Deep Security
p: For easier agent installation and activation, use a deployment script instead. For more information, see
Use deployment scripts to add and protect computers.
Before installing the Deep Security Agent, you must export the installer. See Get Deep Security Agent
software.
After installation, the agent must be activated before it can protect its computer or be converted into a
relay. See Activate the agent.
In this topic:
2. Double-click the installation file (.MSI file) to run the installer package.
Note: On Windows Server 2012 R2 Server Core, launch the installer using this command instead:
msiexec /i Agent-Core-Windows- 10.1 .x-xxxx.x86_64.msi
The Deep Security Agent is now installed and running on this computer, and will start every time the
machine boots.
te: When installing the agent on Windows 2012 Server Core, the notifier will not be included.
te: During an install, network interfaces will be suspended for a few seconds before being restored. If you
are using DHCP, a new request will be generated, potentially resulting in a new IP address for the
restored connection.
te: Amazon has fixed this issue for newly-deployed Amazon WorkSpaces.
Starting ds_agent: [ OK ]
To upgrade from a previous install, use "rpm -U" instead. This will preserve your profile settings.
Solaris requires the following libraries to be installed to support Deep Security Agent:
5. Install the agent. Method varies by version and zones. File name varies by SPARC vs. x86.
Solaris 10:
pkgrm -v ds-agent
For more information on how to do so, see Use deployment scripts to add and protect computers.