In previous versions I have been able to install SyncThing (downloads page, integrations, SyncThing Windows Setup link) and receive the prompt to “Install for All Users” which is needed for my purpose. This lets me create the service and adds the “SyncThing Service Account” user to give folder permissions for syncs.
For some time the current release from the link I’ve described above does not give me this option, and when the install has completed in Add/Remove Programs I see SyncThing for current user only.
I wanted to find out what is different about the newer releases, am I doing something wrong, or most importantly is there a change to SyncThing I should make myself aware of as I use this pretty heavily for some clients.
I think you need to pass a command line argument to the installer if you want to use more advanced options, such as installing for all users, etc.
This is because we used to have a lot of confused users coming to the forum for help, because they had installed Syncthing for all users, as a service, etc. without understanding the consequences.
For specific instructions, I’d suggest checking the readme on the installer’s GitHub page.
For some time the current release from the link I’ve described above does not give me this option, and when the install has completed in Add/Remove Programs I see SyncThing for current user only.
As tomasz86 said, the documentation tells exactly what you need to do.
If you really want to install the service and are aware of the operational implications of doing so, you can run the installer with the /allusers command line option.
Thanks for the reply bill and tomas. My organization uses SyncThing quite heavily to transfer data from other organizations and have always used all users, the service and the SyncThingServiceAccount.
We found that we couldn’t create the .stfolder when trying to make folder syncs with the current user install and would have the file marker missing error, which led me to use an older installer version that I mentioned and eventually to the forums to learn more.
We are typically running from servers where the current windows user is not always static. In the situation I am describing, would you recommend any changes?
We are typically running from servers where the current windows user is not always static. In the situation I am describing, would you recommend any changes?
Keep in mind that these are open-source tools, so we’re not able to provide recommendations to end-users other than to read through the documentation for both Syncthing Windows Setup and Syncthing and to make the choices appropriate for their own environments and situations.