Multi-Language Support

Kaseya now supports multiple languages. Currently Spanish is available with more to follow soon.

Ticketing – Adding notes via email

You can now send an email reply to any administrator ticket notification. The reply is automatically added to the ticket just as if you added the ticket through the web interface. If user notifications are enabled, then the new note is also emailed to the user. If you add ~hide to the text of the message, the new note is added as a hidden note.

Ticketing – Auto fill

Inbound tickets will auto lookup and fill in contact info based on user profiles. New inbound emails will be automatically assigned to a machine ID if that machine id has a contact email address and the auto assign ticket flag is set.

Ticketing -  View Summary

The last search filter is always used (on a per administrator basis) on the View Summary page. Now if you select a different function and come back to View Ticket, the last search filter is automatically filled in and applied. Click the Clear button to remove the filter at any time.

Ticketing – Split Ticket

Sometimes users reply to existing tickets and begin a completely different line of discussion. For better organization, you can now split these tickets in two. A new icon appears by each note in a ticket. Click the icon to split the ticket at that point. All field settings are copied from the original ticket and the original ticket is automatically closed.

Ticketing – Mobile Access

Notification emails sent to administrators contain a link to access the ticket. The system now senses when this link is clicked from your mobile device and automatically renders both the login screen and View Ticket page to fit your mobile device’s browser. Use this capability to view, add notes, or change field status on any ticket.

Ticketing – Due Date Policy

In prior versions the due date policy was applied when ticket data is first received (typically from an inbound email). This did not help much when entering a ticket through the web interface. With this release we have changed this behavior to always apply due date policy to new tickets after any field change. Once ticket ID is assigned, then only a warning is displayed if the due date does not match the policy.

Ticketing Report

• Added ability to show/hide hidden notes for tickets.
• Bar chart showing the tickets for each admin broken down by status
• Option to show a pie chart break down of each list field item.

Patch Mgmt – Expanded Support

Added full patch support for Exchange, Sharepoint, Vista, and Office 2007

Patch Mgmt – Patch Approval

Redesigned Patch Approval page to keep configuration data and patch approval data in different frames for ease of use.  Added the capability to configure a default Approval Status for each collection/policy to control the initial approval status of newly discovered patches.

Patch Mgmt – File Source

Added validation code to alert the admin when a LAN file source Machine ID no longer exists or if any of the required data is missing.

Patch Mgmt – Initial Update

Added support for the execution of a script before Initial Update and/or after Initial Update.  These scripts are configured on a per machine basis in the new Patch Mgmt – Pre/Post Script function.

Patch Mgmt – Alert

Added two new patch alerts:

• Automatic addition of newly discovered patches to existing Patch Approval policies.
• Invalid Agent credentials

Patch Mgmt – Patch Update

Removed processing of KServer.

Patch Mgmt – Command Line

In an attempt to minimize the need for installation media when patching Office 2003, we have added a new command line switch: "/MSOCACHE". The " /MSOCACHE" switch only applies to Office 2003. When the patch database is updated, this switch is automatically added to all Office 2003 patches where an administrator has never modified a particular patch's command line switches. It is not automatically added to Office 2003 service packs. When this switch is used, the system determines if the MSOCache exists on the target machine. If the MSOCache does exist and this switch is used, the system will automatically use the run silently switch ("/Q") thereby relying on the MSOCache rather than requiring the actual installation media. If the MSOCache does not exist on the target machine, the existing switch will be used. If a patch installation fails that uses the "/MSOCACHE" switch, it typically means that the MSOCache could not be used by the patch. In this case, you must clear out all command line switches for this patch. This will result in the "/INSTALL-AS-USER" switch to be automatically added. Re-running the patch installation should now succeed. Unfortunately, this will require user intervention and also probably require the Office 2003 installation media.

Patch Mgmt – Office Source

Added support for configuring a machine with Office installed to use a network share or a directory on the local hard drive as the Office installation source rather than the default CD-ROM.  This feature modifies the machine’s registry so Office will look to the alternate location for the Office installation source. The provided source is validated to be sure that the source is compatible with the installed edition/version of Office.

Patch Mgmt

The explicit listing of "KServer" in various Patch Mgmt screens has been removed.  To process patches on the KServer, an Agent must be installed on the KServer.  All Patch Mgmt processing (except Initial Update – not supported on KServer) can be done with the Agent on the KServer just like any managed machine.

Copy Settings

If the source machine (the machine you are copying from) does not have a credential, then the credential is not changed on the target machines. Use this to create template accounts that do not effect the credential of target machines.

Scripts

All scripts run after a machine reboots were named REBOOT-xxxx. We received several support requests asking why Kaseya reboot their server when in fact the script was run as a result of a reboot and did not cause the reboot. To end this misconception, we have changed this naming convention to START-xxxx

Backup Password

Image passwords are logged and saved forever. Master administrators may retrieve a password for any machine ID, even machines that no longer have backup installed or even have an agent, as long as the machine ID at the time the password was created is known.

Offsite Server

List all offsite servers in the Offsite Server and Local server functions. All listed because the offsite box will probably not be in the same group ID.

Audit – SW License

The product installation key (CD key) is recovered during audit when it is available.

Audit – Add/Remove Programs

Audit now returns the add/remove program list.

Remote Control Status

• Currently logged in user for each machine ID, if any, is displayed on the Control Machine function.
• If any admin is currently remote controlling a box, the admin name is listed also.

Remote Control Notification Policy

D_efine policy on a per admin role basis. Also allow policy to be defined on a per machine basis. If a machine policy exists, it over-rides the admin role policy.

• Silent
• Notify if logged in (now with customizable message)
• Ask if logged in (else deny) (now with customizable message)

Added option to pop up alert when remote session completes (with customizable message).

Option to (or required if policy set) add a note to the admin notes log prior to allowing remote control session to start.

Remote Control Log

You can now report on remote control activity. The system now maintains a separate remote control log for each machine ID. You can view (Agent Tab – Agent Logs) or report (Reports Tab – Logs) on the Remote Control Log just like any other log.

Disable Remote Control on Install

Adding the /x option to the agent install package (Agent Tab – Deploy Agents) automatically disables remote control from the client side after a successful agent installation.

Remote Control User Mode

End users may now use Terminal Server to remote control their own machine.

Remote Control Verbose Mode

The Enable verbose relay flag is now remembered on a per admin basis. If you enable the verbose relay in a remote control of FTP session, that flag is automatically set the next time you remote control of FTP. The verbose relay flag is typically left off and is not needed for normal operation.

System Check

System Check verifies a remote machine, such as a web server, is functioning by connecting to it on a recurring basis. You can prevent temporary outages from sending alarms by specifying the length of time a check must fail before issuing an alarm.

Deploy Agents

Master administrators now have a checkbox to let them view all install packages created. Check this box to clean out and/or remove old agent packages.

Agent Status

Time Zone is now available for display in the Agent Status table.

Monitor – Agent Status Alert

The system now detects when a batch of agents go offline at the same time (usually resulting from an internet outage). The system will now send only a single email listing all machines that went offline at the same time. Prior to this release, an email was sent for each machine ID.

Monitor - SNMP

Shortened time between SNMP monitor requests. In older versions, the interval between SNMP monitor request could have become prohibitively long if the SNMP Probe (Agent) was monitoring hundreds of SNMP Devices. The polling and connections are now multithreaded; creating narrow data sample intervals.

Monitor – SNMP

When Kaseya first discovers an SNMP device, a deeper initial request of SNMP data is now being performed. The initial SNMP Discovery will now include a 'deep dive' return of SNMP data. The SNMP branches currently being queried are:  iso.org.dod.internet.mgmt.mib-2.interfaces and .iso.org.dod.internet.private.

Monitor – SNMP

Added link to Assign SNMP Monitor page to view list of auto discovered SNMP data.

Monitor – SNMP

Added new function allowing the user to customize SNMP Device names and Types.

Monitor – SNMP

Added filters to the SNMP Log function to allow the user to filter log entries that contain certain text or values.

Monitor – SNMP

If the user removes the SNMP Community name, all associated SNMP Devices will be removed and logs cleared.

Monitor – SNMP

The SNMP Probe will attempt to find SNMP Table descriptions where possible and automatically insert the results into the monitor item description. (Example: If asking for the ifEntry.ifInOctets for interface #2, Kaseya will identify, if available, that interface #2 is the ‘external firewall connection’ and add it to the description)

Monitor - General

Pop-up warning on log-in will inform the user that Alarms are currently disabled.

Monitor - General

If the update of a monitor set is not ‘contextual’ (does not significantly change the monitor item), the logs will not be cleared.

Monitor - General

All monitor sets will continue collecting data even if the administrator changes the Kaseya temp directory.

Monitor - General

When a SNMP Community Name reference is removed, all related SNMP Agents will be removed also.

Monitor - General

Added more descriptive information within monitor set expanded information to the following web pages; Log Summary, Alarm Summary, Alarm Status, Monitor Set Status, Monitor Summary, Live Connect.

Monitor – System Check

Added Duration to all system checks for alarms.

Monitor - Alarms

History of note entries can now be kept on all Alarms.

Monitor - Alarms

If a monitor set generates an alarm email, an additional email notification can be sent if the Alarm value transitions back 'out of' its alarm state.

Monitor - Reports

Allows the user the ability to select a monitor counter and calculate the 95th percentile (or 5th) for each counter. Also added was a comparison feature; allowing two machines to be reported (trended) upon side-by-side.

Monitor - Reports

Added trending reports with 'number of days' filter and comparison features.

Monitor - Reports

Added trending reports for all SNMP Objects (again with comparison feature).

Monitor - Reports

Added Monitor Configuration Report listing the monitor set configuration for the machines selected.

Monitor - Copy Settings

'Copy Settings' will now include all monitor sets information when copying machines with the same operating system.  Monitor sets will not be copied if the operating systems isn’t supported by monitoring and/or copying from Windows 2000 to Windows XP/2003.

Monitor – Assign Monitor/SNMP Sets

New edit icon, when clicked will allow the editing of existing monitor set deployment parameters on the specific machine/device.

Monitor Sets and Logs

All monitor sets will stay collecting data even if the administrator moves or renames the Kaseya temp directory.

Monitor – Log Summary

Added icon indicator and action to refresh specific monitor object on the machine or device.

Monitor – Log Summary

Added Filters to log and chart data.

Monitor – Log Charts

Added more description info and X/Y titles to charts.

Monitor Console – Machines Online

Added Customized zones Red/Yellow/Green

Monitor Console – Popup Windows

Fixed positioning of console windows alignment.

Monitor Console – Group Alarm

Removed View drop down list.  Group alarm status page will now use the main view filter.

Agent Changes

• Now supports Windows Vista on i386
• Now supports Windows XP on x64
• Now supports Windows 2003 on x64
• Enhanced processing for various system monitoring changes
• processing a duration prior to reporting an alarm for the System Check
• support for foreign language notation in performance counter data that utilizes commas instead of decimal points
• fixed access rights required to query the status of some services that grant only read-only privileges
• Agent now detects hibernate & suspend. Upon a resume event, the Agent generates entries into the agent log file so that the uptime history report will show the Agent as being powered down over the period. Prior to this, the uptime history report showed the Agent as being continuously online.

Installer

There is now only a single installer rather than the separate versions for with and without the database. The installer asks if you are using your own SQL server or need the database at install time. If you need the database, the installer downloads it and installs it at that time.

Known Issues

Deploy Agents

Agents can not be deployed over the network (using Install Agents function) to Vista machines unless UAC is disabled.

Backup

Backup is not supported on Vista yet

Agent Installer

The agent is not compatible with Vista-64