PowerShell script to configure SQL Server Reporting Services in SharePoint mode


The below mentioned script will take care of the steps listed below :

  1. Installs Reporting Services service and service proxy, and starts the service.2
  2. Creates a service proxy named “Reporting Services”.
  3. Creates a Reporting Services service application named “Reporting Services Application”.
  4. Enables the Power View feature for a site collection.


#Script for SSRS Configuration in SharePoint Integrated mode

write-host -foregroundcolor DarkGray StartTime>> $starttime

Write-Host -ForegroundColor Green “Import the SharePoint PowerShell snappin”
Add-PSSnapin Microsoft.Sharepoint.Powershell –EA 0

Write-Host -ForegroundColor Green “Install SSRS Service and Service Proxy, and start the service”
Write-Host -ForegroundColor Green “>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>”

Write-Host -ForegroundColor Green “Install the Reporting Services Shared Service”

Write-Host -ForegroundColor Green ” Install the Reporting Services Service Proxy”

# Get the ID of the RS Service Instance and start the service
Write-Host -ForegroundColor Green “Start the Reporting Services Service”
$RS = Get-SPServiceInstance | Where {$_.TypeName -eq “SQL Server Reporting Services Service”}
Start-SPServiceInstance -Identity $RS.Id.ToString()

# Wait for the Reporting Services Service to start…
$Status = Get-SPServiceInstance $RS.Id.ToString()
While ($Status.Status -ne “Online”)
Write-Host -ForegroundColor Green “SSRS Service Not Online…Current Status = ” $Status.Status
Start-Sleep -Seconds 2
$Status = Get-SPServiceInstance $RS.Id.ToString()

write-host -foregroundcolor DarkGray StartTime>> $starttime
write-host -foregroundcolor DarkGray $time

Write-Host -ForegroundColor Green “Create a new application pool and Reporting Services service application”
Write-Host -ForegroundColor Green “>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>”
Write-Host -ForegroundColor Green “Create a new application pool”
#!!!! update “-Account” with an existing Managed Service Account
New-SPServiceApplicationPool -Name “Reporting Services” -Account “<domain>\User name>”
$appPool = Get-SPServiceApplicationPool “Reporting Services”

Write-Host -ForegroundColor Green ” Create the Reporting Services Service Application”
#!!!! Update “-DatabaseServer”, an instance of the SQL Server database engine
$rsService = New-SPRSServiceApplication -Name “Reporting Services Application” -ApplicationPool $appPool -DatabaseName “Reporting_Services_Application” -DatabaseServer “<server name>”

Write-Host -ForegroundColor Green “Create the Reporting Services Service Application Proxy”
$rsServiceProxy = New-SPRSServiceApplicationProxy -Name “Reporting Services Application Proxy” -ServiceApplication $rsService

Write-Host -ForegroundColor Green “Associate service application proxy to default web site and grant web applications rights to SSRS application pool”
Write-Host -ForegroundColor Green “>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>”
# Associate the Reporting Services Service Applicatoin Proxy to the default web site…
Get-SPServiceApplicationProxyGroup -default | Add-SPServiceApplicationProxyGroupMember -Member $rsServiceProxy

write-host -foregroundcolor DarkGray StartTime>> $starttime
write-host -foregroundcolor DarkGray $time

Write-Host -ForegroundColor Green “Enable the PowerView and reportserver site features”
Write-Host -ForegroundColor Green “>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>”
#!!!! update “-url” of the site where you want the features enabled
Enable-SPfeature -identity “powerview” -Url http://server/sites/bi
Enable-SPfeature -identity “reportserver” -Url http://server/sites/bi

####To Verify, you can run the following:
#Get-SPServiceApplicationPool | where {$_.name -like “reporting*”}


List of build numbers required to upgrade to the next on-premises version of SharePoint:


I guess it’s very important to check and ensure that your existing environment is running a version of SharePoint that can be upgraded to the next version while you’re planning for a SharePoint upgrade.

So keeping that in mind, I’ve prepared a list of the build numbers for various SharePoint versions that should help in planning the upgrade.

  • To upgrade from SharePoint 2007 to 2010, your SharePoint 2007 farm should be on this build number–> ( i.e. SharePoint 2007 SP2, build number (12.0.6421.1000) )
  • To upgrade from SharePoint 2010 to 2013, your SharePoint 2010 farm should be on this build number–> ( SharePoint 2010 SP1, build number (14.0.6029.1000) )
  • To upgrade from SharePoint Server 2013 to 2016, your SharePoint 2013 farm should be on this build number–>( SharePoint Server 2013 SP1 + March 2013 PU, build number (15.0.4481.1005) )

 Note: Also, please ensure that you fix the errors in the current environment itself before you upgrade to the next version as the errors will not be fixed once you upgrade to the next version of SharePoint. An error in SharePoint is an error on all the versions and just upgrading it won’t fix it.

Upgrade Methods to the next on-premises version of SharePoint:

The tabular column below should help you in choosing the right upgrade method if you’re planning to move to the next on-premises version

tabular column.png

Thanks for reading this post .Happy SharePointing!!!







Recording of my Webinar Session on SharePoint 2016 Overview

webinar pic.PNG

For those who missed my session on SharePoint 2016 overview, please find the link to the video recording below.

Part 1-Webinar on SharePoint 2016 Overview

Part 2- Webinar on SharePoint 2016 Overview

Thanks once again for attending my session and will see you all soon on a different webinar shortly.

Happy SharePointing!!!

Webinar on SharePoint Server 2016.

Hi All,

Please join me for a webinar on Jan 21st at 6:30 pm IST on ” Overview of SharePoint Server 2016” .



  • SharePoint 2016 Overview & Focus areas
  • Software & Hardware Requirements to implement SharePoint Server 2016
  • What’s new & what’s deprecated?
  • Deep dive into MinRole,Feature packs and Zero Downtime Patching
  • Deployment Guidelines and Best practices for SharePoint Server 2016
  • Migration approach to SharePoint 2016
  • Recap & Conclusion

I’ll be discussing in detail Microsoft SharePoint Server 2016 and all it’s new features and functionalities.

Meeting details : http://www.c-sharpcorner.com/events/overview-of-sharepoint-server-2016

SharePoint Infrastructure Assessment Questionnaire for transitioning new customers

The questionnaire which I prepared below can be used to  assess the existing SharePoint environment for support transition and to collect key Information to propose the right support model for the transition.Folks who are working on transitioning new accounts/customers to your team can use this questionnaire to ease the transition phase.


1.Business Goal:

  1. What is the primary business objective of the SharePoint environment? (What needs of your business are met by the existing system – Communication, Collaboration, Knowledge Management, Enterprise Content Management, Document Management, Dashboards, Complete Intranet Solution, Extra-net for suppliers, customers etc.?)
  2. Please share the status of all ongoing and planned activities for SharePoint (Development, migration and upgrade)?
  3. SharePoint farm version (SP 2010, SP 2013, SP 2016 & Office 365)?
  4. Please enlist the sites that are most critical to business?
  5. Please list down all the mission critical services that are hosted in SharePoint and its purpose

2.Infrastructure details:

  1. Explain in detail about how the domain controller is configured and the primary and secondary data center details?
  2. Please provide details or preferably Physical and Logical Architecture Diagrams for Production, Staging and Development Environment (i.e. Farm Topology, deployment diagrams, Virtual environment, SharePoint version details, Directory Services)
  3. Server hardware & software specifications
  4. Total number of users? Number of concurrent users?
  5. Server Naming Convention for Prod/Dev/Test servers
  6. Licensing details for SharePoint, Office web apps, Office Online server, Windows server and other supporting platforms.
  7. Please enlist all Integration points (Interfaces) with External LOB and other applications/ Software (Ex: SAP Integration with SharePoint
  8. Please give a brief explanation about all Web Applications and service applications in scope.
  9. Please provide the list of all 3rd party software’s that has been integrated with SharePoint (Ex: Ninetex Workflow, Doc Ave & Boldon James etc.)
  10. Explain in detail about the load balancing methodology used for the SharePoint Environment ((ISA? TMG? CISCO Ace? Or any other Hardware load balancer, F5 Big IP?)
  11. Is there any redundancy for Service applications and if yes how are they configured
  12. Are there any service applications which are being shared between two farms?
  13. DR farm details and its configuration for Business Continuity. A separate DR farm on a different data-center or a stretched farm where the servers are distributed across two data centers?
  14. Backend SQL Server details (i.e. SQL Server version, what level of permissions do we (i.e. SharePoint admin) have on SQL, SQL alias, named instance for SharePoint etc. . .)
  15. Backup strategy for SharePoint content databases.
  16. RTO and RPO strategy for SharePoint content databases.
  17. High Availability strategy for SQL Server – Clustering in place? Mirroring? Always ON?
  18. Authentication mechanism for SharePoint.
  19. Known issues in the farm if any?
  20. Language pack details if installed?
  21. When the farm was recently patched?
  22. Repository for configuration files, Implementation/Build guides, Known error database (KEDB), Incident Logs, RCA (root cause analysis), (CSV, SVN, TFS, etc.
  23. Deployment architecture? Give an overview (Farm solutions or Sandbox solutions)
  24. Do you have Office web apps/Office Online server deployed? If yes, detailed explanation of the Office web apps farm.
  25. Do you have Workflow Manager deployed? If yes, detailed explanation about the Work flow manager farm.
  26. How often do you perform a data refresh to the UAT and TEST farm?
  27. Details about AV scanning for the SharePoint farm?
  28. Do we have any monitoring in place for monitoring the environment (Ex: SCOM, Zenoss monitoring tool)?
  29. Are you using IaaS platform for SharePoint, if yes details about that? (AWS, Azure & Google Cloud Platform) .VM machine types if the SharePoint environment is on Azure, A series, D series, G series etc.?
  30. Health check scripts if available and it’s frequency. How often does the health check script run and what are the parameter it monitors?

3.SharePoint Online (Office 365) details:

1.What’s the Office 365 plan that your users are using?

2. How are the user identities synced from on-premises AD to Azure AD?

3.Are you using any Hybrid functionalities (One drive for business, Hybrid Search, Hybrid user profile, Hybrid App launcher etc.)?

4.Detailed explanation about the customizations made on the SharePoint Online sites.

5.Documentation of all the customization made on the SharePoint Online sites.

6.Migration tools used to migrate to SharePoint Online from on-premises.

7.What level of permissions will the SharePoint Online tenant admin have on the Office 365 tenant? Just SharePoint administrator or Global administrator?

8. Who will take care of Office 365 license management?


1.Please explain in detail about the most critical sites (in scope) on existing environment?2.Please share the information architecture

3. Please share the governance plan for the SharePoint environment.

4. List of blocked and allowed file types in SharePoint?

5. Content management:

1.What’s the main kind of content that’s stored in SharePoint? (Text content, Documents, Images, flash, Audios, Videos, other formats etc.)

2.Is there any other Content Management or Document management tool in place along with SharePoint (Ex: Onbase from Hyland software)?


1.Are the SharePoint sites secured (Using SSL, encryption)?

2.Details about the SSL certificates used for SharePoint sites?

3.If the SharePoint sites are made available to internet/ external sharing what’s the authentication mechanism followed for that?

4.What is the current Authentication mechanism? (Windows Authentication, Forms based Authentication or Kerberos, AD, LDAP )

5.Authentication mode used for web applications (Claims or Classic)?

7. Customizations:

1.Does the SharePoint farm /SharePoint Online have customizations on it?

2.If yes, what’s the total number of farm solutions, User solutions & sandboxed solutions that’s been deployed?

3.Detailed description /documentation of all the WSP files that’s been deployed and its use?

4.If we have apps deployed to the app catalog, then detailed description about those apps?5. What kind of apps are they? Provider hosted, Auto –hosted or SharePoint hosted?

  • List of custom scripts running on the SharePoint servers and its purpose.
  • How Branding is applied, what’s being done? (Feature staplers/custom site definitions/Themes/Custom CSS, Master pages, etc.)
  • Do we have a SharePoint developer/developer team who takes care of all the development related tasks and if yes his/her details?

 8.Supporting Team details:

1.Who is supporting the existing environment? Please provide existing SLA and priorities for incident management.

2.Please give a brief description about team structure for Support (OS, Hardware, SQL server, Security, Exchange server, SharePoint, Cloud Management team)

3.Do you have a distributed development team across multiple locations/geographies? Please provide details.

4.Do you have a distributed team of site owners?

9.Vendor details:

1.Does this account have Microsoft premier support? If yes, whom to contact for opening a support case. Microsoft PFE and TAM contact details for this account if applicable?

2.Name of the Vendor who did all the SharePoint environment customizations.

3.Can we reach out to the Vendor for any customization issues which is not in our scope of support, if yes contact details of the Vendor?

4.Vendor details for the third party tools that’s used in the SharePoint farm (Ex: Metalogix, AvePoint, Share gate etc…)

5.SLA details with the Vendor and the contact person from the Vendor’s side for this account?

10.Support & Incident Management:

1.What is the Support Type (L1, L2 or L3) expected?

2.Please provide the call flow process. Find below a sample process flow.

3. What’s the frequency of L1, L2 and L3 tasks that you get in a day, in a week & in a month?

Call Flow Process / Diagram

call flow diagram.jpg

4.Who is expected to make calls to Microsoft for support and for other vendors?

5.Is it expected to interact with end users for Support?

6.What are the support hours (time zones) and SLAs expected? What support coverage are you looking? (24*7, 16*5, or 8*5 …)

Service Hours:

The below calendar defines the times that the SLA clock starts and stops excluding weekends.

Day Start  hours(EST) End hours(EST)

1.Do you have any system in place for Incident Management? If yes, please give details so that we can understand about how to accommodate that with our Incident Management system?

2.Please explain the Incident classification criteria. Find sample below.

  Definition Response Time from time of Incident Log Fix Time from time of Incident Log
P1 Impact on All Users /Risk to Business Continuity 10 mins Stay with it
P1 Impact on All Users /Secondary system down    
P2 Impact on Site or Dept. / Significant problem preventing satisfactory operation    
P3 Impact on single User    
P4 Service Request/Advice required    
P4 Service Request/Planning    
P4 New starters/requisitions/supplies/bookings    

3.What is the mode of communication for Support (Email only, Incident management tool, Phone, chat)?

4.Please share the SLAs/ OLAs with existing vendors for 3rdparty software, Infrastructure, Exchange Server, Security, SQL Server, OS and hardware.

5.It is assumed that content and configuration DB of all SharePoint sites are in scope for support. Please confirm?

6.Please confirm if following is out of scope for SharePoint Support

1.OS level support like Server Performance Management, Memory Management, Disk Space and SQL Server Uptime.

2.Installation, Implementation, Deployment of any Software

7.Design, Development, Implementation or any issue on Development and Test servers.

8.Evaluation of any Software, Tool and Processes and Results

9.Design, Development and Implementation of Proof of Concepts

10.Development and Enhancements of 3rd Party Products

11.Platform Troubleshooting

12.Application Migration & Upgrades

13.Optimizing search for website or any other design changes to website

14.Managing Office 365 licenses and supporting the Azure environment.

7.Are there any development or migration projects that are currently in progress? What support is given to these projects by existing (Portal, or SharePoint) support teams?

8.Is there any repository for knowledge documents, Incident Logs, RCA (Root cause Analysis)?

9.Communication plan for any planned/unplanned outages – Key stakeholder list

9.Escalation matrix details.

10.Detailed description of tasks & activities performed in shift / daily / weekly / monthly

11.Please provide us with the following Support statistics (priority wise)

  1. Total tickets logged for SharePoint in last 1 month, 3 month and 6 months.
  2. How many Priority 1 calls were logged in last 1 month, 3 month and 6 months?
  3. Details about past SLA adherence,
  4. Summary of support tickets with case open age

 12.Are there user training requirements for educating the users about the sites? Need for webinars, training material, FAQs etc. to facilitate the rollout and ongoing changes to the sites

13. Any past record of the entire SharePoint environment going down, if yes details about that?

Finally, once all the above mentioned details are gathered and you have understood the customer’s environment well then you’re good to close the transition phase .

Happy SharePointing !!!










Resetting Search Index in SharePoint 2013:


Search is indeed a mission critical service application in SharePoint and it’s very important that it remains healthy so that you get the results in the Search center whenever you execute a search query. However, it’s quite possible that you may notice some errors in the “Crawl log” stating that the crawler is not able to crawl the contents in the content source and at times it might get even worse such that you may notice all “failures” and no “success” in the crawl logs. In scenarios like that you might have to reset the search index so that the content in the index gets flushed away after which you need to perform a full crawl so that search index component receives the newly processed items from the content processing component and writes them to the search index. Of course, directly resetting the index is not a fix for any search related issue, please ensure that you do all the necessary troubleshooting steps from your end to identify and fix the issue and once you reach a point where nothing really helped, that’s when you should think about resetting the search index.

What happens when you reset the Search Index?

When you reset the search index, all the contents will be immediately removed from the search index and users will not be able to retrieve search results when they execute a search query on the search center.  Once you’re done resetting the search index, you must perform a full crawl on one or more content sources to create a new search index. Users will be able to retrieve search results again once the full crawl is finished and the new search index is created. So in a nutshell there will be a downtime when the search index is getting reset. After a search index reset, the full crawl won’t restore all the analytics features that are powered by the Analytics Processing Component. All the analytics results will be erased after resetting the search index.

When we should reset the search index?

As I already mentioned above, resetting the search index should be the final step of troubleshooting for any search related issue. However, based on my experience this when we should reset the search index ….

  1. Index is corrupted
  2. One or all index component status is degraded
  3. You crawl completed successfully but you are not getting the search results.
  4. When you move the index location
  5. When Index location run out of space.
  6. In a scenario where we have Index partitions spread across multiple servers and the indexed document count is out of sync. For example, we have 2 servers set as index partitions, server 1 has 150K indexed documents and server2 has 145k index documents
  7. If we make any changes to search topology such as removing the search components ,adding the components & activating a different search topology

 Alright, now let’s take a look at the steps to reset the search index …


Please ensure that you take care of the below mentioned pre-requisites before resetting the search index .Failing to do so will cause adverse effects and at worst case you may end up recreating the entire search service application.

  1. Make sure the crawl status for each content source is “Idle”. If any crawl is running, wait for the crawl to complete or follow the steps to “Stop the active crawls” below.
  2. Make sure continuous crawl for content sources is disabled [if applicable].This step is only specific to SharePoint 2013 and above.
  3. Make sure the crawl rate is 0
  4. Make sure background activity status is “None” on search administration page.

Stopping the Active Crawl(s):

  1. Navigate to search administration page.
  2. Click on Content Sources link towards your left hand side as shown in the image below.


3. If any content source is crawling, click on the drop down of the content source and click on “Stop Crawl”.

Disable Continuous Crawl:

  1. Navigate to search administration page.
  2. Navigate to Content Sources link appearing on quick launch.


3. Click on the drop down and select “Disable Continuous Crawl” to disable it.


4. Click “Ok” when below warning message appears.


5. Follow the same steps to disable continuous crawl for other content sources. Finally, all the content sources would show “Idle” status as shown in the image below.


Suspend Search Service Application:

This step is to ensure that there is no crawling activity in place while we perform the Index reset.

  1. Open SharePoint Management Shell using service account
  2. Run the below command.

Suspend-SPEnterpriseSearchServiceApplication “Search Service Application Name”

Note: If you don’t know the name of search service application, you can get it by running below command before executing the above command.

Get-SPServiceApplication | Where-Object {$_.TypeName –eq “Search Service Application”}

After suspending the search application, search administration page will show the status as “Paused for: External request” as shown in the image below.


 Ensure Crawl Rate is 0:

  1. Navigate to search administration page.
  2. Check the Recent Crawl rate.


Ensure Crawler Background Activity is none:

  1. Navigate to search administration page.
  2. Check the status of the Crawler background activity and ensure it shows as “none” as shown in the image below.


Once the necessary pre-requisites are taken care, please follow the below steps to perform an Index Reset.

There are 2 ways to perform Index reset.

Using UI [User Interface]: This method can be used when the indexed content in your farm is not much in size i.e. index size is not huge and also when you don’t have large content sources.

Using PowerShell: UI method is not recommended for SharePoint farms with large search index. [i.e. huge count of searchable/indexed documents]. Using the UI method in large farms for resetting the search index can result in time out error. In such cases, we need to use PowerShell method to reset the index.


  1. Navigate to SharePoint Central Administration.
  2. Under “Application Management” category, click on “Manage Service Applications”.
  3. Find out “Search Service Application” and click on the Search service application.
  4. In the quick launch, click on “Index Reset


5. Click on confirm once done .


  1. Login to the SharePoint server using Administrator credentials.
  2. Open “SharePoint management shell” with elevated permissions.
  3. Run the below command to reset search index.


Post Index Reset Steps:

  1. Check whether the number of searchable items is 0.
  2. Resume the search service application by running the command shown in the screenshot below.

133. Enable “continuous crawl” for the content sources if it was enabled prior to index reset.

4. Run full crawl for the content sources one by one.

This confirms that you’re done resetting the Search index successfully and please keep monitoring the full crawl and ensure that it doesn’t get stuck in the middle. The time duration for the full crawl depends on the size of the content source, if you have very large content sources then it might take days for the full crawl to complete successfully. Once done, please verify the search results and ensure that they return fine. Also check the “Crawl log” and make sure you’re not seeing any errors this time.

Thanks for reading this post …..Happy SharePointing!!!

PowerShell script for generating the site collections list with multiple administrators


Running this script will generate a report which displays the list of site collections that has multiple site collection administrators and will also display the total number of users who have access to those site collections.

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

Add-Content “Sites.csv” -Value “SiteCollection Name,SiteCollection URL, SiteCollection Administrators, Users Count,Usage in MB”

$webApp = Get-SPWebApplication

foreach($webapps in $webapp)


foreach ($SiteCollection in $webApps.Sites)


$url = $SiteCollection.Url

$webs = Get-SPWeb $URL

[boolean] $WriteToFile = $true

$weburl = $SiteCollection.OpenWeb()

$siteowner = “”

foreach ($siteAdmin in $weburl.SiteAdministrators)


$siteowner = $siteAdmin.DisplayName + “|” + $siteowner


foreach($web in $webs)


#Grab all users in the site collections

$siteUserCnt = $web.AllUsers.Count

$Siteurl = $web.Url

$siteTitle = $web.Title

$site = Get-SPSite  $Siteurl

$siteusage = $site.Usage.Storage/1MB

Add-Content -Path “Sites.csv” -Value “$siteTitle,$Siteurl,$siteowner,$siteUserCnt,$siteusage”





Thanks for using this script …..Happy SharePointing!!!!

Recording of Webinar Session on SharePoint Architectural Models:


For those who missed my session yesterday , please find the link for the video recording below .

Webinar Recording on SharePoint Architectural Models

Thanks once again for attending my session yesterday and will see you all soon in different webinar shorlty .

Happy SharePointing!!!!


Webinar on SharePoint Architectural Models:


Hi all ,

Please join me for a webinar on Dec 3rd at 7 pm IST on ” The Different type of Architectural models in SharePoint” .


Types of Architectural models in SharePoint

  • SharePoint on-premises
  • SharePoint Online/ SaaS(Office 365)
  • SharePoint Hybrid
  • SharePoint in Azure/IaaS

I’ll be discussing in detail about all these models and when to choose it and when not to choose it and I’ll also be giving some deep insights on all these models .

Meeting detailshttp://www.c-sharpcorner.com/events/learn-architectural-models-in-sharepoint

Feature pack 1 for SharePoint server 2016 is out:


Just in case you haven’t heard the news yet, Microsoft has announced the release of Feature Pack 1 for SharePoint server 2016 on November 2016 and this release brings several enhancements based on the recent innovations in Office 365. Please find the details below.

Listed below are the new capabilities that was introduced in this release:

  1. Logging of administrative actions performed in Central Administration and with Windows PowerShell.
  2. Enhancements to MinRole to support small environments.
  3. A new OneDrive for Business user experience.
  4. Custom tiles in the SharePoint app launcher.
  5. Unified auditing across site collections on-premises and in Office 365.
  6. Unified taxonomy across on-premises and Office 365.
  7. OneDrive API 2.0.

Now let’s take a look at all these capabilities in a detailed manner,

Administrative actions logging:

As SharePoint administrators we spend a considerable amount of time troubleshooting administrative changes in the on-premises environment, which can result in failure conditions or other undesired effects. So for this Microsoft has introduced more insightful, granular logging in Feature Pack 1. The Feature Pack 1 introduces the logging of common administrative actions performed in the Central Administration website and with Windows PowerShell.

MinRole enhancements:

One of the infrastructure advancements in SharePoint Server 2016 was the concept of MinRole. MinRole is designed to transform architectural guidance into code, simplifying deployment and scale with SharePoint by ensuring a request is served end-to-end by the receiving server based on the origin of the request (i.e., end user or batch processing) and role of the destination server.

MinRole was originally optimized for larger farm topologies. With four server roles, the minimal requirement for a supported MinRole configuration was a four-server farm. A farm with high availability (HA) requires two servers for each role, making eight servers the minimal requirement for a HA MinRole configuration. However, customers have reported to Microsoft that they would like to have the benefits of MinRole with smaller farm topologies too. We listened to you and enhanced MinRole to address this request.

Once the new MinRole enhancements are enabled, you will notice that two additional server roles are available: “Front-end with Distributed Cache” and “Application with Search.” The Front-end with Distributed Cache role combines the Front-end and Distributed Cache roles together, while the Application with Search role combines the Application and Search roles together. These new roles let you host a multi-server MinRole farm with just two servers or four servers with HA.


A new OneDrive for Business user experience:

OneDrive for Business is an integral part of Office 365 and SharePoint Server. It provides a place where you can store, share and sync your work files. OneDrive for Business makes it easy to manage and share your documents from anywhere, and work together in real-time, on your favorite devices. Feature Pack 1 brings the modern OneDrive for Business user experience to SharePoint Server 2016. The new OneDrive user experience is a Software Assurance benefit.




SharePoint App Launcher custom tiles:

The App Launcher was introduced in SharePoint Server 2016 with the ability to extend the tiles with the SharePoint Hybrid App Launcher to include apps available in Office 365. The App Launcher provides a common location to discover new apps and navigate between on-premises SharePoint and Office 365 applications. Now, in addition to native SharePoint and Office 365 apps, you can also add your own custom tiles that point to other SharePoint sites, external sites, legacy apps and more. This makes it easy to find and navigate to the relevant sites, apps and resources to do your job.


Hybrid capabilities:

Unified auditing—Unified auditing gives SharePoint administrators’ detailed visibility into file access activities across all site collections, on-premises and in Office 365. With unified auditing in place, the Office 365 Security and Compliance Center can provide audit logs search for your SharePoint Server 2016 on-premises audit logs in addition to Office 365 audit logs.

This hybrid auditing capability—powered by Microsoft SharePoint Insights—enters preview with Feature Pack 1. Configuration is simple: a few clicks in Hybrid Scenario Picker wizard and you’re ready to start viewing and experiencing unified auditing.

Unified taxonomy:

SharePoint’s managed metadata service application makes it possible to create a taxonomy for information architecture across site collections and web applications. With Feature Pack 1, you can implement a unified taxonomy across a SharePoint Server 2016 farm and Office 365. You can seed the term store in SharePoint Online from your on-premises term store and then manage your taxonomy in SharePoint Online. Replication to on-premises SharePoint is performed by the hybrid taxonomy feature.

Developer enhancements:

OneDrive API 2.0—The OneDrive API provides a common API for access to files located on-premises and in the Office 365 cloud. The API provides access and enables developers to build solutions that target user data stored in OneDrive for Business and SharePoint document libraries