Support Forum

This is your problem: Unable to load the service index for source https://chocolatey.rmmmax.com/. Reason: Unknown? You can not use (chocolatey.rmmmax.com) as a source? This system is chocolatey a proxy we setup to demonstrate how to use a proxy to prevent the 409 Errors received when using public re...

No not currently, I have discussed the possibility of creating agent policies that would define what agents should receive what protectors but we had pushback that any type of failure in the process could BRICK the PC and with many MSP managers not knowing BitLocker thoroughly, a misconfiguration co...

Just to be clear, The function worked as expected but the acknowledgement pop up has wrong text displayed? This is not a uncommon mistake. I often copy and paste a code snippet for things like this. It's the same command set with just a different option being requested, I must of missed the response...

APM is pretty cool if you are into package managers. YUM and APt-Get are the pallbearers of package managers. Homebrew came up through the ranks to be the Mac package manger, and Chocolatey.org team worked with Microsoft to create a NuGet based package manager for Microsoft Windows. I asked GPT to d...

We have identified a possible issue that could cause what your seeing. We resolved the conflict and released build 1.0.28 as a result.

You can find it here at Get 1.0.28

Ok there's the problem, first thing is do a restart of the dbagent on automate host. The dbagent service is responsible for creating that table. Once confirmed, relaunch the control center and reopen plug-in. If it still fails report back. As for APM, didn't mean to bait and switch you. LUM is a nic...

Today we released build 1.0.5.18 which added the ability to change agent scanning EDF from any of the agent views.

When this window loads, it calls 1 function that makes a SQL query and fills the table with data. If something is wrong with the data, something missing or SQL failing all together, would cause the error you see. here is that SQL Query, SELECT a.computerid, a.computer_name, a.clientid, a.updates, a....

Yea, that ones has gotten me a few times..

When Screenconnect gets upgrades to a new version, these extensions may not qualify for that version and will disable themselves. Update the extension in SC and reenable it resolves the issues.


Well Awesome!

Ok, I checked your account, Your hostname is setup correctly, I found your license in the system and applied it to your host. You should now see it enabled.

Let me know if not.