Error: Client is trying to register with invalid Domain ID
Updated: 21 May 2010 | 6 comments
I've install SEP 11.4200. deploy all clients smoothly. but when i login into the SEP manager under domian field i saw the following error message.
September 30, 2009 3:18:12 PM BDT: Client is trying to register with invalid Domain ID A3678E2D9E18770301A65CF71FB261BD from Agr-SM08. [Site: My Site] [Server: CTGMXSVR02]
what should i gonna do. plz help
discussion Filed Under:
Comments
Try by replacing sylink file
Try by replacing sylink file in client
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Can check any error in
Can check any error are present in scm-server-0.log or in IIS log files
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
The sylink.xml file being
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 Endpoint Manager was reinstalled or the former Domain deleted.
Replace the sylink.xml file with one that references a valid Domain ID.
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
You also can use below
You also can use below article for replacing sylink.
How to run the SYLINK REMOTE to Replace the Sylink Remotely
https://www-secure.symantec.com/connect/articles/h...
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
This happends when SEPM is
This happends when SEPM is re-installed and clients look for same domiain ID,
In SEPM
Rename default Domain name to something else like Default1 then
ADD this domain ID A3678E2D9E18770301A65CF71FB261BD name it default
then click on Administer Domain
All the clients will start communicating with sepm.
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
When this happened on my
When this happened on my installation I'd uninstalled and reinstalled SEPM. The syslink.xml process didn't work so I uninstalled my clients manually and then deployed from SEPM anew. They registered with the proper domain ID.
Would you like to reply?
Login or Register to post your comment.