Within the SEPM logs or console, it can be seen that a Symantec Endpoint Protection (SEP) client is trying to register with an invalid Domain ID.
When you click on the Admin button of the Symantec Endpoint Protection Manager (SEPM) there are messages that a client is trying to register with an invalid Domain ID.
The SEPM tomcat/logs/scm-server-0/1.log files contain messages such as this:
2011-04-07 01:49:48.252 SEVERE: Unknown Exception
java.lang.IllegalArgumentException: Client is trying to register with invalid Domain ID 45A7120CC0A8ECFE013AFAC794DDE8E0 from xxxxxxxxx.
The sylink.xml file being used by one or more clients refers to a Domain ID that no longer exists. This could occur if the SEPM was reinstalled or a former Domain has been deleted.
There are two different solutions for this issue. The second solution is preferred, particularly with a smaller number of clients.
Within the Admin section of the SEPM, choose Domains. Add a new Domain and click the advanced button and enter the domain ID that the clients are trying to use. Now, delete the default domain, and rename the newly created domain to Default.
Note: Before Deleting any Domain from SEPM ensure that there are no clients reporting in that Domain, or else clients will no longer communicate with SEPM if already in that Domain!
Replace the sylink.xml file on all problem clients (using the SylinkReplacer utility) with one that is currently in use by the SEPM (found in \Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent)
NOTE: The domain ID is just an identifier related to administrative domains under SEPM, it is NOT related to windows domain groups.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.