Endpoint Protection

Just need a simple process for doing this not some 15 step procedure wherein step 11 is "A miracle occurs". If no one knows I'll just uninstall the client and re-install from the new server.

Hi,

       The sylink.xml file is the file which has information as to where and which server should the client report. Replacing this file is a one step process for moving a client from one SEPM to another.

There is another method mentioned in this link.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009022414415348

But it Aint.
The link offers 3 methods
Method #1 Does Not Work
Method#2 I don't have the sylinkreplacer program
Method#3 Step #9 is "A miracle occurs" However I think I figured it out, the sylink.xml file is actually located at c:\program files\Symantec Antivirus.As soon as the users fingers leave the keyboard I will try stopping SMC and replacing the file.

Hi,

Method 3 is provided for an individual client. So that you wont have to go through a long procedure for 1 client.

As far as method 2 is concerned, you can contact support and we will provide you with the sylinkreplacer tool that you can use for replacing the sylink.xml file on multiple computers.

Did you actually, create a new installation setting, export a package with that setting and deploy it on the client, or speaking from a previous experience?

Cheers,
Aniket

Speaking from previous experience. That method only works on a new install not on any of our upgrade installs. Wonderful waste of time though.

I did not mean to sound offensive in my last comment. Just wanted to know more details about your deployment method.

The method of deploying a package on existing clients should point them to the new SEPM.

If creating an install setting and deploying a package with it, fails to point that client towards the new SEPM, then that's something needs attention. When you include the installation setting in a package, it also includes a new sylink.xml file that will help the client to be moved to the new SEPM.

You can refer to the link below for obtaining the sylinkreplacer tool:

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

Cheers,
Aniket

Hi burningtower easiest way to do this is the method used by said by aniket, but before you do this please inspect the sylink.xml, and please make necessary changes if needed (eg. groups) then restart the client.

Your link for obtaining the sylinkreplacer tool gives a "you're not authorized" message.

That's because some tools are on a "ask and you shall recieve basis."

So why bother posting a link if you have to ask for permission?

Simply export the communication settings from the new SEPm and import that into the managed client of other SEPM. The client will response to the sever according to the sylink present in the client.

By the wayu Aniket should have not been marked Offensive if he says so, cuz when u ask a solution it ur duty to properly explain the issue and ur plan of action.

Paul,
"please inspect the sylink.xml, and please make necessary changes if needed "
I have been told, and read in official instructions somewhere, to never, ever try to edit a sylink.xml file as I might mess up the whole magilla. Are you saying that it's okay to edit the file?

The link you provided does not work.
Contacting support involves investing at minimum 45 minutes on hold. I can uninstall and re-install the client in 10 minutes.
I was just asking if there was an easier/quicker way to change from one management console to another.

just edit for the groups if needed, if you edit the server names, by experience it will not work.

For the test, please try the Sylink Replacer Tool,  it is better to receive the Tool from Symantec Support that's why I suggest you to create a case for it.
They can also give suggestions with your situation.

The tool is recommended for big clients (ex, 200+ clients) instead of reinstalling them 1 by 1 then reinstall, the tool is used.

The link for downloading the tool is available now.  [  https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm ]

Aniket

The old SEPM was on Domain1, the client is still on Domain1, the new SEPM is on Domain2 and I have to log on to it as domain admin Domain2,there is a trust relationship between the domains but I'm getting an access denied message from the client when I try to use sylink replacer. I'm guessing that I'd have to log into the new SEPM as domain admin in Domain1 in order to do this and then I'd lose access to all the clients in Domain2. There doesn't seem to be any issues installing the client across domains, as long as I log into the client as an admin.