none
Updates for SharePoint are a disaster

    Soru

  • First of all, 2.2GB of download is NOT a HotFix!

    Secondly, it is extremely difficult to get different SharePoints on to the same version e.g. 14.0.6114.5001 and 14.0.6106.5002 and 14.0.6120.5006 and so on.

    Can't this be easier?


    Dave Anderson

    15 Temmuz 2012 Pazar 23:27

Tüm Yanıtlar

  • Is this a public HotFix? or something that you got from Product Support team when you filed a bug/issue?  What is the KB article for this hotfix.


    Thanks & Regards,
    Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.

    16 Temmuz 2012 Pazartesi 02:03
  • Yes, public hotfix KB 2598151 which is the April 2012 Update for SharePoint Server 2010.

    Dave Anderson

    16 Temmuz 2012 Pazartesi 04:09
  • You aren't the first one to complain about this, and I'm sure you won't be the last.  Unfortunately as of right now, this is the only way to update SharePoint...hopefully we'll see something a little easier in the next version.

    Also, as a reminder, you shouldn't install the cumulative updates unless you are explicitly experiencing a problem that the update fixes.  The CU's are not regression tested as rigorously as the service packs are, so they might actually break more than they fix (for example, the original June 2011 CU).


    Bob Guidinger
    Please remember to click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.

    • Yanıt Olarak Öneren Paul Turner _ 16 Temmuz 2012 Pazartesi 15:00
    16 Temmuz 2012 Pazartesi 14:18
  • Thanks for the response Bob.

    The key issue is backup and restore. For example if you have two SharePoint machines and one "happened" to require a hotfix for a specific issue. Now you cannot backup from the hotfix and restore to the non-hotfix machine because they are at different levels. Even if they are both at SP1.

    This is a major headache since you now HAVE to install the hotfix on the other machine to do the restore even if it is not required (and may even be detrimental)

    Are there alternative content moving mechanisms that are more version independent or do we have to write our own?


    Dave Anderson

    16 Temmuz 2012 Pazartesi 20:00