none
Uninstall cumulative update RRS feed

  • Question

  • Is there an easy way to uninstall the cumulative update for SharePoint and Project Server? I see there are many individual updates installed, do I need to remove them individually? Do I need to remove the cumulative updates for SharePoint and Project Server separately?

    What if I get error in event log that the cumulative update installation is not completed? Can I still remove the cumunlative update and revert the system back?

    Should I always install the same period of SharePoint and Project Server cumulative updates together?

    • Moved by Mike Walsh FIN Wednesday, May 18, 2011 3:22 PM Project Server q (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    Wednesday, May 11, 2011 2:50 AM

Answers

  • There is without question no easy way to uninstall a cumulative update package for SharePoint, and its never something I would recommend doing in a production environment. SharePoint updates are really a one-way street: you can only go forward with them and there's no way to uninstall, roll back, or remove them once you've started the installation process.

    The reason for this is that there are two components to the update process: 1) updating the SharePoint bits installed on each SharePoint server and 2) updating the schemas and configuration of the farm's databases in its SQL Server instances. If you uninstall the bits from your SharePoint servers, those databases are still going to be functioning at the level of the applied CU and will not work with your servers.

    If you get an error during the installation of a CU, you need to closely look at both the event log of the server it happened on AND the upgrade log file that will be created when you run the installer. Microsoft states that you'll need to work to resolve the blocking issue in those log messages, then re-run the SharePoint Config Wizard to see if you've resolved the error. Often times you'll need to run the Wizard from the command line with the FORCE option to get that to work (psconfig -cmd upgrade -inplace b2b -wait -force).

    And yes, you'll definitely want to apply your updates in the following order:

    1. WSS 3.0 CU
    2. MOSS 2007 CU
    3. Project Server 2007 CU

    A couple of other tips:

    • READ THE DOCUMENTATION FOR THE UPDATES CAREFULLY. The info they provide about how to execute the installs is very important. This is not simple, and the process described there (or here: http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx and here: http://technet.microsoft.com/en-us/library/cc263467%28office.12%29.aspx) is worth its weight in gold
    • BACKUP YOUR FARM BEFORE UPDATING. If something goes wrong, you'll have to rebuild the farm from that backup b/c you can't uninstall.
    • ONLY INSTALL A CU IF YOU NEED SOMETHING IN IT: The October 2009 CU has important updates related to upgrading to SharePoint 2010, and I think there was a CU that came out last year that may have some important security fixes in it, but Microsoft's message right now is to only apply the latest and greatest CU if you have a specific need for a hotfix in it.
    • TEST THE UPDATES IN A SEPARATE ENVIRONMENT FIRST, THOROUGHLY. MS does not do full integration testing with these CUs like they do for Service Packs or major Releases, and often times they have to pull them back b/c issues are found in them. Make sure you know how its going to impact your production environment BEFORE you apply it there, not after!

    (sorry for getting on my soapbox a bit with those items, but they're important)

    John


    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.
    • Marked as answer by Nahcyrret Thursday, May 12, 2011 5:09 AM
    Wednesday, May 11, 2011 8:26 PM