Fortinet Document Library

Version:


Table of Contents

User Guide

21.4.0
Copy Link

Prepare an Agent for server imaging/cloning

For Linux Servers

  • Stop cron from running.
    RHEL: service crond stop
    Ubuntu: systemctl stop cron

  • Confirm that cron is inactive.
    RHEL: service crond status
    Ubuntu: systemctl status cron

You should see output similar to the below snippet to indicate that cron is inactive

# service crond status
Redirecting to /bin/systemctl status crond.service
● crond.service - Command Scheduler

Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)

Active: inactive (dead) since Mon 2021-06-28 16:37:17 EDT; 5s ago

  • Delete the panopta-agent.db file.
    rm /var/lib/panopta-agent/panopta-agent.db

  • Delete the panopta_agent.cfg file.
    rm /etc/panopta-agent/panopta_agent.cfg

  • Begin creating server image.

If you restart your server before creating an image, you will need to perform these steps over again unless cron is disabled upon reboot.

For Windows Servers

  • Create the PanoptaAgent.manifest file in the root of the C: drive.

  • Download the latest dotNet4.0 or dotNet4.5 server agent.

  • Run the following command from a PowerShell Window as an administrative user:

Start-Process -FilePath msiexec -Wait -ArgumentList "/q INSTALLATION=`"Install`" /i panopta-agent-prod-NET4.5.latest.msi MANIFESTFILE=`"PanoptaAgent.manifest`" IMAGEINSTALL=`"true`"

The MANIFESTFILE parameter is the path to the manifest file created above. If this parameter is not present, the installer will look for the manifest in C:\ by default.

  • Begin creating the server image.

Prepare an Agent for server imaging/cloning

For Linux Servers

  • Stop cron from running.
    RHEL: service crond stop
    Ubuntu: systemctl stop cron

  • Confirm that cron is inactive.
    RHEL: service crond status
    Ubuntu: systemctl status cron

You should see output similar to the below snippet to indicate that cron is inactive

# service crond status
Redirecting to /bin/systemctl status crond.service
● crond.service - Command Scheduler

Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)

Active: inactive (dead) since Mon 2021-06-28 16:37:17 EDT; 5s ago

  • Delete the panopta-agent.db file.
    rm /var/lib/panopta-agent/panopta-agent.db

  • Delete the panopta_agent.cfg file.
    rm /etc/panopta-agent/panopta_agent.cfg

  • Begin creating server image.

If you restart your server before creating an image, you will need to perform these steps over again unless cron is disabled upon reboot.

For Windows Servers

  • Create the PanoptaAgent.manifest file in the root of the C: drive.

  • Download the latest dotNet4.0 or dotNet4.5 server agent.

  • Run the following command from a PowerShell Window as an administrative user:

Start-Process -FilePath msiexec -Wait -ArgumentList "/q INSTALLATION=`"Install`" /i panopta-agent-prod-NET4.5.latest.msi MANIFESTFILE=`"PanoptaAgent.manifest`" IMAGEINSTALL=`"true`"

The MANIFESTFILE parameter is the path to the manifest file created above. If this parameter is not present, the installer will look for the manifest in C:\ by default.

  • Begin creating the server image.