Endpoint Protection

After updating SEP to 12.1 RU1 MP1 we cannot move clients to other group by using sylinkdrop.exe. Clients can move only from the SEPM console. 
We change sylink.xml ​​according to the instructions described in the article:
http://www.symantec.com/business/support/index?page=content&id=TECH157585
Has anyone met this problem in version 12.1? In version 11.0.7 it worked without a problem.

Regards

Tom

HI,

Do you have export sylink.xml for particular group ?

 

Hi, yes of course (Right-click the desired group (e.g. Default group) and choose Export communications settings.)

Hi,

Check try to only one sep client change sylink.xml .

What happend if you try Method 2 ?

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

 

I tried all supported methods described in the article, but without effect. SEP client still does not change the group. There are no error messages.
Even reinstalling client did not help.

 

HI,

Remove old comments ...

Edit

Check this thread

https://www-secure.symantec.com/connect/forums/sylinkxml-updated-client-not-changing-groups

IF sepm is AD integration you cannot move the client

Check this thread also

How to move client group1 to group2 after replacing sylink.xml from group2?

https://www-secure.symantec.com/connect/forums/how-move-client-group1-group2-after-replacing-sylinkxml-group2

 

SylinkDrop or SylinkReplacer fails to assign Symantec Endpoint Protection clients to a new Client Group

 

if you are importing from ad, 

delete the OU

and reimport the OU, 

you wil find the clients in right group

Just to clarify, you are trying to move your clients into different groups on the same SEPM, is that correct?

If so, swapping the sylink file will not cause the client to changes groups, even if you are not using AD sync (the hardware ID of the client is already linked to the group within the SEP DB).  Within the Sylink, only the Preferred group is defined, which is only used if no record for the client already exists in the SEPM.  If a client is already talking to the SEPM, then it ignores the preferred group field in favour of its actual group in the SEPM structure.

The only way to move clients around when they are already talking to the SEPM are:

• Manually via the console
• Using AD Sync
• Using the moveclient.vbs script

More on the moveclient utitlity below:

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

 

Thank you all for your replies. Check and let you know.

Hi, Tom I encountered similar problem and noticed that after first replacement file SyLink.xml, the SEP client changes its size and internal structure regardless of how change. If then again to stop SMC, manualy delete files SyLink.xml, SyLink.bak, SyLinkEx.bak, copy correct version Sylink.xml and start SMC, then SyLink not distorted and SEP client work correct. Regards, ubi40

Just to clarify, you are trying to move your clients into different groups on the same SEPM, is that correct?

Correct.

If so, swapping the sylink file will not cause the client to changes groups, even if you are not using AD sync (the hardware ID of the client is already linked to the group within the SEP DB). Within the Sylink, only the Preferred group is defined, which is only used if no record for the client already exists in the SEPM. If a client is already talking to the SEPM, then it ignores the preferred group field in favour of its actual group in the SEPM structure.

Understand. So the tool "sylinkdrop" is used only to change/restore client communications settings, and not to change the group, right?
I also understand that such changes were introduced in version 12.1, because as I wrote in the version 11.x by using sylinkdrop we could move clients to other groups without any problems.