| Date post: | 14-Apr-2017 |
| Category: |
Documents |
| Upload: | muhammad-zeeshan-tahir |
| View: | 177 times |
| Download: | 2 times |
SharePoint AdministrationPlanning Architecture Installation Configurations Security and
Content
V 10Muhammad Zeeshan Tahir
MCP MCSE SharePoint 2013
This document contains some helping guide lines By following these it may save time and effort for a SharePoint Administrator Continuehellip
Why SharePoint
Architecture
Architecture is actually the topology that defines the farm Selection of SharePoint architecture depends on the usage target
audience performance and availability Server Roles in the farm
Web Front End Application Server Database Server
Mostly considered topologies are defined into three categories Single Server Two-Tier Farm Three-Tier Farm
ArchitectureRoles and Types
What defines the role of a server
Services provided by a server defines what actually the server role is in the farm ie Handling user requests gt Web Front End Running SharePoint services gt Application Server Storing content and config databases gt Database Server
Server hardware and software requirements for SharePoint
Architecture
WFE APP
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Why SharePoint
Architecture
Architecture is actually the topology that defines the farm Selection of SharePoint architecture depends on the usage target
audience performance and availability Server Roles in the farm
Web Front End Application Server Database Server
Mostly considered topologies are defined into three categories Single Server Two-Tier Farm Three-Tier Farm
ArchitectureRoles and Types
What defines the role of a server
Services provided by a server defines what actually the server role is in the farm ie Handling user requests gt Web Front End Running SharePoint services gt Application Server Storing content and config databases gt Database Server
Server hardware and software requirements for SharePoint
Architecture
WFE APP
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Architecture
Architecture is actually the topology that defines the farm Selection of SharePoint architecture depends on the usage target
audience performance and availability Server Roles in the farm
Web Front End Application Server Database Server
Mostly considered topologies are defined into three categories Single Server Two-Tier Farm Three-Tier Farm
ArchitectureRoles and Types
What defines the role of a server
Services provided by a server defines what actually the server role is in the farm ie Handling user requests gt Web Front End Running SharePoint services gt Application Server Storing content and config databases gt Database Server
Server hardware and software requirements for SharePoint
Architecture
WFE APP
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Architecture is actually the topology that defines the farm Selection of SharePoint architecture depends on the usage target
audience performance and availability Server Roles in the farm
Web Front End Application Server Database Server
Mostly considered topologies are defined into three categories Single Server Two-Tier Farm Three-Tier Farm
ArchitectureRoles and Types
What defines the role of a server
Services provided by a server defines what actually the server role is in the farm ie Handling user requests gt Web Front End Running SharePoint services gt Application Server Storing content and config databases gt Database Server
Server hardware and software requirements for SharePoint
Architecture
WFE APP
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
What defines the role of a server
Services provided by a server defines what actually the server role is in the farm ie Handling user requests gt Web Front End Running SharePoint services gt Application Server Storing content and config databases gt Database Server
Server hardware and software requirements for SharePoint
Architecture
WFE APP
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Web Front End Fast light-weight server which responds to user
requests for web pages All web servers in a farm are mirrors of each other and are load balanced
Application Server Provides the service features of SharePoint
products and technologies An application server often provides all or a subset of service features Multiple redundant application servers can be load balanced
Database Server Stores content and service data All databases can
be assigned to one database server Or databases can be spread across multiple servers All databases can be clustered or mirrored for failover protection
Architecture
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Single Server
Good for evaluation Development Training and Demonstration Best For lt 100 users
Note A Standalone installation is completely different from Single Server Farm installation of SharePoint A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases Uses single account to configure everything and later on cannot add any new server to the farm
All roles in one server including SQL Server
+ +
Architecture
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
SharePoint Farm vs Standalone
Couple of more differences between SharePoint Farm and SharePoint standalone arehellip Using separate account to connect to SQL serverSharePoint server Using other accounts to manage a lot of services such as Excel service
Performance Point setup reverse proxy setup load balancing Allow multiple SharePoint servers join into this farm to improve availability Multiple SharePoint servers can host Central Administration Search Index
Search query Web Application etc for better performance
Server hardware and software requirements for SharePoint
Architecture
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Two-Tier Farm
Can support up to 10000 users per server Can add multiple servers on each level with same roles as below Databases are handled separately by dedicated database servers User requests handled by the same server running the other SharePoint
services
Database Server
All Web and Application server roles
Architecture
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Three-Tier Farm
Split the servers according to their roles One web server can support up to
10000 Can add multiple servers on each level
in WFErsquos Application or Database servers
Dedicated servers can be added for Search service crawling and indexing
Architecture
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Three-Tier Large Farms ExampleArchitecture
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
High Availability - Failover Server
Failover Server acts as the secondary database server in case of main DB server failure A witness server is an optional server
Setting a failover server while creating a web or service application doesnrsquot create everything for you It just points to the server and SharePoint checks whether the mentioned server exists or not
Failover Database Server
Architecture
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Mirroring Log Shipping Replication Always On
Architecture
High Availability
Database Cloning
httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replicationDifferences
SQL Server 2012 Enterprise
ManualManualAuto
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Logical Architecture of SharePointArchitecture
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Installation
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Service Accounts
Use separate service accounts for each type of serviceweb application Min 3 User Profile Service Search Service Farm Account Setup Account SQL Server Svc Account
Apply AD policy for service account User cannot change password Password never expires
Installation
Required Account Example
SQL Server Service Account sqlSvcAcc
SharePoint Setup Administrator spAdmin
SharePoint Farm Account spFarmAcc
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Farm Installation
Always choose Server Farm installation if its not a development machine
Installation
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Config DB Name
Always try to stick with the default DB name Changing the name may cause confusion in case of more than one
Databases Note recommended
SharePoint_Main_DB SharePoint_Config_Prod SharePoint_Config_Prod_Main SharePoint2013_Config_Main
Installation
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
CA Port Number
Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments My favorite is 9000
Easy to remember httpCAServer9000 Not recommended
httpDevCA23685 httpQACA41272 httpProdCA35714
Installation
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Services Auto Configuration
SharePoint provides one click creation of Service Application Very handy when you have less time to configure the single server farm However these services should be configured manually with dedicated service accounts
Installation
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Configuration
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Set Paths to non OS drive
Set ULS logs SharePoint Web Applications and Search Indexes into non OS drive of servers This would be helpful when the ULS logs will increase their size yoursquoll not have any warning message in CA health monitoring
Default path for logs is below Change it to DSharePointAppsLOGS
Default path for web applications is below Change it to DSharePointAppsWebs
Configurations
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Diagnose Logging
Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs
Change it to Critical and amp Unexpected if farm is running fine for all categories
In case you want to troubleshoot any issue and want to track in logs Change it to Verbose temporarily
Configurations
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Health Monitoring
Keep an eye on Health Monitoring ribbon Try to fix the critical errors that may cause any service web
application or farm down
Configurations
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Content
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Consistency throughout entire farm Use complete names not abbreviations
Not Recommended MyComp Pvt Ltd Recommended MyCompanyPrivateLimited
Avoid spaces to limit population of 20 Not Recommended My Company Private Limited Recommended MyCompanyPrivateLimited
Naming ConventionContent
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Microsoft recommends not to increase the size of a content database to more than 200 GB However SharePoint will still work If the size crosses the limit
A content database can contain 60 million items including documents and list items
A content database can support 10000 maximum (2500 non-Personal site collections and 7500 Personal Sites or 10000 Personal Sites alone)
If a site collection seems to have a lot more data in future create a separate content database for it to optimize the size
If a site collection has increased its size which wasnrsquot expected donrsquot worry you can move the site collection by creating a new blank content DB using PowerShell
Content Databases SizeContent
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Create More ListsLibraries
Sometimes the users face the issues related to list view threshold of a list or library
Try to create ListLibrary separately categorized by their types and usage You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items However if once the threshold value increased the recommended solutions may give a bad user experience but will work Turning off list threshold for a listlibrary Adding metadata navigation List column indexing
Content
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
SharePoint creates a ldquoLocal SharePoint Sitesrdquo content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers
Content Sources must split and configured for each web application so can be scheduled for different times for crawling
Content SourcesContent
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Security
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
Permissions Structure
Avoid granting direct permissions on any site collection site or listlibrary
Always use SharePoint groups for permissions If there is any site list or library where newexisting users need to
have access frequently then better way to maintain the permissions structure is to have an AD security group add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
References
httpdownloadmicrosoftcomdownloadA07A07928F6-5153-4E19-B682-B8D28194095Asps_2013_traditional_topology_modelpdf httpstechnetmicrosoftcomen-uslibrarycc262485aspx httpblogstechnetcombquentinarchive20140715the-list-view-threshold-_2800_stop_2100_-don_1920_t-change-it_21002900_aspx httpstechnetmicrosoftcomen-uslibrarycc262787aspx httpstechnetmicrosoftcomen-uslibrarycc825328aspxSection3 httpsocialtechnetmicrosoftcomwikicontentsarticles31035what-are-types-of-sharepoint-installation-what-is-difference-between-farm-and-standaloneasp
x httpstechnetmicrosoftcomen-uslibrarycc263445aspxSubsection2 httpsnilebridewordpresscom20110724log-shipping-vs-mirroring-vs-replication
![[MS-WSSO]: Windows SharePoint Services Overview... · Windows SharePoint Services File, Print, and User/Group administration capabilities. Windows SharePoint Services is a web-based](https://static.documents.pub/doc/80x56/5f48e41b522a451b3434d3f3/ms-wsso-windows-sharepoint-services-overview-windows-sharepoint-services.jpg)
