What is difference between sem5 password and encryption password.

[Migration User]

Hi Team,

 

 

What is difference between sem5 password and encryption password.

 

 

Both password using for which purpose  

[pete]

sem5 is DB password.

Pre shared encryption is the encryption key used to encrypt communication traffic between the server and the client.

[pete]

also check this link

 http://www.symantec.com/business/support/index?page=content&id=HOWTO81146

The server certificate encrypts and decrypts files between the server and the client. The client connects to the server with an encryption key, downloads a file, and then decrypts the key to verify its authenticity. If you change the certificate on the server without manually updating the client, the encrypted connection between the server and the client breaks.

http://www.symantec.com/business/support/index?page=content&id=TECH102333

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.

If a different encryption password is used when performing disaster recovery without a database backup it will be required to replace the communication settings on all clients (by either using SylinkReplacer or reinstalling the clients).

[Migration User]

Hi,

 

Spm5 is your database paswword & encryption password is used for recovery password.

 

[Migration User]

Sem5 password is the Database password.

 

 

Encrypted password is Name of the password that encrypts communication

between the Symantec Endpoint Protection Manager,

clients, and optional Enforcer hardware devices. The

password can be from 1-32 alphanumeric characters and

is required.

 

check thread vikram comment for encryption

https://www-secure.symantec.com/connect/forums/sepm-installation-question-about-password

 

 

[Migration User]

Thanks to reply

 

ODBC Configuration for sql anywhere password is the same password of encryption.

 

[pete]

if its embedded it is same for the first time the way you have set it, however if you change DB password later , the pre shared key won't change.

 

If the Symantec Endpoint Protection Manager was installed in Simple mode, the password specified for use for the Admin account for the Symantec Endpoint Protection Manager is also the encryption password. If the Admin password is reset post-installation, the encryption password does not change.

[Rafeeq]

The concept is Simple. when Installing SEPM if you select the installation type as Simple. The database password and the Encryption password will be one and the same. 

If you select Advanced option during the installation , it will ask you for DB password and also the Encryption password. DB password will help you to connect to the DB(sem5).You have to remember the encryption password which will help you to restore communication between SEPM and SEP in case of disaster recovery. 

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

http://www.symantec.com/business/support/index?page=content&id=TECH160736

[Migration User]

But for the backup restore I am using same password which I use for odbc commination test.

 

So here I am little bit confuse about disaster recovery and backup restore  password

[Migration User]

My encryption and DBA password is different

 

When I reconfigure spem and repair I enter only DBA Password and it accept by sepm console, for odbc communication I am use same password so this right or wrong

 

Example

Encryption password is:- syman…..

DBA password :-5ym@ntec……

[Rafeeq]

If you are running on 12.1 forget the 11.x recovery process. That thing is entirely changed now

With 12.x its all gathered for you

Many of the individual files and data that had to be separately gathered in SEP 11.x are now generated and saved automatically by the SEPM into one file, the disaster recovery file. The recovery file includes the encryption password, keystore files, default  domain ID, certificate files, license files, and port numbers. This file can be imported automatically during the disaster recovery process.

 

[pete]

what's the issue, are you not able to restore?

is the ODBC test failing?

 

[Rafeeq]

Its correct. No need to worry about it. Forget about the Encryption password as of now leave that to SEPM let it handle :) 

 

[Chetan Savade]

Yes,I do agree with you. It's quite confusing.

I would request you to promote this idea:

https://www-secure.symantec.com/connect/ideas/sepm-should-store-dba-password-cache-or-should-have-access-reset-dba-password-admin-embedded-d

[Migration User]

how to test ODBC password if my database on sql server

[Migration User]

Steps to Test ODBC Connection in case of SQL database
 

• • Verify that you have specified a named instance during installation and configuration. Example: \\<server name>\<instance name> <server name=""></server><instance name=""></instance>
  • Verify SQL Server is running and properly configured.
  • Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.
  • Test the ODBC connection.
    1. From the Control Panel open Administrator Tools
    2. Double click Data Sources (ODBC)
    3. Choose the System DSN tab
    4. Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
    
    Name: SymantecEndpointSecurityDSN
    Description: <Anything><anything></anything>
    Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
    Login ID: sa
    Password: <password></password><password>
    5. Leave the defaults for the rest of the items and click Finish
    6. Click the Test Data Source on the next page and ensure it states Success
    7. Click OK

http://www.symantec.com/business/support/index?page=content&id=TECH104746

[pete]

To verify ODBC connection to the SQL database:

1. Click Start button and select Run.  If the Operating System is 32 bit, enter "%systemroot%\system32\odbcad32.exe".  If the Operating System is 64 bit, enter "%systemroot%\syswow64\odbcad32.exe"
2. In the ODBC Data Source Administrator dialog box, click System DSN.
3. On the System DSN tab, double-click SymantecEndpointSecurityDSN.
4. In the Server drop-down list, verify that the correct server and instance is selected.
5. Click Next.
6. For Login ID, type sa.
7. In the Password text box, type the password for the database. This password is the one that you entered for the database when you installed the management server.
8. Click Next and make sure that sem5 is selected for the default database.
9. Click Next.
10. Click Finish.
11. Click "Test Data Source" and look for the result that states: TESTS COMPLETED SUCCESSFULLY!

http://www.symantec.com/business/support/index?page=content&id=TECH160964

[Migration User]

Dear Team,

 

It is possible exist embedded sepm server client to migrate new sql database server without  backup restore , sylink replace  because now I four server one of that 5000 client so I can’t move all clients to new server by slink replace.

If at lest I move one server who has 5000 clients that also ok

 

Please suggest something for this

 

Old server hostname :scsp*

Ip address:172.16.*.*

 

 

New server hostname: INCPLSEP*

IP Address:172.16.*.*

[Migration User]

hi,

you can check this artical

Symantec Endpoint Protection Manager: Moving from the embedded database to Microsoft SQL Server

 

Article:TECH102547

|

Created: 2007-01-27

|

Updated: 2012-08-16

|

Article URL http://www.symantec.com/docs/TECH102547

 

[pete]

yep, keep the same host name and IP

http://www.symantec.com/business/support/index?page=content&id=TECH102547

[Migration User]

Any one have latest sylink replacer tools for 12.1

[Migration User]

Hi,

You need to contact Symantec Technical Support and create a case with them.

How to create a new case in MySupport

http://www.symantec.com/business/support/index?page=content&id=TECH58873

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

• United States: https://support.broadcom.com (407-357-7600 from outside the United States)
• Australia: 1300 365510 ([phone] from outside Australia)
• United Kingdom: [phone]

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

[pete]

if you are using SEPM 12.1 ru2, no need to use sylink replacer tool. You can do it using Client deployment wizard to replace sylink.

[Migration User]

where i get this option i am using RU3

[Migration User]

Restoring client-server communications with Communication Update Package Deployment

 

Article:HOWTO81109

|

Created: 2012-10-24

|

Updated: 2013-06-06

|

Article URL http://www.symantec.com/docs/HOWTO81109

 

[Migration User]

Where we can get failed deployment logs