Endpoint Protection

So I have a few closed lab environments where AV definitions need to be updated manually.  Some are standalone PC's with SEP standalone client running and I run the executable for virus definitions.  One lab is running McAfee epo, and two labs are running SEPM.

Here is my problem:

If I run the SEP AV Update executable (usually around 600mb) on the standalone machines, the update is complete in a minute or two.

If I download the offline AV updates for McAfee epo (usually around 40mb) to import into that network system, the process is complete in about 10 minutes to 15 minutes or so.

However, If I download the jdb file for SEPM (same size as the exe around 600mb) and load it into the inbox\content\incoming folder, it takes a FULL HOUR for SEPM to process that jdb.  You can tell it's not done because the jdb still exists with some other working files/folders along side of it.  It takes a full hour for that incoming folder to clear out again.

For one of my labs, this isn't a problem because there are always people working and I can copy the file in and walk away.

However, my other lab isn't used as often but has a requirement that systems are not allowed to be left unattended.  Which means, I have to sit in that room for a FULL HOUR twittling my thumbs for the .jdb for finish processing so I can then update the clients.  Only then I can shut them all down and pack everything away so I can leave the room.

Is there any way around this?  Why does the jdb take so much longer to process than the standalone exe?  I've got 10 laptops that all have to be packed away in a safe when not in use, and at this rate, it would actually be faster for me to run the exe on each laptop manually than it is to use SEPM.  Somethings not right about that.

Brian

Way too long. What version of SEPM?

I believe it's 12.1.3.

Running windows 2008 R2.  How long should it take?  I've never actually timed it in the lab that I'm able to walk away - becuase I can walk away :) - I've always just assumed it's the same amount of time.

btw, this was a clean install environment.  single server serving as the only DC as well - but I usually don't even bother connecting the clients until the server has processed the jdb, so it shouldn't be hosed up processing AD traffic at the same time as it's processing the jdb.

Haven't used it on a awhile but as soon as I would drop the JDB, it would disappear and start processing within 60 seconds.

I just found another forum post from back in 2009 where someone had to wait for the jdb to process overnight.  maybe I should count myself lucky for it taking an hour?