Hello All,
We try to implement FreeFileSync in our company as a client backup solution. 100+ clients.
Is there any way to disable Automatic Update from command line or registry? It would be usefull if we make a mass deploy and want to install the next version then we can make a test with some client, but not all. We don't want to disable manually the autoupdate in help menu on all client. Is there any way to disable it on another way? Thank You in advance.
Autoupdate disable from commandline
- Posts: 4
- Joined: 13 Mar 2014
-
- Site Admin
- Posts: 7061
- Joined: 9 Dec 2007
Simply deploy the GlobalSettings.xml, too, and be good.
- Posts: 4
- Joined: 13 Mar 2014
Thanks for the answer.
So I have to disable the autoupdate in the Help menu on one client, and copy the Globalsettings.xml file to the other client. Am I right?
So I have to disable the autoupdate in the Help menu on one client, and copy the Globalsettings.xml file to the other client. Am I right?
- Posts: 1
- Joined: 10 Mar 2015
More questions about this topic.
The Globalsettings.xml is saved in the AppData folder of the user, resulting in following entry in the file:
<LastUsedConfig>
<Item>C:\Users\CREATOR\AppData\Roaming\FreeFileSync\LastRun.ffs_gui</Item>
</LastUsedConfig>
<ConfigHistory MaxSize="30">
<Item>C:\Users\CREATOR\AppData\Roaming\FreeFileSync\LastRun.ffs_gui</Item>
</ConfigHistory>
Where CREATOR is the UserID of the user who created the Globalsettings.xml-file.
When deploying this file, without above entry in the file, or with a slightly changed version (replacing the path to the AppData folder by %AppData% or %%AppData%%) to another user (let's say UserID RECEIVER), or when using a Globalsettings.xml file with only the <LastOnlineCheck>-1</LastOnlineCheck>-setting, the <LastOnlineCheck>-1</LastOnlineCheck>-setting is not implemented for the RECEIVER user.
Moreover, the Globalsettingsfile is not changed even when changing the setting via the UI when logged on with RECEIVER. The application does remember the changed setting though.
How should the Globalsettings.xml be adapted, to deploy it to other users, taking into account that it is saved in the profile of the user?
How can FreeFileSync be deployed without the auto-update functionality?
The Globalsettings.xml is saved in the AppData folder of the user, resulting in following entry in the file:
<LastUsedConfig>
<Item>C:\Users\CREATOR\AppData\Roaming\FreeFileSync\LastRun.ffs_gui</Item>
</LastUsedConfig>
<ConfigHistory MaxSize="30">
<Item>C:\Users\CREATOR\AppData\Roaming\FreeFileSync\LastRun.ffs_gui</Item>
</ConfigHistory>
Where CREATOR is the UserID of the user who created the Globalsettings.xml-file.
When deploying this file, without above entry in the file, or with a slightly changed version (replacing the path to the AppData folder by %AppData% or %%AppData%%) to another user (let's say UserID RECEIVER), or when using a Globalsettings.xml file with only the <LastOnlineCheck>-1</LastOnlineCheck>-setting, the <LastOnlineCheck>-1</LastOnlineCheck>-setting is not implemented for the RECEIVER user.
Moreover, the Globalsettingsfile is not changed even when changing the setting via the UI when logged on with RECEIVER. The application does remember the changed setting though.
How should the Globalsettings.xml be adapted, to deploy it to other users, taking into account that it is saved in the profile of the user?
How can FreeFileSync be deployed without the auto-update functionality?
- Posts: 1
- Joined: 7 Dec 2015
Has anyone found a solution to disable automatic updates for all users of a machine using globalsettings.xml (unattended setup)? I tried to copy the file to the user's "%appdata%\FreeFileSync" directory after setup and replaced references to the userprofile. While this works for the user currently installing, it fails for a second user logging on - automatic updates then is back on. Any hints on this?
regards,
Nik
regards,
Nik
