this would be nice to have so i dont need a 3 party program running
+1 me too!
@ilmiglio said:
+1 me too!
Did you click the “Like” button on the original post? +1 is pointless for requesting Plex features
This is truly needed. However, all of these workarounds provided here aren’t even needed. If your Plex host is running on your home network then it should be secure enough to setup an auto-login, which doesn’t require a third-party (or Microsoft “tool”) to configure. Just open the User Accounts applet from the Run menu with “control userpasswords2”. This will open a window for you to config an auto-login user- no one should be paranoid about this if you are on your home network. You need to re-configure your router or install a firewall if you think that computer will not be safe at home with an auto-login. No reason to make things so difficult until Plex FINALLY implements this service.
@sundi712 said:
@ilmiglio said:
+1 me too!Did you click the “Like” button on the original post? +1 is pointless for requesting Plex features
Thanks…
I hope this is a duh obviously for the dev team, that does threat modeling and follows modern dev practices, please implement proper security when you move to a service. (today I run the app on a W2K12R2 VM under a user account with limited local and limited network rights)
- A remote network accessible service means remotely exploitable, not if, but how often.
- Run service under a configurable account, with limited system privileges, not as system.
- Do not allow elevation of privileges in spawned child processes, i.e. drop unused privileges on startup.
- Support specifying remote username/password for accessing remote UNC media paths.
- Support automatic upgrades without requiring user intervention or elevation, e.g. write core binaries to programdata and use service as launcher only, relaunching new version when available
@ptr727 said:
I hope this is a duh obviously for the dev team, that does threat modeling and follows modern dev practices, please implement proper security when you move to a service. (today I run the app on a W2K12R2 VM under a user account with limited local and limited network rights)
- A remote network accessible service means remotely exploitable, not if, but how often.
- Run service under a configurable account, with limited system privileges, not as system.
- Do not allow elevation of privileges in spawned child processes, i.e. drop unused privileges on startup.
- Support specifying remote username/password for accessing remote UNC media paths.
- Support automatic upgrades without requiring user intervention or elevation, e.g. write core binaries to programdata and use service as launcher only, relaunching new version when available
I think we now know why Plex hasn’t implemented this yet. Plex users like this being so demanding. smh
I agree with - (Support specifying remote username/password for accessing remote UNC media paths)… but submit another request.
Not intended to be demanding, I’ve used many projects with open source roots, and many times I cringe when I see how security is overlooked when something small grows into something big, so I trust but I’ll also verify.
+1 need this feature
i use https://nssm.cc/ but updating plex sucks lol
+1 Vote, Please add this…
Seriously, how is this not done yet? It’s been over 4 years since it was first suggested, and does so on every other platform.
+1
Please add Plex as a Windows Service
@psycik said:
I don’t seem why this is such an issue (to get it running as a service), I’ve written plenty of programs and set them to install as services - it’s about 5 lines of code.I don’t see why we should have to be auto logging on machines, running scheduled tasks etc.
Unless there’s a fundamental dependency on something in the UI, I can’t see why this can’t be done.
Yeah, I am also a developer and don’t get why it is 2016 and this still has yet to be done.
I keep seeing people posting workarounds or saying there is no need for it to run as a service.
What people should actually be saying is there is no need for it to run interactively.
- It’s a server
- It’s super easy to make run as a service
- Installing updates would work completely automatic as a service
- There is no reason it needs to run as a task bar application and never should have been built this way
This is a fundamental problem I have with Windows in general. After doing Linux system administration for so long, doing anything in Windows is so clunky, even today.
What it boils down to is this is leftover functionality when it was competing and copied from XBMC back in day, I just can’t for the life of me figure out why they haven’t fixed such a small issue.
Don’t even get me started on more high-end server features they need to add such as remote transcoders, shared database and metadata, swapping the database to something more robust and shareable, etc. Unfortunately, I think the small server/media library XBMC crowd is their largest target so a lot of these features will never come to pass, at least not officially by them other than workarounds.
+1
We’ve been asking forever now. C’mon guys. Throw us a bone. 
@RAlfieri said:
+1We’ve been asking forever now. C’mon guys. Throw us a bone.
LOL, I was just looking at the original post and realized this was from over 4 years ago.
+1
This needs to be taken care of. This feature request being 4+ years old makes it seem as no one is really paying attention. Regardless of how popular something is, this should have been handled by now. If they cannot handle the backlog, then it is time to either hire more people or open it up so the community can help. I mean the most difficult part of the PMS is the transcoding/media scanner and that is almost entirely a direct copy of FFMPEG so I am not certain why they are having a hard time fixing trivial things like this one. In fact, the server part of the code is probably the most basic part of the entire system.
I also want to point out that there is no reason we can’t have both the tray application and a service that is PMS. The tray app can still have all the same functionality it does now, it just doesn’t need to literally also be the PMS as well. That way people who like that feature of starting/stopping PMS can still do that while also making everyone else happy who want a service. The tray app would just start/stop the service as opposed to itself like it does now. This is how most tray applications work. They are usually just an interactive/visual extension of some back-end service, not literally the server itself.
Wow, this is shocking. I thought it would work this way out of the box. Luckily I did my testing on Linux before buying the pass because this omission would have been a clear showstopper. Like many other supporter of this feature request I cannot understand the motivation to keep things the way they are.
Run Plex Media Server as a service. +1
Run PMS as a service. +1
Let’s get on this!!!
