Agent

The full Management Console installation kit has an agent installation option. Some agents installed using this option in the 64 bit installation kit may have the following problems:

• In Administration >> Component Management >> Display Status, the agent status is displayed as red
• In Manage Monitoring, a test connection to the agent is successful, but you are unable to register collections

The following steps will fix this problem:

1. Log on to the agent computer with a Local Administrator account
2. Stop the Longitude services

Longitude uses the Exchange Management Shell (EMS) to monitor Exchange 2007. EMS itself requires the .NET Framework and PowerShell. Install the software in the following order:

1. .NET Framework
2. Windows Powershell
3. Exchange 2007 Management Tools - after unpacking the management installation files, install with the command:
   setup.com /mode:install /role:T

The .NET Framework, Powershell and EMS can all be downloaded from Microsoft Downloads.

***Note::
Once an agent is associated with a managed device, all collections for that device will be made through that agent regardless of the agent selected when you register application monitoring. Each managed device can only have one agent associated with it.
****

If you need to use a specific Longitude agent to monitor a managed device, do the following when you register an application:

1. If using the 2.0 UI, Click on the Advanced option
2. Go to Monitoring >> Manage Applications and select the MONITOR APPLICATION button

We have seen some cases in Longitude 6.2 in which the CPU on a Longitude agent will spike when collecting data for Internet Macros. The Firefox instances used to collect data for the Internet Macro do not close correctly, leaving orphaned Firefox processes on the agent.

Until a patch is available, this problem can be addressed by restarting the Longitude Statistics Server component. This should kill the orphaned Firefox processes, but you may need to check the Longitude server directly and close dialog boxes for Firefox errors.

A component on the Longitude Management Console called the Statistics Server will collect data from monitored devices without installing any additional software (i.e. agents) on the monitored devices. However, the Statistics Server has some limitations:

• For WMI collections, it is restricted to the credentials of the account the Statistics Server runs under
• Firewalls may restrict which devices and protocols can be accessed by the Statistics Server
• Slow links between sites may cause data collection to time out

In Version 6.2 you can remove an agent by going to Monitoring, Manage Applications, and then scrolling down to the bottom of the page and clicking Manage Remote Agents.

Versions Prior to 6.2

The only way to remove an Agent in versions prior to 6.2 and all devices that are being monitored by it so it no longer displays as being inactive is to remove it through the database. To do this you will need to either use SQL Studio or login using webSQL

To Use WebSQL
1. Open up a browser and navigate to http://localhost:7230/webdbm

Longitude can be configured to collect data through an agent installation - this is useful if you need to collect data from devices at a remote site, on the other side of a firewall, or where you would need to use an alternate set of Windows credentials. However, especially for agents at remote sites, there can be a delay in collecting monitored data if the Management Console loses contact with the Longitude agent.

The Syslog application will set up a listener on UDP port 514 on the agent computer. On Linux computers, this port may be considered privileged, and the Longitude agent will not have access to it using a non-privileged account. To work around this, you can either configure the Syslog listener to use a different port (with port number > 1024), and configure your devices sending syslog messages to send messages on that port, or you can run the agent using a privileged account.

To set up the Longitude agent to use a privileged account, modify the Linux Longitude agent as follows:

Unfortunately you can not monitor Windows based applications with a Linux agent as the agent is unable to make WMI Calls to Windows Machines.

If you do a clean install of an agent on a machine that has the same ip address or DNS Name it will automatically repopulate your SS_Collections.xml file and the agent will resume normal operation.