hatharry 83 Posted April 30, 2019 Author Share Posted April 30, 2019 An Emby api key and url is now required. The api key can be created in, advanced menu, security. Then run: .\EmbyServiceUpdater.ps1 -ApiKey "YOUR_API_KEY" -ServerUrl "http://YOUR_SERVER_URL:PORT" -InstallTask Link to comment Share on other sites More sharing options...
jeffshead 3 Posted April 30, 2019 Share Posted April 30, 2019 (edited) An Emby api key and url is now required. The api key can be created in, advanced menu, security. Then run: .\EmbyServiceUpdater.ps1 -ApiKey "YOUR_API_KEY" -ServerUrl "http://YOUR_SERVER_URL:PORT" -InstallTask Thank you! Edited April 30, 2019 by jeffshead Link to comment Share on other sites More sharing options...
hatharry 83 Posted April 30, 2019 Author Share Posted April 30, 2019 Just run the command in powershell. It should overwrite the task with new arguments. Link to comment Share on other sites More sharing options...
chinedooo 0 Posted November 27, 2021 Share Posted November 27, 2021 I get this error when i run the script. PowerShell is updated to the latest Link to comment Share on other sites More sharing options...
hatharry 83 Posted November 30, 2021 Author Share Posted November 30, 2021 On 11/28/2021 at 3:19 AM, chinedooo said: I get this error when i run the script. PowerShell is updated to the latest The server url is missing http:// Link to comment Share on other sites More sharing options...
chinedooo 0 Posted November 30, 2021 Share Posted November 30, 2021 4 hours ago, hatharry said: The server url is missing http:// Awesome that did the trick thanks. Quick question though how does this work. Will it automatically stop the server and install the update then restart the server once an update is available? Can I choose certain times for it to do this? Link to comment Share on other sites More sharing options...
chjohans 31 Posted May 24, 2022 Share Posted May 24, 2022 I've been using this script for years, and with the exception of a few necessary upgrades to the script, it ahs worked flawlessly so I hardly ever had to upgrade my Emby server manually. However a while ago I saw both my Emby servers announcing that Emby v 4.7.* was available. Checked and confirmed that the EmbyServerUpdater script no longer does it's job, it will just run and then bring the old server version back up. Noticed this on both my Emby servers. I updated the script from Github just in case there were changes, but that made no difference. I've not made any changes to my Emby servers, so I'm not sure why this is no longer working. Not sure how to debug this either. Did something change in the latest Emby server update that prevents the script from working? Link to comment Share on other sites More sharing options...
Cortexian 0 Posted June 10, 2022 Share Posted June 10, 2022 On 5/24/2022 at 5:39 PM, chjohans said: I've been using this script for years, and with the exception of a few necessary upgrades to the script, it ahs worked flawlessly so I hardly ever had to upgrade my Emby server manually. However a while ago I saw both my Emby servers announcing that Emby v 4.7.* was available. Checked and confirmed that the EmbyServerUpdater script no longer does it's job, it will just run and then bring the old server version back up. Noticed this on both my Emby servers. I updated the script from Github just in case there were changes, but that made no difference. I've not made any changes to my Emby servers, so I'm not sure why this is no longer working. Not sure how to debug this either. Did something change in the latest Emby server update that prevents the script from working? I just ran it successfully to upgrade to 4.7.2.0. First time using this script as well, thanks to the OP! I encountered an error the first time I tried to run it, as the script requires that it run as "Administrator" but I had a service account setup to run Emby Server on my machine for some more granular security control. I changed the owner of the Emby Server directories to be the Administrators usergroup, while ensuring that my service account still had full control. This allowed the script to proceed (before the owner was the service user itself, and Administrators had Full Control but that wasn't enough, needed to be the owner of the directories). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now