Endpoint Protection

How can we change or reset the Encryption Password that the client use to talk to the SEPM?

I have read that you can't change it but is there a way to discover what that password was?  The one we have down in our documentation doesn't seem to work.  Trying to get the SNAC DHCP installer to communicate with our SEPM but I am thinking it is the Encryption Password that is the issue.

Hi kristopher,

Check the link below,

http://www.symantec.com/connect/forums/changing-sep-encryption-password

Check this link to find out encryption password
https://www-secure.symantec.com/connect/articles/how-find-database-password-odbc

Vikram, the instructions you included are for the Symantec database and not SQL correct?  So if we have a standalone SQL server will these steps still work?  We setup our environment using the Advance feature also.

Its for SEPM's database password that you set at the time of SEPM install. Nothing to do with SQL.

OK.  That password then would be the same as the Encryption Password?  Sorry, just double checking cause I don't want to do the other way that will require me rebuilding all my SEPM's just to get the Password.

The Encryption Password and Symantec Endpoint Protection 11 (SEP11)

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

Thanks.  Looks like I am going to be having some fun here soon then.  Pushing that sylink.exe file to over to 10,000 systems will be fun.  I was told there is a sylinkcrawler program but the Technical support rep that took my ticket closed it with only sending me the same link you guys sent me.  :(

Side question that deals with this issue....  bonus question?  :)   

The Encryption Password has to be one of about 5 passwords we have documented.  Do you use SNAC and the DHCP client?  Is there a log that will so me that the it isn't configuring cause I have the wrong password?

Pushing the sylink.xml shouldn't take more than a day.
I did 17,000 systems off my laptop at a clients site running about 10 scripts in paralell and it all worked flawlessly

If you used the same password as the encryption key and SQL DB in the next step you can find it out by adding an addtional SEPM.
During the install process you choose to add a server to an existing site, then it will ask you for SQL credentials.
I tend to use the same one all the way through the install process, but not sure it will help you out.

good luck

Z

Zer0,

We do that.  Which is why am lost at why the same password doesn't seem to work with the DHCP enforcer for SNAC.  At least that is why I think the software client doesn't connect to any of my SEPM's.   I haven't gotten an answer back from the Symantec Tech I had worked with about looking at logs to see.  All I keep getting are request to close the case and links to KB's that are the same links I can find here in the forums.

Here is what is strange. I just added another SEPM  to the same site using what I thought was the password.  It worked.  Why does the same password not work for the DHCP Enforcer?