Allowing users to set alerts on SharePoint lists and libraries is the easiest way to keep users informed with what is going on within your intranet and team (collaboration) sites. This functionality has been a part of SharePoint for many versions and is an easy feature for users to take advantage of. That is, IF you have all the settings correct. Your first sign that alerts are not setup for use is when looking at the library (or list) tab in the ribbon, and you don't see the Alert me button in the Share & Track section. There are two settings you need to check: first you need to make…
-
-
Convert SharePoint 2016 Trial to RTM License
It is generally a good idea to try software before you purchase or implement it fully. We have already seen a great interest in SharePoint Server 2016 and we have installed the trial version many times to give the ‘try before you buy' experience to our clients. Once you decide to go from the trial license to the ‘full' RTM version, the process to convert your license is simple and is the same as it has been in earlier SharePoint versions. The license conversion starts on the Central Administration site – you can do this via PowerShell, but we will be using the GUI this time. Select the Convert farm…
-
SharePoint 2010 Site Experience With SharePoint 2016
While testing an upgrade today, I was reminded of a requirement when upgrading to SharePoint 2016 using the database attach method – you must upgrade all site collections to the SharePoint 2013 experience before you attempt to attach the database to a SharePoint 2016 farm. My test today is using a SharePoint 2010 content database and attempting an upgrade to SharePoint 2016. I first performed a database attach upgrade with a SharePoint 2013 farm, then performed the Test-SPContentDatabase PowerShell command on the database from my SharePoint 2016 farm. It is important to notice that the LegacySiteDetected error shown above is an UpgradeBlocking error, meaning the upgrade will fail if you…
-
The Future of SharePoint Captured
Yesterday, May 4th 2016, Microsoft hosted “The Future of SharePoint” event in San Fransisco, USA. The host was Jeff Teper, corporate vice president for OneDrive and SharePoint, and along with other Microsoft presenters, Teper showcased the road-map for the SharePoint platform – both on-prem and in the cloud. Along with announcing the general availability for SharePoint 2016, Microsoft highlighted new SharePoint features and functionality. You can read all about the event and the announcements on the Microsoft Office Blogs post. I will in the days and weeks ahead, cover the new functionality with real-world examples. Before the event, Microsoft used the Twitter hashtag #FutureOfSharePoint to promote the event. Whenever I…
-
SharePoint 2010 Workflows on a SharePoint 2016 Farm
[This is a quick post – it will be updated with more information soon] During a recent client meeting, I was asked if SharePoint 2010 version workflows, developed on a SharePoint Server 2013 farm, will continue to work if the server farm is upgraded to 2016. SharePoint Server 2016 has not been released at the time of this writing, but we do have the Release Candidate to test with, so I went about testing. On a SharePoint Server 2013 farm (version 15.0.4719.1002, which is SP1 with May 2015 CU) I created a SharePoint 2010 version workflow and associated it with a document library. I took a SQL backup of the content…
-
Upgrade SharePoint 2010 to 2016 Release Candidate
It is a frequent question – can I skip a SharePoint version when upgrading? For example can I do a direct upgrade from SharePoint Server 2007 to 2013? The answer is no, you can't without having to use a migration product – which isn't really “upgrading.” The path to upgrade SharePoint 2007 to 2013 includes an upgrade to SharePoint 2010 first. In March of 2015, Bill Baer, Senior Product Marketing Manager at Microsoft, asked if there was any demand for skipping ahead when doing a SharePoint upgrade (a.k.a. N-2 upgrade). #SharePoint question…if you could N-2 upgrade would you? I.e. 2010 > 2016 without stopping at 2013 first… — Bill Baer (@williambaer) March…
-
SharePoint 2016 and Maximum Degree Of Parallelism (MAXDOP)
I was a speaker at five SQL Saturdays this year and at each one of them I was asked why SharePoint requires the SQL Server Maximum Degree Of Parallelism setting to be set equal to 1. After explaining the reason, I would get a blank stare and then a response like “so SharePoint is inefficient and is hard-coded to look for MAXDOP=1?” Knowing that I would be asked the same question again at the next SQL Saturday, in late July I sent out a tweet trying to get an answer to the question: “Will SharePoint Server 2016 require MAXDOP to be equal to 1?” The only response I received was…
