in the system tray of the managed machine. The agent menu can be customized.Administrators can belong to none, one, or more administrator roles. The following policies are assigned by administrator role:
In addition, scripts and agent installation packages can be shared by administrator role.
Administrators use the VSA application to maintain the KServer and oversee the monitoring of managed machines by the KServer and its agents. KServer management configuration and other specialized functions can only be performed by master administrators. Standard administrators are typically restricted to the administration and monitoring of managed machines. A background of two alternating shades of beige designates master administrators. A background of two alternating shades of grey designates standard administrators. Access to functions, machine groups and other policies are assigned by administrator role.
The set of options that display when the user right-clicks the agent icon in the system tray of the managed machine. The agent menu can be customized.
The KServer manages machines using agents installed on remote machines. Once installed:
displays in the icon tray of the remote machine. Note: See Agent > Deploy Agents for details about installing agents.
Alarms notify administrators when a machine's performance fails to meet a pre-defined criteria. This differs from an audit, which simply collects selected data for reference purposes without regard to any criteria. Alarms can be reviewed using the View Console page or the Reports > Logs > Alarm Log report. An alert is a response to an alarm.
Alarms are enabled using the following pages:
Alerts have two meanings, generic and specific:
Generic Alerts
An alert is a response to an alarm condition. Typically alerts indicate an alarm is enabled, and provide three types of response to the alarm:
Defining an alert sets the ATSE alarm / response code for that machine ID or SNMP device.
Alerts are defined using:
Specific Alerts
The Alerts page provides a simple set of typical parameters for setting up alarms and their corresponding alerts quickly on a managed machine. For example, low disk space is frequently a problem on managed machines. Selecting the Low Disk type of alarm displays a single additional field that lets you define the % free space threshold. Once defined, you can apply this alarm immediately to any machine ID displayed on the Alerts page and specify the type of alert response to the alarm.
Note: Monitor Sets represent a more complex method for triggering alarms. Typical alarm conditions should be defined using the Alerts page.
The ATSE alarm / response code assigned to a machine ID or SNMP device indicates how the system responds to the triggering of an alarm. Each type of alarm can be assigned a different ATSE response code.
Agents can be scheduled to automatically audit the hardware and software configurations of their managed machines on a recurring basis. Agents report the information back to the server so you can access it even when managed machines are powered down. Audits enable you to examine configurations before they develop into serious problems. The system maintains three types of audits for each machine ID:
The KServer detects changes in a machines's configuration by comparing the latest audit to the baseline audit. The latest audit record is stored for as many days as you specify.
Most of the agent and managed machine data displayed by function pages and Reports are based on the latest audit. The Machine Changes report compares a machine ID's latest audit to a baseline audit. Two alert types specifically address changes between a baseline audit and the latest audit: Application Changes and Hardware Changes.
Online chat is a text-based, instant messaging system. It is included with the KServer primarily to provide immediate technical support. Administrator's can chat with users of managed machines and/or chat with other administrators currently logged on the same Kserver. Administrators can enable or disable the user's ability to initiate chat sessions with administrators. Since Kaseya chats are relayed through the KServer, all chats are protected by the Kaseya 256 bit rolling encryption protocol.
These icons indicate the agent check-in status of each managed machine:
Agent has checked in
Agent is currently offline
Agent has never checked in
Online but waiting for first audit to complete
The agent is online but remote control is disabled
A full check-in occurs when an agent completes the processing of any and all outstanding tasks assigned to it by the KServer. These tasks can include processing a script, posting cached log data, or refreshing the agent configuration file. A quick check-in occurs when an account checks in at the configured check-in interval, indicating to the KServer that the machine ID is still online. This doesn't require the completion of all outstanding tasks. Some functions require a full check-in before an agent can begin processing a new task. For example, System -> Naming Policy.
Machine collections let you group any number of arbitrary machines together. Any machine can be made a member of one or more collections.
Machine collections are defined using Agent > Create/Delete. Machine IDs are assigned to machine collections using Agent > Membership.
The console is a summary display of the alarm status of all machines being monitored. The console's data is filtered by the Machine ID / Group ID filter. Navigation: Home > View Console or Monitor > View Console.
A credential is the login name and password used to authenticate a user or process's access to a machine or network or some other resource. See Agent > Set Credentials.
The dashboard is a summary display of the status of the entire system. The dashboard's data is filtered by the Machine ID / Group ID filter. Navigation: Home > View Dashboard.
The Distribute File function sends files stored on your VSA server to managed machines. It is ideal for mass distribution of configuration files, such as virus foot prints, or maintaining the latest version of executables on all machines. The VSA checks the integrity of the file every full check-in. If the file is ever deleted, corrupted, or an updated version is available on the VSA, the VSA sends down a new copy prior to any script execution. Use it in conjunction with recurring scripts to run batch commands on managed machines.
File Transfer Protocol (FTP) is a commonly used protocol for exchanging files over any network that supports the TCP/IP protocol. The FTP server is the program on the target machine that listens on the network for connection requests from other computers. The FTP client is the program on the administrator's machine that initiates a connection to the server. The FTP client machine requires user access rights to the FTP server machine. It is included with the KServer primarily to provide immediate technical support. Once connected, the client can upload files to the server, download files from the server, rename or delete files on the server and so on. Any software company or individual programmer is able to create FTP server or client software because the protocol is an open standard. Virtually every computer platform supports the FTP protocol. Since Kaseya FTP sessions are relayed through the KServer, all FTP sessions are protected by the Kaseya 256 bit rolling encryption protocol.
The text equivalent of an IP address. For example, the IP address 89.234.7.197 should resolve to the host name of www.kaseya.com. Host names are only available from computers. Hubs, switches, routers, or other network appliances do not return a host name.
Kaseya frequently posts hotfixes to correct small problems in the latest release. If the Enable automatic check box is checked in System > Configure, your VSA periodically checks for new only hotfixes at http://vsaupdate.kaseya.net. If any new hotfixes are available, the KServer automatically downloads and applies the hotfixes without any user interaction.
The hotfix mechanism addresses minor issues only, typically either cosmetic typos, or ASP page errors. The KServer, agents, or database schema are never updated via hotfixes. Any changes affecting system operation go into full product updates that you approve before installing. Hotfixes just correct minor issues without having to wait for the release cycle.
An ISO image (.iso) is a disk image of an ISO 9660 file system. ISO 9660 is an international standard originally devised for storing data on CD-ROM. In addition to the data files that are contained in the ISO image, the ISO image also contains all the filesystem metadata, including boot code, structures, and attributes. All of this information is contained in a single file. CD writers typically provide the option of writing an ISO file as an image when writing to a CD.
LAN Watch uses an existing agent on a managed machine to periodically scan the local area network for any and all new devices connected to that LAN since the last time LAN Watch ran. These new devices can be workstations and servers without agents or SNMP devices. Optionally, the VSA can send an alert when a LAN Watch discovers any new device. LAN Watch effectively uses the agent as a proxy to scan a LAN behind a firewall that might not be accessible from a remote server.
Logs collect event information on agent machines. The different types of logs that can be generated are:
.ini file changes, and other information is captured. The date and time of each activity is also noted.The unique media access control (MAC) identifier assigned to network adapter cards (NICs).
Each agent installed on a managed machine is assigned a unique machine ID/group ID combination. All machine IDs are associated with a group ID and optionally a subgroup ID. Typically a group ID represents a single customer account. Subgroup IDs typically represent a location or network within a group ID. For example, the full identifier for an agent installed on a managed machine could be defined as jsmith.acme.chicago. In this case chicago is a subgroup ID defined within the group ID called acme. Only a master administrator, or administrators authorized by the master administrator, can create group IDs. Any administrator can create subgroup IDs. Group IDs and subgroup IDs are created using the System > Create/Delete function page.
The Machine ID / Group ID filter is available on all tabs and functions. It allows you to limit the machines displayed on all function pages. The View Definitions window lets you further refine a Machine ID / Group ID filter based on attributes contained on each machine—for example, the operating system type. Once filter parameters are specified, click the green arrow icon 
to apply filter settings to all function pages. By default, the Machine ID / Group ID filter displays all machine IDs in <All Groups> managed by the currently logged in administrator.
Note: Even if an administrator selects <All Groups>, only groups the administrator is granted access to using System > Group Access are displayed.
Agent install packages can be based on machine ID templates. A machine ID template is a machine ID record without an agent. Since an agent never checks into a machine IT template account, it is not counted against your total license count. When an agent install package is created, the package's settings are copied from the machine ID template. Typically machine ID templates are created and configured for certain types of machine. Machine type examples include desktops, Autocad, Quickbooks, small business servers, Exchange servers, SQL Servers, etc. A corresponding install package is created based on each machine ID template you define.
When discussing agents it is helpful to distinguish between the machine ID / group ID and the agent. The machine ID / group ID is the KServer's user account name for a managed machine in its database. The agent is the client software installed on the managed machine. A one-to-one relationship exists between the client agent on a managed machine and its machine ID / group ID account name on the KServer. Tasks assigned to a machine ID by a KServer administrator direct the agent's actions on the managed machine.
A monitored machine with an installed agent and active machine ID/group ID account on the KServer. Each managed machine uses up one agent license.
The Management Information Base (MIB) of a SNMP network device is a listing of selected MIB objects that contain information about that device. Each MIB object is identified using a sequence of integers that specifies its location in a global object hierarchy maintained by the international standards bodies ISO and ITU. Each MIB object supports a set of commands and queries that can be used to communicate with that device.
A monitor set is a collection of counter objects, counters, counter instances, services and processes used to monitor the performances of machines. Typically, a threshold is assigned to each object/counter/instance, service, or process in a monitor set. Alarms can be set to trigger if any of the thresholds in the monitor set are exceeded. A monitor set should be used as a logical collection of things to monitor. A logical grouping, for example, could be to monitor all counters and services integral to running an Exchange Server. Monitor sets are maintained using Monitor > Monitor Sets. and are assigned to machine IDs using Monitor > Assign Monitoring. You can assign monitoring to any machine that has an operating system of Windows 2000 or newer. The results of monitoring can be displayed using Monitor > Monitor Log or View Console.
Note: Monitor sets represent a more complex method for triggering alarms. Typical alarms should be defined using the Alerts page.
The Packager is a wizard tool used to create a package when a pre-defined install solution cannot be used. Packager evaluates the state of a source machine before and after an installation and/or resource change. The Packager compiles the differences into a single executable file—the package—that can be distributed via scripts to any managed machine. Distribute a package any way you choose. You can email it, or store it on a server where a custom script can perform a silent installation on any managed machine.
PSEXEC.EXE is a light-weight telnet-replacement that lets you execute processes on other systems without having to manually install client software. It used by Agent > Install Agents to install agents on remote systems after a LAN Watch.
Silent installs, also called silent deploys, do not prompt the user for input. Silent installs may not require user input or else provide a typical configuration that serves the purposes of most users, or else provide command line parameters that enable users to configure the installation at execution. If an install does not support a silent install but still needs to be distributed automatically, administrators can use Packager to create a custom installation package. See Creating Silent Installs.
An SNMP community is a grouping of devices and management stations running SNMP. SNMP information is broadcast to all members of the same communiity on a network. SNMP default communities are:
Certain network devices such as printers, routers, firewalls, servers and UPS devices can't support the installation of an agent. But an installed agent can report the status of these devices back to the Kserver using simple network management protocol (SNMP). SNMP monitoring begins by assigning a machine ID to an SNMP Community. Then that same machine ID is used to perform a LAN Watch of all SNMP devices on the same network.
A SNMP set is a collection of MIB objects used to monitor the performance of SNMP enabled network devices. Typically, a threshold is assigned to each MIB object in a SNMP set. Alarms can be set to trigger if any of the thresholds in the SNMP set are exceeded. A SNMP set should be defined as a logical collection of things to monitor. SNMP sets are maintained using Monitor > SNMP Sets. SNMP sets can be manually assigned to monitor a SNMP device using Monitor > Assign SNMP or Monitor > SNMP Type. SNMP Sets also provides a method of automatically assigning SNMP monitoring to an SNMP device. All SNMP Sets assigned to an SNMP device are displayed in Assign SNMP. SNMP alarms can be displayed using Monitor > SNMP Log or View Console.
System checks are performed on managed machines that don't have agents installed on them. Such machines are called external systems. A machine with an agent is assigned the task of performing the system check on the external system. A system check typically determines whether an external system is available or not. Types of system checks include: web server, DNS server, port connection, ping, and custom.
The system tray is located, by default, in the lower right-hand corner of the Windows desktop, in the Taskbar. It contains the system clock, and other system icons.
Microsoft updates are organized as follows:
Update Classification |
Classification Type |
Included in |
Security Updates |
High Priority / Important Includes critical, important, moderate, low, and non-rated security updates. |
Yes |
Critical Updates |
High Priority / Important |
Yes |
Update Rollups |
High Priority / Important |
Yes |
Service Packs |
Optional – Software / Recommended |
Yes |
Updates |
Optional – Software / Recommended |
No |
Feature Packs |
Optional – Software / Recommended |
No |
Tools |
Optional – Software / Recommended |
No |
In those cases where a machine does not have Internet connectivity at the time of a machine patch scan, Kaseya uses Microsoft's WSUSSCN2.CAB data file. Microsoft publishes this CAB file as needed. It contains a sub-set of the Microsoft Update Catalog. As seen in the table above, scan data for only the high priority updates and service packs are included in the CAB file. The KServer automatically downloads the CAB file on a daily basis to make it available for those machines needing this type of scan. See Windows Automatic Update.
The User Access Welcome Page is the page the user sees when the agent icon on the system tray of a managed machine is double-clicked. The User Access Welcome Page contains user options such as changing the user's contact information, creating or tracking trouble tickets, chatting with administrators or remote controlling their own machine from another machine. Some of these options are enabled by an administrator using Agent > User Access. The function list the user sees on the User Access Welcome Page can be customized using System > Customize.
Virtual Network Computing (VNC), also called remote control or remote desktop, is a graphical desktop sharing system which uses the Remote Framebuffer (RFB) protocol to remotely control another computer. It transmits the keyboard and mouse events from one computer to another, relaying the graphical screen updates back in the other direction, over a network. It is included with the KServer primarily to provide immediate technical support. VNC is platform-independent. A VNC viewer on any operating system can usually connect to a VNC server on any other operating system. The VNC server is the program on the target machine that shares its screen. The VNC client (or viewer) is the program on the administrator's machine that watches and interacts with the target machine. The VNC client machine requires user access rights to the VNC server machine. Since Kaseya VNC sessions are relayed through the KServer, all VNC sessions are protected by the Kaseya 256 bit rolling encryption protocol.
Windows Automatic Updates is a Microsoft tool that automatically delivers updates to a computer. Windows Automatic Updates is supported in the following operating systems: Windows 2003, Windows XP, and Windows 2000 SP3 or later. While Windows Millennium Edition (Me) has an Automatic Updates capability, it cannot be managed as the above operating systems can. Patch Mgmt > Windows Auto Update can enable or disable this feature on managed machines. See Update Classification.