Endpoint Protection

I've read through a ton of information and found 100 different ways to move to a new server where the hostname and IP were changing. The process that I ended up taking was this:

Note: We are using a SQL database. Server1 had SEPM 12.1.4 on it. I updated this server to 12.1.5. I then installed a fresh copy of SEPM on Server2. After installation I did the Management Server Configuration Wizard, in which I chose to Add a Management Server. I went through all the steps using a recovery file so that it would automate most of the information, setup the proper SQL connection information and added Server2.

At this point I was able to login to SEPM at Server2's address, go to Admin -> Servers and now see 2 servers underneath Local Site. I then added a Management Server List that included only Server2 and assigned it to all the machines. I then shutdown all symantec services on Server1 and began updating all the clients with the latest client version and made sure they all connect to Server2.

After all the updating, all the clients successfully were on the 12.1.5 client and communicating with Server2. At this point, Server1 is sitting there with its services disabled, however it still appears under Local Site in Admin -> Servers.

Here is the weird part. If I right-click on Server1 and choose Edit Properties, or Delete Selected Server, or Manage Server Certs, it always gives me Server2. It literally changes the window's information from Server1 to Server2 as if Server1 doesn't actually exist. So my issue is that I am unable to remove Server1 and I don't know the proper way to complete this "migration" of servers.

I am pretty lost at this point as to what situation I am in and would appreciate any guidance. Thanks.

Did you delete SEPM1 first from the console then shut down?
 

I've heard of this happening.  IIRC you're going to have to log a support case to get Symantec on to remove the stale record.

I personally think it's because you used a recovery file on the Server2 installation (this is a brand new server being added to an exsiting site, there should be no existing recovery file), but as I've never done it myself this is pure speculation.

I haven't uninstalled SEPM1 yet for fear that it would leave an orphaned record since I haven't been able to remove it properly yet. Should I go ahead and uninstall?

Also, I can't shut down that server as it is used for other services.

Well to me it seems that the recovery file is simply used to default some of the settings when you are adding the new server to the Management Server list. It pre-populates the SQL database name and some other settings. I didn't think it affected anything with the inner configuration of the site, but I could be wrong.

The recovery file hold certs and SEPM details include the name and (I suspect) the GUID (which may be what caused the confusion here).

I've not personally encountered this error like I said, but then neither have I ever used the recovery file on a different SEPM than the one on which it was created on (or in a DR scenario, when recovering the same SEPM).  As I said, this is pure speculation on my part.

So in any case, would I probably need to open a support ticket?

Yup, that's what was required to resolve the other instance of this issue.

As I understand it, support provided a tool to remove the stale SEPM entry called DeleteServer, but that's going to be specific to SEPM version (due to DB schema changes and whatnot).