win/service - upping from one build to another requires reboot

[bobkoure]

Not a biggie, just can't figure out if this is doc'ed

If I'm running SqueezeCenter as a service, and installing a different build, I need to
- manually stop the SC service (service mgr or net stop)
- install
- reboot (old service is "scheduled for removal", (set in runonce?), new service won't install until this is done
- set SqueezeCenter to run as a service

I am running the SC service as user "LocalSystem". To make this work, I
- configure "SqueezeCenter Startup options" to run as a service, using the username and password of an existing user
- go into the services manager (start/programs/administrator/services), and set the service to run as "LocalSystem" - go to the "Logon" tab, check the "Local System account" radio button (and I've been checking the "Allow service to interact with desktop" to enable local management, for the local control app)
- stop / re-start service (or reboot)

Note that running as LocalService is the wrong thing to do if you're using iTunes integration, but, otherwise, adds a bit of security (and we windows users can use all the help we can get :-) )

[dwilliams01]

Is this for Windows XP?

I'm running SC on Windows XP sp2 and I haven't rebooted in a very long time.

I just do:
1) Start Downloading the new version
2) While it is downloading, stop the SqueezeCenter service (Control Pannel, Services, highlight the SC service, hit stop)
3) Run the SC installation
4) close the browser it pops up and log out - everything is running again.

I haven't rebooted or run the startup options program in quite some time. I believe that I have also not even bothered to manually stop the service previously - it just takes a bit longer for the install to shut it down and I'm impatient.

I'm also running the service under the local system, not a user account.

It seems to work OK for me, anyway.

[mherger]

> If I'm running SqueezeCenter as a service, and installing a different
> build, I need to
> - manually stop the SC service (service mgr or net stop)
> - install
> - reboot (old service is "scheduled for removal", (set in runonce?),
> new service won't install until this is done
> - set SqueezeCenter to run as a service

This should not be needed. But we've seen situations where SC would take "forever" to shut down and the installer wasn't patient enough (it's timeing out after 60 seconds) for it to be terminated. But it's not expected behaviour.

> I am running the SC service as user "LocalSystem". To make this work,

That's default setting - you shouldn't need to do anything at all?!?

What Windows version are you using?

--

Michael

[bobkoure]

That's default setting - you shouldn't need to do anything at all?!?
What Windows version are you using?

Default behavior in the sense that if I select "run as a service", but leave username and password blank - then it's run as Local Service?
I think I tried this a number of builds ago, and the service failed to start - so I gave it a user to run as and it started. So I've been operating under the assumption that leaving those fields blank won't work. Wrong?
BTW, I'm using Win2KServer SP4 on this server (the audiotrons in the house don't like SAMBA)

[mherger]

> Default behavior in the sense that if I select "run as a service", but
> leave username and password blank - then it's run as Local Service?

Correct.

> BTW, I'm using Win2KServer SP4 on this server (the audiotrons in the
> house don't like SAMBA)

But then I must admit that I'm not sure what W2K's behaviour was. Haven't
been using it for a while...

Michael

[bobkoure]

Well, I just tried it again (did a complete uninstall / delete app data / reinstall to see if that would fix my no-albumart issue) and, indeed, just checking "run as a service, and leaving the username/password fields blank sets the service up to run as LocalService.
So, either I did something wrong in that first build of 7.0 I installed (the most likely case) or it just didn't work in that one build, or maybe I just got tripped up by the previous service not being completely removed and mis-interpreted "failure to start".
Sigh...

[dwilliams01]

I seem to remember a long time ago that you couldn't leave the user blank so I think that it has changed. I use the blank method now since I don't need to access anything on the network.