Bugzilla – Bug 675
Installation of SlimServer resets logon account
Last modified: 2009-09-08 09:13:47 UTC
As I use Windows (XP) I have to run Slimserver under an account that is allowed to access my network (administrator and possibly power user group too). I usually upgrade in the following manner: Close Slimserver, stop Slim service, install update over existing installation. Every time Slimserver changes the account it uses to a local account so I loose all the music on my networked drives and have to change it logon under an administrator account instead. Additional request: Can the initiall installation of SlimServer possibly create an account that is a member of a group that is allowed to access networked drives? It's problem that it frequently reported in the mailing list.
The installer should check to see if the service is already installed as the non system user and preseve the existing credentials.
we also don't save the auto restart flag for the slimserver. I suggest that we don't reinstall the service if it's already installed.
Alas, this isn't going to make it for 6.2.1.
Dean?
Simon: is this still an issue for you? After discussion, we're not clear on why you are using a non-system account.
Dean, I run SlimServer under my own administrator account as I can find no other account that has suffient permissions to enable SlimServer to access my my music drive (a Maxtor OneTouch attached to a networked XP Home laptop) I've started to use the latest 6.5s and the problem has resurfaced. I installed last night's exe over my existing (one week old) 6.5 installation the account under which SlimServer runs was changed back to a local account without sufficient permission to access drives across the network.
(In reply to comment #2) > we also don't save the auto restart flag for the slimserver. I suggest that we > don't reinstall the service if it's already installed. That would be the simplest, possibly the only, solution. For anyone with the knowledge to modify the service startup parameters, you shouldn't wipe out their settings. Anyone seeking a completely clean installation can (and should) first do an uninstall.
Triode, this is fixed, right?
Michael - I think this should be yours, but I believe your recent work should avoid it?
This should be fixed in SC7's new installer: logon information for the service should be kept. Please re-open if this isn't the case for you.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.