You can re-deploy a new Install Package to those workstations (ensuring the Communication Reset option is flagged) or acquire our SylinkReplacer Utility from Symantec Support.

These two documents will help you out with the Install Package method.:

Title: 'How to to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.'
Document ID: 2008052008163148
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052008163148?Open&seg=ent

Title: 'How to Deploy Symantec Endpoint Protection to your client computers using the Migration and Deployment Wizard.'
Document ID: 2007111409432848
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111409432848?Open&seg=ent

-or-

Call us to create a Support Case/Create a case yourself using MySupport and request the SylinkReplacer utility.

Title: 'Using the "SylinkReplacer" Utility'
Document ID: 2008062412271448
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008062412271448?Open&seg=ent
 

http://www.symantec.com/enterprise/support/contact_techsupp_static.jsp

-or-

https://mysupport.symantec.com/

Hope that helps!

Hi David

Thanks for the suggestions.  I elected to re-deploy using the Migration & Deployment wizard.  The wizard appear to have executed successfully, but the clients still aren't appearing in SEPM after about an hour.  It is possible that this is because I didn't set the Communication Reset flag - I didn't know where to find it.  If you think this is still the problem, please tell me where to set the flag.

Regards

Andrew

Andrew_H , in MP3 MR3 versions in console SEPM such phenomenon can be observed at various browse modes. Choose browse mode of clients "Default view" and press to update. Clients became visible?

I'm afraid not

try using they sylinkdrop.exe utility to update the sylink file on 1 client.  If it shows up in the console after that (shouldn't take more than a minute or two), I would ask for the sylinkreplacer utility mentioned earlier in the thread.  BTW--I haven't used sylinkreplacer myself, I've only used SMS and a script to update clients with the sylink file.

Andrew-H,

Within SEPM go to Admin>Install Packages>Client Install Settings. Right click in the right pane and click "Add". Give the new Client Install Settings a name, Choose the options you want and when you get to the section titled "Upgarde Settings" choose Remove all previous logs and policies.......

Click "OK" when you are finished and then export a new package with the new settings chosen for "Pick the customized installation settings below". Re-deploy the package and you should be OK.

Sadly, I followed Randy's instructions and the clients still don't show.

Hey Andrew,

I'm not sure if this will help but it's be worth a try. Have you checked that the sylink.xml file on the server has the same content as on your workstation?

I searched on the server and found the most recent sylink.xml which happened to be :

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\80B2972B0ADE64C90190EFA8AC1E0792\Sylink.xml

and checked it's contents against my local machine one :

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Sylink.xml

when i was having problems after i'd moved the SEPM to another server.

If the one on your machine is different then

1. click start/run and type smc -stop

2. copy the sylink.xml file from the server to replace the one on your PC in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\

3. click Start/run and type smc -start

Hopefully then you hsould get a green dot on the Symantec shield on your machine (possibly after a few minutes) and then a client in your SEPM console.

All else fails, remove the client from the machine, clean off any Symantec folders from Program files and in the AppData under user profiles, reboot and redeploy from the Migration & deployment wizard.

Cheers,

Rob.