64 bit clients on SEP not updating
Updated: 21 May 2010 | 13 comments
This issue has been solved. See solution.
I installed SEP ru5 on a network that has no internet connectivity. I cannot connect that network to a machine that can talk to the internet. so i will need to manually load files to a disk and transfer it to that network. i do have SEP installed on a network with internet. my problem is i have both 32bit and 64bit clients. when i go download the .jdb file and place it in the appropriate folder it only updates the 32 bit clients. how can i update the 64bit clients with no internet connectivity?
discussion Filed Under:
Comments
Read : To use the .JDB file
Read : To use the .JDB file to update definitions for Symantec Endpoint Protection Manager:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007100820002048
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
like i said, i did this and
like i said, i did this and only the 32bit servers updated NOT my 64bit.
Check
Check out....
https://www-secure.symantec.com/connect/forums/sep-64-bit-client-not-receiving-definition-updates
A few of us with similar issue.
Paul
Folow this 1. Stop the SEPM
Folow this
1. Stop the SEPM server service.
2. Go to "…\Inetpub\content\{C60DC234-65F9-4674-94AE-62158EFCA433}" folder and deleted all the sub folders
3) Go to C:\Program Files\Common Files\Symantec Shared\SymcData\ and delete the following folders:
sesmipsdef32
sesmipsdef64
sesmvirdef32
sesmvirdef64
4)In the registry, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\InstalledApps.
Delete these keys
SymcData-sesmipsdef32
SymcData-sesmipsdef64
SymcData-sesmvirdef32
SymcData-sesmvirdef64
5). In the registry, navigate to and delete the following keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs\SymcData-sesmipsdef32
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs\SymcData-sesmipsdef64
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs\SymcData-sesmvirdef32
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs\SymcData-sesmvirdef64
6). Start the SEPM service back up.
7) Put the jdb
Symantec Endpoint Protection Manager 11.x is not updating 32 or 64 bit virus definitions. http://service1.symantec.com/support/ent-security....
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
Tried that - no effect. The
Tried that - no effect. The keys weren't even recreated. I've uninstalled SEPM and reinstalled and still it won't update 64 bit defs in the manager.
same for me, the 64bit
same for me, the 64bit folders arent even there to begin with.
Trying Creating the folders
Trying Creating the folders manually and see if that helps
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
that did not help
that did not help
I just want to make sure that
I just want to make sure that you are downloading two .jdb files, one for 32 bit and one for 64 bit right? I know this sounds like a stupid question but I had to ask...
Thanks,
Grant-
Please don't forget to mark your thread solved with whatever answer helped you : )
they are the same exact
they are the same exact files, in my opinion thats the problem. the checksum is the same on both files.
I've never had to download
I've never had to download two .jdb files before. I always downloaded the one and both 32bit and 64bit would be updated.
I noticed weeks ago (while my
I noticed weeks ago (while my definitions were still updating) that the two jdb files listed were pointing to the same location. Only ever downloaded one file and it always updated both 32 bit and 64 bit definitions. I think the fact there is only one file is not the cause of the problem.
My last 64 bit definitions updated on 4th March with a file containing definitions of 3rd March. I update the server weekly with jdb file as there is no internet connection on any of the machines.
I've cleared out the definitions with the process above, repaired SEPM, upgraded to RU5 from 4r1, uninstalled and reinstalled the manager deleting the database and reconnected all clients, still I get no 64 bit definitions in the manager when loading a jdb file.
it was something with the
it was something with the .jdb file. the one from the 18th works fine now.
Would you like to reply?
Login or Register to post your comment.