Endpoint Protection

I recently upgraded couple of my win2003 SAV 10.x clients (behind the fiewall) to SEP 11 and now trying to connect/configure them to SEPM. they were working fine with sav client & symantec system center as firewall port 2967 was open. Now after upgrading/installing to SEP 11, new clients are not seen in SEPM 11. I work in very big comany and to get new firewall port open is a pain. Is it possible that I could modify SEP 11 client registry/settings to change its port to 2967 (which is already opened) . this way i can use same opened ports for SEP 11 too and don't have to go through the pain to request new ports open for SEP 11. I have 7 win2003 clients behind firewall . Is there any workaround like this ?  Thanks in advance

Hello,

It's a question when you're installing SEP 11 or SEP12, by default the communication port is 8014. Without communicating once your clients(for changing communication policy), there's no way known except re-installing manager and clients. You can change it when you're installing.

Regards,

Oykun

The port change needs to be done during the install. You would need to re-install to change this.

Symantec Endpoint Protection 11.x: How to Change the ports used for communication between the Manager and clients

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

Again, Ashish suggested the best one for port change... 

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

Try to check with one client.. then go for the rest....

Hi,

Prior to an upgrade you should have clear picture about ports which SEP 11 uses.

Which Communication Ports does Symantec Endpoint Protection 11.0 use?

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

Ports and Protocols to be allowed when using a proxy in a SEP environment.

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

Second thing, you should have done an upgrade to SEP 12.1 instead of SEP 11.

Check this article:  http://bit.ly/JpDR3U

In current situation could you try to replace sylink.xml on new clients & check whether it works or not.

Restoring communication to clients with a new Sylink.xml file

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