Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Moving SEP 11

Created: 26 Aug 2014 • Updated: 27 Aug 2014 | 5 comments
This issue has been solved. See solution.

Hopefully someone here can shed some light on this for me, i curently have SEP 11 on an old 2003 server, want to move to a new server, when i go thru the cinfig server wizard and select site name, port, replication server, it fails to connect to the old server, i also cannot logon to the console,,i am using the same admin credentials.

 

part 2..if i just do a install and dont say additional site, just a new site, i logon ok but the oush client fails..is this because i am taking the db default (sem) ? do i need to specify something different...i have no prob removing the client by hand, i only have 40 pc's

 

thoughts? ideas ??? suggestions ??

 

Thx

Operating Systems:

Comments 5 CommentsJump to latest comment

.Brian's picture

See here:

How to move Symantec Endpoint Protection Manager from one server to another server

http://www.symantec.com/docs/TECH199292

With only 40 clients, it may be quickest to install a fresh 12.1.4.1 SEPM and move the clients over to it by replacing the sylink. You can do this from the 12.1.4.1 SEPM.

See here:

Restoring client-server communications with Communication Update Package Deployment

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Trapps's picture

i underestand all of that,,however, if i do a clean install on another server with diff ip and diff name, and set it up as a new site, NOT ADDITIONAL, i can logon, but cliet push fails !!  why ??? i am juat taking the defaults for the port and the database....what am i doing wrong ???

MichaelD50's picture

Since we don't know what your version of SEP 11 is (and it really doesn't matter since it will soon be End-of-life) and you only have about 40 clients, why don't you just install a shiny fresh SEPM 12.1 RU4 MP1a and reconnect your clients to the new manager with a sylink.xml or a 12.1 install package with a custom client install setting that will "reset communications"?

Just a thought!

MJD

P.S. The link from .Brian only works from a 12.1 SEPM to 12.1 SEP clients

AJ_01's picture

You are require to open the ports for the SEPM server to manage the client on new server.

Which communication ports does Symantec Endpoint Protection use?

Article:TECH163787  |  Created: 2011-07-01  |  Updated: 2014-06-18  |  Article URL http://www.symantec.com/docs/TECH163787

You can install the new SEPM and create the policy as similar with old server. Either export from old to new.

Then use the client server communication restoration to communicate the client with new Server.

Restoring communication to Symantec Endpoint Protection clients with a new Sylink.xml file

Article:TECH106288  |  Created: 2008-01-17  |  Updated: 2012-06-07  |  Article URL http://www.symantec.com/docs/TECH106288

 

Restoring client-server communications with Communication Update Package Deployment

Article:HOWTO81109  |  Created: 2012-10-24  |  Updated: 2013-10-07  |  Article URL http://www.symantec.com/docs/HOWTO81109

Regard

AJ

SOLUTION
Trapps's picture

Thx for all the help !