There are 4 ways in which we can move SEPM from one server to another.

1. Disaster Recovery

2. Move SEPM form one server to another with the same ip address ( as suggetsed by vikram)

3. Replication

4.Clean install on the new server and then replace the sylink.

1. Disaster Recovery :

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082112135948

2. Move SEPM form one server to another with the same ip address

http://service1.symantec.com/support/ent-security.nsf/docid/2008031204405448

3. Replication : Add a replication partner to the old SEPM. Stop all SEPM service on the old SEPM so that all the cleints move to the new SEPM, then Uninstall the old SEPM

4.Clean install on the new server and then replace the sylink.: Uinstall SEPM from the old server.  Install SEPM on the new server  and replace the sylink using sylink replacer:  

I'd go for the 2nd option in your situation.  But the 4th option should work as well.

[Edit]

Now that I think about it more, I think the 4th option is best.  You can keep the current one running until you get your new one setup as you like then force all the clients to start talking to the new server.

You have mentioned "I do not have the password for it and the reset doesn't work". Why its not working... What was the error...? If you can reset the password its easy to replace the server.

Just have to take a backup of database, server.xml, keystore.jks and restore it on to new server.
 

For me number 4 is the best way to have a new sepm, you can find unmanaged client anyway...then replace the sylink at once.. 

If you have unmanaged client that is the best way to bring back all the client to SEPM... 
You can go for a new version(RU5). You can download it from fileconnect.  

Dear Reaser,

I understand that you have lost the the exixting password. The best and effort less way to do it is:

1. Take the Server privite key backup folder.
2. Download the latest SEP version RU 5 which is avilable in the net.
3. Install the SEPM with a the same IP and Host name.
4. Restoring the server certificate
The server certificate is a Java keystore that contains the public certificate and the private-public key pairs. You must enter the password that is contained in the
Backup.txt file. This password is also in the original server_timestamp.xml file.

To restore the server certificate

1. Log on to the Console, and then click Admin.
2. In the Admin pane, under Tasks, click Servers.
3. Under View Servers, expand Local Site, and then click the computer name that identifies the local site.
4. Under Tasks, click Manage Server Certificate.
5. In the "Welcome" panel, click Next.
6. In the Manage Server Certificate panel, check Update the Server Certificate and click Next.
7. Under "Select the type of certificate to import", check JKS keystore and click Next.
   Note: If you have implemented one of the other certificate types, select that type.
8. In the "JKS Keystore" panel, click Browse, locate and select your backed up as "keystore_<timestamp>.jks" keystore file, and then click OK.
9. Open your disaster recovery text file and then select and copy the keystore password.
10. Activate the "JKS Keystore" dialog box and then paste the keystore password into the "Keystore" and "Key" boxes.
    Note: The only supported paste mechanism is Ctrl + V.
11. Click Next.
    Note: If you get an error message that says you have an invalid keystore file, it is likely you entered invalid passwords. Retry the password copy and paste process as described above.
12. In the "Complete" panel, click Finish.
13. Log off of the Console.
14. Click Start> Settings> Control Panel> Administrative Tools> Services.
15. In the "Services" window, right-click Symantec Endpoint Protection Manager and click Stop.
    Note: Do not close the Services window until you are finished with disaster recovery and establish client communications.
16. Right-click Symantec Endpoint Protection Manager and click Start.
    Note: By stopping and starting Symantec Endpoint Protection Manager, you fully restore the certificate.

5. Re-deploy the clients with SEP RU5, not only the clients will get updated they will also recommunicte with the SEPM Server.

Please let me know if you need any more information.

Warm Regards,
Sumit Bose

@Prachand,

Im my case SEPM is up and running... I have reinstalled and restored the SEPM in many cases(by restoring database, overwriting server.xml and keystore.jks files and reconfiguring SEPM) and i have not come across the use of this password.

  I need to know the scenario where exactly its required in the future, We have other methods of disaster recovery with out that password(Like i have mentioned above).

When we run management configuration wizard after db restore, it wont ask for that password.

I m not importing the Keystroke.jks and server.xml files i m directly copying it to tomcat folder.
When i do that and reconfigure SEPM it wont ask for any password. sem5 db password is the only one asked.

@ All Admins, Specially Symantec Employees .

Why  reaser who starting this froum didn't answer (Feedback) about his Problem ? Who care about hi's last status & what he did at the end ?
If there was a Case Status in Symantec Connect to follow the Problem up to End, it can help to All Customers, even Professionals here .