New features in Kaseya 2008 SP1 (v5.1.0.0) – 7 September 2008
Audit - System Info	Entering data into a manually added field in System Info as http:// or https:// displays the data as a URL link. To manually add a field click the Show More button, then click the New...* button.
Audit - Documents	The Documents function, located on the Audit tab, can now be accessed as a new tab in the Machine Summary interface. The Machine Summary interface displays when you click any agent status icon.
Scripts - Mac OSX Agent	The Mac OSX agent has been improved to handle installation and log off conditions on all platforms up through OSX 10.5.4. Mac OSX agents are now able run the Execute Shell Command and Execute File script commands as either "system" or as "user" using user credentials. In the initial release of the Mac agent, these commands always ran as "system".
New Sample Reboot Scripts	New sample scripts have been added to support several reboot scenarios: · Reboot-Ask-No: If user is logged in, ask if it is OK to reboot; assume no after 5 min. If user is not logged in, go ahead and reboot. This script calls Reboot-Ask-No-2 to ask the user. · Reboot-Ask-Yes: If user is logged in, ask if it is OK to reboot; assume yes after 5 min. If user is not logged in, go ahead and reboot. This script calls Reboot-Ask-Yes-2 to ask the user. · Reboot-Nag: If user is logged in, ask to reboot every 5 minutes until the user allows the reboot. If user is not logged in, go ahead and reboot. This script calls Reboot-Nag-2 to ask the user. · Reboot-No-User: Reboot the machine only if a user is not logged in. · Reboot-Warn: If the user is logged in, warn the user that a reboot will happen in 5 min. If the user is not logged in, go ahead and reboot. (Schedules reboot script 5 minutes from now.)
Dashboards – Alarm Count	All alarm dashboards with an alarm count now pull data from a rollup count table allowing for a more efficient query and update of the dashboard.
Event Log Collection	Prior to this release, when the VSA detected a flood of event log items, the VSA disabled collection of the entire class of events (Error, Warning, Informational, Success Audit, Failure Audit) for a log type on that machine. With this release the VSA introduces two new techniques to better manage certain events from overwhelming the system: Global event log black list - A small number of event types from a handful of machines can overwhelm and cripple your VSA server with volume. Typically the offending event is of little or no value to the administrator. With this release, each agent will continue to process all events, however events listed on the black list will not be sent up to the VSA server. This should effectively cure the flood problem and prevent automatically disabling event log collection on any machine. Alarm detection and processing operates regardless of whether entries are on the collection blacklist. Flood detection - Flood detection is still in place but the action taken has changed. No longer is processing permanently disabled. Instead, after 1000 events (not counting black list events) in one hour are sent to the VSA server, further collection of events of that log type are stopped for the remainder of that hour. A new event is inserted into the log to record that collection was suspended. At the end of the hour, collection automatically resumes. This technique prevents short term heavy loads from swamping your VSA server. Note that these techniques only affect collection. Alarm detection and processing operates regardless of whether collection is suspended.
Monitor Log, SNMP Log	Added start date and time to monitor log display allowing for more flexibility when searching log data.
Ticketing - View Summary	Changing multiple tickets - You can now change any field on multiple tickets at once. On the View Summary function, check the box for all tickets you wish to change a field value for. Then click Set Field… The next screen lets you set a new value for any or all of the fields. Search for phrases enclosed by double quoted strings - The search function looks in all text fields and notes returning all tickets that contain all the elements of the search string. Search string elements are delimited by spaces. Previously this prevented you from searching for phrases. Now you can include phrases as an element by enclosing multiple words in double quotes. WARNING: double quoted strings must be matched exactly. If you enter two spaces together in a double quoted string, then search only returns tickets containing the two spaces. Preview Tickets - Hovering the mouse over a ticket’s preview icon displays the ticket in a quick pop up window. Use the preview function to quickly go through all your tickets without having to open each ticket. Auto submit checkbox - Checking this box automatically re-displays the View Summary page every time one of the field filters changes. If unchecked, change multiple field filters, then click Submit. The page now processes all the field filter changes at the same time and redisplays the page once.
Ticketing – Create/View	The View Ticket function name has been renamed to Create/View to better indicate this is the place to go to create new tickets.
Ticketing - Notify Policy	You can now format/customize additional ticket notifications. On the Notification Policy page click the Format button next to the following options to customize the notification email format: Edit Summary Assignee Change Field Change Due Date Change Send auto response to emails creating new tickets
Ticketing - Access Policy	On a per administrator role basis you can now control access to: Editing submitter information Changing the machine ID associated with a ticket.
Ticketing - Assignee Policy		Assignee Policy is similar to Due Date Policy. It lets you automatically assign a ticket to an administrator based on the values from an combination of the list fields.
Ticketing - Email Reader	The sender’s name is now pulled from the From address in the email header and set as the username in a newly created ticket. Tickets containing no message body and no attachments are now suppressed in place of adding a note that states “No response text provided”
Patch Mgmt - View Definitions	Seven new filter options related to Patch Management have been added: · Machines having no patch scan results (unscanned) · Machines with Reboot Pending for patch installations · Machines with Patch Test Result · Machines with Patch Automatic Update configuration · Machines with Patch Reboot Action configuration · Machines with Patch File Source configuration · Machines missing a specific patch (identified by the patch’s 6 digit KB Article ID)
Patch Mgmt – Scan Machine	Removed the option for master administrators to schedule a refresh of the patch database that only applies to legacy systems no longer supported by Microsoft and to download the latest Office Detection Tool (ODT). An automatic background process now executes daily to ensure the latest ODT is downloaded to the KServer.
Patch Mgmt – Patch Scan Results Processing	· Moved the processing of patch scan results from the general background process to its own separate background process and added process throttling. This improves overall system response and alert processing time when there are hundreds of machines with updated patch scan results. · When processing patch scan results, a new script is generated and executed to bring the KBxxxxxx.log and the WindowsUpdate.log up to the server for any patches that are reported as “failed”. These logs are occasionally useful in troubleshooting patch installation failures. The logs are found in the Get File function under the Scripts tab for the specific machine. The script log for each machine contains entries indicating that these log files have been pulled up to the server as appropriate.
Scripts – Patch Deploy	The patch installation script generated by the Patch Deploy Installer Wizard now schedules a patch rescan for execution right after the next reboot. This ensures the proper reporting of a patch’s status without having to manually run a patch scan on the machine.
Patch Mgmt – Patch Installation Scripts	When patches are executed in a patch installation script, an entry is made in the machine’s Script Log. Modified the log entry to include the patch title in addition to the KB article number/security bulletin number.
Patch Mgmt – Patch Scan Script	Added a new script (“Patch Scan”) that is available in the Script Editor when either Execute Script or Schedule Script is selected. This “Patch Scan” script can be used to schedule a patch scan as part of a custom script. It will execute the appropriate patch scan script for the selected machine. NOTE: Running the Patch Scan script executes only one of three secondary patch scan scripts. Each of the three secondary patch scan scripts is appropriate for the selected machine. When the Patch Scan script is run, you will see an entry in the script log and in the Pending Scripts tab of the Machine Summary interface for one of the following: "WUA Patch Scan 1 (x86)”, “WUA Patch Scan 1 (X64)", or "Legacy Patch Scan".
Patch Mgmt – Windows Auto Update Scripts	The "Disable Windows Automatic Update" and "Reset Windows Automatic Update" system scripts are now available in any Script Search popup and the Script Editor when either Execute Script or Schedule Script is selected. Since it is not possible to configure a template account with a specific Windows Automatic Update configuration, exposing these two scripts as system scripts now allows an administrator to schedule these scripts for any machine, including template accounts, from the Pending Scripts tab of the Machine Summary interface or to add the execution of these scripts in any other script such as a custom machine setup script.
Patch Mgmt – Initial Update