Client Package DB reference LU bug
Had this issue once before (MR3 I think) and support couldn't come up with a point resolution. I wound up having to do a fresh reinstall to clear it.
Just happened again after upgrading SEPM to MR4 MP1 from MR4.
My process for upgrading is to upgrade the SEPM server, then upgrade all client systems. After that is done, I delete the client install packages for the previous version.
The symptom is that when LiveUpdate runs on the SEPM server, it still tries to download updates for the old client package, even though it's been deleted. In LiveUpdate status it will show "Symantec Endpoint Protection Win32 11.0.4000.2295 (English) failed to update. Doesn't hurt anything, just annoying.
What appears to be happening is that the reference to the old package isn't being marked as deleted properly in the binary file in the database used to generate the LuSesmContentCatalog file which LU uses to determine what content needs to be checked.
Comments
I think I saw a defect for this a while back, I'll have to check.
I assume you are either done updating all your clients before you delete the old ones, or you arent using SEPM to update them?
Edit: Yes, its fixed... should ship in MR4 MP2.
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Yep, done updating before I delete the old clients.
The local workstations and servers I update by adding the new packages to groups, then performing a manual LiveUpdate to trigger immediate Upgrade by the client systems, and some remote systems I push out the smaller patch from the FTP using a 3rd party method. I was able to get all of the workstations patched within 30 minutes of finishing the SEPM server upgrade. Once all systems had reported in as being upgraded to MR4 MP1, I deleted the old MR4 packages from SEPM.
Would you like to reply?
Login or Register to post your comment.