Endpoint Protection

I am in the process of re-building my primary (RU6 MP2) SEPM having successfully created a replication partner. The issue is I have discovered that the encryption password my colleague noted in the backup.txt file may not be correct (I haven't got to the point of the DB restore in the build yet). I do have a full backup of the database along with the keystore pass (assuming that is correct) and other recorded info as per http://www.symantec.com/business/support/index?page=content&id=TECH102333

So, is it possible to restore the DB on the newly built box without the encryption password or am I now looking at a scenario of having to use sylink replacer (to about 6,000 - 7,000 clients)?

Hello,

Encryption Password is an important element.

A Quick Tip: Encryption password may be the same password which was set as during the Installation of SEPM for Login Purposes for the first time.

Hope you may find it.

If not, you are correct, use the SylinkReplacer.

Hi,

You will most certainly have to use Sylink Replacer if you enter a wrong Encryption password.

The Disaster Recovery KB says: 

The encryption password used must be the same as your first installation in order to restore a database backup and to re-establish communication with the clients.

Damn, that's what I feared. Thanks guys.

Well, I reconfigured the new SEPM with the values recorded in the backup.txt file and the DB has been restoring for the past 20-25 minutes (it's >8GBs) so here's hoping!

it will take sometime. in progress bar it should show description changing like sync catalogue, building etc. Have patience

Yeah, it completed the restore in about an hour. However, when I attempt to login to the console it kills the semsvc service and I get the "java virtual machine has exited with a code of -1..." error. I had the same issue initially on the replication partner but resolved it by enabling 'integrated windows authentication' within IIS; it isn't working for this one though. Re-booted several times, and even enabled the permissions advised in rickjds's post from here https://www-secure.symantec.com/connect/forums/java-virtual-machine-has-exited-code-1-service-being-stopped - no joy.

run the mangement server configuration wizard again and check !

I ended up uninstalling/re-installing both SQL & the SEPM but got the same problem! I re-checked the scm-server-0.log and could see an entry for "SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: Can't read local server from database!" - the solution in this thread solved it:

 https://www-secure.symantec.com/connect/articles/failed-connect-server-session-has-timed-out

Thanks again guys.