Server names, claims and the relationship between servers, libraries and players

Server Version#:1.43.0.10231
Player Version#:

This has happened a couple of times to me over the years, it happened again and I now want to understand why and figure out how to avoid it.

I recently moved the location of the plex install and data folders onto a dedicated drive since I decided to enable thumbnails. After a couple of weeks I was running out of room on the drive so I moved them again to a larger disk. I kept the same drive letter and path, but noticed there was some duplication because I didn’t understand the paths in the registry the first time around and cleaned things up. After starting plex, I had some issues with the database and was able to fix the corruption and index issues. That went well, but I wound up deleting the registry keys around the logins. That essentially “forgot” for the lack of a better term the server, so even though it was named exactly the same it appeared to Plex and the players as a new server once I logged in again. Which means I had to delete the duplicate libraries and re-pin them in the players. Now, this wasn’t a bit deal, I’m not sharing with a lot of people.

That said, its not great this happens and having to “redo” these libraries and the mess it creates in players and in shared account is not user friendly at all.

The question is, what is it that identifies a Plex server and what needs to be saved to avoid maintenance or migrations from looking like a new server to plex?

Is it any of these keys in the registry?

The next part, is there a process or better way to handle this to avoid having to re-pin libraries and then cleanup the “old”, “missing” server and libraries in players and shared accounts. To me, if the server name is a match, that should be enough. Obviously, a decision was made for some reason or another. That said, things happen and for the sake of user friendliness and ease of use, there has to be a better way to handle this.

If your MachineIdentifier changes it will be seen as a different/new server.

@drzoidberg33

Got it.

How is it generated?

Let’s say I get a new server and install Plex, then migrate everything over. If I use this same ID again, it shouldn’t be an issue?

Thanks!

Simply create a backup of the registry data before switching machines.
https://support.plex.tv/articles/201539237-backing-up-plex-media-server-data/
You just need to be aware that you should never start up the old server again after importing the .reg file on the new machine.

Side note: you should install Plex server in the default location on drive c: (this will not affect the location of the Plex data folder).
It is only ~150MB
The reason for this is that c:\program files has tighter security applied to it by Windows than other folders.

I figured I could copy the ID. I was just curious if it’s a hash generated from hardware… if it could ever be regenerated randomly, IE kicked off by a hardware change (new motherboard) or if it’s a one off process that’s done during Plex install.

It’s the latter. There is no reason to bind it to the hardware in any way.