Endpoint Protection

Hi,

I accidentally added one SEP client to the wrong domain in my sepm server. Is there a way of moving it over to a different domain (not windows domain, but domain of the sepm) without having to manually uninstall it and then reinstall?

Thanks for any help!
Chris

you need to just replace the sylink file on the client follow this document

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/52d862c54842f5b68825733d005ce48e?OpenDocument

if you want to move client from Domain A to Domain B;
follow these steps
take a sylink.xml file from a working client domain B ; you can find that in c:\program files\symantec\symantec endpoint\sylink
got to domain a client
start run smc -stop
put the sylink file in the same path as above
start run smc -start

you can use the above document to find the correct sylnik file

Sounds promising, I will try that and report back. Might take a while though. Thanks!!!

What if you don't have physical access to the machine?  Isn't there a way to perform the transfer from within the console?

You cannot do it from the console ..however you can remotely replace sylink.xml on the client using Sylink Replacer

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

Thanks for the reply.  Is the Sylink Replacer the officially sanctioned means for transferring clients to different domains?  Also, doesn't it require that I input administrative credentials for the machines?  What if I don't have them?  What if I have 1000 users that need to be transferred to a new domain or multiple different domains?  Do I have to instruct every one of them to run some utility?

Also, not to be mean, but I find the Sylink Replacer extremely grating to use and therefore out of the question for distribution to end users.  Is there documentation somewhere such that I could write my own app for transferring clients?  For example, what services must I shut down in order for some watchdog app not to restart them automatically?  Modifying sylink.xml is almost trivial after the issue of the file lock has been resolved.

You have to stop SMC service replace the sylink.xml files and start the service..

However In the Domain environment you will only use 1 Admin Credential for all the clients.

Sylink.xml is the communication files that has all the information about the SEPM.

So SylinkReplacer is a handy tool for many purpose for changing from Unmanaged to Managed, From Moving 1 SEPM to Another..etc

This should really be built into the console in my opinion, but at least it can be scripted.  The main issue is that the service is NOT_STOPPABLE.  Luckily, that can be addressed as well. Instructions (tested on Win7):

1. Open elevated/administrator command prompt
2. SC CONFIG SmcService start= disabled
3. TASKKILL /F /IM smc.exe
4. Copy desired new Domain ID from SEPM
5. As administrator, modify SyLink.xml.  Replace DomainId="..." attribute of ServerSettings element with the new DomainId copied from step 4.  Save changes.
6. SC CONFIG SmcService start= auto
7. SC START SmcService

Client should now appear in the new domain.

https://www-secure.symantec.com/connect/blogs/easy-way-replace-sylinkxml-sepm