SharePoint Patching


SharePoint patching constitute of three types, Service Packs, Cumulative updates and hotfixes. Patching is considered a B2B (build to build) upgrade.

Service Packs

Generally service packs are not a set schedule but they are around 18 to 24 months. They fix all the bugs that have identified since the last service pack or RTM. Sometimes service packs introduce new features and functionality. These are thoroughly tested before release and it should immediately be tested in a test environment. Once tested for feature and functionality in test/non-prod environment they should be released to production at the earliest as service packs are dramatically affect performance and security.

Cumulative updates

Cumulative updates are normally released in every other even numbered month and they are attempt to fix bugs identified in those months plus they include fixes for all the previously fixed bugs as well. The size of these CU’s grows as they are being released. Unless if any current affected issues are resolved in production environment they are not generally necessary to install. Sometimes these Cu’s can break things if they don’t work properly. Patches cannot be uninstall and you will be helpless and wait till the next CU is released. Test the fix the CU is providing thoroughly in test farm and wait for a couple of weeks for any regression before updating to production.


Hotfix or a security patch. These are generally pushed through windows update. These attempt to fix any urgent security issues in SharePoint and are release as early as possible and could be the lease tested of all the patches. Install and run configuration wizard to complete the process. Fingers crossed and prey they should not break any other functionality.


SharePoint infamous direct URL’s

Force Page Edit Mode in SharePoint: http://host/sitecollection/page.aspx?ToolPaneView=2&pagemode=edit
Sign in as Different User:  http://host/sitecollection/_layouts/closeConnection.aspx?loginasanotheruser=true
Important: This option uses an unsupported browser feature which is unreliable and causes other issues. Currently this option does not work in IE 10 and Safari.
Web Part Maintenance Page:  HTTP://host/sitecollection/page.aspx ?contents=1
Show Page in Dialog View: HTTP://host/sitecollection/page.aspx?isdlg=1
Site Features: _layouts/ManageFeatures.aspx
SiteCollection Features: _layouts/ManageFeatures.aspx?Scope=Site
(the query string parameter is case sensitive. “Scope=site” throws an error)
Get the version of the SharePoint server (Patch level): /_vti_pvt/Service.cnf
Application page for registering SharePoint apps: /_layouts/15/appregnew.aspx
Save Site as a template:  /_layouts/savetmpl.aspx
Sign in as a different user: /_layouts/closeConnection.aspx?loginasanotheruser=true
Enable SharePoint designer:  /_layouts/SharePointDesignerSettings.aspx
Welcome Page (Default page settings): /_layouts/AreaWelcomePage.aspx
Change Site Master Page:  /_layouts/ChangeSiteMasterPage.aspx
Page Layouts and Site Templates: /_Layouts/AreaTemplateSettings.aspx
Master Pages library: /_catalogs/masterpage/Forms/AllItems.aspx
User Information List: _catalogs/users/simple.aspx
Quick Deploy List: Quick%20Deploy%20Items/AllItems.aspx
Open Page in Edit Mode:  ?ToolPaneView=2
Taxonomy Hidden List (MMS): Lists/TaxonomyHiddenList/AllItems.aspx
User Information List:  _catalogs/users/simple.aspx
Force displaying the user profile in the site collection:  /_layouts/userdisp.aspx?id={UserID}&Force=True
Note: Some URL’s I have not tested though.

Windows PowerShell script for AD DS Deployment

# Windows PowerShell script for AD DS Deployment

Import-Module ADDSDeployment
Install-ADDSForest `
-CreateDnsDelegation:$false `
-DatabasePath “C:WindowsNTDS” `
-DomainMode “Win2012R2” `
-DomainName “” `
-DomainNetbiosName “CONTOSO” `
-ForestMode “Win2012R2” `
-InstallDns:$true `
-LogPath “C:WindowsNTDS” `
-NoRebootOnCompletion:$false `
-SysvolPath “C:WindowsSYSVOL” `

SharePoint 2013 – Configure Access services On-Premise Installation

Hello Folks, I found the following documents and articles very helpful in setting up Access Services on SP 2013 On-Premise Installation



Between, We need to configure “apps for SharePoint” for Access service to work. Below are the some helpful links:


Hope this helps..:)