Video Screencast Help

How to change the Communication file - please see attachment.

Created: 16 Aug 2013 | 6 comments

I am trying to move a pc from one manager to another by replacing the comm settings file. But when I select Import I get the message that “this function is not supported on a managed client”.

How/where do I change the settings to make this option available.

 

Please see attachment.

 

 

Operating Systems:

Comments 6 CommentsJump to latest comment

.Brian's picture

If you're running 12.1 RU2, you can easily do this from the SEPM. See the instructions here:

Restoring client-server communications by using a client installation package

Article:HOWTO81455  |  Created: 2012-10-25  |  Updated: 2012-12-20  |  Article URL http://www.symantec.com/docs/HOWTO81455

 

I believe you can only use the Import option if this was an unmanaged client and you wanted to make it managed. Otherwise, you can use the method above. Or just use sylinkdrop.exe for a single client. It is in the Bin directory of where the client is installed. C:\Program Files\Symantec\Symantec Endpoint Protection\<version>\Bin

If x64 than will be in Bin64 folder

 

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.

Mithun Sanghavi's picture

Hello,

In case of SEP 12.1 RU2, you can get the client communication by following the steps below:

Why do I need to replace the client-server communications file on the client computer?

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

Restoring client-server communication settings by using the SylinkDrop tool

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

Restoring client-server communications with Communication Update Package Deployment

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

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.

MichaelD50's picture

MzSolo,

What you are describing makes me think your SEP client is SEP 11.x.

The "Import" button in a 12.1 client should not give that error.

MJD

Chetan Savade's picture

Hi,

Thubms up to MichaelD50 advice & Thank you for posting in Symantec community.

Could you please specify the SEPM and SEP client verison details.

Total how many clients have to move on the new SEPM?

Refer this article if number of clients are large in numbers.

Hot to move SEPM from one server to another server.

https://www-secure.symantec.com/connect/articles/hot-move-sepm-one-server-another-server

 

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

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