gasilpodcast.blogg.se - Continuum logmein pro no longer works

Continuum logmein pro no longer works install#
Continuum logmein pro no longer works update#
Continuum logmein pro no longer works Patch#
Continuum logmein pro no longer works full#

I know they aren't really supposed to be pushed with Patch Manager. We would love to get feature updates and cumulative updates fixed. There should be a simplified patch data view that allows us to quickly confirm that our various clients are getting patched as they should be. A lot of times, it seems like all the information is kind of thrown all over the place, and you can't really see it all at the same time.

Continuum logmein pro no longer works update#

In Patch Manager, there should be more reportability so that it is easier to see the updates that I have applied to a machine and when the next update will happen. If we're reaching out to their support team and submitting a ticket, it is because we need it handled quickly." A lot of times, the issue is critical for us. It is a little frustrating when we have to wait for a couple of days. "The wait time for a support ticket to be addressed needs to be reduced.Having these in Patch Manager itself would be great." We've got recommendations from ConnectWise to use the scripted feature update installs, scripted KB updates, etc.

"We would love to get feature updates and cumulative updates fixed.

There should be a simplified patch data view that allows us to quickly confirm that our various clients are getting patched as they should be."

"In Patch Manager, there should be more reportability so that it is easier to see the updates that I have applied to a machine and when the next update will happen.

We use a pretty good portion of information from Automate."

"We use monitors to keep track of our machines.

It is one of the most useful features for us for controlling patches and other things for different clients." Patch Manager is something that we use a lot, and we would love to have it continually improved.

"Scripting and patch management are really important for us.

Which deployment model are you using for this solution? It's a double-edged sword, however, with the customization you can do. In my book, it's the top two compared to the other RMMs out there. I'd rate the solution at a solid seven out of ten. It's a big investment to not know what's about to happen. It's probably going to end up being an amazing product, however, we don't know where it's at currently - especially for an on-prem customer. The question is where does this new merged product sit? If I have an MSP that's asking which arm and platform to go with, it might be an amazing product. You could do anything you want with it, however, it also requires skill and labor. There's no custom stuff, which is great due to the fact that it works.ĬonnectWise is the complete opposite of that. Is it going to be more Continuum? Is it going to be more ConnectWise?Ĭontinuum is a great product for MSPs that are smaller MSPs that don't have the time to do anything. The key thing, and obviously for even us and all the other MSPs, is we don't know what it's going to end up looking like. We don't know to what degree and we don't know what that product afterward is going to look like. ConnectWise bought Continuum, which is a totally different RMM and we know that the RMMs are being merged Automate is being absorbed by Continuum. I would advise potential new users to hold off for now, as we don't know what's going to happen with the purchase of Continuum. We have supported customers with all versions for multiple years.

Continuum logmein pro no longer works full#

Removing that requirement and going full web, would be a good play.

Continuum logmein pro no longer works install#

An engineer wanting to make changes and next-level automation stuff has to install a client locally right now. If it was a totally web-based solution for instance. The solution could be better with not having to install a client locally, to be able to do the advanced stuff. Maybe support for Python would be good, although that's not really even needed. The ability to control where the temporary folder is for automation and not having it in system 32 would be very useful. There are aspects of monitoring that are problematic.Īdding stuff that automates, and offering a better best practice out-of-the-box would be better. Obviously, performance across the board for everybody needs to be better. Scheduling of automation could be improved and made more simple. ConnectWise has to ingest all of the event IDs and that equals large database growth and therefore nobody monitors those event IDs. For instance Kayesa - the way they're doing event ID monitoring is local. They're behind the game on the other RMMs, and we support multiple RMMs. The solution needs to improve Event ID monitoring big time.