Upgrade Process For Windows Running As A Service (NSSM)

[Stremit 2]

Hi,

I have been running Emby Server on Windows 10 as a service (using NSSM) for quite a while and hadn't realised that it wasnt being updated. My server is running at version 4.7.2.0 and I want to upgrade to the latest stable release (4.7.13.0).

As documented I stopped the service and downloaded the setup.exe for the latest release. When running the setup.exex (from the download directory) it seems to be taking me through a blank/new install process, asking for new user passwords, no libraries configured and asking to add them from scratch, setting up configuration for metadata etc.

I exited the upgrade process at this point as I didnt want to end up with another install of Emby on my server. Is there something I have to do to get the installer to recognise that this is an upgrade rather than a new install?

Cheers,

Michael.

[Abobader 3464]

Hello Stremit,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[MBSki 1114]

Best way to upgrade is stop the service, rename the system folder in the Emby-Servee folder to syatem.old, download the Emby portable, then just copy the system folder in the portable install zip file to the Emby-Server folder, then restart the service. Once you reconnect you'll see you're on version 4.7.13.

[rbjtech 5284]

23 hours ago, MBSki said:

Best way to upgrade is stop the service, rename the system folder in the Emby-Servee folder to syatem.old, download the Emby portable, then just copy the system folder in the portable install zip file to the Emby-Server folder, then restart the service. Once you reconnect you'll see you're on version 4.7.13.

I believe Emby are working on a complete Windows install overhaul (and about time!) - so hopefully this muddle of upgrading as a service will be resolved.

I do it slightly differently - I stop the service - and then start the app on the desktop (as an admin), then emby updates itself.  I then restart it and then shut it down.  I then restart the service again.

I believe the two methods probably achieve the same thing - but if there are any 'upgrade' steps during the 'auto' upgrade, then just copying the files may not do this.  I'm not 100% sure - I think you are likely safe with both methods.

@softworkzFYI - Until the new install process is released, what method do you recommend - zip portable overwrite or let the app do the upgrade and then resort back to a service ?  Thanks !

[Stremit 2]

Many thanks for the info @rbjtech. I just tried the in-app method of upgrade, stopping service..., and doing the upgrade via the app. All seemed to go well with upgrade completed and date/time of files in system directory all updated to todays date.  However EmbyServer wouldnt run after that, either as an app or as a service. No error messages on screen, seemingly started to run and then closed down after a second. Not sure if this is because the upgrade was skipping a few versions? 

Anyway then tried the copy portable install system files across and that worked fine, Emby up and running. Fingerst crossed the normal install process doesnt do anything clever apart from copying the files.

Thanks again for your help. Hopefully the install/upgrade process gets the overhaul you mentioned.

[Stremit 2]

Thanks @MBSkithe copy system folder method worked great for me. Your help is very much appreciated.