LabTech – SurfLog Plugin stores browser history for IE, Chrome, Firefox and Safari

Squidwork’s garage is launching another neat plugin that fetches the browsing history from 4 major browsers available on Windows systems. SurfLog collects the browser history for Chrome, Internet Explorer, Firefox and Safari browsers and stores that data inside the LabTech database. The plugin in version 1.0 reads the last 30 days of logs and displays them on the computer console, allows you to launch a new scan and refresh your current view. You can also use the Clear All Logs button to remove all current logs for the computer your viewing or export the data into Excel.

Each column is sort able so you are able to see by Browser Type, URL, Site Title, User Profile or the number of visits to a URL. The plugin comes with one script that collects the data and should be scheduled on widows client groups for once a day.

The Surflog script only grabs the last 24 hours of logs to keep from get to much data that it then cannot import correctly in to the LT database using LT scripting. For this reason you should schedule script to run every 24 hours or less. It will not duplicate any entries into the database so you can run it every hour if you like and only new items will be added to the database. The Surflog script also manages the retention policy and will clear out logs based on the set policy. You can set the policy on the Info Tab of the Client console under the sub tab [SurfLog].

Enable SurfLog on a per client basis

Client Console ->Info Tab -> SurfLog Tab -> Enable Surflog Collection

You can enable Surflog Collection on a per client bases by enabling each client that you would like the collection process to run on. You should schedule the script to run on all windows systems for all systems in labtech then use the enable feature to allow scanner to run or not for each client. The script will validate whether or not to run based on this setting.

SurfLog History Retention

Client Console ->Info Tab -> SurfLog Tab -> Retention Policy

You can set the retention policy for each client between 1 and 90 days, as the collection script runs it will look at the policy for the client and will clear out history based on the retention policy set.

A “Client” must be enabled for any scans on systems under that client to run even if directly scheduled on that system!

SurfLog Key Word Highlight

Client Console ->Info Tab -> SurfLog Tab -> Key Words List

If you place a comma “,” separated list of words in this field the view of each log under this client will highlight those rows where the words show up in the URL, Title and Visit From columns.

We added the ability to surf the links from the history and you can now export the browser history to Excel.

New in version 1.1.0 Cloud hosted LT servers are now fully supported. Just edit the collector script to enable or disable cloud support. See [Grab Surf Logs] script notes for more information.

Get SurfLog 1.1..1

Feel free to donate to our cause if you find this software useful, Help keep our software free.

———New in Version 1.0.5———–
Added new Client Tab with Client level view of all browser histories.

———New in Version 1.0.6———–
Added threading to Excel exports.
Fixed display of Keyword box.
Added UK Time Support to Powershell collector scripts.

——-New in Version 1.1.0 —————-

Rewrote Export function, now really fast and works!
New look and feel
All new graphs and pie charts
Fixed several display issues

—-New in Version 1.1.0.25 —————–
Added support for LT10.5
Plugin now loads script and edfs automatically, no script imports needed
Added auto plugin updater so you will not need to update plugin manually again.

We give a shout out to www.nirsoft.net for their BrowserHistoryView application that provides the CSV creator. Thanks for a great tool.

Cubert 😎

LabTech Plugin -> Office 365 UM keeps improving with new features.

Squidworks Office365 UM Evolves

“New Flash we are now at version 1.8.6 and have added many great features since the writing of this blog, come check out all the new stuff when your done reading.”

Today Version 0.1.7.0 is launching, the 7th release of the first plugin in Labtech to manage Office 365 in the cloud.

GM-O365UM

In the beginning

If you are in the Labtech community then you should know about Cubert’s Office365 Plugin but did you know that it has been evolving?

Back in the beginning our plugin looked a little like this:

In the first version publicly available V 0.0.11 you could only see your users and change their passwords but this was a big step. We were now using remote Powershell CMDs in Labtech scripting and bringing the collected data back into Labtech’s database. This was the first steps to building a plugin for Labtech and getting the data from the cloud into Labtech. We now had a method and a functional process to import data from the cloud and the possibilities opened up for all sorts of new things to come.

It wasn’t long before we were trying new commands and adding some features to our new plugin. Shortly there after we had release a new version that provided the ability to manage some basic permissions like Send As and Send on Behalf As. We started working on added the ability to setup a forwarding email address and full level permissions to allow access for users to other users mailboxes. Version 0.1.4 was released which added the final pieces to our Office365 UM or so we thought.

Moving Day

The Office365 tab’s face was full, no space left to really do anything new but the requests kept coming in for new features. Cubert can you do this was the common theme in the forums. We asked ourselves where are we to put all this new requested functionality? We were out of space and something was going to have to change if we were going to move this plugin any further.

In version 0.1.5.0 we introduced some tabs of our own:

We redesigned the face of the plugin giving us the ability to spread out our functions across different tabs. This gave us the space we needed to really start making this thing preform.We added some new features like adding new users to Office365 , deleting users and also restoring deleted users, converting user mailboxes to shared mailboxes and improving the data collection and error management on the back end.

Our look was getting notice

Cubert heads to Labtech’s Automation Nation 2014 for the second year to see whats in the pipeline in the skunk works at Labtech. Speaking with several people at AN2014 we discovered that there were people using the plugin and had some insight in to how we could make it better and we were determined to do just that.

Our plugin was starting to take shape and the download counts were starting to roll in but with the users comes the problems. The first real wide spread issues started to arise with how Labtech was executing Powershell scripts. This process did not always produce the same results. We found that across platforms that some users were experiencing execution errors with the Data Miner scripts we had designed. We decided a rewrite of the collector was needed, a design that would use the native Powershell application on the PCs instead of the one provided with the Labtech Agent.

We re-crafted the entire data collection process and called it of course “Collect Data” aka “Office 365 Collect Data” . The new method incorporates all user data mining in a single session and adds our newest feature to the Office 365UM Distribution Group Management.

Come and get it

So today we announce our 7Th release of the Office365UM plugin for Labtech available for download now at Squidworks Office365 Plugin for Labtech . We hope you enjoy our products and post here at Squidworks, your experiences with the plugin. This will help drive the development in the direction that is most useful to you and helps us build a better plugin.

Here is what we can do today:

Add, update and delete user accounts and email addresses
Manage Send As, Send on Behalf As and Full Permissions on Mailboxes for other users
Set and delete Forwarding email addresses for users
Restore soft deleted users (30 day limit on retention)
Convert User Mailbox to Shared Mailbox
Set/reset users password
License/unlicense user
Add and delete distribution groups
Add,delete and view group members
Add/Remove groups from Global Address Lists
View License counts and type

Thanks to everyone involved!

Cubert

[LabTech] IPBlock Windows Firewall plugin.

Block entire countries from seeing your PC on the Internet

Squidwork’s garage has released version 1 of their new IPBlock for Labtech RMM. IPBlock is a Country based Network Firewall plugin for Windows based systems. When deployed you can select different countries you do not want to have access to your IP address for any Windows Vista / 7 / 2008 or new system and block them from network access to your PC.

How it works:

The plugin launches a script that goes out and refreshes a complete list of all countries and any IP ranges assigned to those countries. It imports them into the local host and stores them in zone files inside the LTSvc directory. Then based on your selection it applies each zone to the Windows firewall as a rule set.

What does this do for me?

This greatly reduces your Internet footprint and attack surface. Preventing access from countries that have large amounts of attacking systems. It also reduces your ability to be fully exploited by Trojans, Virus or Worms as if infected it makes it much harder to “Phone Home” if the attack comes from a Country you have blocked like “China”.

Version 1 only controls the lists that are applied to your PC it does not turn on or off the actual firewall on Windows. You will need to turn on firewall through the Windows control panel for rules to actually take effect. Then to stop the filtering shut down Windows firewall or go into plugin and select “None” and apply for all rule sets placed in by IPBlock to be removed.

Get Version 1.0.3 here

Enjoy Cubert 😎

APPAssureD – Dell AppAssure Backup Plugin For LabTech

A new plugin is under development here inside the Squidworks garage that allows Labtech MSPs to manage Dell Appassure Backup Cores servers from a common console inside of Labtech. The new plugin leverages Appassure REST API to mine data from each core and send that data back to the Labtech database. Using the same processes the plugin is able to send commands back to the cores to preform various tasks like start a new backup or replication.

The plugin provides a common view of each core at the location level console in Labtech. You can select one of many cores at any location and view the protected servers managed by that core. Selecting a protected server provides details about that server and the list of snapshots preformed on that system. We have many great features planed for this plugin so start following us now!

Client Console

Dashboard View

The plugin is still under development and will we have a release for early beta testers. Place a comment here you would like to be notified of updates and being included in the beta testing.

Get Version 1.0.1 Beta here

You Will need Powershell 3 on all Cores, Here is a script to install Powershell 3 directly from LabTech

Get PS Installer Script Here

LabTech & ConnectWise VMWare ESXi Heath Monitor Plugin v3

ESXi Health Monitor Plugin

Well it’s finally here, the plugin we have all been waiting for, Vmware ESXi Health Monitor plugin for Labtech. This plugin installs into your Labtech system as a Location plugin to monitor the CIM data available in most hardware. Easy to configure controls and full view of the CIM data collected is just part of what this plugin can do. We have incorporated new functions into this plugin that are stark differences from our earlier version 2 and version 1 ESXi Health Monitors. We are now supporting multiple usernames and passwords per location for ESX hosts and only require 1 probe system to monitor all the ESX hosts at a single location. I could talk all day about the plugin but maybe it’s better if I show you.

Here is the main view of the ESXi Health Monitor plugin.

The hosts get listed with status face based on current status and when you select a host the CIM data is displayed so you can see all the reported statuses of the hardware.

This is the ESXi host configuration tab of the ESXi health Monitor plugin.

This is where you will add and edit your host systems to monitor, you can set the system you want to be responsible for probing the ESXi hosts for the CIM data. Then you select a system and “Set” it as the probe the plugin will launch a script against the probe to prep it for monitoring automatically. You will not need to “install” the probe software manually as this is handled by the plugin when the probe system is selected.

The ESXI Health Monitor plugin uses a custom group to locate all the probes available by using a custom search to locate all systems with the EDF of “VMware Master CIM Scanner” selected as seen it the example below. You will find this setting under the Info tab -> VMWare on any system console. Just checking it will not install probe software so you must “Set” the probe via the plugin.

The Custom group should look like this and have the custom search setup as seen in this example.

The custom group also has a scheduled script to run every 2-4 hours and I use the exclude time range as I do not need this data so bad that I can’t sleep with out it running every hour or 2. This is just my personal preference but saves on CPU cycles during backup windows and maintenance schedules. You will need to reset this when you import your group as this seems to always get rest to nothing during imports.

You can see your probe run on the system by watching the script logs on the probe systems console. This helps when troubleshooting common issues.

This version is in Beta! this is the first release of this plugin and as such may have odd behavior issues and or may not work for you as expected. I seriously doubt you will have any issues but as this is Beta expect a few minor glitches. We are actively working on updates and with your help we can make this a great plugin!

You can run the version 2 and version 3 side by side and they will not effect each other.

Updates:
———————————————————————————————————-

Changes in New Version 0.3.0.3

Changed Version number back to what it should of started at. It was a typo starting with (3)
Added Internal monitor called CIM – VMWare ESXi Health Monitor
Added Client View and Global View of System Statuses
Corrected a few minor coding mistakes
Added Linux Probe Support
Updated the data views

Changes in New Version 0.3.0.5

Added Last Scan Time Stamps
Added color coded data views
Added new images

Changes in New Version 0.3.0.6

Fixed Scan Time not updating

Changes in Version 3.0.7

Updated Python Packages to 2.7.8
Fixed several SQL issues with table creation.
Minor enhancements

Changes in Version 3.0.8

Added new instant host probe from the configure tab
Fixed minor issues in plugin
Fixed issues with installer script

Changes in Version 3.0.9

Fixed CIM Monitor in LT
Fixed Versioning context
Fixed password bug when resaving the same password for esx probe.

Changes in Version 3.0.10

Fixed Issues with Installer where latest PY script requires several new Python modules.

New Client Level View

This view give you a look at all systems under the clients control. you can select the system and review the CIM data returned.

This plugin monitors the condition all the systems and will alarm when a system is found to be in error. You can customize the alarms and the methods of alerts received through the Monitors management interface in Labtech .

You can download the latest version here.

Version 3.0.10 Now Available

If you like what we are doing then please donate to our cause, help keep our software free.

How to install plugin

Please post here any comments and issues you may have so we can get them fixed and out in the next release.

Enjoy

Cubert 😎

LabTech & ConnectWise Office 365 User Manager

LabTech Software User manager for Office365 plugin

Get it here -> Version 0.1.8.6

As of Version 0.1.6 we have added several new features and some bug fixes. These new features include ability to manage Send As, Send on Behalf Of and give full permissions to users of Office365. Set forwarding email addresses and reset user passwords, Add new users, Soft delete users (30 days to recover) and update user s Active Directory information. We have also updated the user views to include mailbox sizes and item counts, provisioning status, Client license type and license counts available and consumed licenses.

New in version 0.1.7.0

Distribution Group Management: Add and delete groups and manage the members in the groups.
We rewritten the way we collect data, we now create and run shell scripts directly on the workstation verses using the powershell script cmd in LT scripting. We have combined several sub scripts in to a single script that opens one connection to O365 and grabs all user data in 1 session. This has improved the speed of data collection by several fold.
We fixed a few issues with the Plugin script and added some more error handling.

We have change the layout in version 0.1.5.0 to a tabular design to allow for more controls to be added in a logical manor, We now can restore user mailboxes and convert users to shared mailboxes.

New in version 0.1.8.0

We resolved some issues with several features, added a new license manager, added the ability to export a list of licenses and the users to a CSV file and we now have a documentation and help center located on each tab to better assist users in managing Office 365.

New in Version 1.8.1

We added several new controls to the main application, you can now set domain password policies, manage calendar access for users and set user passwords to never expire. We also made a few fixes and added some new code to help with troubleshooting data collection issues.

New in Version 1.8.2

Several bug fixes, updated scripts and updated Windows Azure packages with latest versions.

New in Version 1.8.5

Added new feature :Powershell Session, this opens up a powershell session with Office365 and hands you the console to run any cmdlet you want on the clients Online services without the need to lookup the clients account information and building a session your self. One quick click and you accessing Microsoft Online and loading all modules needed to manager your Office 365 in the cloud.

Minor issues fixed.

New in Version 1.8.6

Added new Collector Tab that allows you to set the collector, launch new collections or test the collector for readyness.

Added script to update powershell to version 3 on all collector system with powershell 2 installed.

Here is the list of things to setup:

#1 the Zip comes with scripts, a group and a search along with the plugin DLL. You will need to import these into your system and set them up if they do not setup correctly during import. You should also view the plugin first before setting up the group and scripts to mine the data. This will allow the new database tables to be created to store the data the miners will be collecting. When you import the group and search the group doesn’t schedule the Office 365 Collect Data script correctly so you may need to verify and or replace the schedule group script to run every 2-4 hours.

The scripts are:

“Install AD Module for PowerShell” – Setup Powershell on any remote windows 7 x64 or 2008 R2 or newer system.
“Office 365 Collect data” – Should be scheduled in Group to run every 2-4 hours. Collects the user data and keeps it current in database.
“Office365_Plugin.ps1” – Must be placed in L:\Transfer\Scripts\Office365\ for plugin to function. If you are using Labtech from remote and or do not have the mapping available you can use a USB thumb drive and store the script in the same location on thumb drive and mount it as drive L:\ and you will function correctly from remote or cloud based RMM.

Next after you install the Microsoft powershell script on a system that meets the standards (Win 7 x64 +) at each client (any location and only one location needed) Add a new password to the password Tab at the “Client” Level that’s title is “Office365”, the username be the admin email address for client (Example:admin@clientname.onmicrosoft.com) and the password used. All scripts and Plugin will use this location to get the passwords needed to access each clients Office365 accounts.

To prep systems that will be acting as the data miner for the client you should first find a Windows 7 x64 or Windows 2008 R2 or greater system at one of the clients locations. Then run once on that machine the new Office 365 script “Install AD Modules for Powershell” on that system. Once complete the script should automatically “check” the “Windows Azure Active Directory Modules Installed” box as seen here in picture. You will need to also run this script on all workstations you plan to use to support your helpdesk, remembering to “uncheck” the Windows Azure Active Directory Modules Installed” box for all systems on your helpdesk as you do not want them as part of the search group.

You will want to install the powershell tools on all support center personal workstations that meet the minimum requirements. We use these tools in the plugin as well as scripts so console users will need tools also. Remember to go to each of those systems in Labtech and “uncheck” the box “Windows Azure Active Directory Module Installed” so that helpdesk employees do not get office 365 probe running on their systems every 2-4 hours. Next you should setup search and group, the search looks for a flag to be set in the “default” location on the Info tab of a PC. If found “checked” it will add this system to the four hour scripting of the user data fetcher.

“C:\Windows\System32\WindowsPowerShell\v1.0\Modules\MSOnline”
to
“C:\Program Files\Windows Azure Active Directory\Powershell\MSOnline”

There was a security issue with plugin accessing %windir% so we had to move the MSonline module manually to an area we could read from. I will be fixing all this in the upcoming release.

When you execute changes using the new plugin it will launch a Powershell console to execute the connections to MSOnline, pass the information to MSOnline and then close. This can take a little time to complete depending on MSOnlines current load on system. Be patent and allow the Powershell window to close on it’s own.

Import the Group and Custom search:

Whey you import the scripts, custom group and search they may not end up where they were meant to be so you may need to move things around in LT to get it setup correctly.

Once you import the group you should have under the groups drop down a new group called MSOL Office365 Hosts. There should be 1 script scheduled “Office365 MasterMiner”. It should be scheduled to run every 1-2 hours and to skip if offline. This group should be using the custom search you have imported as part of the plugin install. Just verify that this is accurate and if not reset group to use the Office365 search.

If group and search are functioning correctly you should get a list of all systems that have the “Windows Azure Active Directory Module Installed” checkbox checked. This should be only 1 system per client. You do not need to have them installed at every location. It does need to be a Windows 7 x64 or Server 2008 R2 or greater system to operate the powershell functions.

That’s about it…

Enjoy Office365 management via Labtech

Cubert

LabTech Vitals Dashboard

Today we release the next round for the Squidworks Labtech Vitals Dashboard.

The Labtech Vitals Dashboard is a set of web pages that query the local Labtech MySql database and provides visual widgets of important data on the main display of the Labtech Support Console. We currently have 17 different widgets with 10 of them having detail views.

To install the Dashboard you will need to download and install PHP 5 for windows at PHP.net on your Labtech server. Afterwards download the SWVDB zip package and unzip to c:\inetpub\wwwroot\SWVDB. Go into this directory and find the header.php file and open it with notepad. You will need to edit the LT server address, Username and password for the LT database access to work.

Once completed you should be able to browse http://your.labtech.server/SWVDB/ and get the dashboard. Now to have the dashboard auto load in the console for everyone who uses support console go to your LT config dashboard -> Config -> Control Center and set the Initial URL Value to your tested URL from above.

Get the dashboard -> Download SWVDB here

Should look like this:

Widgets:

Systems Missing AntiVirus application

Agents missing patches

Agents Online

Offline Servers Alarms

Dell Appassure 5 Backup Core Monitor

ESX Hardware Health Monitor

Hitman Pro Monitor

Agent Monitors

ESX Monitor Details Page (Failed/Missing/All)

Dell Appassure Monitor Details (Completed and Failed)

Some widgets may not function correctly if you are not using the source data tables and extra monitor scripting I’ve made available like the Squidworks ESXi Health Monitor for Labtech located at ESX Health Monitor, The Dell Appassure Backups/Failures also requires my Appassure Backup Scripting to populate the database with data. You must edit the index.php page in notepad and uncomment the 5 function calls noted in index.php for ESX and Appassure counters to function. They have been commented out so that you do not get errors if tables are missing. Install both ESX and Appassure packages before uncommenting code block.

Enjoy

Cubert 😎

LabTech & ConnectWise ESXI Host Hardware Monitor

NEW ->LabTech ESXi Hardware Monitor v2.1

Squidwork’s ESX Hardware monitor is a set of scripts, a custom group and search for Labtech that will monitor the CIM data provided through the VMWare API for ESX 4 and 5. The probe will launch hourly and report back to Labtech any hardware failure or warning. The script will email an alarm to any email address you would like. The script can be modified to also set an alarm, create a ticket or anything else Labtech scripting will let you do.

New in version 2.1:

We added several checks for false alarms and socket errors to prevent alarms and emails on non failures.

We added alarm flood control, once a email goes out it will not send another until the system has reported a “all OK” then alerts are reset to go out on next fail.

Added extra EDFs to control processes.

Here is how it works:

Download the zip file, extract and import the XML files into your Labtech system.

Addendum Update:

After you import “all” scripts in Version 2.1 Download this zip and import this script. This script should then be used in your group scheduled script probe instead of the v2.1. This v.2.2 of that one script. Download update here

Download extra files directly if import fails for any reason here.

After the import you should have a VMware script group that has 3 scripts in it.

Script #1 (The Installer) will install the monitor to a Windows system. You will need to provide the FQDN or IP of the ESX host you want to monitor when you execute the installer script. When the scheduler pops up make sure to add your ESX host. The only thing you should need to do is execute the installer on a Windows system. The installer will configure the system and add the system to the custom group and search. You do not need to configure anything else at this point. The ESX user and password will be fetched from the Locations password menu for VMWare.

The next script (The Monitor) is assigned to the custom group “Systems that monitor ESX hosts” to run every hour. You can modify this to run at what interval you like. The Monitor will query your “Locations” passwords database table and retrieve the VMWare user listed just like the original Labtech probes do. The monitor get the CIM health data and returns it to Labtech, It also looks to see if we are “Not OK” and fires off a email if failures are picked up.

After the Monitor runs you should see data on the Info Tab -> VMWare sub tab

You will need to edit the monitor script updating the email address that it reports to when failures are found, you can also modify monitor script to create a ticket, fire off an alarm, set an alert or anything your heart desires. Line 39 of the script ESX Hardware Monitor V2-1 needs to be edited and the example@example.com email changed to the email you want to get the alerts.

The 3rd script is a updater script that will fetch the latest build of the Nagios Plugin:”check_esxi_hardware.py” script maintained by www.claudiokuenzler.com You can run this script against any Windows box that has the monitor installed and it will get the latest version of this script and deploy it to that system. This way you can keep up with all the fixes they do to this script. You may want to run this script on the group once or twice a year just to make sure you have the latest fixes and updates.

Enjoy

Cubert 😎

Vitals Dashboard for Labtech MSP Providers.

Squidworks Vitals Dashboard for Labtech Software

Download SWVDB here -> SWVDB-0.1

Install instructions are included in the “install.txt” file inside of zip. You will need to have PHP 5.3.27 installed on you Labtech server and can be downloaded at http://php.net

The purpose of the Vitals Dashboard is to get key pieces of information about the health of your client base in front of you and your techs. Each time you launch your control center your dashboard can appear in the console’s display. This brings the vital information to the forefront like Offline Servers and HitmanPro alarms.

Some dashboard items are interactive and will supply more data if selected. Clicking on the HitmanPro Alarms will launch you to the HitmanPro Dashboard.

HitmanPro Dashboard

The HitmanPro Dashboard shows all the current threats found and lists them by client and computer. By clicking on the computer name you will get a detailed account of the threat alarm. At this main view level you can also see what systems were scanned in the last 24 hours and when, displayed by client.

Hitman Pro detailed alarm viewer allows you to see in detail the cause of the alarm and what threat was found. We have color coded the alarm message and added some formatting to better display the details of the alarm from the default view Labtech offers.

Agents with excessive reoccurring logs

Agents Missing Service packs or are out of date

Agents With Disk Space or Failures

I hope this helps some of you out there.

Cubert

😎

XYMON – ESX Hardware Health Monitor

Grab the Hardware Health of your VMware vSphere ESXi Host

Here is RC1 of my ESX Health Script for the XYmon monitoring server, not to be compared to the ESXi script going around for VM and Snapshot Health. ESXHealth monitors the physical health of the hardware running the ESX hyper-visor This script uses the xymoncgimsg.cgi to send status reports from a remote network to your XYmon Display Server thus allowing you to monitor ESX Host from anywhere really easily. Using this CGI allows you to run it from any windows box and send the notifications through port (http) friendly firewalls.

The only prereqs are, you must have installed the VMWare vSphere Perl SDK and have installed CURL or place the curl-nossl.exe provided in zip in the your PATH on Windows. Your XYmon server must have the xymoncgimsg.cgi moved from the xymon/server/bin folder to your xymon-cgi folder to allow web based status messages.

I have include the curl-nossl portable EXE with zip. Just drop it in the path for windows so you can call it by name. You will need to edit the script and update the URL to send the notifications to. I show an example in the script on how to use with a htpasswd protecting your web CGI for thoes who use that layer of security. If not then just place the standard URL for your xymoncgimsg.cgi and your good to go.

The script is very simple.

If all is good you get a “All’s OK” else if anything is bad it spits out any relevant info about that issue. The last error I got was for redundant Power lost to Supply 1 and was reported with plenty of detail to know what is wrong.

Just schedule windows to run every 15 minutes or so, see script for command line syntax for task scheduler

Download -> ESXHealth-1.1 Monitor for XYmon

The monitor will look like the following examples: (Never mind my XYMon theme)

I hope this helps someone out there.

Cubert 😎

Enable SurfLog on a per client basis

SurfLog History Retention

SurfLog Key Word Highlight

Get SurfLog 1.1..1

Squidworks Office365 UM Evolves

In the beginning

Moving Day

Our look was getting notice

Come and get it

Block entire countries from seeing your PC on the Internet

Client Console

Dashboard View

ESXi Health Monitor Plugin

Updates: ———————————————————————————————————-

Changes in New Version 0.3.0.3

Changes in New Version 0.3.0.5

Changes in New Version 0.3.0.6

Changes in Version 3.0.7

Changes in Version 3.0.8

Changes in Version 3.0.9

Changes in Version 3.0.10

Version 3.0.10 Now Available

How to install plugin

LabTech Software User manager for Office365 plugin

Today we release the next round for the Squidworks Labtech Vitals Dashboard.

NEW ->LabTech ESXi Hardware Monitor v2.1

Squidworks Vitals Dashboard for Labtech Software

Download SWVDB here -> SWVDB-0.1

HitmanPro Dashboard

Grab the Hardware Health of your VMware vSphere ESXi Host

Updates:
———————————————————————————————————-