Replication partner did not take over as priority 1 SEPM server
I am a little confused as to why this did not work as expected. I have two 12.1.2015.2015 SEPM servers running on Windows 2008 R2. All of my clients were reporting to one machine which is in our DR location. I wanted to move all clients to the SEPM Server running in our Production environment. The SEPM Server running in our DR site was built first then I created the second server in our Production environment and added it as an additional site and created replication between the two servers. To move all clients over to the second server (production environment) I made that server Priority 1 on my MSL. I then let about a week go by and a number of replication occurances. Then, this past Friday evening, I stopped the SEPM service and the Embedded Database service on the SEPM server than all clients were currently reporting to. When I checked on the status of the second server this morning I expected to see all clients now reporting there. This was not the case. All clients on the second machine were showing as Online on the Remote server. When I checked that server all clients were showing as offline. I started the SEPM and Embedded database services back up but still nothing is reporting to the orginial server. All clients are now in limbo. Shouldn't all of my clients started reporting to the second server? The I made Priority 1 in my MSL. I followed this procedure below but it didn't work and now I have all of my clients showing as offline. How do I get things back to the way they were before I tried to initiate the failover?
This is the article I followed to move all clients to the other machine: http://www.symantec.com/business/support/index?page=content&id=TECH104389&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1360096189165o7332jvX5mD2iNAby0N749pY17qMJePAbk4NW