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

How to make our existing SEP client v11 communication/get update from new server SEPM v12.1

Created: 21 May 2013 • Updated: 03 Jun 2013 | 22 comments
This issue has been solved. See solution.

 

Hi all

I`ve assigned task to migrate our existing environment from SEPM v11, this server is managing over 700 SEP clients with embedded Database.

1. Our sample diagrame to describe our existing

exist.jpg

 

 

 

2. Now, i `m done for server basic steps such as server build ( 2k3), new SEPM v12 installation, embedded Database( it`s not upgrading from existing SEP V11 to V12.1 ), I assumed we also done for backup database of  SEPM v11 .

newservernewsepversion.jpg

 

 

I preferred few article from Symantec website but there are many related posts, which made me confused. 

 

My question:

 

What need to be done to make our existing clients (over 700 pc ) communicate and get update from new SEPM v12 ? is there anyway like import/export database/policy to make work done ?

I`m badly need your help for this, I really appreciate your help

Thanks so much 

 

 

 

Operating Systems:

Comments 22 CommentsJump to latest comment

.Brian's picture

You can use the new SEPM to replace the sylink file on the 11.x clients to get them to connect to the 12.1 SEPM.

See this KBA for guidance:

Restoring client-server communications with Communication Update Package Deployment

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

 

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.

Tang Bui Quoc's picture

Hi Brian81

Thanks so much for quickly response...I`ve taken a look on the link but I haven`t clear what to do yet...so what the syslink.xml belong to ? i mean this file from old server ( SEPM11 ) or new SEPM12 

I see from the article said "On the Home page, in the Common Tasks drop-down list, click Install protection client to computers."

not sure which home page  this artical mentioned ? it also does not explain this page from old server v11 or new server v12...

Could you please help to explain this ?

Thanks so much for this

Tang

.Brian's picture

The sylink file is what tells the client which SEPM to connect to.

The article references the Home page for the 12.1 SEPM. You can push a new client install from the 12.1 SEPM to your 11.x clients if you wish.

I'm not sure how you currently upgrade clients. Do you use the SEPM or some other third party method?

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.

Tang Bui Quoc's picture

By the way, do I have to backup old database on existing SEPM v11 then restore on new SEPM v12 ?

Thanks

.Brian's picture

It is not possible to directly restore an 11.0 backup on a 12.1 system - the recommended steps are to restore on a new 11.0 SEPM install, then upgrade to 12.1.

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.

Tang Bui Quoc's picture

I had new SEPM 12 installation on new server... so replacing Syslik.xml will be resolution for me, is that right ?

Can you please help to explain some points on my question for replacing syslink ? I`m not aware of what syslink ( file from old version or new version ) should be work on, also not currious that what "Home page" on the artical, it seemed not be Console page

 

Great thanks

.Brian's picture

Yes, you need to replace the sylink file on the 11.x clients with one from the 12.1 SEPM.

If you log in to the new 12.1 SEPM you will be on the Home page. At the top under Common Tasks click the dropdown and select Install protection client to computers.

This will bring up the Client Deployment Wizard

Check the radio button for Communication Update Package Deployment

If you have your groups set up on the 12.1 SEPM than select which group you want the old 11.x clients to land in. If you have a password set to stop the smc for the 11.x clients than enter it in.

Select the radio button for Remote Push

Than you can search the network for the 11.x clients, once they show up you just need to push out the new sylink file and once replaced they will start reporting to the new 12.1 SEPM.

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.

technical_specialist's picture

Hello,

If you only require to communicate all existing client to new Server, Replace the sylink file is best practise.

Sylink is file which can help to communicate client with Server.

But you have not mention your current version of SEP clients?

Is it 11.x or it 12.x?

If it 11.x then you can upgrade the clients in 12.1 version.

For the upgradation of Client version

https://www-secure.symantec.com/connect/forums/best-practice-upgrade-sep-11x-clients-sep-12x

 Best practices for upgrading to Symantec Endpoint Protection 12.1.2

 

Article:TECH163700  |  Created: 2011-06-30  |  Updated: 2013-01-02  |  Article URLhttp://www.symantec.com/docs/TECH163700

 How to upgrade Symantec Endpoint Protection clients by using Auto-Upgrade

 

Article:TECH96789  |  Created: 2009-01-14  |  Updated: 2012-06-04  |  Article URLhttp://www.symantec.com/docs/TECH9678

 Client Deployment Wizard - SEP 12.1

 https://www-secure.symantec.com/connect/articles/client-deployment-wizard-sep-121

https://www-secure.symantec.com/connect/articles/upgrade-clients-sep-121-auto-upgrade-feature

Tang Bui Quoc's picture

Thanks ...You are brilliant,

I see what the artical said now, I will test with it tomorrow if have any barrier come up then come here to get help

Thanks so much

.Brian's picture

Sounds good. Check back in to update status.

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.

Tang Bui Quoc's picture

Hi technical_specialist

Our current SEP client are v11., we might need to upgrade them up to v12 before decommission old sepm v11, then replace syslink.xml . 

 

Thanks so much

.Brian's picture

You can push the upgrade from the 12.1 SEPM to the 11.x clients if you wish. That way you won't need to replace the sylink.

How to upgrade Symantec Endpoint Protection clients by using Auto-Upgrade

Article:TECH96789  |  Created: 2009-01-14  |  Updated: 2012-06-04  |  Article URL http://www.symantec.com/docs/TECH96789

 

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.

technical_specialist's picture

Hello Tang,

If you can upgrade your client then there is no require to replace the sylink file. Because it can directly communicte with new Server.

technical_specialist's picture

Hello Tang,

This link help you to create the client package of 12.1

How do I create and configure a custom Symantec Endpoint Protection installation package in version 12.1?

https://www-secure.symantec.com/connect/articles/how-do-i-create-and-configure-custom-symantec-endpoint-protection-installation-package-vers

You are using fresh SEPM server of 12.1. So push deployment wizard is the best solution for upgrade the clients

Push Deployment Wizard helps to deploy client software by pushing the client software to remote computers and automatically installing it. IT only require admin access for deploying

https://www-secure.symantec.com/connect/articles/overview-push-deployment-wizard-symantec-endpoint-protection-121

Client Deployment Wizard - SEP 12.1

 https://www-secure.symantec.com/connect/articles/client-deployment-wizard-sep-121

How to Deploy Symantec Endpoint Protection to your client computers using the Migration and Deployment Wizard.

 

Article:TECH102907  |  Created: 2007-01-14  |  Updated: 2013-01-08  |  Article URL http://www.symantec.com/docs/TECH102907

 

SOLUTION
Mithun Sanghavi's picture

Hello,

In your case, there are 2 steps which you would have to work on.

1) Export and Import all the policies from the older SEPM server to the Latest SEPM server. Check this Article on how to perform the actions -

How to export/import an existing Symantec Endpoint Protection policy

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

Before importing a policy, make sure the source computer's version of Symantec Endpoint Protection matches the computer's version you are importing to.

Note: You can migrate the source computer to a newer version before exporting the policy to avoid this problem.

Reference: http://www.symantec.com/docs/TECH163090

2) To get all the 700 clients report to the new SEPM 12.1 server, you can perform either of the following steps -

SylinkReplacer Utility - This utility would assist you to replace the Sylink.xml file to all the 700 clients remotely.

OR

Perform the steps provided in the Articles below:

Restoring client-server communications with Communication Update Package Deployment

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

SEP 12.1 RU2 and Reset Client Communication

https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication

How to point clients to a new SEPM after decommissioning or replacing the primary SEPM.

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

SylinkReplacer for SEP 12.1 is only available with Symantec Technical Support Team.

Create a case with with Symantec Technical Support Team.

How to create a new case in MySupport

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

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

  • United States: 800-342-0652 (407-357-7600 from outside the United States)
  • Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
  • United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Tang Bui Quoc's picture

Thanks everyone so much,

I`ve taken the look on replacing syslink.xml solution ... but I experienced with this message

error.JPG

my existing sep client is not listed on new SEPM v12.1 after that... We had password protection and I provided it during replacing, not sure why i have this barrier

any recommend for this ?

Thanks

Tang

 

Rafeeq's picture

check the windows firewall and UAC, both should be turned off during the remote push

Tang Bui Quoc's picture

Eventhough I replace for Window server 2003, fireware was off but I still have the same message

Do you think Syslinkreplacer might fix this ?

 

Thanks

 

 

Rafeeq's picture

on how many machines you are facing this? 

if you have handful of them left you can  manually replace the Sylink. 

Or call support they will provide you the sylink replacer tool for 12.1

Tang Bui Quoc's picture

I`m in testing phase with replacing sylink.xml for a few machine

I`ve created ticket to support yesterday, hope I will get response soon

Thanks

 

technical_specialist's picture

Hello,

May be you are trying to replace the sylink of 11.x client in 12.x Server using 12.1 RU2 Deployment wizard. That is the reason to getting this error

For this you can choose

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

Because 11.x clients sylink path is different and different sylink replacer for 11.x version.