Scripting Archives - Squidworks

Plugins4Automate Announces – PowerShell Command Manager Goes Premium

Plugins4Automate announced yesterday that they are now releasing the Powershell Manager for LabTech / ConnectWise Automate as a premium plugin to the RMM platform formerly known as LabTech. Over 600+ users enjoy the efficiency of the PowerShell Command Manager for LabTech and the control they have over each of the MSPs client’s environment. This is a must have plugin for MSPs that have clients using Microsoft products and services.

To read more about Plugins4Automate’s new premium release and to get a special deal for acting quickly please visit the P4A’s announcement blog post. In this post you will find a discount code that you can use to permanently discount the subscription but you need to act fast, it’s for a limited time only.

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

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

[Kaseya Agent Procedure] Mac OSX and Windows – Send A Friend a YouTube Video Surprise!

Kaseya YouTube Me Script Plays Youtube videos on desktop inside a player.

Here is a script that carries a warning, Use Wisely… I am not responsible for misuse! If you play porn on the bosses PC why he is in a meeting with the board of directors I am not liable for your termination and or execution depending on the boss…

Now with that disclaimer said here is what I made for you. This script will “based on the OS installed” (Windows) copies a portable version of VLC to c:\temp and runs it with a URL as a option or (Mac OSX) Downloads a DMG of VLC and installes it if not found already on system and then runs the same URL.

The URL is a cartoon of a stick guy beating himself to death while a stupid song plays in the backgrond. It will pop up on the desktop of the user logged in and if the speakers are up it may be a jolt!

Here are the files you will need

The script -> Procedure YouTube Me

WIndow Portable VLC -> Windows VLC

Mac OSX VLC (dmg) vlc.2.0.1

Download all 3 files and upload the VLC files to your VSA SharedFiles Folder. Edit script after importing it into Kaseya and make sure you do not have any red lines in code. If so you may have file location issues, check where you uploaded VLC files. Post here any good YouTube URL to use for script.

Have fun

Cubert 😎

[VB Script] Automate the copy of folders across the network to a local removable drive in Windows.

So you need a quick method to grabing folders from a UNC path and place a copy of them on a removable drive. I had a customer who wanted to do the old USB drive swap for off site backup storage. I tried to explain that now with the advent of the cloud we could move the files off site without any user intervention but they really wanted to do it manually.

So here is a Automated script to help with a manual process.

Download Script Here

Here is the basic beak down of the script.

In the first part of the script we set the email server to relay mail to, our domain name and the email addresses we want to send reports to.

‘ Company Internet Domain Name
ODomain = “mydoamin.com”
‘ Set the SMTP server IP
oMyIP = “192.168.1.5”
‘ Where do you want the message to be delivered
oTo = “myemail@mydomain.com;another@email.com“

This next part sets up the local directory we will be copying to, The script during execution will delete all things off the drive and then rebuilds the directory structure you want so we have to tell it the directory we want added back after the delete.

‘### Check folders exist and prep for copy

Dim oName, ODomain, oMyIP, oTo, newfolder, newfolderpath
Set FSO =CreateObject(“scripting.FileSystemObject”)

‘###Change my folder path ######################
If FSO.FolderExists(“F:\Backup\”) Then
   FSO.DeleteFolder “F:\Backup”
   wscript.sleep 90000
End If

‘##### Change My folder path#########
newfolderpath = “F:\Backup”
If Not FSO.FolderExists(newfolderpath) Then
   Set newfolder = FSO.CreateFolder(newfolderpath)
   wscript.sleep 5000
End If

Now we need to start the actual copy and get some files on our removable disk. You will need to edit the “newfolderpath” so it reflects where you want the files copied to. You will need to edit the FSO.CopyFilder so that it resembles your UNC path. You can copy the em=ntire code block and repeat over and over again for multiple UNC paths or folders.

‘###Grab files and place them in new folder (We must create that new folder now)

‘### Change my new folder path ###################
newfolderpath = “F:\Backup\MyNewfOLDER”

If Not FSO.FolderExists(newfolderpath) Then
Set newfolder = FSO.CreateFolder(newfolderpath)
End If

FSO.CopyFolder “\\MyIP Address\MyShare\MyFolder”, “F:\Backup\mYNewFolder” ,True
wscript.sleep 5000

‘### You can copy the top several lines starting with the new folder creation and repeat as many times as needed. This will allow for mulitple locations and folder

Next we write an event log in windows reporting that we completed the copies.

Set WshShell = WScript.CreateObject(“WScript.Shell”)
strCommand = “eventcreate /T Warning /ID 99999 /L SYSTEM /D ” & _
Chr(34) & “The Script has completed the scheduled backup copy to the offsite drive (F:)” & Chr(34)
WshShell.Run strcommand

Then we send off a email to the users we set in the above script area.

‘ Get the computer name
Set WshNetwork = CreateObject(“WScript.Network”)
oName = WshNetwork.ComputerName
‘ Set the visual basic constants as they do not exist within VBScript.
‘ Do not set your smtp server information here.
Const cdoSendUsingMethod = “http://schemas.microsoft.com/cdo/configuration/sendusing“, _
cdoSendUsingPort = 2, _
cdoSMTPServer = “http://schemas.microsoft.com/cdo/configuration/smtpserver”

‘ Create the CDO connections.
Dim iMsg, iConf, Flds
Set iMsg = CreateObject(“CDO.Message”)
Set iConf = CreateObject(“CDO.Configuration”)
Set Flds = iConf.Fields

‘ SMTP server configuration.
With Flds
.Item(cdoSendUsingMethod) = cdoSendUsingPort

‘ Set the SMTP server address here.
.Item(cdoSMTPServer) = oMyIP
.Update
End With

‘ Set the message properties.
With iMsg
Set .Configuration = iConf
.To = oTo
.From = oName & “@” & oDomain
.Subject = “Backup Copy to Offsite Drive Started”
.TextBody = “The NTVI Server Backup copying is now taking place. The drive should be ready to remove offsite.”
End With

‘ An attachment can be included.
‘iMsg.AddAttachment Attachment

‘Send the message.
iMsg.Send

Thats it, You can download a zipped copy of the entire script using the above link.

I hope this helps you, Enjoy..

Cubert

Kaseya Agent Procedure -> Alert if Privileged Account are changed in Active Directory

Out of the skunkworks here at Squidworks comes a new Kaseya Agent Procedure. This procedure (Script) pulls all members of privileged accounts groups like Domain Admins, Enterprise Admins and Schema Admins and stores it to the GETFILE location on your K-Server. Also viewable using LiveConnect -> Agent Data -> GetFile Tab. You can add and remove groups from the VBScript to match your needs. The nice thing about this script is it finds out what your Forest is and queries the domains inside. You do not need to edit script for every domain in your customer base. This 1 script will query any domain it is pointed at, with out knowing what the domain name is! (Sweet) This makes it a great tool to deploy across all customers as it requires no edits to run on any domain.

The script should be scheduled to run every day, each time it is run it copies a new file up to the GETFILE area and does a compare of the 2 files. If they are not exactly the same it will send an alert that a change has happened.

You then need to watch for this alert to happen and alarm on it. To do this you will goto your Monitor tab in Kaseya. In the main menu under Agent Monitoring select Alerts. In the main window under alerts you will find a drop down selection box called “Select Alert Function“. In this drop down list locate and select “Get Files” then select the AD server you are running the script on and set it to Alarm and email you upon change.

That’s It. It will check your accounts and if a change takes place it then alerts you that a change has happened to which you can investigate. This works great if you need to keep people out of these privileged accounts groups.

AD Admin Audit Kaseya Script Zip

Enjoy

Cubert