Replacing Sylink.xml doesn't automatically move client to new group
Created: 16 Dec 2011 | 13 comments
If you want to move a computer to Group A, you replace it with Sylink.xml exported from Group A.
However, I find on numerous computer, this doesn't work.
Below are steps
Stop SEP
Replace the Sylink.xml
Start SEP
When I open SEP console, it still shows it is in old group. When I go into SEPM, I see computer in the old group with a green dot.
The only way I can successfully move the computer to group A is to delete the computer from the old group, restart SEP on the computer, then, finally it joins group A.
Is this a software bug?
By the way, we are on RU7, MP1
Discussion Filed Under:
Comments
it is recommended to move
it is recommended to move clients using the SEPM console.
Also check is the supposed group is not allowing new clients to join the group.
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Delete those old entries
Delete those old entries first from sepm if already exsist .
2) replace sylink and do update policy should have green dot and in sepm should be reporting to correct group
try on few machines first .
Swapnil
SOC Team .
Please don't forget to mark your thread solved with whatever answer helped you.
You cannot use a sylink file
You cannot use a sylink file to move a client from group A to group B. It simply does not work and is not supported.
As pete said, it's best to move computers in the SEPM by right clicking on the client and choosing "Move"
In other words, sylinkdrop
In other words, sylinkdrop and sylinkreplacer are not supported by Symantec?
From what I understand, it is an automated way of stopping the service, replacing the sylink, and restarting the service.
its for convenience the tools
its for convenience the tools have been provided.
I believe the GUI is best way to do that instead of using manual method on client side.
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
I'm not sure about the
I'm not sure about the support but if you wanted to migrate current SEPM server to new server (clients migration) both sylinkdrop (if you have SNAC, it will use HI policy) & sylinkreplacer (required in same Domain i believe?) will be suggested.
Hi dear, Sylink.xml holds the
Hi dear,
Sylink.xml holds the communication configuration from server to client or vice versa, same file guides to client that which server is responsibble to provide you updation.
Sylink.xml file is not using to move the client from one group to another.
Regard
Sunny Chauhan
Questions and Suggestions
Hello,
Could you let us know:
1) Is there a Replication set on the SEPM?
2) Is there are AD Integration Set on the SEPM?
3) Are you manually replacing the Sylink OR Using Tools like SylinkReplacer or SylinkDrop to Replace Sylink?
Try Moving Clients using these Steps:
OR ELSE
Work on the Steps provided in the Articles below:
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | SCTS | ITIL v3
Follow me on Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helped yo
1) Is there a Replication set
No replication
No AD Integration Set
Yes, I was stopping smc, manually replacing sylink, then starting smc.
Hi
Do the following steps and revert if it solves your issue.
1. Stop the SMC on affected client system.
2. On SEPM Console deleted the duplicate entry.
3. Gone to registry by going to following location HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\Sylink\Sylink
4. Cleared the Hardware ID.
5. Gone to C:\Program Files\Common Files\Symantec Shared\HWID.
6. Finded the "sephwid.xml" and Rename it to "sephwidxml.bak"
Regards
What is the acctual status of
What is the acctual status of Client system. Share the snapshot.
Regard
Sunny Chauhan
Hi Rasaka
Kindly clear the step that your system is showing online in SEPM or not??
If it showin online then simple move the Required Group.
If it showing offline then stop the smc service
delete the Hardware ID files
Path:- Remote System\Hkey_local_machine\Software\Symantec\Symantec Endpoint Protection\SMC\SYLINK\Sylink\(HardwareID)
Delete the Sephwid.xml
Path:- C:\Program Files\Common Files\Symantec Shared\HWID
then Restart the service and check it.
Hope it help you
Regard
Sumit G.
Hi Rasaka- Your issue resolve
Hi Rasaka- Your issue resolve or not?
Regard
Sumit G.
Would you like to reply?
Login or Register to post your comment.