Automatic Server Updates?

[chjohans 34]

For the longest time I've been using the powershell EmbyServiceUpdater script to automatically upgrade my Emby server(s), all running as a service. But when I reinstalled Emby on a server just now I see that under Server -> Settings I now have "Enable automatic server updates" and "Allow the server to restart automatically to apply updates" available, and this is after I have started the server as a service. These options ate *not* there on my other and much older Emby installations (they are all upgraded to the latest version).

So, will now Emby automatically apply any upgrades even when running as a service?

 

And if that's the case, will it do so for updates to Plugins as well?

 

And if this is the case, any chance that I can enable these options on my other Emby servers?

[chjohans 34]

Is this really a difficult question? Could somebody please enlighten me?

[Carlo 4561]

Historically you had to do the updates manually due to account permissions and how the service ran.

I honestly don't know if it can update itself as a service but I'd doubt it.  You could probably find out yourself by installing the beta version and then see what happens when the next beta is released.

Anyone running Emby as a service that can comment?

[Luke 42080]

Officially the server does not support automatic updates when running as a service. You need to shut it down and install the update manually. Plugin updates will be downloaded, but you need to restart manually for their updates to take effect.

[chjohans 34]

Ok, thanks @Luke

Any idea why I see the optionsr Server -> Settings I now have "Enable automatic server updates" and "Allow the server to restart automatically to apply updates" on the newly instaleld server, but not on my older installs (all with the same server version)?

 

Also IO notice that the file layout has changed, on a new update it's a bit different (in the install dir) than on my older installs, but I assume that is just "evolution"?

[pwhodges 2012]

I just posted this in another thread:

Running as a service on Windows using nssm, Emby cannot update itself.  I have a routine for updating manually which takes me only a couple of minutes via remote desktop, and of course I control when it happens that way; I do not consider this a significant disadvantage, even when following all the beta releases.

The installation is no different from normal - I merely choose to run it as a service.  Since I choose what account to run the service under, there's no need for any changes in access rights for the media folders either.

In terms of actual operation, I can see no disadvantage; since the service starts automatically, Emby is always available if the machine is running (which it is, being part of my little server farm).

Paul

[Carlo 4561]

Very nice.

Do you use HW transcoding?

[pwhodges 2012]

Yes.  I use a video card with an nVidia GTX1050Ti and passive cooling.  As the machine is running headless as a server (there's a dummy load on the video), it is necessary for it to be quiet because my server farm is not in a soundproof place.  Although the i7-3770 it's built on can do transcoding, I think I worked out that the GTX1050 would be a better bet; something to do with remote access killing the Intel video, as I recall.  The OS is Windows 10, not a server OS (I've run out of licences for Windows servers - I accumulated several while working in university IT as well as several Windows 7 & 8 licences which I was able to update to Windows 10).

Paul