I’m trying to install Syncthing v2.0.0.0 on windows as a service using the /ALLUSERS switch. This creates a user with a 20 character username(SyncthingServiceAcct). I’m trying to sync files to a TrueNAS system but TrueNAS has a username limit of 16 Characters. Is there any way to change this username so it can be shorter and more secure not being the same for every install?
The author of Syncthing Windows Setup recommends the default “current user” mode for most installations. Is there a specific reason why you need Syncthing to start as a Windows service? (It involves all kinds of permissions hoops to jump thru.)
Syncthing doesn’t do or require user authentication when syncing, so could you provide more details about your setup?
Yes, included in the documentation: https://github.com/Bill-Stewart/SyncthingWindowsSetup/
Fantastic. After using the swtich below I was able to change the username and then the password to something with access on TrueNAS. syncthing-windows-setup.exe /ALLUSERS /serviceaccountusername=username
Unfortunately until I did this I couldn’t write to the TrueNAS share as all file access is controlled by the service and uses the service credentials. If I used the user only install it uses the local user credentials so everything worked.
The reason for wanting to use the service was so Syncthing would run even without the system being logged in. For instance after a windows update.
Thanks for the fast response.
Ken
That’s very odd. Not sure I completely understand the setup. Normally Syncthing would be installed on the TrueNAS and is completely isolated from the permissions on the Windows side. There shouldn’t be any requirements regarding having shared user credentials.
There’s an option in Windows Task Scheduler to start a program at boot time and without the user being logged in.
It’s generally less complicated to manage compared to a Windows service which has additional restrictions and is generally more secure.