PowerShell to perform Visual upgrade of a SharePoint 2010 Upgraded site in SharePoint 2013

Once a Sharepoint 2010 site is upgraded to 2013, the sites will still be rendered in the 2010 mode.  We have two options to upgrade the sites:

  1. Use the Visual Upgrade option in SharePoint 2013, which would in turn create an entry with the SharePoint timer job and will take a minimum of 10-15 minutes (or more depending on the site's size) to upgrade to the new 2013 look and feel.
  2. Use the Powershell and perform the upgrade.

I always prefer the second option, as it allows you to script the Upgrade and perform the visual upgrade sequentially on many sites (especially if you have a parent site collection with 10 or more sub sites in it).  The below is the powershell that needs to be executed to upgrade the site. (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)

Upgrade-SPSite http://<Your_Web_Site_URL> -VersionUpgrade

How to verify if the sites are upgraded?

In order to verify if the sites are upgraded to 2013 look and feel, execute the below PowerShell which will display the site's compatibility level alongside (will either be 14 or 15) to indicate if the site's are upgraded or not: (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)

get-spsite -Limit All

 

2,484 total views, 1 views today

PowerShell to Upgrade Classic Windows Based SharePoint site to Claims Based Authentication (SharePoint 2013)

During upgrade from SharePoint 2010 to 2013, when we execute the TEST-SPCONTENTDATABASE command, we run into the below exception that says :

"The <Web site> web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.  There is an inconsistency between the authentication mode of target web application and the source web application.  Ensure that the authentication mode setting in upgraded web application is the same as what you had in previous SharePoint 2010 web application…."

Continue reading

3,963 total views, no views today

Accessing a site from within Windows 2012 server throws 401 unauthorized error (by displaying the Windows Prompt repeatedly)

Too often when we want to try accessing a website hosted in IIS in Windows Server 2012 configured under Windows Authentication, from within the server, we are repeatedly presented with the "Windows Prompt" even after providing the correct credentials.  Per Microsoft, this behavior is per design and to access the site we had to perform the below modification in the Registry:

  1. Run "Regedit"
  2. Expand HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Control -> Lsa -> MSV1_0
  3. Look for a key named "BackConnectionHostNames".  If it doesnt exist then create a new one, by right-clicking onthe empty space and choose New -> Multi-String Value and provide the name as "BackConnectionHostNames"
  4. Now add the name of the site (FQDN address), example http://test.contoso.com
  5. Click Ok.

Now if you try accessing the site, it will load without prompting for credentials.  For more information on this topic visit, https://support.microsoft.com/en-us/kb/896861

2,501 total views, no views today

Open Documents From Document Library in Microsoft Office in SharePoint 2013

Too often Colloboration sites built on SharePoint, when accessed by users who try to open up documents from the document libraries would like to see the content on the native Microsoft Office than on Excel Services. Since on an OOB SharePoint 2013 installation where all services are enabled, when users click on an Excel document, it will try to open the document on the browser itself using Excel Services.  The following configuratinos can be tried to change this behavior and force the documents to be opened in native Microsoft Office Clients:

Continue reading

1,662 total views, no views today