Clear the SharePoint Configuration cache

To clear the config cache on the farm, follow these steps:

  • Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
  • On the Index server, navigate to:

Server 2008/2012 location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory.

  • Delete all the XML file in the directory. NOTE: ONLY THE XML FILES, NOT THE .INI FILE.
  • Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
  • Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
  • After you see XML files appearing on the Index server, repeat steps 2, 3 & 4 on each query server, waiting for XML files to appear before moving to subsequent servers.
  • After all of the query servers have all been cleared and new .xml files have been generated, proceed to the WFE and Application servers in the farm, following steps 2, 3, 4 and 5 for each remaining server.

New and improved features in SharePoint Server 2016 IT Preview

This section provides detailed descriptions of the new and updated features in SharePoint Server 2016 IT Preview.

The following new Access features are available when you deploy Access Services in SharePoint 2016 Preview:

The document deletion policy allows you to delete documents in users’ OneDrive for Business sites after specific periods of time. The In-Place Hold policy allows administrators to preserve documents, email, and other files.

For more information, see Overview of document deletion policies.

The following features are now available for working in SharePoint Server 2016 IT Preview document libraries:

  • Landmarks to a page make it easier to navigate, and there are alt text improvements for all major navigation links.
  • Keyboard shortcuts are provided for the following document tasks:
    • Alt + NNew
    • Alt + EEdit
    • Alt + UUpload
    • Alt + MManage
    • Alt + SShare
    • Alt + Y – Synchronization
  • Focus improvements, such as keeping focus on prior elements and focus trapping.
  • Announcements for upload progress.
  • Announcements for file name and file types when browsing folder and file lists.
  • Improved callout reading.
  • Fixed use of color issues for views switcher.
  • Updates to the Help documentation.

When you set up an SSL binding in Internet Information Services (IIS) Manager to host your web application, SharePoint uses TLS 1.2 connection encryption if your client application supports it. SharePoint also supports TLS 1.2 connection encryption when connecting to other systems, for example when crawling websites.

A security vulnerability was identified in the SSL 3.0 protocol that can allow an attacker to decrypt data. For enhanced security, some SharePoint features now disable SSL 3.0 connection encryption by default, as well as certain encryption algorithms (for example RC4) with known weaknesses.
SharePoint Preview customers should test all of their SSL/TLS/HTTPS connection scenarios with SharePoint Server 2016 IT Preview. We recommend that connection testing includes any third-party software that might integrate with SharePoint Server 2016 IT Preview.

This new feature provides templates that work at same level as SQL Server, which reduces the round trips required between the SharePoint and SQL servers. Use Windows PowerShell cmdlets to create sites and site collections quickly.

SharePoint has historically blocked file names that included the &, ~, {, and } characters, file names that contained a GUID, file names with leading dots, and file names longer than 128 characters. These restrictions are removed in SharePoint Server 2016 IT Preview and are now available to use.

Restricted characters such as % and # are still not allowed in file names.

In SharePoint Server 2016 IT Preview, new hybrid features are available to enable hybrid solutions.

Hybrid sites

Hybrid sites features allows your users to have an integrated experience while using SharePoint Server and SharePoint Online sites:

  • Users can follow SharePoint Server and SharePoint Online sites, and see them consolidated in a single list.
  • Users have a single profile in Office 365, where all of their profile information is stored.

For more information, see Plan for hybrid sites features.

Hybrid OneDrive for Business

Hybrid sites features are used in concert with Hybrid OneDrive for Business (introduced in SharePoint Server 2013 with Service Pack 1 (SP1)):

  • Users can sync files with Office 365 and share them with others.
  • Users can access their files directly through Office 365 from any device.

Cloud Hybrid Search

Cloud hybrid search is a new hybrid search solution alternative. With cloud hybrid search solution provided in SharePoint Server 2013 lets you create a single search index that is deployed in Office 365:

  • You index all of your crawled content, including on-premises content, to your search index in Office 365. You can set up the crawler in SharePoint Server 2016 IT Preview to crawl the same content sources and use the same search connectors in Office SharePoint Server 2007, SharePoint Server 2010, and SharePoint Server 2013.
  • When users query your search index in Office 365, they get unified search results from both on-premises and Office 365 content.
You will be able to configure and test Cloud Hybrid Search on September 7, when the Office 365 component of the hybrid topology is enabled.

For more information, see Plan for hybrid OneDrive for Business.

For more information about the hybrid solutions available today, please visit the SharePoint Hybrid Solutions Center.

With this new capability, you can:

  • Search for sensitive content across SharePoint Server 2016 IT Preview, SharePoint Online, and OneDrive for Business.
  • Leverage 51 built-in sensitive information types (credit cards, passport numbers, Social Security numbers, and more).
  • Identify offending documents, export a report, and adjust accordingly.

Information on configuring and using this feature is documented in SharePoint Online and Office 365. For more information, see:

In SharePoint Server 2016 IT Preview when you post images and videos to a document library, you can see a preview by hovering the mouse over the image or video, or by clicking on them.

Previous versions of SharePoint did not support uploading or downloading files larger than 2,047 MB. SharePoint 2016 now allows you to upload or download larger files. You can configure the desired maximum file-size limit on a per-web application basis in your SharePoint farm.

The role of a server is specified when you create a new farm or join a server to an existing farm. SharePoint automatically configures the services on each server based on the server role, optimizing the performance of the farm based on that topology. There are six predefined server roles that are available, as shown in the following table.

Server role Description
Front end Service applications, services, and components that serve user requests belong on front-end web servers. These servers are optimized for fast performance.
Application Service applications, services, and components that serve back-end requests, such as background jobs or search crawl requests, belong on Application servers. These servers are optimized for high throughput.
Distributed Cache Service applications, services, and components that are required for a distributed cache belong on Distributed Cache servers. Optionally, you can configure these servers to also load balance farm traffic using the SharePoint Request Manager.
Search Service applications, services, and components that are required for search belong on Search servers.
Custom Custom service applications, services, and components that do not integrate with MinRole belong on Custom servers. The farm administrator has full control over which service instances can run on servers assigned to the Custom role. MinRole will not control which service instances are provisioned on this role.
Single-Server Farm Service applications, services, and components required for a single-machine farm belong on a Single-Server Farm. A Single-Server Farm is meant for development, testing, and very limited production use. A SharePoint farm with the Single-Server Farm role cannot have more than one SharePoint server in the farm.

The Standalone Install mode is no longer available in SharePoint Server 2016 IT Preview. The Single-Server Farm role replaces the Standalone Install mode available in previous SharePoint Server releases. Unlike Standalone Install, the SharePoint administrator must separately install and prepare Microsoft SQL Server for SharePoint. The SharePoint administrator must also configure the SharePoint farm services and web applications, either manually or by running the Farm Configuration Wizard.

For more information about the MinRole feature, see MinRole overview.

When you use a mobile device to access the home page for a SharePoint Server 2016 IT Preview team site, you can tap tiles or links on the screen to navigate the site. You can also switch from the mobile view to PC view, which displays site pages as they are seen on a client computer. This view is also touch enabled.

You can click a control to create new Office documents, upload files, synchronize your files for offline use, and share your files. For more information, see “Simple controls” on The OneDrive Blog.

The Open Document Format (ODF) enables you to create new files in a document library and save as ODF files so that users can edit the new file with a program they choose. For more information, see Set Open Document Format (ODF) as the default file template for a library.

Project Server 2016 Preview for SharePoint Server 2016 IT Preview has many new capabilities and features. For more information, see What’s new for IT pros in Project Server 2016 Preview.

Project Server 2016 Preview is installed with SharePoint Server 2016 IT Preview. Currently there is no licensing restriction, but there will be in the future releases.

The following list shows the sharing improvements that are available for SharePoint Server 2016 IT Preview:

  • Create and Share folder
  • Sharing Hint
  • See who the folder is shared with when viewing a folder
  • Members can share
  • Improved invitation mail
  • One-click email to approve or deny a request for access

SharePoint Search supports indexing of up to 500 million items per Search Server application.

The following list shows the SharePoint 2016 requirements that are needed to negotiate connection encryption with an SMTP server:

  1. STARTTLS must be enabled on the SMTP server.
  2. The SMTP server must support the TLS 1.0, TSL 1.1, or TLS 1.2 protocol.
    SSL 2.0 and SSL 3.0 protocols are not supported.
  3. The SMTP server must have a server certificate installed.
  4. The server certificate must be valid. Typically, this means that the name of the server certificate must match the name of the SMTP server provided to SharePoint. The server certificate must also be issued by a certificate authority that is trusted by the SharePoint server.
  5. SharePoint must be configured to use SMTP connection encryption.

To configure SharePoint to always use SMTP connection encryption, open the SharePoint Central Administration website and browse to System Settings > Configure outgoing e-mail settings and set the Use Secure Sockets Layer (SSL) drop-down menu to Yes. To configure SharePoint to always use SMTP connection encryption in Windows PowerShell, use the Set-SPWebApplication cmdlet without the -DisableSMTPEncryption parameter. For example:

$WebApp = Get-SPWebApplication -IncludeCentralAdministration | ? { $_.IsAdministrationWebApplication -eq $true }

Set-SPWebApplication -Identity $WebApp -SMTPServer -OutgoingEmailAddress -ReplyToEmailAddress

To configure SharePoint to never use SMTP connection encryption in SharePoint Central Administration, browse toSystem Settings > Configure outgoing email settings and set the Use Secure Sockets Layer (SSL) drop-down menu to No. To configure SharePoint to never use SMTP connection encryption in Windows PowerShell, use theSet-SPWebApplication cmdlet with the -DisableSMTPEncryption parameter. For example:

$WebApp = Get-SPWebApplication -IncludeCentralAdministration | ? { $_.IsAdministrationWebApplication -eq $true }

Set-SPWebApplication -Identity $WebApp -SMTPServer -DisableSMTPEncryption -OutgoingEmailAddress -ReplyToEmailAddress
If SharePoint is configured to use SMTP connection encryption, it will only send email messages if it successfully negotiates connection encryption with the SMTP server. It will not fall back and send email messages unencrypted if connection encryption negotiation fails. If SharePoint is not configured to use SMTP connection encryption, it will always send email messages unencrypted, even if the SMTP server supports connection encryption.

You can now pin sites that you see on the sites page. A pinned site shows at the top of the list of sites that you’re following.

For more information, see “Site folders” in The OneDrive Blog.

To configure SharePoint to use a non-default SMTP port open SharePoint Central Administration, browse toSystem Settings > Configure outgoing email settings, and set the SMTP server port to the port number of your SMTP server. To configure SharePoint to use a nondefault SMTP port in Windows PowerShell, use the Set-SPWebApplication cmdlet with the -SMTPServerPort <port number> parameter. For example:

$WebApp = Get-SPWebApplication -IncludeCentralAdministration | ? { $_.IsAdministrationWebApplication -eq $true }

Set-SPWebApplication -Identity $WebApp -SMTPServer -SMTPServerPort 587 -OutgoingEmailAddress -ReplyToEmailAddress 


SharePoint 2016

I recently installed SharePoint 2016 in a VM using VMWare Workstation and below is what I found so far. I will continue testing it and will add more information to my blog at least once a week.

Use the following link to download SharePoint 2016 and use the product key below.

Use the link below to download a 180 days trial version of Microsoft Server 2012 R2 and SQL 2014 SP1

30 days trial of VMWare

Oracle VirtualBox (Free)
Below are some of the differences between SP 2013 and SP 2016 in Central Administration.
Application Management
– Web Applications – NO Changes
– Site Collections
o When Creating a new Site Collection
 Templates
• Collaboration – NO Changes
• Enterprise
o Two new templates
 In Place Hold Policy Center
 Compliance Policy Center
• Publishing
o Product Catalog is not listed
• Custom – NO Changes
System Settings
– Servers
o Two new options
 Manage services in this far
 Convert Server role in this farm
– E-Mail and Text Messages (SMS) – NO Changes
– Farm Management – NO Changes

Monitoring – NO Changes

Backup and Restore
– Farm Backup and Restore – NO Changes
– Granular Backup – NO Changes

– Users – NO Changes
– General Security – NO Changes
– Information Policy – NO Changes
Upgrade and Migration
– Upgrade and Patch Management – NO Changes
General Application Setting
– External Connection Settings – NO Changes
– InfoPath Forms Services – NO Changes
– SharePoint Designer – NO Compliance
– Search – NO Changes
– $Resources:ReportServerResources,AdminReportServerGroupTitle – NEW
– Content Deployment – NO Changes
– PWA Settings – NEW

– SharePoint and Office Store – NO Compliance
– App Management – NO Changes

Office 365
– Configure Yammer – Removed
– Configure OneDrive and Site Links – Removed
– Configure Hybrid OneDrive and Sites Features – Added

Configuration Wizards – NO Changes

Distributed Cache Service – Change Account

When AppFabric is installed as part of the SharePoint pre-requisites, it is configured to run under the credentials of the server farm. This is not recommended, and will eventually trigger a violation of a Health Analyzer Rule. To avoid this, you can change the account used by the Distributed Cache service. In the example below, we’re retrieving a managed account that has already been registered with our farm, called “CONTOSO\my_managed_account” with the Get-SPManagedAccount cmdlet. We then set that as the ManagedAccount property of the ProcessIdentity object of the Distributed Cache (“AppFabricCachingService”) SPService.

$farm = Get-SPFarm
$cacheService = $farm.Services | where {$_.Name -eq “AppFabricCachingService”}
$accnt = Get-SPManagedAccount -Identity domain\ManagedAccount
$cacheService.ProcessIdentity.CurrentIdentityType = “SpecificUser”
$cacheService.ProcessIdentity.ManagedAccount = $accnt

Error when you click on “Manage Shared Schedules” under Reporting Services

Try the following if you are using SharePoint 2013 with SSRS 2012 in SharePoint Integrated Mode.

– Launch Central Administration
– Click on Application Management
– Click on Manage Services Applications under Services Application
– Select the Reporting Services Service Application
– Click Manage – Provision Subscriptions and Alerts
– Click ‘Download Script’
– Copy the script
– Log in to your SQL Server and Launch SQL Server Management Studio
– Click ‘New Query’
– Paste the script that you previously copied
– Click on Execute


SharePoint 2013: How to Hide the Newsfeed, Skydrive and Sites Buttons

– Open the master page of your site in SharePoint Designer
– Check Out – Edit File in Advanced Mode

– Search for ‘SuiteLinksDelegate’  and comment the following line.
<SharePoint:DelegateControl ID=”ID_SuiteLinksDelegate” ControlId=”SuiteLinksDelegate” runat=”server” />

This is how it looks after is commented.

<!–  <SharePoint:DelegateControl ID=”ID_SuiteLinksDelegate” ControlId=”SuiteLinksDelegate” runat=”server” /> –>

– Save the Master Page – Check In – Publish a Major Version – OK





How to display original images in SlideShow web part

1- Save below JavaScript code to file, for example in SlideshowObjectInitializer.txt and upload it to SiteAssets Library
2- Add CEWP on page where Slideshow web part is located and in the Content Editor tool pane, under Content Link, type /SiteAssets/SlideshowObjectInitializer.txt.

For more information, please check the blogs below.


<script type=”text/javascript”>

function SlideshowObjectInitializer() {

ShowPic = (function(ShowPicOrig) {       return function() {

var ssObj = arguments[0];  //SlideShow object            var curPicIdx=ssObj.index; //current picture index

ShowPicOrig.apply(this, arguments); //call original ShowPic

//apply some changes to display original picture in SlideShow control            ssObj.image.src = ssObj.linkArray[curPicIdx]; //display original image instead of web image            //change picture & container size to auto instead of fixed (by default web image size is used)              ssObj.image.setAttribute(‘height’,’100%’);              ssObj.image.setAttribute(‘width’,’100%’);              var cell = ssObj.cell;     = ‘auto’;     = ‘auto’;     = ”;              var pcell = ssObj.cell.parentNode;   = ‘auto’;     = ‘auto’;       };   })(ShowPic);


ExecuteOrDelayUntilScriptLoaded(SlideshowObjectInitializer, ‘imglib.js’);


How to change the Central Administration URL desktop icon link

If you happen to run the ‘SharePoint 2013 Products Configuration Wizard’ and change the name of the server where Central Administration was initially installed. Everything will be ok, but the link will still be pointing to the previous server. Below are the steps to update the URL.

– Open the registry by running regedt32 from command prompt
– Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS
– Right Click on ‘CentralAdministrationURL’ and Click on Modify
– Change the name of the server and make sure to add ‘/default.aspx’ at the end
– Click OK

You need to do the same on other Front End servers if Central Administration is running fron more than one server.