Agent Deployment

Agent Deployment

< Guide Menu

Quasar uses “Agents” on each of the servers or workstations that need to be scanned. There are agents for different operating systems and you can use various ways to install them. This pages provides an overview of the most common methods of installing agents.

The Quasar agent can be installed on the same device that the Quasar server is running on, or it can be installed on the servers / workstations / etc. that need to be scanned.

Default Deployment

By default, the agent is usually installed on the same box as the server, and can be run “out of the box”. A single agent can run multiple jobs concurrently.

Mass Deployment

For mass-scanning of desktop machine or server hard drives, it can be ‘baked into’ the desktop build, or mass deployed using SCCM, GPO, or similar technologies.

Quasar has no external dependencies apart from the standard Microsoft runtime library. See ‘Installers’ below for more information on this. SCCM is the most common installation method.

You only need to ensure that the server IP / hostname is configured. The Agent installer includes command line parameters which will assist with SCCM deployments.

Remote Installation (Windows)

The recommended type of installation is a remote installation via SCCM or other suitable deployment technology.

The Agent installer features commandline parameters to assist with this process.

A typical scripted install will follow the steps below:

Step 1

SetupQuasarV4xxAgent.exe /S /Server=111.222.333.444 /D=C:\pathtoinstall
CommandConfiguration
/SSilent install – do not display installer UI or prompt dialogs.
/ServerServer IP address. If this is specified, the installer will overwrite the 127.0.0.1 (the default) in local.cfg with the IP address given on the command line as a final step after files are installed.
/DDirectory / folder to install the agent files into.

Step 2

Once the installer has completed, SCCM or similar can be scripted to run the following command:

quasarscan.exe --startup auto install

Optionally, other changes to local.cfg (log levels, etc) should be made at this point.

Any required changes to the Quasar Agent Windows Service configuration (e.g., service user accounts if applicable) should be made at this point also.

Finally, the SCCM may be scripted to actually start the service.

Manual Installation Instructions

Windows Installation

1. Install Quasar Agent

Obtain the most recent version of the software from the Quasar Specialist you are working with. Install the SetupQuasarV###.exe file where ### represents the version number. Your Quasar specialist will will provide you with the most recent version of the file. Follow the on-screen prompts to complete the installation of the Quasar Agent package.

The default installation path is c:\quasar\quasaragent

2. Configure the Quasar Agent

You will need to configure the Quasar Agent so that it is able to connect to the Quasar Server. Navigate to the path where you installed the Quasar Agent and open the file local.cfg in a text editor.

Ensure that the server address is set to either the DNS name or the IP address of your Quasar Server, otherwise connectivity will fail.

{
    "agent" : {
        "server" : "127.0.0.1"
    },
...
}

3. Install the Quasar Agent Service

Open a command prompt as an administrator. Go to the path where you installed the Quasar Agent, then complete the installation of the Quasar Agent Service:

cd c:\quasaragent
quasarscan.exe install

4. Configure the Service

Open Services (services.msc) as an Administrator and go to the Quasar Scanner Service. Right click on the service and select properties.

Verify that “Start Up” is configured to “Automatic”.

If the Service is not started, click the “Start” button before clicking “OK”

Quasar Agent Properties

5. Check that the Agent is Visible in the UI

On the Quasar Server UI, refresh the page to confirm that the Quasar Agent shows up in the list of Agents. If it does not show up, there may be connectivity problems. Ensure that you have configured the Quasar Server information correctly in local.cfg and that the relevant network ports are open.

6. Check Connectivity (If the Agent Does Not Show Up)

If the agent does not show up in the list of agents, run a comms test.

  • Run the following command: quasarscan.exe commtest
  • The agent will attempt to connect to the server and send a ping message. If a ping message is received, the agent output will look like the following:
Agent Foreground Comms Test
  • If connectivity fails, the foregrounded agent will wait forever. Halt it with Ctrl+C If connectivity fails, ensure TCP ports 55555, 55557 and 55559 are open through to the quasar server’s host machine. (Quasar V3 and V4 – current)
  • On some Windows versions, you may need to close and reopen the command prompt terminal window.

Installers (Windows)

The Quasar agent has no additional dependencies except for the standard Microsoft VC runtime library, which is already present as part of modern Windows installs.
There are two editions of Agent installer:

  1. The standard edition, which includes the Microsoft VC runtime files. Best used when you have older Windows machines, or when you want to be sure the agent will run with no problems. This edition is fully supported.
  2. The ‘no-VC’ edition, which does not include the VC runtime files. Best used when you have modern Windows machines, where the VC runtimes are already installed. This edition may be supported depending on your agreement.
    Example agent installer downloads:
Quasar Agent Downloads

Linux (Red Hat)

1. Untar the Quasar Agent

Untar the Quasar Agent tgz to /opt/quasar.

mkdir /opt/quasar && cd /opt/quasar && tar xzvf quasar-agent-redhat-32bit-sysvinit.tgz

2. Edit the Agent Configuration

Go to /opt/quasar.

Edit the local configuration file (local.cfg) to set the IP address / hostname of your Quasar Server host. Quasar can use either the DNS name or the IP address. If you do not edit local.cfg to specify the Quasar server, connectivity will fail and the Quasar Agent will not show in the list of agents available to the Quasar Server.

Test to ensure that the Quasar Agent is able to connect tot the Quasar Server:

./quasarscan-linux commtest

If successful, it will return: Comm test: Success!
If unsuccessful, you will need to interrupt it with ctrl+c. Go back to the local.cfg file to ensure that you have entered the Quasar Server name / IP address correctly. If this is correct, verify that the required ports are allowed.

3. Make the Agent Executable

Copy the quasarscan init script to /etc/init.d/quasarscan and make it executable.

cp quasarscan /etc/init.d && chmod +x /etc/init.d/quasarscan

4. Enable the Quasar Agent Service

Enable the Quasar Agent Service:

chkconfig --add quasarscan

5. Configure the Agent Service to Run Automatically

Configure the Quasar Agent service to run automatically:

chkconfig –level 2345 quasarscan on

6. Confirm the Quasar Agent Has Installed

Check and confirm that the Quasar Agent has been installed correctly

chkconfig --list | grep quasarscan

7. Start the Quasar Agent

Start the Quasar Agent as a daemon in the background:

/etc/init.d/quasarscan start

8. Check the Agent Has Started

Check that the Quasar Agent has started successfully:

/etc/init.d/quasarscan status

By default, the agent logs to syslog. The agent will log the start up status and the default / configured folder locations (log, data, and tempspace) to syslog upon starting up. You should check that the logs are being generated correctly by running the command:

tail /var/log/messages

Linux (Ubuntu)

1. Untar the Quasar Agent

Untar the Quasar Agent tgz to /opt/quasar

mkdir /opt/quasar && cd /opt/quasar && tar xzvf quasar-agent-ubuntu-64bit-sysvinit.tgz

2. Edit the Agent Configuration

Go to /opt/quasar

Edit the local configuration file (local.cfg) to set the IP address / hostname of your Quasar Server host. Quasar can use either the DNS name or the IP address. If you do not edit local.cfg to specify the Quasar server, connectivity will fail and the Quasar Agent will not show in the list of agents available to the Quasar Server.

Test to ensure that the Quasar Agent is able to connect tot the Quasar Server:

./quasarscan-linux commtest

If successful, it will return: Comm test: Success!
If unsuccessful, you will need to interrupt it with ctrl+c. Go back to the local.cfg file to ensure that you have entered the Quasar Server name / IP address correctly. If this is correct, verify that the required ports are allowed.

3. Make the Agent Executable

Copy the quasarscan init script to /etc/init.d/quasarscan and make it executable.

cp quasarscan /etc/init.d && chmod +x /etc/init.d/quasarscan

4. Enable the Quasar Agent Service

Enable the Quasar Agent Service:

update-rc.d quasarscan defaults

5. Confirm the Quasar Agent Has Installed

Check and confirm that the Quasar Agent has been installed correctly

service --status-all 2>&1 | grep quasarscan

7. Start the Quasar Agent

Start the Quasar Agent as a daemon in the background:

service quasarscan start

8. Check the Agent Has Started

Check that the Quasar Agent has started successfully:

/etc/init.d/quasarscan status

By default, the agent logs to syslog. The agent will log the start up status and the default / configured folder locations (log, data, and tempspace) to syslog upon starting up. You should check that the logs are being generated correctly by running the command:

tail /var/log/messages
Previous Agent Configuration Reference
Next Testing Agent Connectivity
Table of Contents