Labtech.  RMM tool.  (Remote Monitoring and Management).

What is so great about it?  Well, once you learn it… once you understand it… you can do anything you want with it.

Like what?  Well, you have your normal RMM things like keep track of the computers on the network, what OS, what programs, keeping up with Microsoft patching, installing software, removing software, etc.  Then you have the monitoring – you can monitor just about anything you can think of from registry entries (including installed programs), event logs, pretty much anything you can find in a readable file on the computer, you can monitor and trigger alerts or even emails and text messages on those events.

Then you have scripting.  Some of the things I can accomplish with scripting:

Extract the backup status of a computer from the logs of the backup program and send an email if there is a failure.

Read a file version, compare to an internet site and send an alert if the two are different or off by more than two, etc.

Launch a series of powershell scripts to configure a new windows server, with variables put in when starting the script in Labtech.

With a little creativity, anything you can do via command line or powershell, can be done remotely, in the background, with Labtech.

Yes, that is very cool.

My home computer has been running Ubuntu Desktop (Debian Linux) for years.  It has only been recently that I have had the pleasure of working with Linux Servers.  I have set up, configured and administered a few LAMP (Linux, Apache, MySQL and PHP) web servers.  For the last couple days, I have been playing with Citrix Xen Server and HyperV to proof-of-concept virtual host NIC Bonding / Teaming and it’s effect on existing Virtual Machines on each platform.

I set up an environment (Xen, then HyperV) on a test server (Dell R710) and added a few Linux VMs (Got to play with Ubuntu Server 16.04 LTS and CentOS 7).  Then I did the Bonding/Teaming and watched for what happened to the existing servers and network connectivity.

Xen Server did very, very well! It had zero network disruptions as NIC Bonding was created and put into place.  Very impressive.

HyperV was less impressive.  There were multiple connectivity disruptions and panic-inducing bouncing before it settled down.

All that, to show off a screenshot:

I have two small items on Sourceforge.

Nothing Fancy Drive Space Recovery
and
BMC CM Tuner Log Helper

Source files available!

It took some time, but :

Speaking of Certs…

One of my favorite accomplishments was the “Trustmark Computer Console” that I created for use at Trustmark National Bank.  It was used by the call center and help desk from the time I created it until at least two years after I left.  It may still be used some.

I wrote the original in AutoIT3.  After a while, I re-made it into a VB .NET project.  However, the VB .NET did not do a WMI query quite right, so I had to write a helper script in AutoIT3 to get that piece of information.

Here are some screenshots :

Some items are blurred out, but under “Computer Name” is a text box where you would put in the name of the computer in the network you wanted to get the info from.  The red/green buttons under that were our major services or processes that should be installed and running.  You could right click on the buttons and start/stop/install those items.

Pressing “Enter” from the Computer Name box would go out and get the current information – such as OS, logged in user, free space, IP address, last boot time, mfg and model, processor, memory, etc.

The buttons on the right would run different scripts to automate common tasks.  At the time, on a single domain, it was fairly great for Help Desk Technicians to quickly gather info and fix common items.  I now use Labtech for almost all that functionality.

Here is the User Guide that I wrote for it – Computer Console User Guide