LabTech & ConnectWise Plugin – Printer Health Status

Printer Health Status

Mr Keigher posted on the Labtech forums that wouldn’t it be great if there was a Printer Status Plugin for Labtech that could show if there were any issues with a printer and maybe even interact with a failed printer. Well Marty your ship has come in! Let me introduce you to your new Printer Status Plugin. The team down in Squidwork’s basement went to town taking what seemed like minutes (and it looks like it) to build a Labtech plugin that would do what had to be done.

In Version 1.0.4 you have good management over printers in 2 main views; the global view and the client view. The Global view allows for the full management suite of tools to be executed on any printer being scanned and will give you a quick view in to the troubles your clients maybe having. The Client view provides the same management functions but also allows you to enable and disable scanning for a client and to include desktops in printer scans.

Lets show you what we have:

Printer Status Global Manager:

Printer Status at the Client Console:

Printer Status Exclude Printers:

Download Labtech Plugin – Printer Status Version 1.0.4

Enjoy

Cubert

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 & 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 😎

[LabTech] Patches not showing accurately for systems after onboarding with Ignite

I had an odd issue with a new client I had taken over from a previous MSP where after we onboarded the client Labtech showed systems as fully patched but when we scanned system using Windows update they returned with 60+ updates or more. We would then re run the inventory update and would still get all patches up to date. We noticed that the list of patches that were returned did not cover all approved patches. After some investigation we discovered that the previous MSP was using a 3rd party WSUS server and had set the server information in the registry. If the following Keys are present then you may also be seeing similar problems.

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate:WUServer HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate:WUStatusServer HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateAU:UseWUServer

Here is a Labtech script to clear out the settings and to allow you patch inventory command fetch the correct patches for your system. Execute script against each system that has been configured for a different WSUS server. Once script has completed then execute a hotfix update command from your inventory menu and wait for it to populate with the correct settings.

Download Script WSUS Settings Removal

Enjoy Cubert 😎

[Labtech]Mac Script to install Vipre Business AntiVirus.

So you want a script to install Vipre AV on Mac systems well I got just the thing for you.

Here is what I did.

Create a 2 line LT script,
In the description field of your new script type in the following, feel free to cut and paste if you want.

“I promise if this script works for me to send Cubert a Starbucks Gift card”
Now lets add our first line to the script

Line 1 = “write file” command to /tmp/myviperinstall.sh

content =

cd /tmp

curl -O http://myserver/labtech/transfer/Vipre/MacVIPREBusiness2.0.87.dmg

hdiutil attach MacVIPREBusiness2.0.87.dmgcd “/

Volumes/GFI Software VIPRE Business – 2.0.87″/

installer -pkg “GFI Software VIPRE Business Install.pkg” -target “/”

cd /tmp

sleep 5

hdiutil detach “/Volumes/GFI Software VIPRE Business – 2.0.87″/

Do not forget to edit the URL and name of the viper DMG file. I was using 2.0.87 when I wrote this so you will need to make any changes to file names and mount directory names.

*note* I left out the first line of text which normally would be (#!/bin/sh). The “Write File” function had issues with the !, not sure if I needed to escape that or not so I just left it out.

The next script line should be “Shell Extended” with a cmd of “/bin/sh /tmp/myvipreinstall.sh”

The 2 lines combined will write the script file to the Mac system and then execute the shell script. The shell script uses curl to download your DMG and then mounts DMG, and executes the PKG installer.

I am also working on updating the server preference for Mac to point to Vipre server and then updating LT database to show that AV is installed.

That will come later in the show!

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

😎

[Kaseya Agent Procedure] VMWare ESXi Hardware Health Monitor

VMWare ESXi Hardware Health Monitor Script

From the skunk works here at Squidworks comes another great monitoring script for Kaseya.

This script uses the SDK provided by VMWare to query the ESX host and return a good or bad variable. If the hardware test fails then the script grabs the log of the test and uploads it to Kaseya Server then places it under the “Get File” area for the host that ran the test. You can run this script on any windows box, I have also included the current vSphere SDK installer and a Kaseya script to install it if it is not found on the Windows Host.

Upload the SDK installer and Import the scripts to your public files area in Kaseya under the directory “VMWare”. If you place files anywhere else you will need to edit script for the new location of files.

The script then makes a unique event log entry into the Windows Application Event Log under the Application Events that can then be picked up by Kaseya’s Event Log Monitor. When Kaseya picks up this event you can instruct the monitor to create an alarm, create a ticket, run another agent procedure or email the alarm to an address(s). Just schedule the agent procedure to run a couple of times a day to keep an eye on your customers VMware vSphere ESXi Hardware health.

This script links to the CIM information provided by the hardware to the ESX host. You will see CPU, Memory, Fans, RAID and Controller Health. The log file that is uploaded will only show failures and will tell you what failed and on what ESX host.

Download -> Kaseya VMWare ESXi Hardware Monitor

Enjoy

Cubert 😎

[Kaseya Agent Procedure] Free Active Directory Health Monitor Script

Active Directory Health Monitor Script

From the skunk works here at Squidworks comes another great monitoring script for Kaseya.

The Active Directory Health Monitor Agent Procedure executes DCDiag on your Windows Active Directory server and captures any failures reported. The script then makes a unique event log entry into the Windows Application Event Log under the Application Events that can then be picked up by Kaseya’s Event Log Monitor. When Kaseya picks up this event you can instruct the monitor to create an alarm, create a ticket, run another agent procedure or email the alarm to an address(s). Just schedule the agent procedure to run a couple of times a day to keep an eye on your customers Active Directory health.

The script also provides a complete report of the DCDiag results in the event of a failure that you can view by going to the “Get Files” area of your host in Kaseya and under this folder will be an Active Directory folder where the DCDiag.txt file results are stored.

All files and a README are included in the ZIP. Feel free to POST here any issues or comments you may have.

Download -> Kaseya-ActiveDirectoryHealth

Enjoy

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 😎

Printer Health Status

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

NEW ->LabTech ESXi Hardware Monitor v2.1

Squidworks Vitals Dashboard for Labtech Software

Download SWVDB here -> SWVDB-0.1

HitmanPro Dashboard

VMWare ESXi Hardware Health Monitor Script

Active Directory Health Monitor Script

Grab the Hardware Health of your VMware vSphere ESXi Host

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