Server as a service?

[Gilgamesh_48 1240]

Since I enjoy a bit of experimentation I was somewhat considering trying installing the Emby server on one of my test servers as a service. What I want to know is:

What are the advantages of running Emby as a service?

What are the disadvantages?

What are the issues of moving from a regular Emby install to running as a service and moving back?

Are there any pitfalls to watch out for?

Is there anything else I need to know?

I may or may not take this step but I do want to be as informed as possible before taking the plunge.

Thanks.

[pwhodges 2012]

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

Edited July 26, 2020 by pwhodges