Windows Server and Synology

[hMeco 0]

I have been experience massive issues with Synology box and Windows Server OS, after 3 bottles of red wine ive figured it out and now writhing this post.

When you install Emby server on Windows server its placed as a service and starts automaticly with the OS (we all know that, what we don´t know is what account its running on).

 

So to prevent this on future installs..

 

1. Don´t use Administrator as account, make one sepperate.

2. Create the "sepperate" account on you´r nas.

3. Attach the service to the "sepperate" user account (user is Administrator as well, but username Administrator its way to easy to guess I´ve disabled it!)

 

- To attach a service to you´r user login via RDP on ANY administrative account you have.

1) Right Click on progress bar and choose "Task Manager" go to "Services" and find "Emby"

2) Right Click on Emby and choose "Open Services"

3) Now find "Emby Server" and right Click on that say "Propeties"

4) Choose "Log On", you will guess it from there, simply choose an account and search for it.

 

Once done Apply and save, restart service and no more credential issues.

 

and last very important step.... ENJOY!

P.S Sorry for spelling errors if any, I´m 1) Partialy Drunk and 2) still drinking

Edited June 24, 2017 by hMeco

[Luke 37019]

hi @@hMeco, please be aware, this is not fully true:

When you install Emby server on Windows server its placed as a service and starts automaticly with the OS 

We do install a windows service, but we don't configure it to run automatically. That's left for the user to configure if they want to do so.

[hMeco 0]

hi @@hMeco, please be aware, this is not fully true:

When you install Emby server on Windows server its placed as a service and starts automaticly with the OS 

We do install a windows service, but we don't configure it to run automatically. That's left for the user to configure if they want to do so.

 

No, True that, but unfortinetly due to Windowsthing Server OS it will run as a Systemadministrator and not the user installing it, therefore to make sure it runs under the correct premissions, here is a workarround

 

EDIT: added.. Systemadministrator != (is not equal to) the user you make, and install the service with. It´s a totaly different user that is not even, even equal to Administrator. 

If it makes any sense

 

BAZINGA

Edited June 24, 2017 by hMeco

[Luke 37019]

Thanks for the info !

[hMeco 0]

Thanks for the info !

No no, thank you for a awseome software, Il help as much as I can