Check according with the Window Server used, either Windows Server 2008 or Windows 2012, if any of the features are installed. Otherwise proceed to install them.
Server Manager, Add Roles and Features
These prerequisites can be installed either manually configuring via Server Manager or running SharePoint 2013 prerequisite installer.
To configure User Account Requirements, follow these instructions:
1. To add a user as a SharePoint Shell Admin, execute “Add-SPShellAdmin” cmdlet (http://technet.microsoft.com/en-us/library/ff607596.aspx):
2. Make the SharePoint Application Pool account a Search Service Application administrator:
3. Make the user the Default content access account:
4. Make the user a Business Data Connectivity Service administrator:
5. Give the user Metadata Store permissions:
6. Add administration content database role membership:
7. For search databases, confirm that you have the SPSearchDBAdmin database role. This should be added to the account you set up as the Search Service Application administrator. If not, add them manually.
To run the deploy scripts, use an account with the following requirements:
Once the previous manual steps have been completed, verify the following points:
If the user running the SharePoint Application Pool is different from the user you are using to access the Notification Service, then the Application Pool account should be the one that has the Search Service Application administrator permission and not the account that has access to the service. In that case, after setting the application pool account as a Search Service Application administrator, confirm that you have the following permissions on that account in the Search Databases, if not, add them manually:
Database Name | Role |
---|---|
Search_Service_Application_AnalyticsReportingStoreDB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_CrawlStoreDB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_DB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_LinksStoreDB_<GUID> | SPSearchDBAdmin |
Database Permissions Checklist
After doing all the changes specified previously, this is the complete list of user database roles as they should be.
Database Name | Role |
---|---|
SharePoint_Config | SPDataAccess SharePoint_Shell_Access |
SharePoint_AdminContent_<GUID> | SPDataAccess WSS_Content_Application_Pools SharePoint_Shell_Access |
Bdc_Service_DB_<GUID> | SPDataAccess |
Search_Service_Application_AnalyticsReportingStoreDB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_CrawlStoreDB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_DB_<GUID> | SPSearchDBAdmin |
Search_Service_Application_LinksStoreDB_<GUID> | SPSearchDBAdmin |
Since SharePoint setup user and server farm accounts have these privileges, it is recommended to use one of those accounts for this. Setup user is recommended since it has machine admin rights as well.
The Security PreTrimmer requires that the user identity sent to it contains at least one of the following claim types: