This project is read-only.

Project Description
A Windows PowerShell v3 module for applying (cumulative/security) updates to SharePoint Server 2013/2016 and Office Web Apps Server 2013 remotely.

Installing security/cumulative updates and upgrading SharePoint Server farms and Office Web Apps is a intensive and time consuming. This project is focused on trying to make this task more easier for SharePoint IT admins.

This project consist of code found all over the internet and not written solely by me but also other very talented people and changed if needed to fulfill certain purpose needed for this project.

Note: Please provide feedback via discussions and issues or twitter. I'm looking forward to your opinion, likes, new feature requests or issues you came across.

Why use this module?

  • Automated patching of your SharePoint Server farm (including AppFabric1.1 updates).
  • Automated patching of your Office Web Apps Server farm.
  • Completely unattended.

What you need?

  • Windows PowerShell v3 (including SharePoint Servers, this is because we are using PowerShell Workflows for updates installations).
  • A windows file share, accessible for all the SharePoint Server servers in the farm.
  • A windows server or client machine from where you will execute AutoSPUpdater (e.g. A workstation or another server, as long as it's part of the same Active Directory domain as the SharePoint Server servers and that also can access the AutoSPUpdater file share). 

Support Operating Systems

  • Windows Server 2012/2012 R2.
  • Windows 7/8/8.1/10.

Note: AutoSPUpdater has now been fully tested on a multi-tier multi-server SharePoint farm and also a two nodes Office Web Apss server farm. The tests where run from a Windows Server 2012 R2 management server with PowerShell v4, we will be testing AutoSPUpdater using e.g. PowerShell v3 in a short while.

Supported features

  • Remote SharePoint Server cumulative/security updates installations.
  • Remote AppFabric1.1 cumulative updates installations.
  • Remote SharePoint Server upgrade (SharePoint Products & Technologies Configuration Wizard).
  • Remote Office Web Apps cumulative/security updates installations.

Note: The sections below explains how to get started with AutoSPUpdater.

Before installation (SharePoint)

Open SharePoint Central Administration and confirm that the following is true:

  • Upgrade and Migration > Review database status > Databases status must report 'No action required' (automatically done by AutoSPUpdater during test phase).
  • Application Management > Manage service applications > Search Service Application > Search application topology should be healthy (only green check marks, also automatically done by AutoSPUpdater during test phase).

Note: If any of the above conditions isn't true, try fixing them before installing any updates! Also if you are using availability groups for hosting the SharePoint usage database, you will also have to ask the SQL team to remove the usage database from the AG group temporarily for AutoSPUpdater to be able to run the farm configuration wizard successfully.

Example usage

  • Extract AutoSPUpdater*.zip content somewhere on the file server.
  • Share the AutoSPUpdater root folder directory using the default set of permissions.
  • Grant the install account, the account you will be using for installing the updates, write permissions to the \\<fileserver>\AutoSPUpdater\LogFiles directory.
  • Modify \\<fileserver>\AutoSPUpdater\AutoSPUpdater\ConfigurationFiles\AutoSPUpdater-ConfigurationFile.xml.
  • Open windows file explorer and navigate to the file share, make sure you use \\<fileserver>\AutoSPUpdater\AutoSPUpdater as path, it is very important that you execute the scripts from the file share and not using the local path!
  • Execute _AutoSPUpdater.cmd as an administrator (this will automatically start PowerShell and set the path to the share location, in this case the AutoSPUpdater share. It will also add the file share to your $Env:PSModulePath for the current session).
  • Execute SharePointSampleScript.ps1 or OfficeWebAppsSampleScript.ps1.

The file share should look something like this (this is an example share):

  • \\<fileserver>\AutoSPUpdater
    • AutoSPUpdater
      • ConfigurationFiles
      • HelpFiles
      • Modules
      • ...
    • LogFiles (This folder must be writeable)
    • Updates
      • AppFabric1.1
        • KB3092423
          • AppFabric-KB3092423-x64-ENU.exe
        • KBXXXXXXX
          • AppFabric-KBXXXXXXX-x64-ENU.exe
      • OfficeWebApps
        • KB3054930
          • wacserver2013-kb3054930-fullfile-x64-glb.exe
        • KBXXXXXXX
          • wacserver2013-kbXXXXXXX-fullfile-x64-glb.exe
      • SharePoint
        • KB3114723
          • ubersrvprj2013-kb3114723-fullfile-x64-glb.exe
        • KBXXXXXXX
          • ubersrvprj2013-kbXXXXXX-fullfile-x64-glb.exe
      • WorkflowManager

Note: Please replace <fileserver> with the fully qualified domain name (FQDN) of the file server hosting the file share.


  • Grant the setup account (the account you will be executing the scripts with) sysadmin permissions on the SQL server(s) hosting your SharePoint databases.
  • Grant the setup account (the account you will be executing the scripts with) local admin permissions on the SharePoint servers.
  • Grant the setup account (the account you will be executing the scripts with) local admin permissions on the Office Web Apps servers.
  • Grant the setup account (the account you will be executing the scripts with) local admin permissions on the computer that you will be running the scripts from.

Features currently being develop

  • Send mail notification when done (SMTP server needed that supports anonymous authentication).

Known issues

  • Installing updates in sequence is not yet fully supported, the reason is that the SharePoint servers will get stuck on waiting for the search service application to stop (get into a paused state). Therefore you will have to pause/resume the search service application multiple times during updates installation for each SharePoint server except for the server hosting the search administration component (stopping the search service application is currently done on the first SharePoint server hosting the admin components).

Last edited Apr 14, 2016 at 8:44 AM by JuniInacio, version 60