Symantec Endpoint Protection 11 Client reverts to old group after being moved to new group with SylinkDrop

Article:TECH105886

Created: 2008-01-12

Updated: 2012-11-26

Article URL http://www.symantec.com/docs/TECH105886

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

SylinkDrop.exe was used to move a client to a new group, but when the client checked in it appears back in the original group.

Cause

When a SEP 11 client is moved manually (or with the SylinkDrop or SylinkReplacer tools), it must first be deleted from Symantec Endpoint Protection Manager (SEPM). After the client has been deleted, use the SylinkDrop tool or SylinkReplacer tool to apply the new Sylink.xml. The database still has a reference for the client belonging to the original group, so when it checks in, the database places it into the group where last knew the client to exist. Another way of interpreting this is that clients cannot dictate what group they belong to: instead, the manager determines group membership as it is based off a record in the database. That record must be expunged before a new group assignment can be applied.

Solution

Delete the client from the Symantec Endpoint Protection Manager and then drop the new sylink.xml file.

For detailed instructions see How to move Symantec Endpoint Protection clients to a different group...