Endpoint Protection

Long story, short.  I uninstalled a seemingly corrupt installation of the SEPM which already had a few groups each containing a few computers.  After I reinstalled SEPM, I can add in the old clients but they don't ever seem to communicate/sync up with the server.  I have tried to update the policy from the Client, tried to manually add in clients, tried to reinstall the client via Migration and Deployment Wizard which is what I used the 1st time and I even ran a searh on unmanaged clients.  While the search works great, these computers happen to be managed from the previous installation so they won't show up on an unmanaged search. 

I am pretty sure I could do a complete uninstallation of the Client then reinstall via the Manager but I don't get why I can find unmanaged computers and have my way with them when I can't find managed ones and do the same.

Any help/Ideas would be greatly appreciated.

This is something I put together from posts in this forum.

I found a thread in Symantec's forum on making an unmanaged agent managed.

First, find sylink.xml in the following directory: E:\Program Files\Symantec\Symantec Endpoint Protection manager\data\outbox\agent\  There are several random character folders that hold the client builds, each folder having its own sylink.xml.  I picked one at random figuring I can control the group membership once things link up.

On the client you need to run a command prompt

Change directory to the client install directory.  The directory Symantec mentioned was: C:\Program Files\Symantec\Symantec Endpoint Protection  My client is installed at: c:\Program Files\Symantec Antivirus due to being an upgrade from an older version.

From the command prompt run the following commands

Smc -stop

Over write the symlink.xml in the client directory with the one from the server.

Now run this command

Smc -import symlink.xml

Smc -start

The client should now be registered with the server.

Open the client and Choose Help and Support / Troubleshooting.

You can now see what group your client is assigned to.

My client was assigned to the Temporary Group.  I then moved it with the consol to the IT Test Group.  Clicking on Update or Update Policy makes the client pull down new settings from the server.

Worked like a charm!  Thanks Matt :smileyhappy:

Hey Steve,

I just wrote a little batch file that I had all my users kick off in order to make my life easier.  Use Matt's guide to create it.

This is assuming a few things.  1) Your installations were installed onto C Drives and default location  2) You have a network shared location that the file Sylink.xml can be centrally located wgich all workstations have access to.  3) You have copied the Sylink.xml from the SEPM directory and placed it in your share location(This is explained in Matt's response).  Text in bold is what you want in the .bat file although not exact depending on your setup.

c:
cd \"Program Files"\"Symantec Antivirus"\ 
This could be cd \"Program Files"\Symantec\"Symantec Endpoint Protection"\  If you didn't upgrade your installations from Symantec Antivirus like I did.  Either way you need to be in the programs directory on the local computer.
Smc -stop This stops your Anti-Virus service.
copy "Your shared network drive"/Sylink.xml C:\"Program Files"\"Symantec Antivirus"\ Again this could be \"Program Files"\Symantec\"Symantec Endpoint Protection"\.
Smc -import symlink.xml Imports the new file into Endpoint Protection.
Smc -start Restarts the Anti-Virus server.

Hello,

I'm having this problem as well--clients are not showing up in the SEPM console and are not getting updated. I've tried to install clients using the deployment wizard method and via the find unmanaged computers methods. The only client that is showing up in the console is the one that is running the SEPM console (local machine).

I have tried the above sylink.xml method with numerous clients, have experimented with creating new client packages with both push and pull installs, and have even reinstalled both the server and client with no better results.

Does anyone have any other suggestions?

Thank you.

 http://data.versiontracker.com/drivers/autoExtract/aopen/pub/nb/1945/driver/winxp/Copy%20(59)%20of%20wireless_ext/extract/Wireless/Client%20Manager/README.TXT


browse this link..!!