The archive folder is hard-coded to the base Uptime Infrastructure Monitor installation directory on the server hosting the up.time Data Collector or uptime_ core service.

To change this location, you have the option of creating a logical link to another folder on the same server or a different server.

For example, using the ln command for Linux or Solaris environments: 

# cd /usr/local/uptime/archives

...

# mv archives archives_old

...

# ln -s </new/archive/location>

...

Windows Agent

...

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

...

 archives