Small Business Susan

KB2630976 is showing up in WSUS as "needed".


 


KB2630976 is showing up in WSUS as “needed”.  Sorry folks, I don’t know what game WSUS is playing but I think this is a total screw up.


Don’t approve it, hang loose.



5 comments ↓

  • #   Doug H. on 12.09.11 at 12:06 am     

    DEFINITELY DO NOT INSTALL!

    I installed this updated on a SBS 2001 Standard box. It did two things that I noticed quite quickly:
    1. Symantec EndPoint Protection Manager died. The database was working but the IIS portion would not start.
    2. There are a lot of external recipients in the GAL, and some of them began to fail when sent to with this error:
    IMCEAEX-_O=DOMAIN_ou=first+20administrative+20group_cn=Recipients_cn=Alias@domain.com
    #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

    Luckily I was able to uninstall the update. After a restart things seems back to normal now.


  • #   Doug H. on 12.09.11 at 12:22 am     

    Sorry but my problems were with a different KB released on Dec 7th, 2011: KB2608646 (Update Rollup 6 for Exchange Server 2010 Service Pack 1).


  • #   Mark Berry on 12.10.11 at 11:38 am     

    I approved it for “Update Services Client Computers” (SBS 2008 group). I do use Office 365 on one client so theoretically it could be legit. However even after approval, when I check for updates from that Win7 client, the client says “Windows is up to date” and won’t pull the patch from WSUS. Come to think of it, I’m not using the Sign-In Assistant, so there is nothing to update.


  • #   David on 12.18.11 at 7:30 am     

    Well I did approve it for all clients even though none of them use Office-365. Now my server says my clients need a update even though the clients say they are current.

    How do I remove the approval from the Server?


  • #   bradley on 12.18.11 at 3:59 pm     

    Go into the WSUS console and decline it in there.