Hello @azon2111 ,
RMM has been incorporated in ITSM. The goal is to be able to manage everything (security, RMM and patches) from one dashboard - ITSM dashboard. In the near future all the features offered by RMM Administration Console will be available in the cloud dashboard.
okay so I get cocs installation failed with error code 1603 for x86 or x64 on Win 10, any good admin manual/post you can point to get some help with this issue?
and what is the plan for rollout methods to migrate to ITSM from RMM agent without touching each PC again or using email links where users don’t have admin rights for deployment?
Hello @azon2111
Regarding the first issue, we will continue via email as my colleague Nick stated in this forum post: ITarian Forum - ITarian Forum
In regards to the second questions, if you would like to enroll the devices in ITSM using the RMM you can use a procedure such as the from the attached image.
In order to do so, you will need to:
Please note that the Default MSI will enroll the devices under the account you used to login (the main admin usually), but this can be changed from the ITSM Console
We are also going to provide an “Upgrade” option where you can trigger auto synchronization process of RMM devices to ITSM.
The upgrade process will perform the following processes:
Customer accounts will be synchronized between ITSM and RMM.
The RMM extension will be enabled inside ITSM. The RMM portal will be removed from the Comodo ONE - Licensed Application view.
Adding new devices will be disabled in the RMM Technician Console. All new endpoints should be added via the ITSM interface to keep your inventory synchronized.
Synchronization of endpoints will be completed by installing the ITSM client software on all missing endpoints in your current RMM deployment. For offline devices, Comodo ONE will continuously check for one week and install once the devices are available. You can track installation status from the Comodo ONE dashboard.
The upgrade will be complete once all devices are synchronized , or the one week grace period finishes.
It is planned to be enable on next maintenance release 16th of May.
Ilker
Thanks for all the updates here. I will try the default installer msi but from what I understand that the 32-bit and 64-bit versions are separate installs (OS versions required for each x86 or x64 but for deployment purposes a combined one should be offered so that retrieval of OS architecture is not a manual process thus the need for deployment or redeployment is not cumbersome as most of us have a mix of 32-bit and 64-bit Windows clients). Personally making the installer bigger is worth the headache not to worry about discovery for 32-bit or 64-bit windows prior to deployment.
All of this imho of course.
Thanks for the great work here in the forums, makes all the difference in whether we use it or lose it with regards Comodo One.
Now if we can just get the billing portion of the ticket system up to speed with the rest of the modules in terms of maturity we could be rockin’ this exclusively.
Hello @azon2111
Thank you for you feedback.
I will forward this as a feature request to have a combined installed for both the 32 and 64 bit OS versions.
We will advise further when we have more information on the case.
we are always here to help. We are here to develop any features you may require too.
Our job is to provide you the platform to run your business for free. And this platform will be to your 100% satisfaction. Any areas of improvements will be developed immediately because less than 100% satisfaction is not acceptable for us. We will always strive to give you 100%.