So many times we hear some one say that they are proactive and not reactive in their approach to support. It is an approach to systems management and support that is sound and makes sense, but getting there is tricky right? 100% proactive support is unrealistic, as are flying unicorns, but there are certainly tools and tricks to maximizing proactive work and to minimizing the load that reactive support activities place on your IT organization.
Led by MSP pricing expert Erick Simpson of MSP University, this webinar presented key MSP pricing tips to achieve optimal margins as part of an MSP service delivery offering.
As a sneak peak of the session, Erick’s presentation on determining optimal IT managed service margins covered:
With the last build, we have now released a Lua script that can monitor your Microsoft server cluster. The released version will check for operational status in nodes and shared resources.
Prerequisites:
Kaseya Network Monitor v4.1 Build 7394 or higher
Microsoft Windows Server 2003/2008 Cluster
Setting up this monitor involves setting up an object that represents the cluster. Testing of individual nodes is also possible but in case the node you are testing against would go down, the script would just fail, not being able to read any values.
With the release of Kaseya Network Monitor version 4.1, we now have two built-in ways of monitoring your VMware infrastructure. We support versions 4.1 and 5.0 of ESX/ESXi from build 7345.
With the Lua script that comes with the install package, you can easily setup monitoring of the most common health counters’ operational status. The counters that are checked are the following:
Kaseya has always been at the front of the pack in terms of tools that successful MSPs use to run their businesses. Its not a brag, well it is a brag, but its also a fact. Kaseya MSPs continue to dominate the MSP Mentor 100 list globally.
Let’s look at a break down of how many MSPs running Kaseya were represented on the various lists:
So you got testing up and running, but what happens when a monitor fails a test ?
KNM tests a monitor according to its test interval setting defined in the monitor property page. This is normally between 30-60 seconds. Alarm generation and alarm test interval is two properties that come in to play when a monitor fail a test.
Alarm generation tells the monitor how many consecutive times it has to fail a test to go from ok state to alarm state. In between those two states there is an intermediate state called “failed” , the failed state is a mere visual indication that something may be about to happen.
Continue Reading…
We have a great new MIB packaging to allow for robust network monitoring and systems monitoring with Kaseya Network Monitor. A new MIB file package for KNMv4 has been added to the download center. This package contains 29 MIB files from different vendors such as Cisco, Dell, HP, Checkpoint, Avaya, Sonicwall, Riverbed, VMWare and Juniper.
Toplists in Kaseya Network Monitor is summarized statistics that are updated in real time and contains a wealth of information that can answer many questions, for example
Lets take a look at a real world example
Continue Reading…
Kaseya Network Monitor includes support for the Lua scripting language. Lua is a powerful light-weight programming language designed for extending applications. With Lua customers can create custom made monitors to test systems and equipment not supported by any built-in monitor.
This post is the first post (!) in a series that will offer tips and tricks for the newest addition to the Kaseya family, Kaseya Network Monitor. Feel free to sound of in the comments if you have any questions or requests for articles in this series.
One of the most important aspects of a monitoring system is its capabilities to monitor all kinds of file and folder related processes. KNM has several ways to perform file and folder monitoring, one of them being the directory property monitor.
