Video Screencast Help

PWD

Created: 26 Nov 2012 • Updated: 26 Dec 2012 | 6 comments
SKP's picture
This issue has been solved. See solution.

Any way to confirm or cross verfiy the SEPM Encryption password which i had

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Ashish-Sharma's picture

HI SKP,

Can you clear your question ?

Thanks In Advance

Ashish Sharma

 

 

Mithun Sanghavi's picture

Hello,

What version of SEPM are you running and What Database are you running?

Check these Articles:

How to find the Database password for Embedded Database

https://www-secure.symantec.com/connect/articles/how-find-database-password-embedded-database

Password recovery for Symantec Endpoint Protection and Symantec AntiVirus

http://www.symantec.com/docs/TECH97006

Hope that helps!!

 

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

SKP's picture

I had the SEPM Encryption password, but i want to confirm the password.

SEPM 11 RU6 MP3

Mithun Sanghavi's picture

Hello,

To confirm the same, you would have to find it from the Database.

Work on the steps provided in the Article below to find that password - 

How to find the Database password for Embedded Database

https://www-secure.symantec.com/connect/articles/how-find-database-password-embedded-database

Hope thathelps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

SOLUTION
Ashish-Sharma's picture

No

No way for verfiy encryption password.

You can only recover embedded databse password.

 

How to find the Database password for Embedded Database

https://www-secure.symantec.com/connect/articles/how-find-database-password-embedded-database

Thanks In Advance

Ashish Sharma

 

 

_DW's picture

The "How to find the Database password for Embedded Database", to my knowledge, no longer works as we stopped passing the password in plain text for obvious reasons.

 

Check the KCS value in a sylink.xml of an old client machine vs the KCS value in a sylink of a new client.  If they do not match, the same password was not used.

Even easier if you are using 12.x since it creates a settings.properties file containing the hash of the "encryption.password".  This hash will need to match, exactly, your KCS value in a client sylink.xml.

 

Hope that helps.