(16-10-2016 20:59)roadster Wrote: [ -> ]There is another way by putting a script ( .bat file usually) in the following folder
C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup
It might be necessary to run gpedit.msc to enable startup scripts in group policy but usually that's not necessary.
This is doing something very different. In windows a "Startup Script" is run in the machine context, i.e. as system. Because MinimServer stores its working files and configuration in the profile of the "user" who is running it, the settings would be saved in the system profile.
System is the most privileged "account" on a windows system, it has more rights than an administrator. So, you really don't want to run anything as system unless it's absolutely essential to do that. Furthermore startup scripts aren't supposed to be for long running processes.
If you want MinimServer to always run on a windows system, you have two reasonably sensible options.
1: The fully supported method: Run MinimServer with your ordinary user credentials, and make sure it starts by copying the shorctut into your personal Startup folder. (Calling this the Startup folder, is somewhat confusing, but that's what Microsoft chose.) If the folder is empty, then it may not appear in your start menu (e.g. on windows 10), but you can find it by typing 'shell:startup' (without the quotes) into the run command.
This assumes that you are always logged on with the same account when your computer is running, which is a very common scenario.
MinimServer is running with the same rights as you, which is more than it needs, but far less than system has.
2: Install MinimServer as a windows service with a restricted virtual service account. I've described a way of doing this here:
http://forum1613.minimserver.com/showthr...3#pid21793 .
MinimServer is then running with no more rights than it needs, it can read the programs it needs, and your music library (because you've given it permissions to do that), and it can write to its own profile. The downside is that this is much more complicated, and you need to understand what you are doing. It also isn't a supported configuration, although it's essentially identical to the configuration you'd use on a linux server.
If you have windows system administration experience, then you'll be able to review method 2, and implement it, otherwise stick to method 1.