SharePoint
Feedback by UserVoice

I suggest you ....

Upgrade V2V or B2B

Will like to smooth process and see less down time when upgrade from 2013 to 2016 or installing patches/SPs.

21 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Umar shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • yogeshpatel2 commented  ·   ·  Flag as inappropriate

        It would be nice if the patch process were more modular, and only specific components required restart. I just patched my 3-tier dev SP2013 farm to Dec 2015 CU, and it would be nice if you could deploy patches at the farm level and somehow automate the deployment to each server in the farm.

      • Paul Flatt commented  ·   ·  Flag as inappropriate

        Schema updates in particular should be automatic, zero-downtime, and more or less silent in the background.

        An interface for resolving missing binary packages/version mismatches should be present in Central Admin. I would think that it should be technically feasible for servers automatically share missing patches with each other. Centralized update cache?

      • Inderjeet commented  ·   ·  Flag as inappropriate

        SharePoint updates should not be in GB. not sometime when site of actual software is 2gb where as CU is 4 gb

      Feedback and Knowledge Base