So, this appears to be working thus far. After removing the pkg file , the bandwidth utilization now has dropped significatly for these clients.
However, our System admin wanted me to ask a few questions.
He wanted to know if there was an error or bug in the way that the client updates itself from SEPM? We have 2 packages advertised to the clients, 1-64bit and 1-32bit client. Maybe some clients are trying to get the 64bit client when they shouldn't be?
Is this possible?
also, this appears to be an older SEP client pkg that I removed from the download folder. I believe from the pkg file it is update 11.0.6000.5507. This is the update that was issued to rid of the bandwidth issues that symantec endpoint had before , correct? Our admin also noted that this package has been removed from the SEPM servers a while ago, so he's not sure why it would still be pushing to client still.
Any ideas? Or are we leaning on the fact that this somehow got corrupted and basically the client just kept trying to update itself even after it was updated using this old file that is pointing at the server, that no longer has this update available? Does that make sense?
Thanks so much for all of the assistance!