Try Office365 For ConnectWise Automate For 1 Month Free

Office365 for ConnectWise Automate

The team over at Plugins4Automate is offering a great value to try out their new Office365 for ConnectWise Automate plugin. Get the first month free and have a go at this great plugin. Here is just a few of the neat things you can mange.

Azure Active Directory

Need to add a new user, re-enable a user after lockout or just manage a password change, you can perform quick tasks in Office365 directly from your Labtech consoles.

MSOL Exchange

Need to add a forwarding address or maybe convert a users mailbox to shared, set a users Out Of Office replies or view their current mailbox stats, with our Exchange integration you have access to Exchange online with just a few clicks inside of LabTech

Sharepoint Cloud

Create new sites or manage users and groups for existing sites quickly and easily inside of LabTech.

 

For more information about this plugin and how to get started visit:

Get Office 365 For Free

Monitoring Your Clients VMWare Infrastructures.

Who manages your VMWare ESX Hardware Health?

If you are using ConnectWise Automate or LabTech RMM tool then this is a must have plugin for your environment. Plugins4Automate has a great plugin for managing ESXi Health monitoring in ConnectWise Automate and LabTech.

Visit them at www.plugins4automate.com

VMWare ESXi 6.5 CIM Data Disabled by Default

I was recently tasked with an issue where our CIM probe was failing during CIM requests to new VMWare ESXi 6.5 servers we deployed. We were getting connection rejected failures from our probes which resulted in no valuable data being returned. We started following the breadcrumbs which lead us back to the ESXi host. We opened the UI and checked the health monitor in the UI and found it was showing “No sensor data available”. The first thing we checked was to see if the sfcbd-watchdog was running, and it was not. By default, this service was turned off, or so we thought! We turned on the service and the UI reported that the service was now running.

 

Even after several refreshes of the UI it stilled showed running but we still received a connection rejected. We rebooted the ESXi host and after it came back we tested the connections again and are still failing. We reopen the web UI and looked at the services again and there was our watchdog service stopped. We had set the service to autostart with host so this lead us to believe it must be dying at some point.

 

The best way to see what a service doesn’t like is to login to ESXi host using SSH and manually start the process and see what it’s output is. A quick /etc/init.d/sfcbd-watchdog start showed us that the service was “Administratively disabled”.

After digging around Google for some reference to this new data we came across a blurb about setting an option to allow CIM manager to run.

The command esxcli system wbem set –enable true followed by /etc/init.d/sfcbd-watchdog start allowed the sfcb-HTTPS-Daem process to start. This process is the TCP Listener that takes CIM requests from probes like ours and returns the health of the hardware.

You should get an output like the following

/etc/init.d/sfcbd-watchdog start
sfcbd-init: Getting Exclusive access, please wait…
sfcbd-init: Exclusive access granted.
sfcbd-init: Request to start sfcbd-watchdog, pid 69438
sfcbd-config[69448]: No third party cim providers installed
sfcbd-init: snmp has not been enabled.
sfcbd-init: starting sfcbd
sfcbd-init: Waiting for sfcb to start up.
sfcbd-init: Program started normally.

 

 

Invoking lsof -nPV | awk {‘count[$2]++}END{for(i in count)print count[i], i’} | sort -n in the SSH console will produce a list of running processes minus all the junk. You can use this list of processes to determine what is running on the ESXi Host.

 

We also used esxcli network ip connection list to get a list of ports the ESXi host was listening on to help determine if the port 5989 was active.

 

 

If you are deploying VMWare ESXi 6.5 in your environments and need CIM health data, remember to enable it and do not just assume that the WebUI is telling you it is active.

 

Check out our ESXi Health Monitor for LabTech (Automate) here

How-to keep a user synced with DirSync, to be excluded from DirSync while retaining the AD user

Converting DirSync User to a Cloud user in 365

I’m not sure if anyone has run into this problem before, so I figured I would share a quick fix that I found to take care of this problem. The easiest process that I have found to accomplish this without having the user be deleted each time dirsync runs is the following:

  • On a domain controller in the environment, move the user out of the DirSync scope. The Domain has a Synced and UnSynced OU, moving the user to the UnSynced OU accomplishes this.
  • Force replication on the DC a few times (unless there is only one DC in the environment)
  • Login to Office 365 and delete the user from Office 365- this will put them in a soft-deleted state.
  • From a DC in the users environment, run all of the DirSync/Azure AD Sync profiles to allow the changes to sync with 365
  • From Office 365 web portal, find the users mailbox in the Deleted Users section, select the appropriate user and re-attach the mailbox. You will need to specify a new password for the user to use when accessing Office 365 since they are no longer synced with AD.
  • Open up a PS-session to Office 365, Import the appropriate modules including MSOL modules
  • Run the following command substituting the appropriate value. The ImmutableID is what will prevent DirSync from deleting the user’s mailbox each time it is run. ImmutableID links the 365 account to the AD account and is what DirSync looks at to bind the two accounts (generally speaking).

    Set-MSOLUser -UserPrincipalName %user@domain.com% -ImmutableID $null

  • From a DC in the user’s environment, run all of the DirSync/Azure AD Sync profiles to allow the changes to sync with 365
  • Validate that you can login via Office 365 with new password and that the account shows being in the cloud.

 

Good Luck!

Office365 for LabTech Pre-Release Feature Overview

0365Plugins4LabTech is about to release to the community it’s next generation of Office365 Management for LabTech

 

Plugins4LabTech has completely rewritten this plugin from the ground up. No longer are your required to go through a set of manual installs and system prep to use the plugin. No longer is your workstation tied to processing Office365 commands. No longer do you have to deploy MSOL scanners at every location that uses Office365.  No longer do you have to have a client systems collecting Office365 data. So say goodbye to all that luggage and say hello to the new and improved Office365 for Labtech.

Let’s go over some of the new innovations we have coming with this new plugin. Our biggest change comes in the form of a single pane of glass. We have moved all views into one master manager so you can flip from client to client without ever leaving the windows console you are in. This centralization does not stop at the user’s view but continues to the data collection and control systems. You now assign a single system anywhere across your MSP to manage Office365 for all your techs and clients. You can control what is collected and at anytime you can start a manual collection of data through the plugins control center.

 

The Control Center

Configure

 

The Control Center allows you to deploy all the MSOL modules you need to manage Office365 to your master scanner. If you find that you would like to use the Console Shell feature on your local workstation as well then you can select from the list of systems, your workstation PC and “Deploy MSOL Modules” to your workstation quickly. You can execute manual scans of all clients MSOL data, MSOL Statuses and more from this convenient window.  Verify when the last scans took place to know if your data is up to date and how many clients were scanned. We also monitor and display if your scanner is online and available and if we see it up to date with it’s MSOL modules. All this is done automatically when you install and add your clients. LabTech will execute scanner twice every 24 hours to keep all data up to date with the clients real world data so as to capture changes made from AAD Connect if active for clients.

 

Your Single Pane Of Glass

Main-Azure

 

The Office365 for LabTech console is pretty strait forward, At the top you have your active Office365 client list to select any client configured for Office365. From this view you get to manage the clients Azure, Exchange, Groups, Sharepoint sites and licensing usage along with the most recent MSOL hosting statuses for each client. Once a client is selected then their list of users becomes available for selection. By selecting a user from the list each tab will reflect that users information where relevant allowing you to manage many aspects of the user’s experience. In Azure you can manage new users, user passwords, unblocking a locked out user, setting strong password requirements and enabling and disabling many other features in Azure.

 

Azure Groups

Main-AzureGroups

Quickly manage new groups and removing old groups and Add and remove users from groups without ever leaving LabTech.

 

Exchange Management

Main-Exchange

 

Easily Convert user mailboxes to shared mailboxes saving your client license usage when archiving expired employees. Setting mailbox permissions quickly like Grant Send on behalf of, read only or full access to mailboxes for any user is a snap with Office365 for LabTech. Set forwarding addresses and manage a users Out Of Office messages and activity all right inside this single pane of glass.

 

Manage Sharepoint

Main-Sharepoint

 

Add and remove sites  from Sharepoint. Manage Sharepoint groups and members site access.

 

MSOL License Management

Main-Licensing

Get access to all the license information for your clients, see what service plans exist for each license the client holds and the usage of each license. Add and remove licenses for users quickly without ever leaving your LabTech console.

 

MSOL Status

Main-MSOLStatus

 

MSOL statuses keep you informed as to the state of the hosted services Microsoft is providing to your clients. Each client can have different status messages based on location of hosted services and the systems and services affected. These status messages are extensive and provide detailed information from Microsoft on the issues and resolutions completed.

 

The All Powerful MSOL Shell

MSOLShell

Our Holy Grail, The MSOL Powershell console, Launched from Office365 For Labtech’s single pane of glass, has also been rewritten from the ground up to include module loading management, new commandlets and a clean look. If you are one for shells then this makes it easy to launch a Powershell console for access to any clients data directly from your workstations (no login information required). Run commands and scripts directly from the shell accessing all the MSOL services the client is entitled to as the tenant admin.

 

Our plugin has a little something for everyone, Stats and metrics for the senior staff, High level control over clients settings and global data for you engineers and access to common tech functions like password updates and removing lockouts making Office365 for LabTech a must have tool in your Labtech Tool Belts. We are not stopping there, Plugins4Labtech development team is continuously adding new features and functions to this plugin allowing the plugin to grow as MSOL services change and develop.

 

Office365 for Labtech will be released to the general community on Monday, June 20th for the opening of Automation Nation. If you are going to be at Automation Nation come seek me out if you would like more information on this release.

Visit Plugins4LabTech.com for more information and downloads. Would you like to see a Demo of Office365 being used in LabTech?

apple-icon-114x114

 

Network drives fail to connect error 1208 and System error 2148073478

We had a problem where a Windows 2012 R2 Domain Controller would not browse the shares of another Windows 2012 R2 WorkGroup Server. We kept getting error 1208 and then we tried to force a mapping to share and received System error 2148073478

This problem is caused by the “Secure Negotiate” feature that was added to SMB 3.0 for Windows Server 2012 and Windows 8. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. Some third-party file servers and other Windows Systems not on a domain may not not return a signed error response. Therefore, the connection fails.

We had this issue with a Windows 2012 R2 Domain Controller trying to connect to a Windows 2012 workgroup server share.

The Domain Controller had the local network set to Public and not Private, We had to change this by running a few PoSh commands.

 

Get-NetConnectionProfile

This gives us the index numbers for each interface then we find the interface marked public and change it to Private by running the PoSh command

Set-NetConnectionProfile -InterfaceIndex 10 -NetworkCategory Private

Change the InterfaceIndex number to the number of your interface.

 

Next we need to low the security level for SMB so that we can allow the connection to complete.

To do this we Edit the registry and change the value of  RequireSecureNegotiate to zero

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force

Once that has completed you will now be able to access your network shares on other NAS servers or Windows systems.

 

Hope this helps someone out there, Enjoy!

Cubert

LabTech Plugin : Expiry the AD Password Expiration Notifier

logo

Are Your Users Expired?

 

Yes, It is Monday morning,  you walk into your office and the Help Desk lines are already lit up. Clients are calling with emergency lockouts and emails not coming in on their phones and computers. You know their passwords are expired and they didn’t see the desktop popup from Microsoft warning them it was coming. You now have to get busy resetting passwords to get these people back to work as fast as possible. Password expiration issues can account for up to 10% of the weekly tickets a MSP’s help desk has to manage and although it only takes a minute or two to fix that time adds up.  Here is where we come in.

 

Expiry AD is a plugin for LabTech that checks the Active Directory of any client to see what Domain User passwords maybe ready to expire, creates a list of the users expected expiration times and emails them a custom email notice to please update password when they come close to the limit you set for them. You can personalize each email to the user that is receiving it or have a generic global email that goes to everyone.

 

Client-Config1

 

There is some basic information needed to complete the password expiration checks,

You will need to supply the AD server you want to scan, this should be an up to date AD server with Powershell 2 or higher installed. You will need to know how many days ahead of the expiration you want to send a notification and the LDAP root you want to look for users in.

Once this information is entered into the system and the apply button pressed the plugin will request if you would like to run a scan now. Scans will run daily on systems that are set to notify users automatically, just turn on the Notify Users switch at the top of the management window.

We supply a HTML capable Email Body template maker that will allow you to create unique emails that are personable to each user. Once you are finished you can view what your emails will look like by selecting the Email Viewer control. We have provided two wild cards for email templates @MYNAME@ and @DAYSLEFT@ which will allow you to personalize each email sent with the users full name and the current days left before expiration.

Client-Config2

 

By selecting the [Results] tab yo can see the result of the last scan and who is in line to get emails. All user will be listed here and will show how many days left until they expire. Users marked in RED have expired or are with in the windows set by you for expiration emails.

 

Client-results

 

 

Not all users of Active directory will show up in list or scans. We have some basic filters in place for the scanner that prevents non actionable users from showing up in scans.

For instance.

  1. Users who are set to never expire will be excluded
  2. Users who are disabled will be excluded
  3. User who are set to no be able to change password are excluded
  4. User who have no official Email address listed in directory are excluded

You will only get a return of people you can actually affect and emails will only be sent to users who can receive them and react. This limits the efforts needed by the Labtech system and provides for maximum coverage for the domain users.

 

Version 1.0.1.21

download

 

 

 

 

Enjoy

Cubert

LabTech Scripts – Cryptolocker probe script finds infections fast

 

 

cryptolocker-680x400

Catch Cryptolocker in the act

We have created a script for LabTech that you can schedule against any system to scan for possible Cryptolocker Decrypt Files, a sure sign that you been infected.

 

The script can be scheduled against all agents and if an agent is a Mac or Linux it will skip it, The probe will scan each drive letter found and then review that scan to see if it has found any files. Once it finds a file it will email an address but you can easily have it create a ticket or even set an alarm state.

 

When executing probe against a system you can monitor the Scripts Tab for the progress of the probe.

Capture

As the image above shows, a scan takes just a minute to complete. The C drive scan started at 1:08:34 and ended at 1:09:51, the scan took 1 minute and 17 seconds to scan 80GB hard drive.

 

Version 1.0.1 download

 

 

 

download

 

 

 

 

 

Enjoy  Cubert

How-to Windows 7 OEM Activation

I recently came across a system that had been rebuilt and the activation was not re-applied so after 90/120 days the system started reporting it was not genuine and realized a few of you may not know how to re-apply OEM activation.

 

In windows Vista, 7, server 2008, 2008r2, and server 2012 OEM activation is accomplished by the combination of 3 elements.

  1. The bios of the system must contain what is called a “SLIC” string, all systems made by a major OEM such as Dell, HP will include this. Home built systems will not (unless you modify the bios yourself)
  2. A certificate file that matches up against the “SLIC” string that is stored in the BIOS. These certificate files are unique to each OEM so Dell has their own, HP has their own, etc. and are not interchangeable.
  3. A Windows product key that tells the system to use OEM activation instead of the traditional Microsoft activation process. These keys are not specific to a particular OEM and are interchangeable.

If all 3 are present the system is instantly activated, does not communicate with MS to determine if activation is valid or to activate against a MS server. The activation is already trusted.

windows-7-activation

When you rebuild a PC component 1 is still present but #2 and # 3 are missing.

Attached in the SLIC.zip file you will find the certificate files used by Major OEM’s such as Dell, HP, Lenovo, as well as product keys that can be used for Windows 7 Professional, and Ultimate.

 SLIC Zip File Download

To use this, for example if you had a Dell.

Open an elevated command prompt, extract the Dell certificate to C:\temp

The certificate is called Dell-Dell-2.0.xrm-ms

So issue the command slmgr –ilc c:\temp\dell-dell-2.0.xrm-ms

Then issue the command slmgr –ipk 2QTV2-3CMPP-FQBYK-XXXXX-XXXXX (For windows 7 Pro)

Wait about 5 seconds and if you look that system is now genuine and activated.

 

PowerShell – Powershell plugin for LabTech

ps

  LabTech PowerShell Plugin

 

 

 

Squidworks has now released their PowerShell plugin for LabTech that will allow you to run basic Powershell commands on the remote computers under management. You no longer need to remote in to a server or workstation to run basic Powershell commands against that system. In this version we added a process to check to see if the computer is an Exchange server 2007,2010 or 2013 and if the system is a supported Exchange server then we will load up the exchange modules when we process your Powershell command so that you can take advantage of all the Powershell commands that the Exchange server provides. If we find the system is not an Exchange server we do not load any extra modules and run in a standard PowerShell.

mainview-1.0.4

 

 

 

*New – PowerShell Command Manager

Save and execute complex PowerShell commands with just a mouse click. There is no longer a need to try and remember hundreds of PowerShell commands you have crafted, with Squidworks PowerShell Command Manager you are able to create and save these little jewels so your entire team can use them on any PC console inside of LabTech. (Available on the [View] menu of your LT console.)

 

add-cmds-1.0.4

 

 

 

Version 1.0.4 available for download

download

 

 

 

 

 

Version 1.0.2 fixes
————————————————–

Fixed bug where pipe key would cause errors (|)
Added Multiline command box

 

Version 1.0.3 fixes
————————————————–
Added the ability to determine if we are an exchange server and what version, We will load Exchange Powershell modules if Exchange is found for that version.
Setup terminal to grow and shrink with size of window.
Changed colors to better reflect PS terminal
Changed formatting so it mirrors Powershell standard output.

 

Version 1.0.4
—————————————————

Added PowerShell Command Manager available via the [View] menu in your LT console
Added ability to launch saved powershell commands on any PC console