...

The Windows agent runs as the uptmagnt.exe process and is controlled via the Uptime Infrastructure Monitor agent Windows service. The agent is running if these services are running and you can verify that it is accepting connections using the simulation steps listed above. Enter the "sysinfo" command (including the quotes) to verify connectivity. 
AnchorHow to configure automatic recovery actiHow to configure automatic recovery actiUptime Infrastructure Monitor uses action profiles to perform recovery steps when a service monitor returns a critical status. Action Profiles are templates that define an action to perform when a monitor encounters a problem and can be applied to one or more service monitors.
An Action Profile allows you to specify:
Image Removed When to start and stop performing the action (escalations).
Image Removed The name of the log file to which Uptime Infrastructure Monitor writes error information.
Image Removed The name and location of a recovery script that can reboot a server or restart an application, process or service. Image Removed The name of a Windows host and service, as well as whether to start, stop or restart the host or service.
Image Removed An SNMP trap to be sent to a specific traphost and trap community.
Use the following steps to create an action profile:

1. Click on the Services tab.
2. Click the Add Action Profile link on the left tree menu.
3. Set up the action profile to perform the desired steps (e.g. log to file, run a script, start / stop Windows service, send an SNMP trap, etc.) and click Save.

Next, attach the action profile to an existing service monitor with the following steps:

1. Click on the Services tab.
2. Locate the service monitor in the list and click its name (or click the View icon).
3. Scroll to the bottom of the page and click the Edit Action Profiles button.
4. Add the appropriate Action Profile to the right list and click the Save button.

...

1. Take LDAP Query, replace %s in the query with the name under LDAP Username
2. Connect to LDAP using the distinguished name pointing to that user. If authentication fails (or user is not found), it will return "Invalid Credentials"
3. On success, it takes LDAP Group Distinguished Name, and reads the object.
4. If it can not find the object at all, it will output "No Group exists under that Distinguished Name."
5. If it finds the object but the Group object is not under a domain name, it will not be able to read it and returns "Could not get members listing for Group Distinguished Name."
6. If object is read, and the distinguished name in the object exists, the users are inserted into the local Uptime Infrastructure Monitor database
7. If object is read, but it contains entries that do not link to a user, that particular user is skipped and not inserted into Uptime Infrastructure Monitor.

...

Active Directory Explorer

http://technet.microsoft.com/en-ca/sysinternals/bb963907.aspx^{Image Removed}

Wireshark

http://www.wireshark.org/download.html^{Image Removed}