Clients reverting to the old SEPM after SEPM moved to a new server.

book

Article ID: 157910

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

After migrating Symantec Endpoint Protection (SEP) clients to a newly built Symantec Endpoint Protection Manager (SEPM) the clients are reverting back to the old SEPM.

 

Cause

The default policies encourage Clients to connect to the server they last successfully communicated with.

 

Resolution

*This method is intended for when all other methods have failed.*

Create a new Management Server List which specifies only the new server and over-write the reconnection preferences.

1.From the Management Console open the Policies tab, drop-down the Policy Components box and click Management Server Lists. Then Add a Management Server List.
 

2.Name the new list as desired and add a New Server under Priority 1.

3.Add one entry with the IP address of the new server and one with the Hostname of the new server and click OK.

4.Now Right-Click your new Management Server List and click Assign. Check the boxes for each group in the dialog that pops-up and click Assign.

5.From the Admin tab, click Install Packages. Select the Client Install Settings and click Add Client Install Settings.

6.In the dialog that opens; Name your new Client install settings as desired, check the box to Remove all previous settings and click OK.

7.From the Clients tab click Add a Client.

8.In the dialog that opens choose New Package Deployment and click Next.

9.Select the appropriate options for your environment and from the Install Settings Drop-down box select the new Install Settings we created in Step 6 and click Next.

Complete the process by deploying the new package in the manner appropriate for your environment.
(For assistance see: http://www.symantec.com/docs/TECH204046)

 


Applies To

Symantec Endpoint Protection 12.1

Attachments