xmachine - Thanks for the reply. we are running 10.1.8.8000 due to policy. I have tried the KB you mentioned, specifically the workaround for those who can't upgrade to Symantec AntiVirus 10.0.2 or Symantec Client Security 3.0.2. Our LoginCaCertIssueSerialNum value is 232 so the REgistry Key was not changed. I also tried the resolution "To restore managed client communication after reinstalling Symantec AntiVirus server" and that did not correct the issue. I have waited to try the resolution "To force the pki information to be recreated" because of the amount of work entailed. I wanted to exaust other possibilities first. I have also tried the following resolutions noted in the following KB's and Forums: "symantec system center reporting that clientsis missing the scan engine", thread#742-1415361, kb2005033015282148, "ssc client security fails to show managed clients', kb2005063007112648, kb2005050916281848, "clients do not appear in system centre", kn2005040513373748, kb2004092913144648, kb2005090810290448, kb2005041910541048, "cannot get client to appear in ssc", kb2006032717252948. All mentioned resolutions have failed to correct. Currently I have uninstalled sav from the server and I am reinstalling manually rather than pushing from the sav primary server. once the server is protected, I will uninstall sav and the ssc from the primary server and reinstall according to the kb2005063007112648 "to force the pki information to be recreated" resolution. I will post the results. Thanks! If you have any other suggestions please let me know.
Main Topics
Browse All Topics





by: xmachinePosted on 2009-08-28 at 03:12:11ID: 25206129
Hi,
om/support /ent-secur ity.nsf/ 85 4fa02b4f50 1367882573 1a007d06af / ac6f6e8e8 0367c84882 57030004df 3a1?OpenDo cument
Check the following KB article:
http://service1.symantec.c