Tag: plugin

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:

office365UM

 

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.

Office365UM0.1.4

 

 

 

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:

Office3650.1.5

 

 

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.

 

GM-O365UM

 

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:

  1. Add, update and delete user accounts and email addresses
  2. Manage Send As, Send on Behalf As and Full Permissions on Mailboxes for other users
  3. Set and delete Forwarding email addresses for users
  4. Restore soft deleted users (30 day limit on retention)
  5. Convert User Mailbox to Shared Mailbox
  6. Set/reset users password
  7. License/unlicense user
  8. Add and delete distribution groups
  9. Add,delete and view group members
  10. Add/Remove groups from Global Address Lists
  11. 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.

ipblock-main

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

download

Enjoy Cubert 😎

APPAssureD – Dell AppAssure Backup Plugin For LabTech

appassured-logo600

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 Console5-20-look

Dashboard View

dashboard

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

download

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 Plugin – Printer Health Status

print-icon

     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:

printerstatus-preview1

Printer Status at the Client Console:

printerstatus-preview2

Printer Status Exclude Printers:

printerstatus-preview3

Download Labtech Plugin – Printer Status Version 1.0.4

download

Enjoy

Cubert

LabTech & ConnectWise VMWare ESXi Heath Monitor Plugin v3

ESXi Health Monitor Plugin

weblogo

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.

mainview

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.

config-tab

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.

master-scanner

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

group-join-search

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.

group-schedule-probe

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.

probelogs

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

mainview

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 .

monitors_alarm

You can download the latest version here.

Version 3.0.10 Now Available

download

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

mainview-1.8.6

Get it here ->  Version 0.1.8.6

download

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.

Office3650.1.8Office365-Permissions

Office3650.1.5-3 Office3650.1.5-4

groups-tabLicensing

collector-tab

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.

office365-pass

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.

Azure-installed

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.

O365-Execution

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.

Office365-group-0.1.4

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