The default sylink.xml packages are missing the <preferred group= GroupName> tag that tells the client where to register. See-

http://service1.symantec.com/SUPPORT/ent-security....

Does this help?

Thomas

That is what I have done.  I am using MR4 - and chose Export Communication Settings.  Upon export I save the My Company_Laptop_sylink.xml file.

After I sylinkdrop this onto the client, the sylink.xml file shows :
<RegisterClient PreferredGroup="My Company\Laptop" PreferredMode="1" />

However the client GUI and SEPM still shows it located within the old group.

Did you read the best practice for moving clients using the SEPM?

http://service1.symantec.com/SUPPORT/ent-security....

I need to do this on a scripted basis - so I need to use sylink.  I have read the following article:

http://service1.symantec.com/SUPPORT/ent-security....

Is there any way to get around having to delete the client from the console - prior to running sylink?

---snip
Right-Click on the clients that you selected and click Delete.
---

 
The utility is designed to move clients from one SEP Manager to a different SEP Manager.  It is not designed (nor will it) move clients within the console from one group to another.  Thus, if you want to use it to move clients from one group to another, you have to delete it from the console first so it will re-register with the client just as the article suggests.   

So what I am hearing is that there is no way to script this?  It used to be easy with the grc.dat file.

Is there anyone out there that has been able to figure out a way to automate this process?

As per Cycletech.. you have to right click the group where you want to put the client to...
Thant is also what I had been doing... from there you access the export communication settings...

thanks..

We are also using the same method as Cycletech has explained in his post

Regards,
Peter

Here is a script that will update the files remotely: http://www.fishandscripts.com/?p=23 

I built it using an active directory export as my input file for a psexec batch script.