Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Request created on
Posted on
Eblanchard wrote:
So I got the password issue fixed and the host update correct ip. Thanks. However open dns referred me to you all cause your product runs better in the background and prevents users from noticing and removing it. How do I lock it down so it cannot be killed or uninstalled?
Posted on
Marc wrote:
Only users with administrative privileges can kill or uninstall the background system service. If you have a setup with different users for people who are not allowed to do that kind of stuff, you are already fine.
The updater has 3 processes. Only the systray process which shows the balloon messages can be run by non-admin users. The settings dialog can be run by admins and the system service is run by the SYSTEM user.
Just disable the autostart of the systray process in the settings dialog and they will never notice it is running as long as they don't have admin privileges.
Posted on
Eblanchard wrote:
Unfortunately, because of proprietary software from our other vendors, all users have admin privileges. Is there a way you can add a lock pass-code to it to kill or disable it in future versions? This way, even if an admin account is signed on, you still have to verify you have authority to remove or kill the app.
Posted on
Marc wrote:
Sorry, that's not possible, because any admin user can just open the task manager and kill the processes.