Hosted Kaseya Managed Services Software - Release Notes
Help File for SecureMyCompany Hosted Kaseya Managed Services software
| New features in Kaseya 2008 (v5.0.0.0)– 10 March 2008 Monitoring, Active Directory, State Management, and more…
| |
Agent Icon | The agent icon will always remain visible in the system tray for systems configured to show the icon. Prior to this release, Windows would hide the icon if it had not been accessed in a while. |
Status Icon | Added a new status icon to represent that an agent is online and that someone is logged into that machine. If someone is logged in, then the tool tip for the icon lists the login name. |
Machine ID / Group ID filter - Machine Count | The machine ID / group ID filter area now lists the number of machines matching the current machine/group/view filter. Use this information as a quick reference to identify the number of machines potentially effected by any action. |
View Definitions - Collections | Collections are now defined using the View Definition window in the machine ID / group ID filter. A new check box labeled “Only show selected machine IDs” lets you specify an arbitrary list of machine IDs seen when using this view. Collections, as with all View Definitions, can be private, shared or public. |
View Definitions - Missing Patches | The View Definition window includes a new “Use Patch Policy” check box showing machines missing patches greater than or equal to a specified number to optionally apply the patch policies. If this box is checked, only missing approved patches will be counted. |
View Definitions - Patch Scan Options | The View Definition window includes the following new options for patch scan scripts:
|
All alert email functions have database access | All alert email functions now include data pulled from the database. The same format provided in the Get Variable script function may be used in any alert formatted as follows: <db-view/column>. For example, to include the computer name of the machine generating the alert use <db-vMachine/ComputerName> |
SW License | The Audit > SW Licenses function highlights when duplicate licenses are found on the same group. The duplicate license count is now a link that lets you drill down and get a list of machines that share the same license code. |
Machine Summary | Added the following to the Machine Info tab:
Added new log type Log Monitoring |
Machine Summary - New Ticket link | The Machine Summary page now includes a New Ticket link at the top of the page. Clicking the link opens a new ticket assigned to this machine id. An optional interface allows you to configure this link to access external systems as well. See the Machine Summary online user assistance topic for details. |
External Link to Machine Summary | The following URL displays the Machine Summary web page for a specific machine ID: http//servername?machName=MachineID.groupID |
Packager | The application Packager function used for creating custom installations now supports output packages larger than 2 GB. |
Distribution | The Distribution function, under the Scripts tab, histograms the recurring schedules for scripts. This function quickly highlights potential server loading by showing peaks where multiple machines are scheduled to run the same script at the same time. This release adds a drill down capability to the histogram such that you can click any peak on the histogram and get a list of machines that make up that peak. |
Scripts -CheckVariable - Evaluated Expression | A new script IF EvaluateExpression command evaluates expressions consisting of script variables from a parent script and six mathematical operators +, -, *, /, (, and ) to perform the comparison to determine whether to execute the THEN or ELSE statements. For example, you can evaluate the expression IF (#variable1# + #variable2#) * 100 > #variable3# where the variables contain numeric values from a parent script that obtained them using GetVariable commands. |
Scripts - OS Type | The OS type selection for script steps now includes the options for “Mac OS X” and “All Windows Operating Systems”. |
Scripts - GetFile | A new option sends an alert for the GetFile script command when the file is identical to the one that was retrieved the last time. |
Scripts - GetVariable - Expressions | Added the ability to specify an expression that consists of script variables and six mathematical operators +, -, *, /, (, and ) that will be evaluated and assigned to a new script variable. For example, ((#variable1# + #variable2#) + 17.4) / (#variable3# * 4). The script variables must contain numeric values. |
Scripts- GetVariable - WMI Values | Added the ability to specify a WMI namespace, class, and property and assign the retrieved value from a managed machine to a script variable. The format of the specified WMI property is NameSpace:Class.Property<. For example, root\cimv2:Win32_OperatingSystem.FreePhysicalMemory |
Scripts - Set Registry Value | Added ability to set registry values with the data type REG_MULTI_SZ. Separate each string with the two character sequence of “\0”. Use the three character escape sequence of “\\0” to include “\0” as part of a value string. This capability requires the Kaseya 2008 agent. |
Dashboards and Dashlets | Added a new Dashboard List function to manage configurable monitoring windows called “Dashboards”. Each administrator can create their own dashboards and add one or more custom “Dashlets” in each dashboard. Each dashlet has the following customizable attributes; position, size, machine filter, header and refresh rate. Dashlets include:
|
Alert - | The Alert > Agent Status > Format Alert Email window now has two new formats. One for a single machine going offline. The second when multiple machines in the same group go offline. Note that a separate alert is generated for each machine group. |
Pre-Packaged Monitor Sets and Event Sets | Kaseya 2008 features a wide variety of performance and service monitor sets and event sets. These sets monitor server and workstation performance objects including SQL, Exchange and other key performance objects such as DNS, DHCP and disk drives. Event sets monitor the Windows event logs for a variety of application, security and system event entries. Events set alerts are defined using Monitor > Alert > Edit Event Sets. Sample monitor sets and events sets are loaded with the installation of Kaseya 2008 or by using the System > Configure page. Sample monitor sets and sample event sets can be identified by the naming convention. Each name begins with ZC-. Monitor Set Naming Example: ZC-SV3 – DHCP Server – DHCP Services Event Set Naming Example: ZC-CM1-E1 Antivirus Events |
Monitoring - General |
|
Log Monitoring | Added new function to monitor the parsing of log files.
|
Windows Event Logs | Enhancements to Windows Event Logs:
|
Monitor Sets - Counters | In the Counter Thresholds tab of Monitor Sets enter an instance of *ALL for a monitor set object, as opposed to selecting *Total which combines the results. For example, if multiple drives are determined to exist on a machine, based on the Audit function, the monitor set with an instance of *ALL will dynamically select a counter for each drive. |
Monitor Sets - Services | In the Services Check tab of Monitor Sets, select the *ALL selection to monitor all services set to automatic on a monitored machine, instead of having to address each service individually. |
Monitor Sets - SNMP | In the SNMP Sets wizard in SNMP Sets select an instance of All to address each SNMP instance in an SNMP object separately. These instances are identified by the last SNMP walk perform during a LAN Watch. |
SNMP Sets – Percentage Comparison | SNMP Sets now provides a percentage comparison of one SNMP Object to another, for example, if ifInErrors is greater than x% of total UcastPackets. |
SNMP Quick Sets | An SNMP walk during a LAN Watch identifies all SNMP objects that apply to an SNMP device. Using Assign SNMP, you can click the link of a discovered SNMP device and create an SNMP "quick set" to monitor that device. |
Monitor Sets and SNMP Sets - | Monitor sets and SNMP sets can to set to automatically adjust their alarm thresholds based on real word data for a specfied time period. Once an auto-learn session has been completed, the alarm thresholds can be fine-tuned manually. |
Monitor Sets and SNMP Sets -Individualized Sets | An “individualized” monitor set or “individualized” SNMP set can be created for a specific machine or SNMP device, based on a “standard” monitor set, a “standard” SNMP set or a “standard” SNMP quick set. From that point forward changes made to the individualized set apply only to the machine or device it is monitoring. |
System Check - Custom Name | Added custom name to system check. The name is used in alarm and email format templates. |
Email Reader | Ticketing > Email Reader can now be customized to ignore emails containing specific text strings. Use this feature to prevent ticket creation when emails are received from things like email bounces. Typical bounced emails contain the string “Undeliverable: ". |
External Link to View Ticket | The following URL displays the Ticketing > View Ticket web page for a specific ticket: |
Product Identification | Added a Product column to various patch screens to help identify the product category associated with the specific patch. Also added this attribute to the Patch Details screen. For those cases where a specific patch is used across multiple operating system families (i.e., Windows XP, Windows Server 2003, |
Patch Status - | Added a “Reboot Now” button next to the “Reboot Pending” notification on the Patch Status page. Clicking the button schedules an immediate reboot on the machine. A confirmation dialog box is presented to prevent inadvertent reboots. |
Automatic Updates | Added capability to schedule automatic updates on a monthly basis. Automatic Updates can be scheduled daily, weekly on a specified day of the week, or monthly on a specified day of the month (1-31). NOTE: When processing monthly automatic updates, if the current month has fewer days than the scheduled day of the month, the automatic updates is processed on the last day of the month. For example, if the current month is April and the scheduled day of the month is 31, the patches are scheduled on April 30th. |
Patch Alerts | Added a new machine level patch alert. This alert, when configured, is generated when the Windows Automatic Update Policy on the machine is changed to a setting (disabled, enabled, user control) that is different from that specified in the Windows Auto Update function under the Patch Mgmt tab. The Windows Auto Update function displays the current Windows Automatic Update Policy setting on the machine. This setting is obtained during each patch scan, and the alert is generated, if necessary, during the processing of patch scan results. |
Patch Update | A “Patch Group By” dropdown list has been added to allow the user to change how the displayed patches are grouped. Before this release current grouping was based on the update classification and could not be changed. Now, the user can group by either update classification or product. The screen layout was modified to include both product and update classification in the presented data. Patches are still sorted by KB article within each grouping so that patches having the same KB article number are next to each other. |
Patch Policy | Changes to approval/denial of patches include:
|
Approval by Policy - Group By | Modified the screen to be able to select the view of the status table based on update classifications or based on products. Both views are presenting totals from the same data source, so the total patch count for each approval status are the same, just distributed differently depending on the view selected. When a drill down is selected to the patch details page, the patches are grouped by the classification (sorted within classification by product) or by product (sorted within product by classification) based on the view selection. |
Approval by Policy - Save As | Added “Save As” capability to copy the current patch approval policy as a new policy with identical settings. All patch approval/denial statuses are copied as are the default approval statuses for the policy. |
Approval by Policy - Default Approval Status | Default approval status can now be set for each update classification and each product within a patch policy rather than just for the policy. This allows setting patch policies to automatically approve selected update classifications such as security updates while automatically denying other update classifications such as service packs and automatically setting the rest of the update classifications to pending approval. It also allows setting patch policies to automatically deny patches for selected products such as Office 2000 while automatically approving patches for products such as Office 2007 while automatically setting patches for the rest of the products to pending approval. NOTE: If there is a conflict between the two default values, the more restrictive default value is used. For example, if one default is denied, the patch is set to denied. If one default is pending approval, the patch is set to pending approval. Both defaults must be approved for the patch to be set to approved. |
Approval by Patch | Added a new function under Patch Mgmt > called “Approval by Patch”. The data displayed on this page is the same data available in “Approval by Policy”. It is just displayed from the patch perspective rather than from the policy perspective. Approving or denying patches from this page provides an “approve or deny once” capability. Includes the ability to filter the list of patches. NOTE: This function is only available for master administrators because it affects ALL patch approval policies. |
KB Override | Added a new function under Patch Mgmt called “KB Override”. Using this page, you can set a default patch approval status override (Approve or Deny) for a specific Microsoft knowledge base (KB) article. This override status is used rather than the patch policies' default approval status when adding a new patch to all patch approval policies. It also resets the approval status for the specified KB article in ALL patch policies. To add the KB override, a patch must already exist in the system with the specified KB article number. NOTE: This function is only available for master administrators because it affects ALL patch approval policies. |
Chat | A new option in Remote Cntl > Chat, “Automatically close chat window when either party ends chat” lets you control how the window behaves at the end of a chat session. Uncheck this box to leave the chat session open after the other side closes the window. This gives people a chance to read the last message or copy data into another file. |
ActiveX | ActiveX installs all remote control views for the admin and the remote control server for the user when the admin uses the Video Streaming function. This can cause problems if the user’s browser blocks ActiveX controls from running. With this release, if the user’s browser detects the ActiveX control could not run, then the user is presented with a link to manually download and run the remote control package manually. |
K-VNC | K-VNC is now supported on Windows 2000, XP, and 2003 in addition to |
Backup Status | Added a new Backup Status dashboard, which provides:
The time period over which to collect results is selectable. |
Backup Sets | Enhancements to backup set management include:
|
Backup Alerts | Alarms are now optional for alerts. Additionally, two new alerts have been added:
|
Backup Logs | Enhanced error detection and recovery.
|
Reports - Backup | Backup report now offers option to include or exclude machines without data. |
Reports - Patch Management |
|
Reports - Logs |
|
Reports - Monitor Action Log | New log describing the actions that occur when a monitor alarm threshold is met. Contains information on alarm created, ticket created, scripts scheduled, and emails sent. |
Reports - Event Log Frequency | New report displaying top number (N) of windows event logs per machine ID. |
Reports - Executive Summary | Added Log Monitoring to system activity. Added Log Monitoring Custom allowing to count, total, average, min and max of log parser custom number fields. |
Report – Monitor Action Log | Added monitor action log to monitor reports section. |
DNS Computer Name | The fully qualified DNS computer name is now available for any machine that is a member of a domain. Members of workgroups return the computer name only in this field. Display the DNS Computer Name in either the Agent > Agent Status function or in the Aggregate Table report. |
CPU Count | The CPU Count number, returned by audit, is now available on both the Agent > Agent Status function or in the Aggregate Table report. |
Log History | Added capability for the following to be aged and/or archived:
The archiving of logs places log table data into text files. These text files are stored at a specified location and categorized by log table and machine ID. |
Agent Install Packages - Standard Administrators | Standard administrators are now restricted to creating agent install packages using existing group IDs. |
Macintosh Agents | A Macintosh agent is now supported. The agent type is specified in the Create Package wizard in the Agent > Deploy Agents function. If an administrator password is omitted from the Macintosh installation package, the installer prompts for administrator credentials during the installation as long as the silent option is not selected. |
Rename Group | The Agent > Rename Group function under the agent tab, lets you rename any machine group ID or subgroup. |
Rename Agent | Agents now check in using a GUID instead of the machine ID. Old agents can still check in using the machine ID and are fully supported except for renaming capability. Renaming now just changes the display name of the agent. The agent GUID stays the same. So in order to rename agents in the new system, the agent must be upgraded to Kaseya 2008 first. |
Hide Common Computer Names | Typical laptop computers may have multiple MAC addresses and LAN Watch may detect both MAC addresses for the same laptop, for example, wireless LAN vs. direct connect LAN. So an additional checkbox has been added to hide machines that have a common computer name in the same group ID. Only the MAC address used by the agent to connect to the Kserver is reported. |
vPro | This release supports Intel’s vPro-enabled processors.
|
Active Directory | LAN Watch has been extended to integrate with Active Directory. Running LAN Watch on a primary domain controller automatically discovers all computers and users listed in AD. Two new functions, View AD Computers and View AD Users, display Active Directory results. You may also deploy agents to Active Directory computers found by LAN Watch as well as update user information pulled from Active Directory. |
AD Logon | Any user discovered by LAN Watch may be tagged as a new Administrator logon or User logon to the VSA using View AD Users. These logons are all authenticated by the domain controller the logon is attached to. So now you can use a single logon on both your network and the VSA, all controlled by Active Directory. NOTE: You can remove both the Domain field and the Remember Me checkbox from the logon page by checking the appropriate boxes on the Logon Policy function under the System tab. |
Copy Settings - Exclude Patch File Source | A new Agent > Copy Setting option, Patch File Source, lets you exclude or replace the patch file source. The patch file source is frequently a customer-specific setting and should not be overridden when copying settings. |
Import/Export | The System > Migrate function has been replaced with a new Agent > Import/Export function. Exported accounts capture all machine settings, including script schedules, into an xml file. Use Import/Export to move settings attached to any agent. Note that Import/Export only moves settings and not data attached to a machine. Log data is not moved with Import/Export. |
Suspend Agent | Suspend all agent operations (scripts, monitoring, patching, etc...) without changing the agent settings. Use Suspend to disable accounts without deleting the agent or modifying any of the agent’s settings. |
Admin Role Management | Administrator management has been enhanced with this release to allow non-master administrators to more securely manage other administrators. The administrator management functions under the System tab, restrict non-master administrators to only seeing other administrators that are members of the same roles. Note that master administrators rights may never be removed by standard administrators. Effected functions are:
|
Function Access | A new Enable All/Disable All button gives you a quick way to turn access on or off for all functions for an admin role. Click Disable All when configuring an admin role that does not have access to many functions. |
Function Access - Summary Page | Access to the tabs on the Machine Summary page can now be granted or blocked on a per admin role basis using Function Access. |
Function Access - Lock Settings to Match | Function Access settings for an admin role may now be locked to some other admin role. Any changes to the Function Access list for one admin role are automatically applied to all roles locked to it. If you create unique admin roles in order to isolate access to machine group, but want to give each role the same list of functions, then you can use this new feature to manage all function access from a single role. |
License Manager | License limits now flow down to subgroups. Subgroups now inherit the license limit applied to their parent groups if the subgroup does not have a limit specifically applied. |
Login Policy | The login policy is now enforced for both user and administrator logins. Prior releases only applied login policy to administrator accounts. |
Customize | The customize function now lets you further customize the logon screen. You can add additional links on the left edge of the screen. This may be a useful spot to place a link to the Video Streaming page (/getHelp.asp) for example. |
Database Views - vBackupLog view | Added a new column to the vBackupLog database view. imageSize shows the size in bytes of the backup file. If the log entry does not relate to a backup then this column returns a zero. |
API Web Service | Added a web service that provides an API (application programming interface) to the VSA. Enable the web service using the System > Configure function. Once enabled, the web service may be queried from the URL http://<your-vsa-server>/vsaWs/KaseyaWS.asmx using a valid administrator credential. A test client example, access control rules, and further details may be found in the directory <kaseya-install-dir>\vsaWs. |
Kaseya Endpoint Security v1.2 (v1.2.0.0) – 10 March 2008 | |
View Status | The current available version is directly off the Grisoft RSS feed and will be updated within 15 minutes of Grisoft posting an updated |
View Status | The “Threats” column nows present a link to the manage threats page filtered on that individual machine. The top machine filter is not affected. |
Updates | Individual agents no longer have update schedules. The KServer now tracks updates and schedules update scripts on individual agents only as needed. This results in timelier updates with less overall activity. |
Updates | Because of the new automatic update script assignment, periodic (recurring) updates are no longer allowed. This page is for “manual push” only. |
Updates | KES updates now honor the “File Source” settings under Patch. So KES can now deploy updates to agents that are not internet-connected (as long as they can reach the file share and the file share can reach the Internet). |
Updates | The KES Agent now goes to the VSA server for updates when the File Source is KServer or Internet |
View Threats | Select All has new behavior. Now it selects all of the threats in the current filter instead of just the current page. |
View Threats | Now has a “Purge” button in the action bar for “clean up”. This will remove the threat from the active threat list (and put it in the history list) without triggering any script on the agent. |
View Threats | There are now two tabs. The “Current Threats” tab is conceptually identical to the old page, showing threats that are current or in process of being taken care of. “Historical Threats” are threats that have been taken care of either through a clean, delete, restore, or purge. |
View Threats | Additional filters: “machine”, which allows narrowing by machine without affecting the top-level filter (useful for stepping back and forth from the status page). “Time” filters on the discovery date by min/max/in between. “Categories” filters on the threat type—whether antivirus or antispy. “Action” and “Status” filters by what action (if any) has been taken and what the progress of that action is (pending/failed). |
View Logs | Filters added to make log more useful. “Time” filters by when the event occurred (you have a lower and an upper date, and if either is empty that end is “open”, so both empty means “all”). “Categories” lets you pick events to view by category. “Message” lets you text search the message for some particular string. |
Alarms | KES Alarms are now assigned via sets. These sets are created on the new ‘Define Alarm Sets’ page, and assigned on the ‘Apply Alarm Sets’ page. |
Alarms | There are new KES alarms. |
Define Profile | The profile UI has been updated to more closely reflect AVG. A few new options have been added as well.
|
Define Profile | A new tab called “Exchange” allows for configuration of the new real-time monitor for Exchange (see MS Exchange Install/Remove below) |
PUPs | There is a new button on the view threats page ‘Add to PUP Exclusion List’. Any threats selected when this is pressed will be added to an exclusion list for the profile assigned to the machine they were found on. If AVG decides a file by this name is a PUP on any machine with this profile, this file will be ignored (excluded). |
Install/Remove | There is now an option to choose which profile to assign to a machine at install time. |
MS Exchange Install/Remove | Added support for real-time monitoring of Exchange Servers. This page allows you to install Exchange Server support on any KES endpoint that is also an Exchange Server. Different licensing applies. |
Kaseya User State Management v1.2 (v1.2.0.0) – 13 March 2008 | |
Policy Management | Functions to support definition and deployment of machine policy for power, mapped drives and printers. Support for backup, deployment and migration of user accounts, system and application settings. |
Power | Create power policies for different groups and/or machine roles. Schedule and deploy power settings to all users on targeted machines. |
Mapped Drives | Create drive mappings for different groups or roles. Deploy mapped drive settings to all users on targeted machines. |
Printer Mappings | Create network printer definitions, schedule and deploy printer configuration to groups of machines. |
Desktop Standards | Create a desktop standards package to deploy specific system and application settings to all users on groups of machines. |
User Settings Backup and Restore | Back up user account information and system and application settings from groups of machines. Restore allows selective restore of account information and settings to the same or a different machine. |
Migrate | Multi-machine migration of user account and system and application settings. Enables ordered migration of user account information and preservation of user settings migrations to new machines during hardware or Windows OS upgrades. |
New features in v4.8.0.0 - June 5th, 2007 | |
|---|---|
Exec Sum Report | The OS score weighting can now be customized. You can individually weight the OS score given to Vista, 2003, XP and 2000. Enter the % weights (0 to 100) in the four columns normally used for %score. Place Vista in the 100% column, 2003 in the 75% column, and so on. All legacy OSs are given a zero. If you have a large number of legacy OSs deployed, considered turning off the OS score. |
Patch Mgmt | Added WARNINGS and/or NOTES to screens affected by Initial Update to better inform users of its impact on patch management functions. |
Patch Mgmt - Patch Status | Enhanced the Patch Status page with the following:
|
Patch Mgmt - Rollback | Added the date, if available, that the patch was installed to the screen similar to the Patch History screen. |
Patch Mgmt - Cancel Updates | Add a notation to the "Pending Update Install Status" column to indicate that the patches currently pending installation are being processed by Initial Update. Canceling pending updates will now also cancel Initial Update. |
Patch Mgmt - File Source | Enhanced the File Source page with the following:
|
Patch Mgmt - Windows Automatic Update | Added checkbox to "Force auto-reboot if user is logged on" to the "Configure - Force Windows Automatic Update configuration to the following settings" setting. We also changed the underlying default to NOT force the reboot. This is a Windows Update registry setting that only affects Windows Automatic Update. Windows Automatic Update cannot use Kaseya's Reboot Action settings. |
Patch Mgmt - Office Source | Added the ability to filter by Office products/product codes to make it easier to set multiple machines to a common Office source share. Since the same Office product can have one of several product codes, the filter ensures that only products with the same product code are selected together. |
Status Monitor | The status monitor pop up window no longer counts or displays template accounts (agents that have never checked in). |
Script Editor | Fixed problem with file list that would not list shared files unless that admin also had rights to upload and delete shared files. All admins may see shared files. |
Disk Info List | Show used space in addition to free and total space for all disk drive space tables and reports. |
Application Changes Alert | You can now add exclude directories to the Application Changes alert. Any application added or removed to these directories will not generate an alarm. The exclude path may contain wildcards. |
KServer | KServer modifications include the following:
|
Agent - Pause Command Processing | The processing of the Pause Script command has been shifted from the KServer to the Agent to avoid the possibility of putting all process threads to sleep in the server for a prolonged period which would result in Agents going offline. |
Agent - Workgroup/Domain name | The Agent now reports whether the computer is joined to a workgroup or domain and the corresponding name. This information can be used in creating a view as well as shown on the Agent status page and reports. |
Agent - Response Issue | The Agent detects a connection corruption caused by security software that blocks KServer messages requesting an immediate checkin. The corrupted connection was causing a 3 minute timeout before establishing a new connection to run the pending tasks. When the Agent detects the symptoms of this condition, it removes the timeout so that the tasks can run at the specified checkin period. |
Agent - Event log description | Resolved an issue so that the event log description is properly retrieved when the vendor provides multiple event log message DLLs. Also fixed an issue with retrieving the description when the vendor provides only a 64-bit event log message DLL. |
Agent - Event log collection | Resolved an issue with retrieving event log information on Vista when the application provides access only through the newer event log interface and omits backward compatibility through the legacy interface. |
Agent Contact Administrator Menu Item | Resolved an issue that opened the Administrator login page instead of the User login page when selecting the ‚Contact Administrator agent menu item. |
Log display | You can now sort the Event Logs and Script Log by column in the Agent Logs function under either the Agent Tab or the single machine interface. |
Edit Profile | Added a checkbox to the Edit Profile function called Show notes as tooltip. Checking this for any machine ID will display the notes field for that machine to display on the tooltip for the agent's status icon. Use this feature to quickly access notes for any particular machines. |
Exec Summary Report | The OS score weighting has been changed to (Vista-2003:100%, XP:75%, 2000:50%, NT4:25%) |
Chat | Administrators can not remove their names from the list of available administrators to chat with. The list seen by administrators (in the Chat function under the Remote Cntl tab) and the list seen by users in the user login are controlled separately. |
Set Credentials | Added a test function to verify the credentials work |
System Info | System information now inserts a link to the PC manufacturer's support site when a field in the System Information table may be used to access this data. Currently supported manufacturers are:
|
Views | Added option to list machines that have never checked in. Use this filter to list template accounts. |
Monitor - System Check | Enhanced the capabilities of Custom command within the System Check function. Custom commands will now require an output file assigned by the administrator. Alarms will be created by searching the output file for a specific value(s) by using the operator contains or does not contain. |
Remote Control - K-VNC | Added support for K-VNC to provide remote control on Vista. |
Remote Control - RAdmin | Added support for RAdmin 3.0. RAdmin 3.0 includes full support to remote control Vista. |
Remote Control RDP | Support remote control of a terminal server running on a port other than the default port 3389. |
Remote Control Policy | Machine Policy now support a fourth policy type. Require permission will not allow remote control unless a user gives permission. If no one is currently logged in, then permission is denied. |
Automatic SQL Script Variables | SQL view parameters are now available as automatically declared script variables. Use the format #SqlViewName.ColumnName# in a script variable to access the dbo.SqlView.Column for the machine ID executing the script. These automatic variables allows you to skip the call to GetVariable with the option SQL View Data with the format of SqlViewName/ColumnName. See the context sensitive help for the System tab. Database Views function for a list of the SQL views and columns that are available. |
GetVariable Script Command | Added a new option‚ SQL View Data‚ that will place the result of a database query to retrieve data from an SQL view for a specific machine ID or for the machine ID executing the script. The format of the parameter for this option is SqlViewName/ColumnName/mach.groupID or SqlViewName/ColumnName. The latter format is an explicit form of the automatic SQL script variable. See the context sensitive help for the System tab; Database Views function for a list of the SQL views and columns that are available. |
Audit - Documents | There is a new function under the Audit tab named Documents. Use the Documents function to store files associated with a machine ID. Typically, people store things like scanned copies of purchase receipts, contract information, and configuration notes here. |
Agent on Vista x64 | The Agent now runs on Vista x64. Drivers provided with the Agent are signed. The only known restrictions are:
|
Reset Password | The password is now set to never to expire when it is set using the Reset Password function under the Remote Cntl tab. This feature requires a new Agent, version 4.7.0.19 or above. |
New features in v4.7.0.0 - January 29th, 2007 Vista Support, Improved Monitoring | |
|---|---|
| Patch Management, Expanded Support | Added full patch support for Microsoft Exchange, SharePoint, Vista, and Office 2007 |
| Patch Management‚ File Source | Added validation code to alert the administrator when a LAN file source Machine ID no longer exists or if any of the required data is missing. |
| Patch Management‚ 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 Management‚ Alert | Added two new patch alerts:
|
| Patch Management | In an attempt to minimize the need for installation media when patching Office 2003, the new command line switch, /MSOCACHE‚ has been added. The " /MSOCACHE" switch only applies to Office 2003. When the patch database is updated, this switch is automatically added to all Office 2003 patches. 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. |
| Patch Management‚ 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. |
| 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 Kaseya 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 |
| Audit - Software 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 also listed. |
| Remote Control Notification Policy | Allow policy to be defined on a per machine basis.
|
| 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 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. |
| 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 | Time between SNMP monitor requests has been reduced. 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 is not 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 |
|
Known Issues | |
| Deploy Agents | Agents can not be deployed over the network (using Install Agents function) to |
| Agent Installer | The agent is not compatible with Vista-64 |
Kaseya Managed Service Provider Software v4.7 - January 2007 Pre-Release Announcement | |
|---|---|
| Platform Support | Kaseya is ready for Windows Vista. Version 4.7 allows administrators to extend the power of automated IT services to workstations and servers running Windows Vista. In addition, Kaseya 4.7 now includes a Vista Readiness report that will identify which machines are ready for upgrade and which are not ready and why. In addition, support for the Kaseya agent has been extended to systems running the Windows XP and 2003 64 bit operating systems. |
| Audit | To provide more detail to the information collected from machines during the audit process, the audit will now collect the Add/Remove Programs listing from managed machines. |
| Audit - Add/Remove Program Listing | A new menu option has been added to view the Add/Remove Programs information. The Machine Summary and Software reports have been enhanced to support the reporting of the Add/Remove Program information. |
| Audit - Software Licenses | In version 4.7, the Software License audit will collect, display and report the corresponding product keys. |
| Patch Management | The enhancement and expansion of Patch Management is a continuous process. With version 4.7, the scope of platforms supported has been expanded. Support for Microsoft Office 2007 has been added along with various usability enhancements. |
| Patch Management - Supported Platforms | Full patch scan and patching functionality has been added for the following servers:
|
| Patch Management - Microsoft Office Media Location | To ease the process of patching machines with Microsoft Office, a function to specify the location of the Office media has been added. This function will allow the administrator 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 source is validated to ensure that it is compatible with the installed edition/version of Office. |
| Patch Management - File Source | To help ensure the reliable delivery of patches to a machine, the system will now alert the administrator when a LAN file source Machine ID no longer exists or if any of the required data is missing. |
| Patch Management | To further minimize the need for installation media when patching Office 2003, a new command line switch /MSOCACHE has been added. The switch only applies to Office 2003. When the patch database is updated, this switch is automatically added to all Office 2003 patches. It is not automatically added to Office 2003 service packs. |
| Patch Management - Patch Database Distribution | To conserve bandwidth in an environment, the system allows for the designation of a local file share as the patch file source. To extend the conservation of bandwidth, the patch database, mssecure.xml, will also be distributed from the local file share if it is specified as the patch file location. |
| Remote Control | To increase security, privacy and accountability, new features have been added to the Remote Control function. The administrator can now create access notification polices by machine. In addition, there is a new log to track the remote access. |
| Remote Control - Access Notification Policy | Remote control access notification policies can be created by machine. The access notification policy can be set for the following:
|
| Remote Control - Logs | A new log has been added to the system to track the start and end of a remote control session along with administrator notes if required. The Remote Control Log can be viewed and reported upon in the same manner as other logs within the system. |
| Kaseya Agent | The Kaseya agent is one of the key components of the system. The agent is responsible for the service delivery, data collection and overall management of the servers and workstations where it is installed. With each new version of Kaseya, the capabilities of the agent are refined and expanded. In version 4.7, the agent will now utilize a persistent connection with the Kaseya server. This enhancement provides huge benefits not only in version 4.7 but in the future releases of the Kaseya framework. |
| Kaseya Agent - Connection | Currently the agent uses a polling frequency to perform a quick check-in with the Kaseya server. With version 4.7, the agent will utilize a persistent connection with the Kaseya server. This persistent connection creates a series of benefits.
The reduction in the amount of data flowing as well as the reduced resource usage on the server increases the scalability and performance of the system. A persistent connection between the agent and server also increases the performance of the system. For example, a request to remote control a machine can now be carried out almost immediately. |
| Kaseya Agent - LAN Watch | More flexibility in defining the new device alert has been added in version 4.7. In previous versions, LAN Watch generated an alert when a new device was found on the LAN that had not previously been on the LAN for the last 7 days. This time period is now selectable. |
| Reports | New reports are being added along with updates to existing reports. The details will be identified in the Release Announcement. |
| Real Time Monitoring | To increase performance, ease of use and the overall functionally of Real Time Monitoring, version 4.7 adds new features and enhancements in the following areas:
|
| Real Time Monitoring - Console | Several enhancements have been added to the Console for increased performance and better visibility. These include:
|
| Real Time Monitoring - Alarms | To provide better tracking and analysis of Alarm information, a history of the note entries can now be kept on all Alarms. To provide better visibility and management of the agent and SNMP monitoring, the system can now send an email notification when the alarm value transitions out of' its alarm state. |
| Real Time Monitoring - System Check | System Check verifies if a remote machine, such as a web server, is functioning by connecting to it on a recurring basis. To prevent temporary outages from sending alarms, the length of time a check must fail before issuing an alarm can be specified. |
| Real Time Monitoring - SNMP Monitoring | The SNMP monitoring in version 4.7 has been significantly enhanced. The enhancements provide increased performance and capacity, more depth in the information collected from devices and better presentation of the information collected. The following items have been enhanced:
In version 4.7, when an SNMP device is first discovered, a deeper initial request for SNMP information is being performed. This deeper request will automatically discover objects within the device that can be monitored. This will help ease the process of setting up the SNMP monitoring for a particular device. This information can be viewed from a new link that has been added on the Assign SNMP Monitor page. To further aide the identification of devices, a new function has been added to allow for the entry of a user defined Device Name and Type. By increasing the information collected, displayed and defined for a particular device, the creation of monitor sets becomes easier and, the monitoring is more accurate which creates a more productive environment for the management of the machines and devices. |
| Real Time Monitoring - Logs | Data collected as a result of the Monitor and SNMP Sets is stored in the monitor log for query and reporting. In version 4.7, the monitor logs can be filtered to view entries that contain certain text or values. |
| Real Time Monitoring - Reports | The following reports have been added:
|
New features in v4.6.3.0 - 21 August 2006 Minor Maintenance Release | |
|---|---|
| Maintenance | Fixed minor display related problems |
| Monitor - Edit | Changed 'alarm duration' logic. The system will now look back in the log table to see if there any records that were under the alarm threshold. If there are none, instead of going into 'alarm' (old behavior), it will continue to look to the next oldest log value. If that value is over the alarm threshold, the system will only then go into 'alarm'. |
| Monitor - Reports | Added trending reports with 'number of days' filter and comparison features. |
| Monitor - Copy Settings | 'Copy Settings' will now include monitor sets. |
| Monitor - General | When a SNMP Community reference is removed, all related SNMP Agents will be removed also. |
| Monitor - Edit | When a monitor set is edited, the logs will not be reset unless the counter, service or process specific information is changed. |
| Monitor - Logs | Logs now have icons that indicate that there are log entries for the corresponding monitor item. |
| Monitor - Logs | Added 'character match' filters to log tables. Allowing for searches of the log table entries (i.e. " ... show all service log entries like 'stop'") |
| Monitor - Logs | Added 'day range' filter to counter graphs (similar to SNMP logs). |
New features in v4.6.2.0 - 19 July 2006 Minor Maintenance Release | |
|---|---|
| Maintenance | Fixed minor display related problems |
| Remote Control | Added ability to independently set the screen width and height in terminal server sessions. See the Set Parameters function |
| LAN Watch | IP scanning range is now restricted to 11 bits (2048 addresses) |
| Patch Mgmt - Initial Update | Modified the Initial Update screen to include update status from "scheduled" through the various "processing steps" to "completion". |
| Patch Mgmt - File Source | Modified the File Source screen to improve the clarity of the source for the patch files and the patch file's destination on the target machine. |
| Monitor - Edit | Added 'Group Alarm Column' selection as a step in the Add function for Monitor Sets and SNMP Sets. |
| Monitor - Assign Monitoring | Modified PerfMon commands to start counters after an agent machine has been re-booted. |
| Scripts (support of Monitor) | A script named ExecuteSNMPWalk.has been included in the Sample Scripts/Config Changes area. This script is very valuable if the user is new to the SNMP device. |
| Reports - Patch Management | The Patch Status section of the Patch Management Report has been modified to display the same patch status as displayed on the Patch Mgmt - Machine Update page. Previously, the only statuses presented were "installed" or "missing". Now, more detailed status information is displayed when applicable. |
New features in v4.6.1.0 - 30 May 2006 Advanced Monitoring, Backup, Ticketing, and more... | |
|---|---|
| User Remote Control Options | Users logging in to remote control their machine are now presented with the standard remote control options prior to starting remote control. |
| Event Set alerts | You can now set independent email addresses for different event sets on the same machine ID. This lets you send alerts generated by different application events to different administrators. |
| Event Sets | Added the ability to import and export event sets. |
| Agent Menu | Due to popular demand, we have returned to calling the agent the 'Agent'. All references to Client have been changed back to Agent. |
| Script Directory | Added ability to import and export entire script directories (all scripts and sub-directories in any script directory). |
| Script Commands |
|
| Agent Status | Added a Reset Filter button to quickly remove any advanced filter settings on the Agent Status function. The advanced filter may reduce the number of machine IDs displayed. Click Reset Filter to quickly display all machine IDs. |
| Views | You can now share views with other administrators or administrator roles. Click the Share button on the edit views page to set up share permissions. This release also adds significant filtering capability to views. You can now:
|
| Run Audit schedules System Info | You can now schedule System Info data collection in conjunction with Run Audit (under the Audit tab). System Info may cause high CPU utilization on the client and normally runs once after the first audit. Use the new checkbox option to schedule System Info collection to run again or run recurring for any checked machine. The System Info scheduler has been removed from the System Info data display. |
| Reset Password | Added a new option allowing you to specify whether to create a new account in the administrators group or not. |
| LAN Watch Alert | In previous versions, LAN Watch generated an alert when a new device was found on the LAN that had not previously been on the LAN for the last 7 days. That time period is now fully programmable. If you have a network where devices may be turned off for extended periods, increasing this value beyond the longest time a device remains off prevents that device from generating an alert when it turns back on. |
| Agent Status | Added clickable column headers so you can sort this table by any column displayed. Clicking a header the second time sorts in reverse alphabetical order. |
| Status Monitor | Added a paging control to the status monitor. Previously you were limited to at most 100 machines. Now you can monitor all machines using the standard paging control. |
| Alerts | With the introduction of advanced monitoring, Alert functionality takes advantage of advanced monitoring by incorporating options beyond just simple email alerts. Alerts now support: alarms, email, script execution. The alert summary list on the Home page has been replaced with the alert status list on the monitoring console. Here you can Open/Close alerts. |
| Patch Installation Issue | An issue that prevented patches from being scheduled for installation by either Machine Update or by Automatic Update when the number of uninstalled patches for the specific machine was large (about 70) has been resolved. |
| Patch Mgmt - Windows Automatic Update Configuration | A new Patch Mgmt function, Windows Auto Update, has been added under the Configure section. This function will report the machine's current Windows Auto Update settings for Windows 2000 (SP3 & SP4), Windows XP and Windows Server 2003. Additionally, an administrator may override the user's setting, including disabling it, and prevent the user from making changes. |
| Patch Mgmt - Initial Update | A new Patch Mgmt function, Initial Update, has been added under the Setup section. This function allows an administrator to schedule a machine to be fully updated with all approved service packs and patches. This function is typically used after a new machine is initially scanned for missing service packs and patches and basically performs a 'patch-until-done' process. |
| Patch Mgmt - Exclude Machines | This function has been removed. Use the manual scheduling (Machine Update and Patch Update) to control what machines get which patches. |
| Patch Mgmt - Patch Update | The capability to ignore a machine for a particular patch has been removed. Use manual scheduling (Machine Update and Patch Update) to control what machines get which patches. |
| Patch Mgmt - File Source | Added option to copy the downloaded patch files to the temp directory on local drive having the most free space (default), or to copy them to the temp directory on the same drive where the Agent is installed. |
New features in v4.5.0.1 - 18 October 2005
Updater change.
Updater change
Corrected a problem that failed to update correctly in rare situations. This data dependent problem only occurs in certain combinations of Microsoft SQL 2000 and IIS. This release handles any configuration and will safely update to v4.5.0.1
New features in v4.5.0.0 - 17 October 2005 | |
Backup and Disaster Recovery | New optional add-on module providing complete volume and folder backup facilities. Scheduled offsite replication transfers all image backups to a remote FTP site at scheduled times. |
Office Patch Installation | The Patch Mgmt system now supports Microsoft Office updates for Office 2000, Office XP, and Office 2003 on the Windows 2000, Windows XP, or Wondows 2003 operating systems. |
Because virtually all Office 2000 service packs and patches require the user to provide the Office installation CD(s), the user must be logged in and must respond affirmatively to a dialog in order for the Office 2000 patches to be | |