- #MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER INSTALL#
- #MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER UPDATE#
- #MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER UPGRADE#
- #MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER PRO#
#MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER PRO#
#MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER UPGRADE#
Then we will upgrade the new server to 12.1.2.
After the successful Migration, uninstall SEPM from MACHINE_1 Delete the Replication Partner from MACHINE_2 SEPM: Click on the Admin button | Under View Servers, Expand Replication Partners and select the partner to delete | Under Tasks, choose Delete Replication Partner | Type Yes when asked to verify deletion of the replication partner.ġ7. Once verified that all the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.ġ6. Stop the "Symantec Endpoint Protection Manager" and "Symantec Embedded Database" service on MACHINE_1 to verify whether all clients now report to the new SEPM on MACHINE_2ġ5. Add MACHINE_1 under Priority 2 and add MACHINE_2 under Priority 1, and assign this New Management Server List to all the groups.ġ4. Click Add> Priority and a new Priority would get added named as "Priority2"ġ2. Click Policies > Policy Components > Management Server Lists > Add Management Server Listġ1. Log in to the new SEPM on MACHINE_2 and ensure that all the clients and policies have Migrated successfully.ġ0. In the Database Server Choice panel, do one of the following, and then click Next:Ĭheck Embedded database or Microsoft SQL server (whichever database type you'd prefer to install), then complete the installation.ĩ. In the Certificate Warning dialog box, click YesĨ. The password used to log on to the old console.ħ.
The Username used to log on to the old console. In the Replication Information panel, type values in the following boxes: In the Site Information panel, accept or change the name in the Site Name box, and then click Nextĥ. In the Server Information panel, accept or change the default values for the following boxes, and then click NextĤ.
#MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER INSTALL#
In the Management Server Configuration Wizard panel, check Install an additional site, and then click Nextģ. The new management console can be migrated to a newer version once the transition is complete.Ģ. NOTE: The version installed to the new server must be the same version as on the old server. Install Symantec Endpoint Protection Manager on MACHINE_2 Since we are going to change the server name and IP, we are looking at the replication option which involves the following steps:ġ. Thanks for the info. I was having trouble getting into the forums when I was researching as well. I just want to make sure we do this right the first time.
#MIGRATING SYMANTEC ENDPOINT MANAGER DATABASE TO SQL SERVER UPDATE#
Has anyone had any issues migrating to a new server in this kind of scenerio? What steps did you follow exactly from start to finish? Did you just setup the new server and run the Communication Update Package to connect existing clients (Home > Common Tasks > Install protection client to computers)? Do we just backup the database from the old server and import it into the new? We want to take advantage of the Communication Update Package to connect existing clients to the new SEPM server that is part of the 12.2 version, 12.1 and lower do not have that option, you have to use another method to update the clients. We want to upgrade to 12.2 so we plan to install it fresh on a new Windows 2008 R2 圆4 server. Here is the scenerio: We have 700 clients and currently have SEPM 12.1 on a Windows 2008 圆4 box. There are many options on the Symantec site to migrate SEPM 12.1 to a new updated 12.2 install on a new server and I would like to know what worked best for you?
0 kommentar(er)
