This solution consists of collecting the SEPM configuration/communication settings per the Disaster recovery document, uninstalling the current SEPM install and reinstalling it. This process will result in a clean install of the SEPM, utilizing the current settings to maintain communications with the SQL server and the SEP clients. This process will retain the current SEPM/DB content, such as policies and definitions. Preparation Steps: 1. Follow the first two steps of the Disaster Recovery for 12.1 document: Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager a. Backup Existing database just in case of unexpected issues. The database backup folder is saved to the following directory: Drive: Program Files Symantec Symantec Endpoint Protection Manager data backup.

• How To Install Sql Client
• How To Install Sql Developer

Installing SEPM 11 step-by-step In this post I will show the procedure to follow to install Symantec Endpoint Protection Manager 11, console, and embedded database on a Windows Server 2008 R2 Enterprise Edition. Installing clients with Microsoft SMS 2003. If you use continuous, the server downloads the latest updates when they are posted. By default, the updates appear in the Default group's clients' content outbox folders. These folders are organized by content type. You can then pick up one or more content packages from the content outbox folder and deliver it to the client's inbox folder. Did you Install SEP 12.1 with Embedded or SQL Database? The initialization of the database is the process in which SEP Manager starts creating the database and its tables on the SQL Server. There are couple things that can be checked.

The backup can be accomplished by using the Backup and Restore utility (From the SEPM Start Menu) or inside the Symantec Endpoint Protection Manager or by using the SQL DB backup functionality. This step should be accomplished to ensure that the SQL server database is not impacted by the SEPM uninstall - install. Back up the SEP recovery file. This file contains the current SEPM configuration and communication settings. Typically this file is located at: Drive: Program Files Symantec Symantec Endpoint Protection Manager server private key backup If the SEPM Server OS is 64bit, the file path will be: Program Files(x86) Select the file with the newest file date. Disable SEPM Replication If the SEPM is part of a site that uses replication, you must disable replication before uninstalling the SEPM. Disable replication at each site that replicates.

If this SEPM is not part of a replication plan, skip ahead to 'Procedure for Re-installing the SEPM' a. Log-on to the Symantec Endpoint Protection Manager Console. Click the Admin tab, then Click the blue Servers tab at the bottoms of the pane. On the Servers tab, in the left pane, expand Local Site, and then expand Replication Partners.

For each site that is listed under Replication Partners, right-click the site, and then click Delete. In the Delete Partner prompt, click Yes. Log-off the console, and repeat this procedure at all sites that replicate data.

Procedure for Re-installing the SEPM: 1. Uninstall the current SEPM install: Control Panel Programs and Features Symantec Endpoint Protection Manager Uninstall 2. Install the SEPM using the install set provided by Symantec (i.e. Clean Install.) - Use the same version of the SEPM as was previously installed.

Run the Configuration Wizard and point it to the recovery file selected in step 1.b 4. Make sure to select 'Install an Additional Management Server to an existing site.'

If you use new site, it will override the current database selection. This is the second option on this menu. In the next screen, click Next. If the recovery file was used correctly, the next screen should display the correct SQL server information, except for the database password. Enter the correct password and press Next. The following warning prompt should appear: 'The management server name already exists. Do you want to replace it with the new name?'

The SEPM Wizard will proceed to reconnect to the SQL server. Log in to the SEPM and confirm client connectivity. Re-apply replication to the SEPM/Site as required. In some cases, the administrator will have to go in to the SEPM and re-apply policies to the assigned client groups. SEP clients designated as GUPs may need to be re-selected and re-designated as a GUP. Applies To Symantec Endpoint Protection 11.x and 12.1 SQL Data Base is used. (Not Embedded.).

If you install Symantec Endpoint Protection Manager with a SQL Server database, there are specific configuration requirements for SQL Server. Before you create the database, Symantec recommends that you install a new instance of SQL Server that conforms to Symantec installation and configuration requirements.

You can install a database in an existing instance, but the instance must be configured properly or your database installation fails. For example, if you select a case-sensitive SQL collation, your installation fails. Table: Required SQL Server configuration settings Configuration setting Installation requirement Instance name Do not use the default instance name. Create a name such as SEPM. By default, a database named Sem5 is created in the SQL Server instance when you install Symantec Endpoint Protection Manager. The default name is supported, but can cause confusion if you install multiple instances on one computer. Authentication configuration Mixed mode or Windows Authentication mode See.

How To Install Sql Client

Sa password Set this password when you set Mixed Mode authentication. Enabled protocol TCP/IP IP addresses for TCP/IP Enable IP1 and IP2 TCP/IP port numbers for IP1, IP2, and IPALL Set TCP Dynamic Ports to blank, and specify a TCP port number.

How To Install Sql Developer

The default port is typically 1433. You specify this port number when you create the database. The Symantec Endpoint Protection Manager database does not support dynamic ports. Remote connections Must be enabled. TCP/IP protocol must also be specified.

If your database is located on a remote server, you must also install SQL Server client components on the computer that runs Symantec Endpoint Protection Manager. SQL Server client components include BCP.EXE. The version number of the SQL Server client components should be the same as the version number of SQL Server that you use. Refer to your SQL Server documentation for installation instructions. During the Symantec Endpoint Protection Manager database configuration phase of the installation, you select and enter various database values.

Understand the decisions you must make to correctly configure the database. Displays the settings that you might need to know before you begin the installation process. If you install to a named instance on SQL Server 2005, the instance name is appended to MSSQL with a dot numeric identifier. For example, MSSQL. N MSSQL Data. If you install to a named instance on SQL Server 2008, the instance name is appended to MSSQL10.

For example, MSSQL10. Instance name MSSQL Data.

If you install to a named instance on SQL Server 2008 R2, the instance name is appended to MSSQL1050. For example, MSSQL1050.

Instance name MSSQL Data. If you install to a named instance on SQL Server 2012, the instance name is appended to MSSQL11. For example, MSSQL11. Instance name MSSQL Data. If you install to a named instance on SQL Server 2014, the instance name is appended to MSSQL12. For example, MSSQL12. Instance name MSSQL Data.

If you install to a named instance on SQL Server 2016, the instance name is appended to MSSQL13. For example, MSSQL13. Instance name MSSQL Data.