@Macivervfr said:
Sorry, no go.
I notice it’s not running, did you try and start it? I think I might need to do another release with that dependency removed
That, or change the installer to make it enable the offending dependency.
@cjmurph said:
@Macivervfr said:
Sorry, no go.
I notice it’s not running, did you try and start it? I think I might need to do another release with that dependency removed
No, and i couldn´t start it. I got a message “Error 1068”
Tried to reboot the server and then start the service - Same result.
But i think i have the solution:
I had to activate 2 more services to get it to be active.
I activated
Function Discovery Resource Publication
SSDP Discovery
Then i could activate
UPnP Device Host
After this i could also activate the Network Discovery feature in the network Advanced sharing settings.
Then i tried to install the 1.1.3 and it did install and the PMS service started. I haven´t restarted the server yet so we will se what happends then.
So there a several dependacys.
We are destabilising a solid product by adding these dependencies
In any case uPnP automatic port allocation is not a reliable way to get remote access working. Many routers do not behave and end up with loss of connectivity and PMS fails to find an IGD route to re-configure
@sa2000 said:
We are destabilising a solid product by adding these dependenciesIn any case uPnP automatic port allocation is not a reliable way to get remote access working. Many routers do not behave and end up with loss of connectivity and PMS fails to find an IGD route to re-configure
I tend to agree. This was a mistake. If a user wants upnp host running, they can set that to auto themselves.
It is not actually a requirement for the plex service so I’m going to remove it. It’s doing more harm than good.
1.1.4 is on the releases page. functionally the same as 1.1.3 but without the upnp host service dependency
Works like a charm. Thanks for a good service.
How is “Run as a service” still not included in the Plex Windows server app!? I switched from Windows to XPenology for my server a few years ago. Now I am currently looking at other options for my next hardware upgrade. If Plex added the service functionality, this decision would be a no-brainer.
Finally got around to setting it up and the only question I have is why haven’t I done this before! Good job, cjmurph. (I wish there were an option to hide the tray icon from some accounts [don’t want my kids to mess Plex service]). Thank you!
@compulsorysignup said:
How is “Run as a service” still not included in the Plex Windows server app!?
Well if we knew that, we wouldn’t be here.
Won’t stay running for me, if I’m logged in as the service account I can access my Plex library fine, but when I log off it starts refusing the connection and shows as Offline. If I log on with my admin account, my Plex library is not updated as it runs under the context of the service account. The only way this works for me is to remain logged in with the service account which renders the PC running PMS unusable. This is running on Windows 7
EDIT: Stopped and started the service through services.msc and now running perfectly 
@alekdavis said:
Finally got around to setting it up and the only question I have is why haven’t I done this before! Good job, cjmurph. (I wish there were an option to hide the tray icon from some accounts [don’t want my kids to mess Plex service]). Thank you!
The autostart for the tray app is in the registry, hklm\Software\Microsoft\Windows\CurrentVersion\Run
Find it and remove it to stop it so starting for every user.
Has there been any improvements made on this service yet?
I dont see any support for Windows Server 2016 yet. 
@SmoothRunnings said:
Has there been any improvements made on this service yet?I dont see any support for Windows Server 2016 yet.
I’m not sure what “improvements” you’re after, maybe you could elaborate.
Have you tried it? I don’t have server 2016 to test on. Can’t see why it wouldn’t work though. Give it a go and report back. If it works fine I’ll update the first post.
I’ve been running it on Windows Server 2016 Standard Edition for more than a year. Zero issues! It works great, even after a migration from 2012.
I’m actually here looking for the script to update Plex automatically when a new version is released, since invoking the update from a client doesn’t work when using the service wrapper, but the clients will pester users if I don’t do the upgrade right away.
Wasn’t that script on this thread somewhere?
Edit: OK, so I see there are a few of them. I settled on this one because of the email notifications and logging, all of it very customizable: https://forums.plex.tv/discussion/290109/update-script-for-pmsservice-pms-as-a-windows-service
Is this the one you are after?
@cjmurph said:
@SmoothRunnings said:
Has there been any improvements made on this service yet?I dont see any support for Windows Server 2016 yet.
I’m not sure what “improvements” you’re after, maybe you could elaborate.
Have you tried it? I don’t have server 2016 to test on. Can’t see why it wouldn’t work though. Give it a go and report back. If it works fine I’ll update the first post.
I can also verify that it runs perfectly on Windows Server 2016 Standard. The mapped drive functionality also works in it, btw. I created a Distributed File System share named Media with the various media shares on my NAS (separate box), then mapped it to drive M:.
This thing flat out REFUSES to let me log in. I go to “check credentials:” and it fails every effing time. I’m following the directions, so I simply do not understand.
Having problems with “PMS as a service”. Previously, I never had problems with it being accessible outside of home. Since running as a service, it rarely is accessible without another reboot or too … which negates the whole value of running as a service if I have to massage it before it works. Anybody else with that problem?
Also… If I decide to do it, how do I uninstall “PMS as a service” and go back to the generic PMS within my account?
@“brian.don” said:
Having problems with “PMS as a service”. Previously, I never had problems with it being accessible outside of home. Since running as a service, it rarely is accessible without another reboot or too … which negates the whole value of running as a service if I have to massage it before it works. Anybody else with that problem?Also… If I decide to do it, how do I uninstall “PMS as a service” and go back to the generic PMS within my account?
Only aware of issues if you have Plex Media Server.exe running in another user account perhaps not as a service due to auto launch on login being set. This possibility would only arise if you install Plex Media Server using a different windows account from the one that you normally run the service in. You can check windows task manager to see if there are multiple instances of Plex Media Server.exe processes running.
