All posts in SharePoint 2016

A few weeks ago, I started playing with Hybrid SharePoint Server 2016 scenarios, to see if there are any differences with SharePoint 2013. As I am mostly an IT Pro, usually I never did the OData Source myself, but had a developer set that up for me. This time, I was in my lab, and I was both the DEV and the SharePoint Admin that had to do the IT part. (Talk about DevOps). That and the fact that I had quite a lot of problems with getting it to work with Entity Framework 6, I decided to do a blog post for all the SharePoint Admins and Developers out there that want to create a SharePoint 2016 External Content Type with an OData Source.

This blog will really be a step by step that everyone could follow, so if you are a more experienced dev, you can probably skip most of the screenshots, but I am sure that if you’re an IT Pro and first time doing this, you will find it valuable.


Our Goal for this blog post is to get the following table, in SharePoint Server 2016. The Hybrid configuration will be done in another blog post, for this one, we simply want to make it work in SharePoint 2016 On-Premises.

You will need to have access to a SharePoint Development machine with Visual Studio, as well as a IIS server where you can deploy your WebService at after (This can be done on the SharePoint Server).

Note, and this one is especially for people (like me) who will simply do this for testing. You need to have a Primary Key in your table for this to work. Without a Primary Key, you will get strange errors. For production, I hope this will not be a problem, but if you create a quick Database for testing, make sure your table has a PK defined.

Creating the OData Source

Create a new Project of type ASP.NET Web Application and name it as you wish. (For this scenario, we disabled the checkbox for Application Insights , since we don’t want to use /configure it).

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

In the next page, select Empty, since we want an Empty Web Application where we will add our own stuff.

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

Now, we will need to start adding items in this Project, so right click on the project name, Add, and Add New Item.

Select ADO.Net Entity Data Model under the Data tab, and give it a proper name such as “ContosoModel”

In the Entity Data Model Wizard, choose EF Designer from Database.

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

On the “Choose your Data Connection” page, click on “New Connection”

Enter the Connection Information for your business needs. If you use Windows Authentication, it will use the account that the Application Pool you run your Web Services Site runs it to access the Database. (Once deployed). There are multiple other ways to configure it depending on your business needs, but for this demo, we will use Windows Authentication.

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

After you configure it, click on Test Connection to make sure that everything is configured correctly.

Back to the “Choose Your Data Connection” Page, you will have your connection selected, and you can optionally change the connection setting in the Web Config.

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

Choose Entity Framework 6.x so we use the latest version available for our project.

On the next page, choose all the tables that you want included in the OData Service and give a good name to your Model Namespace.

If everything worked correctly, you will see a next page, with the columns of your table(s) in a designer. If you don’t, check out the error log at the bottom of your Visual Studio

After this is done, we need to add another item to our Project!

Creating a SharePoint 2016 External Content Type trough OData in VS 2015 with EF6

This one is the WCF Data Service, which should be under the Web Tab. Make sure to give it a proper name.

A page will appear, mostly Pre-populated

And here is where it gets a bit tricky. The first thing we have to do is replace the “public
WcfDataService1 : DataService< /* TODO: put your data source class name here */ >

Where we will have to replace it with DataService<
ContosoEntities> . (The connection string we created in Web.Config when creating our connection earlier). However, this will fail. The reason is that, Visual Studio wrongly defaults to using “DataService”, when this will not work with Entity Framework 6. We will need to make some changes!

In the Top Bar, under Tools > NuGet Package Manager, open the Package Manager Console

In the Console, run the following command to get the Entity Framework Provider Package “Install-Package Microsoft.OData.EntityFrameworkProvider –Pre”. It should successfully install as seen in the following screenshot.

At the top of your file, add the “using System.Data.Services.Providers;line to load the proper classes.

A bit lower in the file, change the DataService<ConnectionStringName> to EntityFrameworkDataService<ContosoEntities> (Where ContosoEntities, is the connection string name you defined earlier in this blog post)

Lower again, in this example, I used the “UserVerboseErros = true”, for debugging, but you can delete that line for production. More important, make sure to do a config.SetEntityAccesRules(“TableName”) EntitySetRights.(rights); . In my case, I gave them AllRead.

The Project is now ready, so I created a IIS Site called WebServices, as well as an Application called Contoso.

From Visual Studio, Click on “Publish ProjectName”

From now on, the procedure might vary depending on where you’re publishing your project to. The screenshots I will put here are for deploying on localhost. On the First Page, select “Custom”

Enter a Profile Name for this custom Profile

Enter the Server where you wish to deploy it (in my case localhost) and the Site name in format IISSiteName\ApplicationName

Also enter what the destination name will be, depending on the bindings you use on your IIS Site. Once you click on Validate Connection, you should see a green checkbox that appears near the button.

In the Database, select the available Connection String.

On the next page, you will see the items that will be deployed, and since it’s a new deployment we will see a bunch of them. Simply click on Publish and it should only take a few seconds.

If Everything works correctly, You should be able to navigate to the URL where you deployed your webservice /Servicename.svc and see something similar to this. An XML with your tables inside!

Next step, is to go to webservice/servicename.svc/TableName?TOP10 (Tablename IS Case Sensitive!) For example. . The result will depend on the browser. On IE you will see a RSS Feed Screen, with as you see, 6 results, but we can’t see the results.

On Chrome, you will see an XML, and if you look closely, you will actually see the customer data in there!

Cool , so our OData Service works, and is able to show data from the SQL Database in the Browser. You can now close that Visual Studio solution, and start a new one! This time, is of type “SharePoint Add-in”. And don’t worry, we will not actually deploy it, so you don’t need to have Add-ins Configured for this to work. You will however need a Dev Site Collection!

Enter the URL of your Dev Debugging Site, and then SharePoint-Hosted.

For the API version, I will select SharePoint 2016, since that’s where I want to deploy this Add-in

We will now need to add a New Item, Content Type for an External Data Source. And strangely, this is not in the “New Item” pop up as before, but directly on the Add!

For the OData Service URl, enter the URL to your Service, and give it a name!

Select the Table(s) on which you want to create External Content Types and make sure to leave the checkbox at the bottom checked.

After this is done, you should have two .ECT files in your Project.

Open the ECT file with the built in XML text editor in Visual Studio

In the top of the document, within the Model element, you will see a Name attribute. This Name attribute is the name you selected when you connected to the OData source, such as NorthwindCustomersModel. The value of this name is the same in all of the ECT files created from the entities, but it has to be unique in order to use it in SharePoint. You will need to change the name based on the ECT you are using , for example CustomersTable

Now, navigate to your project, copy this ECT File to somewhere on your desktop

You can then go into Central Admin, BCS Service Application and upload the ECT File. Also, If you didn’t already do it, make sure you have set the permissions!

Afterwards, make sure to use “Set Metadata Store”, to give it the required permissions

After that is done, go to any Site Collection, and add an “External List”

Select your External Content Type

And everything should work!

You now managed to show data in SharePoint, by using Business Connectivity Services consuming an OData Source! If you want to configure Hybrid BCS , you will need to follow a future blog post that will start from this point. I will link to it once it’s live!

4.92/5 (13)

Please rate this

As more people start playing with Data Loss Prevention (DLP) in SharePoint 2016, some of them have come across an “Unexpected” error when applying a DLP Policy to a Site Collection.

Value cannot be null. Parameter name: site

The error message in the ULS Log for your correlation ID would be similar to the following line:

Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.ArgumentNullException: Value cannot be null. Parameter name: site

This error most commonly arrives when you try to setup a policy for a Site Collection that is not in the same Web Application as your Policy Center. Due to Security reasons, the Compliance Policies can only apply DLP Policies to the same Web Application, so if you want to apply a policy to a Site Collection in a different Web Application, you would need a Policy Center Site collection in that Web Application.

I know the previous paragraph might sound confusing a bit, but to put it a different way, you need to create a Policy Center Site Collection in every Web Application that you want to apply DLP Policies in. If you try to apply a DLP Policy to a Site Collection in a different Web App, you will get the error above!

If you want an overview of Data Loss Prevention in SharePoint 2016, check out my CMSWire article over here: 

For a step by step tutorial on how to setup DLP in SharePoint 2016, check out my blog : 

Follow me on Social Media and Share this article with your friends!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
4.58/5 (12)

Please rate this

The Cloud Search Service Application has been in beta since August 2015, and will come Out of the Box with SharePoint Server 2016, and is available with SharePoint Server 2013 August 2015 Public Update or later. The Cloud Search Service application greatly improves the Hybrid Search experience by mixing up your SharePoint On-Premises results with Office 365 results in the same view, instead of the limiting results blocks we had to use with Federated Search.

Cloud Search Service Application

At Ignite last year when Microsoft showed it off to the world for the first time, they used our favorite fictional company Contoso for an example on how they could save money by using this new feature.


Cloud Search Service Application


Cloud Search Service Application

After implementing the Cloud Search Service Application, Contoso was able to go from 10 servers down to only 2 search servers. Saving 8 SharePoint Server licenses is indeed a very big incentive for Contoso to use this new service! However, until February 17th we had no idea if this service was going to cost us money, and if yes how much. With the latest blog post by Mark Kashman on the Office Blog called Auditing, reporting and storage improvements for SharePoint Online and OneDrive for Business we finally have some real numbers to put on the table.

In the blog post we learned that for every 1TB of pooled storage in SharePoint Online, we are allowed to put one million index items from our On-Premises SharePoint Farm. Let’s break it down to know what this all means.

First, let’s talk about pooled storage. Pooled Storage means the total amount of storage your company has for SharePoint Online. By default, we get 1TB included, plus 0.5 GB per user that we license in Office 365. So for a company with 2000 users, we would have 1TB + (2000 * 0.5 GB) = 2 TB. If we need more space, we can buy the “Office 365 Extra File Storage” Add-on at 0.20$/GB/Month so ~200$/TB/Month.

While most of the companies probably have under one million items in their On-Premises Search Index, which comes free with the included 1TB in Office 365, companies that have maybe 10, 15 million documents in their index will need to calculate their costs. Let’s take Fabrikam for example, another fictional MS company that currently crawls 20 million items with SharePoint 2013 and has 5000 employees.

Fabrikam would have 1TB + (5000*0.5GB) = 3.5TB of space in the cloud included with their subscription, but in order to move all their index in the cloud, they would need an additional 16.5 TB costing them 3300$ per month.

Remember that paying that 3300$ per month will also give them a total of 20 TB to store documents in the cloud, so Fabrikam could move some of their SharePoint sites in the cloud, and the less content that is crawled On-Prem, the less you need to pay since there is no price per document indexed in SharePoint Online.

Also remember that storage prices might change in the future as hardware prices drop, and with cloud competition also increasing, Microsoft might include more storage by default in Office 365.

Even with this price, I still think that the Cloud Search Service application can save money to enterprises and more importantly, provide an a lot better Search Experience for the Business users!

If you are not familiar with the Cloud Search Service Application, I did an overview at CMSWire: SharePoint Cloud Search: What’s in it For You

Do you think the pricing for the Cloud Search Service Application is fair? Looking forward to read your opinions in the comments!

Follow me on Social Media and Share this article with your friends!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
4.73/5 (11)

Please rate this

As I do more conferences and webinars around the brand new SharePoint Server 2016, I get a lot of questions asked by email, or private channels that could benefit everyone! So I will update this blog post as time advances with the latest events, and add answers to the questions you might have! Hopefully it will be useful!

SharePoint 2016 Frequently Asked Questions

Crow Canyon Webinar: What’s new for IT Professionals in SharePoint 2016 (January 21, 2016).

Q: Will the slides be made available?

A: Yes, slides are available at this link:

Q: Can I download this record later?

A: Yes, you can find the recording on Channel9:

Q: Will each server in the Min Role architecture require a SP license? If so, that’s really costly.

A: There is no official word on licensing yet, but I am pretty sure you will need a license for every SharePoint Server in the farm!

Q: I would love to see a demo on durable links? Is it possible on your blog post?

A: I will try to do a webinar on the durable links feature only in the future.

Q: Do you have a tutorial to setup a dev environment like the one on your demo, which can be used to evaluate all new features?

A: Not yet, I will wait for the SharePoint 2016 to be RTM so it doesn’t change that much anymore. You can simply install a single server VM for now and play with it!

Q: What are some reasons to upgrade to SharePoint Server 2016 from earlier versions?

A: Multiple reasons from new features, better stability and faster speed. Here is a blog post from a fellow MVP on some great reasons:

Q: Any information on mobile support for publishing sites?

A: I didn’t try it, but didn’t hear anything about support for publishing sites yet!

Q: Is PerformancePoint in this version yet?

A: Performance Point will be in SharePoint 2016!

Q: Are there any new BI features?

A: SSRS now uses HTML 5, and has some cool small features, but that’s it!

Q: Can you give some more info about how setting up the cloud search service application?

A: Check out this blog post:

Q: Is the DLP Feature available in SharePoint Server 2016

A: Yes it is! Check this blog post to learn how to set it up:

Q: Do we still have to migrate the WSS content database and use PowerShell to migrate from 2013 to 2016?

A: Yes

Q: Is Shredded storage still available in SharePoint 2016?

A: Yes

Q: Can you confirm that you have to have all four MinRole, before you are considered to have a MinRole farm?

A: Yes. If you don’t have one of each (WFE, APP, Search, Distributed Cache), your farm will not work properly and you should use “custom” and start services where you need them.

Q: Does SharePoint now have shortened URL for documents?

A: Not out of the box, but there are some third party tools that offer it.

Q: What’s the penalty for not having a MinRole farm?

A: You don’t fully benefit from Microsoft’s latest investments into SharePoint 2016 for performance and stability, However you are still fully supported.

Q: Is there any change in the App-Model?

A: From an IT Pro perspective the only change is that now it’s called the Add-in Model J.


Q: SharePoint 2016 supports TLS 1.2. What version of TLS does SharePoint 2013 support?

A: SSL 3 & TLS 1.0

Q: Will SharePoint 2016 run on Server Core for Windows Server 2012 R2?

A: Nope!



Q: Can we author custom DLP rules?

A: We cannot create new templates at the moment in SharePoint 2016. If this feature changes, I will update the post.

Q: Do durable links work across site collections and web applications?
A: It works in the same Site Collection for sure. Will have to test if it works cross-site collection / Web Application.

CardioLog Analytics Webinar: What’s New in SharePoint 2016 for End Users (February 3, 2016)

Q: Can we download the slides?

A: Yes, you can find the slides on SlideShare here:

Q: Is Enterprise license needed for DLP? Or is it included in the standard?

A: It’s an Enterprise only feature as per 


Q: What Service update patch is required for the Cloud search service (For SharePoint 2013)?

A: August 2015 Public Update

Q: I’m a SharePoint branding person and how it works with the design manager in SharePoint 2016? Will that be existing? What is the work around?

A: I am not a branding person, so I didn’t test it, however since Design Manager is available on SharePoint Online, I am 90% sure it’s also available in SharePoint 2016. I will test and update blog post with answer!

Q: Do you have any idea when Microsoft will release SP2 for SharePoint 2013?

A: Nope.

Q: What are the minimum software and hardware requirements for SharePoint 2016?

A: Software: Windows Server 2012 R2, Windows Server 2016. SQL Server 2014 SP1 or SQL Server 2016. Hardware are same as 2013. 12-16GB Ram, 4 Core CPU, 80GB of space on C Drive.

Q: Can Hybrid Search work the other way i.e. O365 (SharePoint) online searching for content on-prem?

A: Hybrid Search pushes your on-prem index in the cloud, therefore from O365 you can search on-prem content. You can setup your on-prem farm, to query Office 365 afterwards to show content from on-prem as well as Office 365.

Q: Does SharePoint forms customized with InfoPath on SharePoint 2013 works on SharePoint 2016 after migration?

A: It should work, yes!


Follow me on Social Media and Share this article with your friends!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
5/5 (4)

Please rate this

I am extremely happy to announce that my third Pluralsight course has been released over the weekend. While my Planning and Deploying Office Web Apps 2013 and my PowerShell for Office 365 courses were more geared towards the IT Pro audience, this course on Creating a Workflow in SharePoint Designer is really for everyone from End Users to IT Pros that want to know how to create simple and powerful workflows with SharePoint Designer.

Creating a Workflow in SharePoint Designer

In this course, I will cover the following topics:

  1. Learning the Basics

    In this module, I cover the basics of SharePoint Workflows, and all the terms you need to get started. We learn the types of Workflows, the Start Types as well as what exactly are Actions and Conditions.

  2. Out of the Box Workflows

    SharePoint 2010 and 2013 both include some basic Out of the Box Workflows that can do a good job, without any customizing. Before going in SharePoint Designer, we will learn what SharePoint has to offer Out of the Box!

  3. Creating a Workflow in SharePoint 2010 Mode

    In this Module, we will learn how to create a SharePoint Workflow, the basics of creating workflows in SharePoint Designer, the available actions and conditions as well as go through two Real World scenarios.

  4. Creating a Workflow in SharePoint 2013 Mode

    In this Module, I will go through the differences between 2010 and 2013 mode workflows, and you will learn the new things such as steps, loops and finish the module with a real world scenario.

  5. Visio Integration

    In this Module we cover the integration between SharePoint Designer and Microsoft Visio.

This course applies to SharePoint 2010, 2013, 2016 as well as SharePoint Online in Office 365. The only module that doesn’t apply to SharePoint 2010 is module 4.

Creating a Workflow in SharePoint Designer

You can find the course at or by clicking the image below! If you don’t have a Pluralsight account, you can open a 10 Day Free Trial or you can also try to get the Free Pluralsight 6 Month Subscription that still appears to work!

Creating a Workflow in SharePoint Designer

Follow me on Social Media and Share this article with your friends!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
5/5 (11)

Please rate this

As part of the release of SharePoint 2016, and included since Beta 2, Microsoft included Data Loss Prevention (DLP) Capabilities in SharePoint Server. DLP, not to be confused with DPM (Data Protection Manager), is a way to make sure that your employees do not put sensitive information such as Social Security Numbers, Credit Cards, Passport Numbers or more in sites where they shouldn’t. When users upload documents they shouldn’t, the item can be blocked from viewing, and the user and selected administrator will receive an email notification. To give you a glimpse of the final result, here are some screenshots:

Configure DLP in SharePoint 2016


Before getting DLP to work, there are some pre-requisites, but don’t worry they aren’t big.

  1. Configure the Search Service Application
  2. Crawl the location of the conflicting documents
  3. Configure Outgoing e-mail
  4. Your Users need to have an e-mail address in their profile.

For this example, I will put those two files in SharePoint. File one contains A Social Security Number as well as Tax Information.

File two is a list of credit cards from my consumers.

You can download both files on my OneDrive here. Make sure to upload all your files in SharePoint, and start a crawl. To make sure they are searchable, do a search for them in a standard SharePoint Search box.

If those four pre-requisites do not work properly, your DLP will not work!


2. Configure DLP in SharePoint 2016

After your pre-requisites are done, the first thing we need to do is create two site collections. The first one is the Compliance Policy Center. Simply create a new Site Collection and give it that template, which is under the Enterprise Tab.

The second one we have to create is an eDiscovery Center. This template is also under the Enterprise tab.

Now that our two Site Collections are created, let’s go to the eDiscovery Center to see if the SharePoint system can correctly identify our documents. So Navigate to the eDiscovery Center and click on Create DLP Query

Afterwards, once you’re on the Data Loss Prevention Queries page, click on “New Item”

A popup window will show to ask us what kind of DLP Query we want to test. For this example, I will select PCI Data Security Standard. If you look at the description, this will find Credit Card Numbers, and since one of my demo files had a credit inside, it should work.

NOTE: If you don’t have a file with credit cards, this won’t work. If you only have Social Security Numbers, choose US Personally Identifiable Information.

Afterwards, we have the option to show results, only if a certain “violation” is committed a certain number of times. Since we only want to test our system, we will put “1” in that box. Afterwards click on “Next“.

After we click next, a New “Query Item” window will open, and the Query will already be pre-created for us. First thing we have to do is Give it a Name, and afterwards click on Modify Query Scope.

Select the “Select Sources” checkbox, and afterwards “Add Location”

Add the Site Collection on which you uploaded your documents earlier. In my case it was https://portal.demo.local . Afterwards click on OK.

If you put the Root Site Collection, you will get the warning that the search will happen in all the Web Application which works for us! Simply Click OK!

After that is done, Click the Search Button, and you should have at least one result, the file we just uploaded that contains Credit Card Information.

If you uploaded multiple documents and want to test them all, make another DLP Query on that item. In my case, I also had another document with a Social Security Number, so I created a new DLP Query looking for US Personally Identifiable Information. As you can see, the eDiscovery center was able to find my document.


If it all works for you until now, it means that your Search is configured correctly, and SharePoint can find your documents, however you don’t have a policy yet. Now, we need to navigate to the Compliance Policy Center site we created previously. On the site, click on “Data Loss Prevention Policies”

Afterwards, click on “Data Loss Prevention Policies” again.

We are then going to click on “New Item”

Then we will have a very similar screen as in the eDiscovery Center, except a few differences. First thing first, enter the Name of your policy and select the type. I selected PCI Data Security Standard in order to find documents with credit cards. Afterwards, select how many conflicts there must be for this rule to take effect, I selected one. Until now the screen is pretty similar to eDiscovery, but that’s where it changes.

Enter an email address where a notification must be sent when there is a document in violation. In my case, I want to notify my compliance department, so I entered compliance@demo.local . We then have the choice, to enable or not the Policy Tip. The Policy tip is what you saw in the first screenshot where, directly in SharePoint, the user is notified via a red popup that his document is violating certain rules. The other choice is do we want to block that document? As soon as the document is found, we can limit the access to Site Admins and the owner/editor of the document. No one else can then see the document. In my case, I selected both checkboxes and clicked save.

Configure DLP in SharePoint 2016

Afterwards, I created a very similar one but about US Personally Identifiable Information. I won’t include a screenshot of it. After your Policies are created, we need to assign them to Site Collections. So Click on “DLP Policy Assignments for Site Collections”

In that list, click on “New Item”

As the form says, click on “First choose a site collection”

Enter the Title or the URL of the Site Collection you want to assign it to, then select the checkbox next to it and click “Save”

You will notice that the Site Collection got added at the top. Now click on “Manage Assigned Policies”

Select the Policy you want to apply, and then click Save.

NOTE: In SharePoint 2016 Beta 2, it’s a 1 to 1 mapping between SC and Policies. Meaning you cannot add multiple Site Collections in the same Assignment, and you cannot select multiple Policies in the same assignment. To apply two policies to the same Site Collection, create a new Site collection assignment! It might, or might not change in RTM.

You will notice the Policy got assigned to the Site Collection now click Save.

Since I wanted to also apply the SSN policy to my Site Collection, I created a new Policy Assignment and my list now looks like this:


Now What? Well, it doesn’t happen right away! If you noticed at the top of the “New Policy Assignment” page, there was an information stating that, it might take up to 24 hours before you see the results. That is because, depending on the importance of your policy, it might take up to 24h to run! However, if you created “High Priority” rules like we just did (SSN, Credit Card), the timer job runs every 15 minutes.

The results


So, we wait a bit, and then, we will start receiving emails! Let’s look at the emails first:

There is a bug in SharePoint 2016 Beta 2, where the email that should go to the user with subject “Notification: DocumentName.docx” goes to the email you defined in the Policy instead. Microsoft is aware of this bug and will be fixed by RTM.

So let’s look at our notification, only for the SSN, the Credit Card one will be the same but different small details.

  1. The User notification for the SSN error. (In Beta 2 it was sent to Compliance@demo.local, but it was supposed to be sent to adamb@demo.local, since he uploaded the document)

  1. The Administrator notification for the SSN Error. As you can see there is a lot of useful information and I highlighted some of it!

The Policy Tips

Now that we see the Email Notifications, let’s look at the Policy Tips which personally, I find pretty cool! First thing that you will see is that The documents now have a “Stop” sign on them, showing something is wrong.

The document information panes tells us that the access to the document is blocked because it conflicts with a policy in your organization. If a user sees this prompt, it means he has access to the document. When the document is blocked, users who can’t access it don’t even see it in the document library. Afterwards click on “View Policy Tip”


The Policy Tip shows us what is wrong with the item, as well as who has access to it now. As a User you have two choices, you either go in the document, edit the bad part or if you think it’s an error, you must click on Resolve.

When you click on Resolve, You can either ask to Override the Policy, which means that you are aware, and its normal the data is in the document. The other choice Reporting, which means that you think the document is fine and shouldn’t trigger the policy.

When you click Override, you are encouraged to provide a business justification. So I made up a justification and clicked Submit.

I got the information that My response has been recorded, and that the Policy Tip has been resolved.

The document is also not blocked anymore.


Now let’s see what happens when we click “Report”. We simply Click Report, and then we get the same “Thanks Message”

Note: In SharePoint 2016 Beta 2, I didn’t receive any notification information as the policy creator that someone said it was ok.


That is about it for configuring SharePoint 2016 DLP. This post was written for SharePoint 2016 Beta 2, but I will update as needed when RTM comes out. If you have any questions or opinions, ask in the comments!

Follow me on Social Media and Share this article with your friends!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
4.83/5 (36)

Please rate this

While setting up a lab environment for SharePoint 2016 Public Beta 2, everything went well up to when I tried to run the SharePoint Config Wizard. I was hit by this ugly error:


api-ms-win-crt-heap-l1-1-0.dll is missing

Psconfiggui.exe – This program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

After researching and troubleshooting I found out that I have this error because I was missing the Windows 10 Universal C Runtime update. This comes by default in Windows Server 2016, so this should only happen to you if you’re using Windows Server 2012R2. So, first thing, go to the download center and download KB2999226 here:

Seems like a pretty easy fix, and in 80% of the cases this will work for you. If you manage to install it without errors, PSConfig should work for you with no problems. However, when I tried to install I had this error… The update didn’t apply to my computer.


That left me with a lot of questions, since I was sure that I downloaded the Windows Server 2012 R2 patch. What I discovered is that the Windows 10 Universal C Runtime KB2999226, is dependent on a Windows Server 2012 R2 Cumulative Update package in KB2919355 . So, if you have the “The update is not applicable to your computer”, make sure to run Windows Update first, then download KB2919355 and do a full reboot. Afterwards, you will be able to install the Windows 10 Runtime, and everything will work properly.

This post was written for SharePoint 2016 Beta 2, and prerequisites might change between now and then! I hope this saved you a few hours of searching on google and your update history! Don’t hesitate to drop a comment if this worked for you, and if you did something different!


Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.
5/5 (1)

Please rate this

InfoPath, everyone’s favorite forms-creation and data-gathering tool that helps organizations streamline business processes is now available as a standalone download on the Microsoft Download Center.

After it was doomed to be discontinued and replaced by an advanced FoSL solution, InfoPath won the battle and is currently the only out of the box Microsoft product to create and modify custom forms in SharePoint. If you want to read the whole story, check out this blog post: InfoPath is back in SharePoint 2016 & FoSL vNext is dead!


InfoPath 2013 Standalone

Since InfoPath 2013 is the last version of InfoPath, it will not be included in the Office 2016 suite as it was previously. So, Microsoft just posted the standalone version of the product on the Microsoft Download Center. One important thing to note is:

“The download and use of InfoPath 2013 software requires an active Office 365 ProPlus subscription.”

So, if you want to use InfoPath 2013 with Office 2016, you will need to have an active ProPlus subscription on Office 365, and not just the Office 2016 license. I did not test to see if this policy is enforced, but if anyone does, please tell me in the comments!

Here is the download link for the InfoPath 2013 for Office 365 ProPlus Subscription standalone client:

Share this blog post with your followers on twitter by clicking the birdie below!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page   on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  I am also a Pluralsight author, and you can view all the courses I created on my author page.

No ratings yet.

Please rate this

SharePoint Server 2016 Preview just came out, and a lot of you have probably already downloaded it, or plan to download it and test it to find out what is new. Sometimes when installing SharePoint 2016 I had this error randomly, and I Saw on twitter that I wasn’t the only one, so I decided to make a blog about it.

Basically, when installing SharePoint Server 2016 you get the “Microsoft SharePoint Server 2016 encountered an error during setup”, and when the error page opens you see its error 1603.

SharePoint Server 2016 encountered an error during setup

In my case, I only had to restart the installer and everything went fine, but in the past when the installer crashed, it used to be because the SharePoint VM only had one core. So, try to re-start the SharePoint setup, and if that doesn’t work, make sure your SharePoint VM has at least two cores.


If that doesn’t work, try this fix by Luis Valencia!  Run this in PowerShell as an Administrator!

if(!(Test-Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer)){
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer | Out-Null
$regProps = Get-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer
if(! $regProps.logging){
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer -Name logging -Value voicewarmup -PropertyType String | Out-Null
if(! $regProps.debug){
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer -Name debug -Value 3 -PropertyType DWord | Out-Null

Let me know in the comments if you had this error!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

No ratings yet.

Please rate this

SharePoint 2016 Preview

By now, you probably know that SharePoint 2016 Preview will be out in August! This is big news since initially, the first Public Beta was supposed to come out during Q4 2015!

SharePoint 2016 Preview

Why release it in August instead of Q4?

Microsoft wants to solicit feedback and validate the stability of SharePoint 2016, while the product is still not finished. In the past, Microsoft relied heavily on the TAP program to get the feedback, and when the preview was released, it was almost in its final form. Similar to what Microsoft did with Windows 10, they really want the feedback of the community early, so they can still incorporate it in the product before the final release. August is actually this month, so I hope you are really excited! Hopefully as excited as Julia White at WPC!

In this blog post, I got information from all around the web about what you need to know about SharePoint 2016 Preview!


Q: What do I need to get ready for SharePoint 2016 Preview?

A: You need to prepare some Virtual Machines, between 3 (1 SharePoint -1 SQL – 1 DC) and at least 6 (1 WFE -1 Application – 1 Distributed Cache – 1 Search – 1 SQL -1 DC) for a best practice MinRole deployment. Here is a screenshot of the available roles from the Ignite slides. You need to set them up on Windows Server 2012 R2 or Windows Server Technical Preview, with SQL Server 2014 SP1 or SQL Server 2016 Preview

SharePoint 2016 Preview Minrole

Q: Does the final product will be released earlier?

A: Nope. Preview is released earlier to get more feedback, but that doesn’t mean the final product will be released earlier.

Q: What is included in the Preview?

A: In the SharePoint 2016 Preview, you will mainly see the investments in the Infrastructure part of SharePoint. Since SharePoint 2016 is the first release of SharePoint built from the cloud down, Microsoft got a lot of experience in managing SharePoint and improving performance and stability, so that’s the main set of “features” that will be included in SharePoint 2016 Preview. Here are some of the features:

  • MinRole
  • Increased Max File Size
  • Everything else that Bill Baer mentioned at Ignite in BRK2188

Q: Will full trust code be deprecated?

A: Nope!

Q: Will there be any new end-user features in SharePoint 2016 Preview?

A: There will be, however there are no news on what they will be!

Q: Why focus on IT Pro features in the SharePoint 2016 Preview and not end user features?

A: To quote Bill Baer, to build a house, you first need a solid foundation. When you look at SharePoint, what the end users see is all the features, which is the house, but before building the house, you need that solid foundation to build it on.

Q: Will the Cloud Search Service Application be included in SharePoint 2016 Preview?

A: Yes!

Q: Will there be any cumulative updates to test the new patching in SharePoint 2016 Preview?

A: No, the preview is static, so no cumulative updates will be available for it.

Q: What about Office Web Apps?

A: The Office Web Apps team and SharePoint team are separated at Microsoft, so it’s not known when they will be ready to release their preview.

Q: What will be the new List Threshold limit for SharePoint 2016 Preview?

A: For the preview, it will still be at 5000, and Microsoft wants you to test with thousands of list items, and tell them what performance you are getting. Since it’s not a final product, Microsoft cannot do proper scale tests yet. Remember that it’s a recommended limit, and you can play with it as you want from the Central Admin!

Q: Are there any Easter Eggs in SharePoint 2016 Preview?

A: Maybe! To find them, you will really have to push the limits of SharePoint

Q: What are the minimum hardware requirements for SharePoint 2016?

A: Read this blog post:

Q: Can I upgrade Site Collections in 2010 mode (or 14.5 mode) directly to SharePoint 2016?

A: No, Site Collections will have to be in full 2013 mode

Q: What can I read or listen to be ready for SharePoint 2016 preview?

A: Here are the resources I used for this blog post which you should definitely read or listen to:

Last Thoughts

When you test SharePoint Server 2016, please remember that it’s not the final product, and not many end user features will be included inside. The preview is a great opportunity to give feedback to Microsoft on what they are doing right, and what they are doing wrong and hopefully they will do it all right by the time RTM comes out! There have been talks about SharePoint dying for the past two years, and as you see, that is certainly not the case as Microsoft really wants SharePoint 2016 and SharePoint Hybrid to be very successful.

Who else can’t wait for the preview?


Share this blog post with your followers on twitter by clicking the birdie below!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

No ratings yet.

Please rate this