LabTech vs Kaseya

[AN-Tech]

I've seen a few posts recently regarding LabTech. If anyone has experiance with both LabTech and Kaseya I'd love to hear your thoughts on the two. We are currently using Kaseya through a hosted provider so we are not tied into any MSP solution yet. I'd also like to know how well they can be tied toCommitCRM. Whatever solution we end up using long term both on the PSA and MSP side have to talk well to each other.


Thanks in advance.

[ajgyomber]

Re: LabTech vs Kaseya

I just attended the webinar for Labtech and it seems just a capable as Kaseya especially when it comes to automation and scripting. If CommitCRM and LabTech have two-way synchronization I think it may be the direction we want to go. It's not that pretty but looks extremely functional.

[g2computersolutions]

Re: LabTech vs Kaseya

The integration between CommitCRM and Labtech is finishing it's beta process as I type. I will have two-way syncing between the two application.

One of the really nice features is the ability to have all the 'assets' in Labtech go directly into the 'assets' inCommitCRM. Believe me, when I had this work, it was a WOW moment as I had never really used the asset function because it was a pain to try filling the information in. This solves that problem.

Another really cool feature is how the monitors can be setup to do any of about 10 different thing, including opening a ticket in CommitCRM (with priorty support). You can send and email alert, print a page, simply raise an alert in Labtech, run a script, and on and on and on.....

I'd encourage any of you to download the trial, then email them and let them know you want to use it withCommitCRM.

[lpopejoy]

Re: LabTech vs Kaseya

ascendnet,

Just curious if you've started using Labtech yet. I'm on hosted Kaseya as well. I've been attending their demos. Looks like promising stuff. A lot of stuff Kaseya can only dream of!

Luke

[AN-Tech]

Re: LabTech vs Kaseya

Luke,

Funny you should mention that I've been playing with it for the last week. If things go like I think they will I expect to be moving from Kaseya shortly. I haven't tested the LabTech to CommitCRM integration yet but I believe this was just released by LabTech on friday.

Ed

[ajgyomber]

Re: LabTech vs Kaseya

Luke,

I've been deep into LabTech this last week and I pretty much have the CommitCRM integration working which is way cool. It appears to be very powerful and I have yet to scratch the surface. It is not the most user-friendly system but I don't think any of them really are. They all have a learning curve. The automation and scripting functionality of LabTech looks fantastic.

--AJ

[rkniffin]

Re: LabTech vs Kaseya

I've been using Kaseya for 2+ years. I'm looking at Labtech. I saw it mentioned here. Looks interesting.

Just started looking at it yesterday. Anyone actually make the switch from Kaseya to Labtech? Can you give any feedback on transitioning from one to the other?

Thanks,

Rich

[lpopejoy]

Re: LabTech vs Kaseya

I just downloaded the demo after attending two webcasts myself. Looks like some nice stuff. I mean, it does stuff that kaseya can only dream of. I know K has a new release coming in June/July, but from what I've heard it isn't going to bring anything that Labtech isn't doing already. I'm building up a Server 2003 VM to play with it in.

I'm on Kaseya right now, but I'm just leasing it. If this works well, it may be worth the switch. I'd love to hear from someone who is actively using it. What are the Con's? What I hate about Sales reps is they always say "We are the industry standard.", etc... What is the TRUTH?

--Luke

[vsouthmayd]

Re: LabTech vs Kaseya

Could anyone using the Commit/Labtech Integration specify the integration hooks between the two systems: ie. Assets, Tickets, etc

Vernon Southmayd
Creative Computing

[ajgyomber]

Re: LabTech vs Kaseya

Vernon,

I almost thought to contact you. I'm still gaining an understanding of the integration but I can tell you that for asset information the following is transferred from LabTech to CommitCRM automatically:

OS Version
Model
Processor
MAC Address
IP Address
Gateway
Manufacturer
Serial Number

It is my understanding that as far as ticketing goes, a monitor can be configured in such a way that it automatically generates a CommitCRM ticket (as well as other things). It will automatically create the ticket and assign the correct asset to the ticket.

It is also my understanding that you can look at your outstanding alerts and simply right-click one and create a ticket as well. This is useful for not so critical alerts but ones that still require some level of work.

One super-cool feature is that you can right-click the LabTech agent icon in the task tray and it opens an email-like window that allows a user to submit a ticket and it will automatically be created in CommitCRM. This particularly was something I have wanted for my clients for awhile now.

Hope this helps.

--AJ

[jtfinley]

Re: LabTech vs Kaseya

Is it agent or probe based monitoring/scripting/checking?

[lpopejoy]

Re: LabTech vs Kaseya

Agent. I believe you can probe the network to find new machines, etc, but all the scripting & monitoring is done from the agent installed on the monitored machine.

[Easy I.T.]

Re: LabTech vs Kaseya

I've installed the Labtech trial - and have the CommitCRM integration setup. I've managed to import Assets and Clients but the ticketing doesnt seemt to be passing from Labtech toCommitCRM. Did you have to do anything special to get this working ? (other then ticking "Auto create new tickets" in the Integration config in Labtech. - I have all options ticked).

[Easy I.T.]

Re: LabTech vs Kaseya

ignore my last - Tickets created within Labtech Control Centre are passing to CommitCRM , just not tickets created when a client enters a ticket from the Client Agent within their system tray

Anyone else that has integration working notice the same? or is it just me?

[ajgyomber]

Re: LabTech vs Kaseya

I have successfully received tickets submitted via the LabTech agent intoCommitCRM. It works so it must be a configuration problem on your end.