Connecting The Dots Seeing things past it's face value

One Month into Labtech

So I bet many people are looking to find out what it takes to make a switch to something like Labtech.

As you know migrating from one system to another is not usually an easy task, this is why most people the endure pain their in. Executing on a new solution can be scary especially with a paradigm like LabtechSoft. I wanted to point out a few things I have learned in my roll out experience which may help some who are "scared" to move.

1.  I already paid so much into the RMM I am currently using. Yes I personally have spent 7-8 years using the Kaseya Platform, not including money invested in the solution but my time and expertise in the product was a heavy burden I had to tend with in my migration. While I sympathise with you on the cost issue, you have already made your money back if you had a minimum of 3-4 MSP contracts. Opt Out and move on...

2. As given the privilege I have been on the "Beta team" for the upcoming Labtech version. While I cannot say specifically about any features as of yet, I can say that things I have been doing for YEARS now using workarounds in Kaseya and hacking certain tables Labtech has built into the new version... Thus making life in the IT Support world more streamlined. So if any point is to be made in this part of the blog, They are on the same thinking wavelength as I am if not more so! Again further confirmation that I made the correct choice.

3.  Templates and Groups... Can I just say AMAZING, the entire world of templating is actually made CORRECT. Gone are the days that I have to go into my Kaseya system and make sure SLA's and schedules are audited, and cleaned up.

4. Scripting, this was the primary reason I left Kaseya. K2 has made nested IF statements (finally) Labtech has always had this feature. However here is the kicker for me, RAW sql access from a script! another great feature is the SPEED! in K2 I would have to wait for 50 (clicks) in IE for a stupid step to be added, before I could continue. In labtech we don't have a refresh as its a Client based application. Very Nice. Another Key in scripting is the import, this makes all your Kaseya scripts become Labtech Scripts. This was useful for only a hand full of my scripts as I had been hacking the Kaseya system for some time. Not only this but I needed to "Re-Think" my scripts as it was.. so many new powerful features i can cut out the FAT on some of my scripts in Kaseya.

5. Support at Labtech has been AWESOME. They have an online support chat system, I have been able to solve most of my learning curve issues though this, and usually right when I am needing the answer NOW. Unlike a support system that you submit a ticket and wait 2 days (if lucky Kaseya). Perhaps because Labtech uses ConnectWise. is the reason for great support.

Some draw backs right now are really only 2 things:
1. Dot net dependency for the agent installs, I have only had 2 instances for this where the client machine did not have DOT.NET 2.5 installed on the machine and the Agent would not install. Most of my customers already had DOT.NET 2.5 installed, and I am not a believer in Patching every day.

2. While I only have a hand full of Mac users and a few linux the agents from labtech are not that streamlined as of yet.
For MAC you need to install MONO framework before you install the agent, Still not working for me though... Perhaps because I am on a beta still.

OH one other thing I should mention.
ConnectWise integration is a Dream come true! I can have my customers use the built in Labtech agent ticket system and everything syncs with connectwise. One major reason for this is the Screen Shot button right on the ticket entry form, customers now have an instant way to capture an error. I am currently trying to debate the need for customer portal stuff right now. Its another paradigm I am working though.