Do anybody REALLY use Comodo One RMM in a production environment?

[StrobeTech]

Dear All,

Please see the following information.

And now I had a very bad review with the macOS AV Client... To sum this up: ITarian has potential but I am using features very very carefully since sometimes they fire back and if they do it always hurts very bad.

I'm pleased to say that the reports on MacOS protection is from tests back in 2017. Sine then Comodo have a complete new engine for detection and more which I'm told by the team is much better. Unfortunately we currently do not have any updated test results to show this but we have been informed this is currently being arranged with 2 or 3 different testing companies soon.

However after 2 years of absence I finally start to give the RMM another chance and I currently enrolled around 250 devices for remote Control, maybe patch management and if macOS AV gets better maybe even for that. My primary solution is Intune but Comodo is a good addition offering features that Intune lacks (Remote Control, Patch Management or macOS Antivirus).

We are glad you have come back to the solution and seen how well it has grown.
The product set is always improving and the more people that use the system allows for more great feedback and improvements.

And btw: I am a SCCM/Intune-Consultant working for bigger companies with >10k Clients I am not recommending comodo there out of "Quality reasons" but boys: If you get the surprises out of your applications I would be more than happy to recommend your patch management and remote control.

I'm glad to say that Comodo have been working hard on processes and structure so they can start producing better products that are more stable and have no surprises. Obviously this is not happening over night, but they are listening to us all and working very hard to achieve this for us all.


Keep up the good work all and hopefully this information is helpful for the community.

Regards
Robin

[Rickkee]

I have been testing the RMM product on a limited basis since 09/2015, I was never comfortable using it for clients other than ad-hock, one-off non-MSP clients. I took another look CCEndpoint and was about ready to go production until I saw the Armageddon post about machines going off-line because of a bad release, and then needing to be reformatted after uninstal. Had we been in production with our 350 endpoints, a bug like this would have bankrupted our company. We barley have enough time to take care of our clients maintenance needs in addition to project work. There simply is no time for us to waste until we can see the product go six months without catastrophic failure. Putting it back on the shelf for another six months and will give it another whirl.

[melih]

I have been testing the RMM product on a limited basis since 09/2015, I was never comfortable using it for clients other than ad-hock, one-off non-MSP clients. I took another look CCEndpoint and was about ready to go production until I saw the Armageddon post about machines going off-line because of a bad release, and then needing to be reformatted after uninstal. Had we been in production with our 350 endpoints, a bug like this would have bankrupted our company. We barley have enough time to take care of our clients maintenance needs in addition to project work. There simply is no time for us to waste until we can see the product go six months without catastrophic failure. Putting it back on the shelf for another six months and will give it another whirl.

just to clarify...the issue was NOT with Itarian RMM......the issue was with one of security vendors Comodo's firewall.......

[Rickkee]

Thanks for the update. Portal was out for 31/2 days last quarter, desktop system tray shortcuts changed to ITarian without any notification, lets see if it can go 6 mos without a serious outage or crippling bugs.

[StrobeTech]

I have been testing the RMM product on a limited basis since 09/2015, I was never comfortable using it for clients other than ad-hock, one-off non-MSP clients. I took another look CCEndpoint and was about ready to go production until I saw the Armageddon post about machines going off-line because of a bad release, and then needing to be reformatted after uninstall. Had we been in production with our 350 endpoints, a bug like this would have bankrupted our company. We barley have enough time to take care of our clients maintenance needs in addition to project work. There simply is no time for us to waste until we can see the product go six months without catastrophic failure. Putting it back on the shelf for another six months and will give it another whirl.

We are in a similar position to you on the front of staff and devices.

On the ITARIAN front, we are extremely happy with the solution and helps us daily by allowing remote access, automated patching and application updates and more.

On the Comodo side, we also use the Client Security which is also known as Advanced Endpoint Protection. This unfortunately as you say has had numerous issues of late.

As melih states, this is due to the firewall section of the tool. If you disable this feature the rest of the product is rock solid and works extremely well.

Hope this real-world information helps.

[Weatherlights]

Ok I have another no go I discovered last week: We require our users to approve any remote Control session due to GDPR. Recently I connected to a machine and was suprised that the approval went this fast... after another test I realized that the approval is not working anylonger. I discovered in the Portal that the Settings regarding remote Control were reset to the Default values (even our custom message was reset). I confirmed this on both my tennants… my employees trust our IT Department that we are not spying on them and this really hurts their trust in us and my trust in ITarian.

[Vincent C]

HI Weatherlights ,

Good day!
We've created a support ticket on your behalf.
Please respond to the email so we can assist you further in determining why the values have gone back to default without making any changes on your policy settings

Thank you.