I am unable to apply policies to endpoints.
I created a policy containing some monitoring information and I tried to apply it to two different endpoints. One running Windows XP, the other running Windows 7 Pro. The RMM tries to apply the policy, but then says “Apply Failed”. I downloaded the RMM console and agents three days ago, so I assume it’s the latest versions.
I’m having trouble opening the RMM module. When I try to open it on the web console via Comodo1, I enter my user info and it just spins and doesn’t log me in. When I try to login via the desktop app I get an error stating: Network error on activating license, please check your network connection and try again. There a link to Renew License or boxes to enter new license information. I turned off my firewall and antivirus but it still doesn’t work. Any ideas?
Yes. I works after the update. Thank you.
But I’m having another issue with policies. I can’t make any changes to a policy. If I want to remove a certain test from a policy, I can’t do that. I have to create a brand new policy omitting that test.
RMM console not working.
I’m running the 64 bit version on Windows 8.1 and this morning the RMM Console responded to my login with the attached.
I had no problems logging into the web console using the provisioned credentials for my account.
The previous day I added several systems manually to the RMM system and several of them stopped responding on the initial connection to the system with an indication of a licensing error. However, at the time. the systems showed in both the web and local consoles.
This error is shown when there is a connection problem between server and admin console. It is most probably a temporary issue. Could you please check your connection again? If it doesn’t work, I would request the logs from your computer.
The RMM console is not updating my endpoints’ external IP addresses. They list the IP address that they had when the agent was installed but the external IP address changed recently and it was not updated to reflect that.
It should be working without providing Username and pass again. Looks like a glitch, please try clicking again the module name from the module view if you see this problem again. It should work on second try.
We are also checking it to see why it sometimes gives this error.