Endpoint Protection

We recently updated our virus definitions (3/9/10) on our Endpoint manager server.  None of the machines on this network are connected to the internet, so we download the .jdb file and copy it over to the server via cd.  We had issues with the clients not updating past December, but were able to get past that and everything updated to 2/3/10 definitions.  When we updated the server with the 3/9/10 definitions, all of our XP 32bit machines updated fine, but none of our XP 64bit systems updated.  I tried going back to the server and deleting all of the older definitions and the sesmvirdef32 and sesmvirdef64 folders and then copying the .jdb file to the server again and the sesmvirder32 folder came back with no problems, but the sesmvirdef64 folder did not get re-created.

I hope that makes sense.  For some reason, our server has stopped updating the 64bit clients and I'm not sure why.  Any ideas?

Run Repair for SEPM or Run Management Server Configuration wizard once.

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). Run Live update from within the Symantec Endpoint Protection Management console. Symantec Endpoint Protection Manager 11.x is not updating 32 or 64 bit virus definitions. http://service1.symantec.com/support/ent-security....

I've already tried the step above.  The 32bit clients connected back up fine, but the 64bit ones are still having issues.

I tried running both a repair and the wizard and now I've completely lost connection to all of the clients.

In SEPM whether 64 bit updates are present?

Check it in Admin----->servers--->local site--->show live update downloads..

try this mate:

# Open the Windows Registry editor (regedit.exe) browse to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
# Verify the following Reg Multi String value PendingFileRenameOperations exists under this key.
Note: If you do not find the PendingFileRenameOperations value in the location above, this error message can be generated if there are pending changes in:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SessionManager\PendingFileRenameOperations
 
make sure you empty the temp folder as Prachand said

 delete the value of the sub key and see how it goes.

Hello All,

Please check the KB article provided below:

Only 32 Bit Antivirus / Antispyware Definitions are not updating on the 32 Bit / 64 Bit Operating System.
 
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010012923154448

Mithun - Did you misread the problem?  You seem to be pointing to a KB article which purports to help users who are unable to update 32-bit clients from a SEPM Server, but the issue described herein is exactly the opposite.

To wit: I'm experiencing the same issue described by others in this thread.  My SEPM Server is running on Windows Server 2003 (32-bit), and I'm attempting to update a mix of 32-bit and 64-bit Windows clients. The latest update which I've applied to my server was the "vd30e003.jdb" file, (2010-03-16 rev.003) and the update applied immediately prior to this was the "vd30a027.jdb" file, (2010-02-16 rev.039) and all of my 32-bit clients are now updated to the March 16 definitions, while all of the 64-bit clients continue to show the February 16th definitions.

Even though I was skeptical of your advice, I went ahead and performed the steps described in your knowledgebase article (short of the full reintstall*) and they did not help at all; the March 16h definition update simply does not populate the 64-bit folder with any data.

* In addition, I had already performed a full reinstall of my SEPM Server only a couple of weeks ago, in order to get it updated to the Febuary 16th definitions, as I discovered that previously they had not been updating since December 2009.  So since prior definition packages worked just fine on these systems, and since the problem has cropped right back up on this newly installed SEPM instance, I would infer that another full reinstall would be nothing more then a time consuming stop-gap measure, and that the SEPM jdb files themselves are somehow corrupt.

Please advise...

There apparenty was something wrong with the 2010-03-16 .JDB file (and perhaps preceeding updates), that was not updating the 64 bit clients.  Using the .JDB files from 2010-03-18 and beyond work just fine updating both the 32 and 64 bit clients.  Note: Although they list 2 separate .JBD files for download (32 &64 bit) they are in fact the same file, and either will update both clients.  There's no need to install both.