Sharepoint Knowledge share

Users cannot see the checked out files in the folder/ library

2018-08-28T22:53:00.000+05:30

I Came across a Issue today wherein the user opened a ticket for the below issue

Issue : Users cannot see the checked out files in the folder/ library

Checked with the user for the url and browsed the site and yes was not able to see any files

Asked the user if he had checked in the files for the first time as it was nothing to do with the permissions of the user or any setting

He said he might have so asked him to check in the file once and then check out .
He did and there were all the files visible to the user

Resolution : Check in the files atleast once for the user to see the files in the folder / Library

Restore options in SharePoint Online

2018-06-21T20:54:00.004+05:30

Site Collection Restore
Contact Microsoft Support for assistance with possible data loss issues. They will work with you to assess the best route to restore the desired content, whether that be versioning, the recycle bin, or an actual restore.Backups are retained for 14 days, so the sooner we can get started with data gathering the better.

Recycle Bin
By default Sites, Lists, Libraries, Folders, Items and Documents will all go into the recycle bin.
If an end user empties his recycle bin, the content will be transferred into the site collection recycle bin.
A site collection administrator is able to restore items from the site collection recycle bin.
Items that have been deleted into the recycle bin will remain there for 93 days.
The 93 days is the total length regardless weather the items are in the user recycle bin or in the site collection recycle bin.
More info:
Manage the Recycle Bin of a SharePoint Online site collection

Versioning
It is possible to turn on versioning on documents and items in SharePoint Online.
If versioning is turned on and no limit has been set on the amount of versions to keep, you can go back in time for as long as you want.
If you delete something into the recycle bin, all versions will be delete as well.
If you restore something from the recycle bin back into a library, all versions will be restore as well.
If you have set to keep only 3 major and 3 minor versions, the oldest versions will be purged once a new version is being created.
More Info:
Enable and configure versioning for a library
Versioning, content approval, and check-out planning

Examples
So let’s say that if a user deletes an item and waits 95 days, the item will be gone. If they contact technical support, we can request a restore from a backup taken up to 14 days prior, so we could restore the entire site collection back to a point where the item is still in the recycle bin and is capable of being retrieved. As we would be restoring the entire site collection, all data from the point of the backup to current would be lost.

Let’s say that we have turned on versioning and set to keep only 3 major and 3 minor versions. If we already created 3 major versions and we create a new one, the oldest major version will be purged. In order to restore this purged version, we would need to restore the complete site collection up to a point where the version is still there so we can restore it from the version history.

3rd party solutions
Note that there are 3rd party solution out there that are capable of migrating content from an on-premise environment into SharePoint Online. Usually if these tools are able to migrate content into SharePoint Online, they are able to grab content from SharePoint Online as well. Below are some 3rd party solutions that might be able to create interim backups of SharePoint Online as well.

Avepoint
Quest
Metalogics
Metavis
Thinkscape
There are also ways to manually export some of the data yourself using for example Outlook or SharePoint Workspace. Please see this post from a colleague of mine for more information.

Reference : https://blogs.technet.microsoft.com/akieft/2012/01/09/restore-options-in-sharepoint-online/

SharePoint URL shortcuts

2018-05-25T22:12:00.001+05:30

Please find the List of Shortcuts using URL to the Sharepoint internal pages

Below listed URL’s work for SharePoint 2010 for SharePoint 2013 please add /15/after /_layouts.

Add web parts to any page: /append ?PageView=Shared&ToolPaneView=2
Create New Site Content: /_layouts/create.aspx
Create New Site: /_layouts/NewsbWeb.aspx
List Template Gallery: /_catalogs/lt/Forms/AllItems.aspx
Master Page Gallery: /_catalogs/masterpage/Forms/AllItems.aspx
Manage your Alerts: /_layouts/SubEdit.aspx
Create New Alert: /_layouts/SubChoos.aspx
Manage Site Collection Administrators: /_layouts/mngsiteadmin.aspx
Manage Sites and Workspaces: /_layouts/mngsubwebs.aspx
Manage People: /_layouts/people.aspx
Manage User Permissions: /_layouts/user.aspx
Modify Navigation: /_layouts/AreaNavigationSettings.aspx
Modify Site Navigation: /_layouts/SiteNavigationSettings.aspx
Recycle Bin: /_layouts/AdminRecycleBin.aspx
Site Directory: _layouts/SiteDirectorySettings.aspx
Save Site as Template: /_layouts/savetmpl.aspx
Site Settings page: /_layouts/settings.aspx
Create New Web Part Page: /_layouts/spcf.aspx
Site Template Gallery: /_catalogs/wt/Forms/Common.aspx
Site Column Gallery: /_layouts/mngfield.aspx
Site Content Types: /_layouts/mngctype.aspx
Site Content and Structure Manager: /_layouts/sitemanager.aspx
Site Usage Summary: /_layouts/SpUsageWeb.aspx
User Alerts: /_layouts/sitesubs.aspx
View All Site Content: /_layouts/viewlsts.aspx
Web Part Gallery: /_catalogs/wp/Forms/AllItems.aspx
Web part maintenance mode: /append ?contents=1 to the URL of the page
Open the page in Edit Mode – In Address bar, Type: “javascript:MSOLayout_ToggleLayoutMode();” or “javascript:MSOTlPn_ShowToolPane(’2′);” in the Address bar
Add Web Parts Pane: ?ToolPaneView=2
Display all content types of sites: /_layouts/mcontent.aspx
Sign as different User: /_layouts/closeConnection.aspx?loginasanotheruser=true

SharePoint Online limits

2018-05-24T19:28:00.000+05:30

SharePoint Online limits that apply to all plans. For storage and user limits for current Office 365 plans and SharePoint Online standalone plans

Service limits

Items and files - A list can have up to 30 million items and a library can have up to 30 million files and folders. Views can have up to 12 lookup columns.

Subsites - Up to 2,000 per site collection

File path length - The total length of the URL, including the file name, can't exceed 400 characters.

File size - Less than 15 GB per file. Files attached to list items can be up to 250 MB in size.

Sync - For optimum performance, we recommend storing no more than 100,000 files in a single OneDrive or team site library. If you use the previous OneDrive for Business sync client (Groove.exe), the sync limit per library is 5,000 items.

Versions - 50,000 major versions and 511 minor versions
SharePoint groups - A user can belong to 5,000 groups, and each group can have up to 5,000 users. You can have up to 10,000 groups per site collection.
SharePoint hosted applications – 20,000 instances per tenant.
Users - 2 million per site collection.

Software boundaries and limits for SharePoint 2013

2018-05-24T02:38:00.000+05:30

This article contains information to help you understand the tested performance and capacity limits of SharePoint Server 2013, and offers guidelines for how limits relate to acceptable performance

The following table lists the recommended guidelines for web applications.

Limit	Maximum value	Limit type	Notes
Web application	20 per farm	Supported	We recommended limiting the number of web applications as much as possible. Create additional host named site collections where possible instead of adding web applications.
Zone	5 per web application	Boundary	The number of zones defined for a farm is hard-coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom.
Managed path for host-named site collections	20 per farm	Supported	Managed paths for host-named site collections apply at the farm level. Each managed path that is created can be applied in any Web application.
Managed path for path-based site collections	20 per web application	Supported	Managed paths are cached on the web server, and CPU resources are used to process incoming requests against the managed path list. Managed paths for path-based site collections apply at the Web application level. You can create a different set of managed paths for each Web application. Exceeding 20 managed paths per web application adds more load to the web server for each request. If you plan to exceed twenty managed paths in a given web application, we recommend that you test for acceptable system performance.
Solution cache size	300 MB per web application	Threshold	The solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions. If the cache size is exceeded, solutions are retrieved from disk, which may slow down response times. You can configure the size of the solution cache by using the PowerShell cmdlet Set-SPInfoPathFormsService. For more information, see Set-SPInfoPathFormsService.

Web server and application server limits

The following table lists the recommended guidelines for web servers on the farm.

Limit	Maximum value	Limit type	Notes
Application pools	10 per web server	Threshold	The maximum number is determined by hardware capabilities. This limit is dependent largely upon: The amount of memory allocated to the web servers The workload that the farm is serving, that is, the user base and the usage characteristics (a single highly active application pool can utilize 10 GB or more)

Content database limits

The following table lists the recommended guidelines for content databases.

Limit	Maximum value	Limit type	Notes
Number of content databases	500 per farm	Supported	The maximum number of content databases per farm is 500. With 500 content databases per web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use PowerShell to manage the web application when a large number of content databases are present, because the management interface might become slow and difficult to navigate. With 200GB per content database, and 500 content databases per farm, SharePoint Server 2013 supports 100TB of data per farm.
Content database size (general usage scenarios)	200 GB per content database	Supported	We strongly recommended limiting the size of content databases to 200 GB, except when the circumstances in the following rows in this table apply. If you are using Remote BLOB Storage (RBS), the total volume of remote BLOB storage and metadata in the content database must not exceed the 200GB limit.
Content database size (all usage scenarios)	4 TB per content database	Supported	Content databases of up to 4 TB are supported when the following requirements are met: Disk sub-system performance of 0.25 IOPS per GB. 0.2 IOPS per GB is recommended for optimal performance. You must have developed plans for high availability, disaster recovery, future capacity, and performance testing. You should also carefully consider the following factors: Requirements for backup and restore may not be met by the native SharePoint Server 2013 backup for content databases larger than 200 GB. It is recommended to evaluate and test SharePoint Server 2013 backup and alternative backup solutions to determine the best solution for your specific environment. It is strongly recommended to have proactive skilled administrator management of the SharePoint Server 2013 and SQL Server installations. The complexity of customizations and configurations on SharePoint Server 2013 may necessitate refactoring (or splitting) of data into multiple content databases. Seek advice from a skilled professional architect and perform testing to determine the optimum content database size for your implementation. Examples of complexity may include custom code deployments, use of more than 20 columns in property promotion, or features listed as not to be used in the over 4 TB section below. Refactoring of site collections allows for scale out of a SharePoint Server 2013 implementation across multiple content databases. This permits SharePoint Server 2013 implementations to scale indefinitely. This refactoring will be easier and faster when content databases are less than 200 GB. It is suggested that for ease of backup and restore that individual site collections within a content database be limited to 100 GB. For more information, see Site collection limits. > [!IMPORTANT]> We do not recommend the use of content databases that exceed 4 TB, except in document archive scenarios (described in the next row in this table). If, in the future, you need to upgrade your SharePoint Server 2013 installation, upgrading the site collections within the content databases can be very difficult and time consuming. > It is strongly recommended that you scale out across multiple content databases, rather than exceed 4 TB of data in a single content database.
Content database size (document archive scenario)	No explicit content database limit	Supported	Content databases with no explicit size limit for use in document archive scenarios are supported when the following requirements are met: You must meet all requirements from the "Content database size (all usage scenarios)" limit earlier in this table, and you should ensure that you have carefully considered all the factors discussed in the Notes field of that limit. SharePoint Server 2013 sites must be based on Document Center or Records Center site templates. Less than 5% of the content in the content database is accessed each month on average, and less than 1% of content is modified or written each month on average. Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint Server 2013 objects in the content database. Note: Document archive content databases can be configured to accept documents from Content Routing workflows. For more information about large-scale document repositories, see Estimate performance and capacity requirements for large scale document repositories in SharePoint Server 2010, and the Typical large-scale content management scenarios section of the article Enterprise content storage planning (SharePoint Server 2010).
Content database items	60 million items including documents and list items	Supported	The largest number of items per content database that has been tested on SharePoint Server 2013 is 60 million items, including documents and list items. If you plan to store more than 60 million items in SharePoint Server 2013, you must deploy multiple content databases.
Site collections per content database	10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone)	Supported	We strongly recommended limiting the number of site collections in a content database to 5,000. However, up to 10,000 site collections in a database are supported. Note that in a content database with up to 10,000 total site collections, a maximum of 2,500 of these can be non-Personal site collections. It is possible to support 10,000 Personal site collections if they are the only site collections within the content database. These limits relate to speed of upgrade. The larger the number of site collections in a database, the slower the upgrade with respect to both database upgrade and site collection upgrades. The limit on the number of site collections in a database is subordinate to the limit on the size of a content database that has more than one site collection. Therefore, as the number of site collections in a database increases, the average size of the site collections it contains must decrease. Exceeding the 5,000 site collection limit puts you at risk of longer downtimes during upgrades. If you plan to exceed 5,000 site collections, we recommend that you have a clear upgrade strategy to address outage length and operations impact, and obtain additional hardware to speed up the software updates and upgrades that affect databases. To set the warning and maximum levels for the number of sites in a content database, use the PowerShell cmdlet Set-SPContentDatabase with the -WarningSiteCount parameter. For more information, see Set-SPContentDatabase.
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS)	Time to first byte of any response from the NAS should remain within 40 milliseconds 95% of the time.	Boundary	When SharePoint Server 2013 is configured to use RBS, and the BLOBs reside on NAS storage, consider the following supported limit. From the time that SharePoint Server 2013 requests a BLOB, until it receives the first byte from the NAS, 95% of the time no more than 40 milliseconds can pass.

Site collection limits

The following table lists the recommended guidelines for site collections.

Limit	Maximum value	Limit type	Notes
Site collections per farm	750,000 per farm (500,000 rooted with the Personal Sites template and 250,000 rooted with other sites types)	Supported	The maximum recommended number of site per farm is 500,000 site collections containing only one Personal Sites plus 250,000 site collections containing any other for all other site templates. The Sites can all reside on one web application, or can be distributed across multiple web applications. Note that this limit is affected by other factors that might reduce the effective number of site collections that can be supported by a given content database. Care must be exercised to avoid exceeding supported limits when a container object, such as a content database, contains a large number of other objects. For example, if a farm contains a smaller total number of content databases, each of which contains a large number of site collections, farm performance might be adversely affected long before the supported limit for the number of site collections is reached. For example, Farm A contains a web application that has 200 content databases, a supported configuration. If each of these content databases contains 1,000 site collections, the total number of site collections in the web application will be 200,000, which falls within supported limits. However, if each content database contains 10,000 site collections, even though this number is supported for a content database, the total number of site collections in the farm will be 2,000,000, which exceeds the limit for the number of site collections per web application and per farm. Memory usage on the web servers should be monitored, as memory usage is dependent on usage patterns and how many sites are being accessed in given timeframe. Similarly, the crawl targets might also exhibit memory pressure, and if so the application pool should be configured to recycle before available memory on any web server drops to less than 2 GB.
Web site	250,000 per site collection / 250,000 per farm / 500,000 personal sites per farm.	Supported	The maximum recommended number of web sites is 500,000 sites based on the Personal Site template, and 250,000 sites based on all other templates. This limit applies per site collection as well as per farm. Performance can degrade as the number of subsites surpasses 2,000 at the site collection level. > [!IMPORTANT]> Staying below 2,000 subsites per site collection is strongly recommended. You can create a very large total number of web sites by creating multiple site collections with up to 2,000 webs per site collection. For example, 125 site collections that contain 2,000 webs each will equate to 250,000 sites in the farm. However, this would be considered the maximum recommended limit for non-personal sites. If you have 250,000 site collections, all containing a root web site that is not the Personal Site template, adding a sub-site to any of those root sites would exceed the 250,000 web site boundary. If the recommended limit of 2,000 sites per site collection is exceeded, the following issues may occur: Deleting or creating a site or subsite can significantly affect a site's availability. Access to the site and subsites will be limited while the site is being deleted. Attempting to create many subsites at the same time may also fail. When having more than 2,000 subsites, the performance of actions such as executing PSConfig when adding a new server to an existing farm, or after installing SharePoint updates the drastically decrease. Executing the stsadm -o checklocalupgradestatus operation, or the daily execution of the Product Version Job timer job may take many hours to complete. Browsing the Review database status page (<your_SharePoint_CentralAdmin_URL>/_admin/UpgradeStatus.aspx) on the Central Administration web site may result in a timeout.
Site collection size	Maximum size of the content database	Supported	A site collection can be as large as the content database size limit for the applicable usage scenario. For more information about the different content database size limits for specific usage scenarios, see the Content database limits table in this article. In general, we strongly recommend limiting the size of site collections to 100 GB for the following reasons: Certain site collection actions, such as site collection backup/restore or the PowerShell cmdlet Move-SPSite, cause large SQL Server operations which can affect performance or fail if other site collections are active in the same database. For more information, see Move-SPSite. SharePoint site collection backup and restore is only supported for a maximum site collection size of 100 GB. For larger site collections, the complete content database must be backed up. If multiple site collections larger than 100 GB are contained in a single content database, backup and restore operations can take a long time and are at risk of failure.
Number of device channels per publishing site collection	10	Boundary	The maximum allowed number of device channels per publishing site collection is 10.

List and library limits

The following table lists the recommended guidelines for lists and libraries. For more information, see Designing large Lists and maximizing list performance (SharePoint Server 2010).

Limit	Maximum value	Limit type	Notes
List row size	8,000 bytes per row	Boundary	Each list or library item can only occupy 8,000 bytes in total in the database. 300 bytes are reserved, leaving 7700 bytes for end-user columns. For details on how much space each kind of field consumes, see Column limits.
File size	2 GB	Boundary	The default maximum file size is 250 MB. This is a configurable limit that can be increased up to 2 GB (2,047 MB). However, a large volume of very large files can affect farm performance.
Documents	30,000,000 per library	Supported	You can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.
Major versions	400,000	Supported	If you exceed this limit, basic file operations—such as file open or save, delete, and viewing the version history— may not succeed. This value is set on the library level for files.
Minor versions	511	Boundary	The maximum number of minor file versions is 511. This limit cannot be exceeded. This value is set on the library level for files.
Items	30,000,000 per list	Supported	You can create very large lists using standard views, site hierarchies, and metadata navigation. This value may vary depending on the number of columns in the list and the usage of the list.
Bulk operations	100 items per bulk operation	Boundary	The user interface allows a maximum of 100 items to be selected for bulk operations.
List view lookup threshold	12 join operations per query	Threshold	Specifies the maximum number of joins allowed per query, such as those based on lookup, person/group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the object model (by not specifying any view fields), SharePoint will return up to the first 12 lookups. Note: After applying the SharePoint Server 2013 cumulative update package released on August 13, 2013 (https://support.microsoft.com/en-us/kb/2817616), the default value is increased from 8 to 12.
List view threshold	5,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at the same time outside the daily time window set by the administrator during which queries are unrestricted.
List view threshold for auditors and administrators	20,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at the same time when they are performed by an auditor or administrator with appropriate permissions. This setting works with Allow Object Model Override. Note: This threshold needs to be enabled by using custom code to set the SPQueryThrottleOption.
Subsite	2,000 per site view	Threshold	The interface for enumerating subsites of a given web site does not perform well as the number of subsites surpasses 2,000. Similarly, the All Site Content page and the Tree View Control performance will decrease significantly as the number of subsites grows.
Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files	10 concurrent editors per document	Threshold	Recommended maximum number of concurrent editors is 10. The boundary is 99. If there are 99 co-authors who have a single document opened for concurrent editing, each successive user sees a "File in use" error, and can only open a read-only copy. More than 10 co-editors will lead to a gradually degraded user experience with more conflicts, and users might have to go through more iterations to successfully upload their changes to the server.
Security scope	50,000 per list	Threshold	The maximum number of unique security scopes set for a list cannot exceed 50,000. For most farms, we recommend that you consider lowering this limit to 5,000 unique scopes. For large lists, consider using a design that uses as few unique permissions as possible. When the number of unique security scopes for a list exceeds the value of the list view threshold (set by default at 5,000 list items), additional SQL Server round trips take place when the list is viewed, which can adversely affect list view performance. A scope is the security boundary for a securable object and any of its children that do not have a separate security boundary defined. A scope contains an Access Control List (ACL), but unlike NTFS ACLs, a scope can include security principals that are specific to SharePoint Server 2013. The members of an ACL for a scope can include Windows users, user accounts other than Windows users (such as forms-based accounts), Active Directory groups, or SharePoint groups.

Column limits

SharePoint Server 2013 data is stored in SQL Server tables. To allow for the maximum number of possible columns in a SharePoint list, SharePoint Server 2013 will create several rows in the database when data will not fit on a single row. This is called row wrapping.

Each time that a row is wrapped in SQL Server, an additional query load is put on the server when that item is queried because a SQL join must be included in the query. To prevent too much load, by default a maximum of six SQL Server rows are allowed for a SharePoint item. This limit leads to a particular limitation on the number of columns of each type that can be included in a SharePoint list. The following table describes the limits for each column type.

The row wrapping parameter can be increased beyond six, but this may result in too much load on the server. Performance testing is recommended before exceeding this limit.

Each column type has a size value listed in bytes. The sum of all columns in a SharePoint list cannot exceed 8,000 bytes. Depending on column usage, users can reach the 8,000 byte limitation before reaching the six-row row wrapping limitation.

Limit	Maximum value	Limit type	Size per column	Notes
Single line of text	255	Threshold	30 bytes
Multiple Lines of Text	350	Threshold	22 bytes
Choice	255	Threshold	30 bytes
Choice (multiple selection)	350	Threshold	22 bytes
Number	550	Threshold	14 bytes
Currency	550	Threshold	14 bytes
Date and Time	550	Threshold	14 bytes
Lookup	750	Threshold	10 bytes
Yes / No	1000	Threshold	7 bytes
Person or group	750	Threshold	10 bytes
Hyperlink or picture	127	Threshold	60 bytes
Calculated	255	Threshold	30 bytes
GUID	350	Threshold	22 bytes
Int	750	Threshold	10 bytes
Managed metadata	190	Threshold	60 bytes for the first, 40 bytes for each subsequent	The first Managed Metadata field added to a list is allocated four columns: A lookup field for the actual tag A hidden text field for the string value A lookup field for the catch all A lookup field for spillover of the catch all Each subsequent Managed Metadata field added to a list adds two more columns: A lookup field for the actual tag A hidden text field for the string value
Geolocation	2	Threshold	30 bytes

External Data columns have the concept of a primary column and secondary columns. When you add an external data column, you can select some secondary fields of the external content type that you want to be added to the list. For example, given an External Content Type "Customer" which has fields like "ID", "Name", "Country", and "Description", when you add an External Data column of type "Customer" to a list, you can add secondary fields to show the "ID", "Name" and "Description" of the Customer. Overall these are the columns that get added:

· Primary column: A text field.

· Hidden Id column: A multi-line text field.

· Secondary columns: Each secondary column is a text/number/Boolean/multi-line text that is based on the data type of the secondary column as defined in the Business Data Catalog model. For example, ID might be mapped to a Numbercolumn; Name might be mapped to a Single line of text column ; Description might be mapped to a Multiple lines of text column.

Page limits

The following table lists the recommended guidelines for pages.

Limit	Maximum value	Limit type	Notes
Web parts	25 per wiki or Web Part page	Threshold	This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.

Security limits

Limit	Maximum value	Limit type	Notes
Number of SharePoint groups a user can belong to	5,000	Supported	This is not a hard limit but it is consistent with Active Directory guidelines. There are several things that affect this number: The size of the user token The groups cache: SharePoint Server 2013 has a table that caches the number of groups a user belongs to as soon as those groups are used in access control lists (ACLs). The security check time: as the number of groups that a user is a member of increases, the time that is required for the access check increases also.
Users in a site collection	2 million per site collection	Supported	You can add millions of people to your web site by using Microsoft Windows security groups to manage security instead of using individual users. This limit is based on manageability and ease of navigation in the user interface. When you have many entries (security groups of users) in the site collection (more than one thousand), you should use PowerShell to manage users instead of the UI. This will provide a better management experience.
Active Directory Principles/Users in a SharePoint group	5,000 per SharePoint group	Supported	SharePoint Server 2013 enables you to add users or Active Directory groups to a SharePoint group. Having up to 5,000 users (or Active Directory groups or users) in a SharePoint group provides acceptable performance. The activities most affected by this limit are as follows: Fetching users to validate permissions. This operation takes incrementally longer with growth in number of users in a group. Rendering the membership of the view. This operation will always require time.
SharePoint groups	10,000 per site collection	Supported	Above 10,000 groups, the time to execute operations is increased significantly. This is especially true of adding a user to an existing group, creating a new group, and rendering group views.
Security principal: size of the Security Scope	5,000 per Access Control List (ACL)	Supported	The size of the scope affects the data that is used for a security check calculation. This calculation occurs every time that the scope changes. There is no hard limit, but the bigger the scope, the longer the calculation takes.

Limits by feature

This section lists limits sorted by feature.

Search limits

The recommended guidelines for search are organized according to the aspects of search that they impact: the topology, the size of items, dictionaries, crawling, schema, queries and results, ranking, and the index.

Note

Limits for Search have changed significantly as the feature has been updated. For more information, see Plan search in SharePoint Server.

Search: topology limits

The topology limits ensure efficient communication between search components. Exceeding these limits slows down the communication between search components, which can result in longer query latencies and ultimately outage of search.

Limit	Maximum value	Limit type	Notes
Analytics processing components	6 per Search service application; 1 per server	Supported
Analytics reporting databases	4 per Search service application	Threshold	You can exceed this limit to accommodate specific requirements. When scaling, add an analytics reporting database when the size of any of the deployed analytics databases reaches 250 GB total size, or 20 M total rows. This way repartitioning is as balanced as possible.
Link databases	4 per Search service application	Supported	The highest tested number of items a link database can contain is 100 million.
Crawl components	16 per Search service application; 1 per server	Supported
Index components	60 per Search service application; 4 per server	Supported	To calculate the number of index components you have, multiply the number of index partitions with the number of index replicas. For SharePoint Foundation 2013 , this limit is one index component per Search service application and cannot be exceeded.
Index partitions	25 per Search service application	Supported	An index partition holds a subset of the Search service application index. Increasing the number of index partitions results in each partition holding a smaller subset of the index, reducing the RAM and disk space that is needed on the servers hosting the index components. For SharePoint Foundation 2013, the maximum number of index components per Search service application is one, so the maximum number of index partitions per Search service application is limited to one.
Index replicas	3 per index partition	Supported	Each index partition can have a set of replica. If you increase the number of index replicas, this has a positive effect on the query performance and it provides better fault tolerance. But, if you add too many replicas to your index partition, this can adversely affect indexing. For Internet sites scenarios, which typically have a high query rate but low content volume (less than 4 million items per partition), the supported limit is 6 index replicas per partition. For SharePoint Foundation 2013, the maximum number of index components per Search service application is one, so the maximum number of index partitions per Search service application is limited to one.
Content processing components	1 per server	Supported	The search topology supports scaling out the number of content processing components. Although a specific physical host or virtual machine does support multiple content processing components, you achieve better usage of the CPU capacity by using one content processing component. The reason is that a built-in mechanism maximizes CPU usage by adjusting the number of feeding sessions according to available CPU cores. Multiple feeding sessions allow the content processing component to process incoming documents in parallel. This mechanism assumes a single content processing component per host. If the number of physical cores on the host equals N, then the content processing component will have NK feeding sessions. K is a constant coefficient with the initial value 3. A 4-core server will have 12 feeding sessions, which means that the content processing component can process 12 documents in parallel. You can change the value of K by setting the *NumberOfCssFeedersPerCPUForRegularCrawl property of the Search Service Application. SharePoint Server 2013 limits the value of N upward to 12, even if a server has more than 12 physical cores. Therefore a 16-core server will have NK = 12 3 = 36 feeding sessions. In the case that there still is idle CPU time, consider increasing the K coefficient instead of adding an additional content processing component. If you increase the K coefficient, you must make sure that the host has sufficient available memory.
Query processing components	1 per server	Supported	SharePoint Server 2013 only supports one query processing component per physical machine or virtual machine.
Search components	64 per Search service application	Supported	This limit does not include crawl components. The sum of all the other search components must stay within this limit.
Search service applications	20 per farm	Supported	Multiple Search service applications can be deployed on the same farm, because you can assign search components and databases to separate servers. This limit is lower than the limit for the total number of service applications in a farm.
Content sources	500 per Search service application	Boundary	There is overhead associated with each content source, so we recommend that you create the smallest number of content sources that satisfy your other operational requirements, for example differences in crawl priority and scheduling.

Search: item size limits

The item size limits safeguard crawling performance and the size of the index. Here are some examples of how the limits can affect searching:

· If you can't get results when you search for an item, the item could be too large. A warning will show up in the Crawl Log, stating that the file exceeded the maximum size that the crawler can download.

· If you search for text in an item and only get results from the first part of the text, the content processing component may have truncated the item because it exceeded some of item size limits. When the content processing component truncates an item, it indicates this by setting the managed property IsPartiallyProcessed to True. A warning will also show up in the Crawl Log, stating why the item was truncated.

If you tune item size limits, we recommend that you work with them in the order they appear in this table.

Limit	Maximum value	Limit type	Notes
Document size crawl component can download	64 MB (3 MB for Excel documents)	Threshold	Search downloads meta data and content from a document until it reaches the maximum document size. The rest of the content is not downloaded. Search always downloads a document's meta data. You can change the default limit for the maximum document size. Do this by using Microsoft PowerShell cmdlets to change the Search service application property MaxDownLoadSize or MaxDownloadSizeExcel. MaxDownLoadSize doesn't impact the maximum size for Excel documents. Enter the value in megabytes. The maximum value for the maximum document size is 1024 MB, also for Excel documents. If you increase the limit for the maximum document size, search indexes more content and needs more disk space.
Parsed content size	2 million characters	Boundary	Search stops parsing an item after it has parsed up to 2 million characters of content from it, including the item's attachments. The actual amount of parsed characters can be lower than this limit because search uses maximum 30 seconds on parsing a single item and its attachments. When search stops parsing an item, the item is marked as partially processed. Any unparsed content isn't processed and therefore isn't indexed.
Characters processed by the word breaker	1,000,000	Boundary	Search breaks content into individual words (tokens). The word breaker produces tokens from the first 1,000,000 characters of a single item, including the item's attachments. The actual number of processed characters can be lower than this limit because search uses maximum 30 seconds on word breaking. Any remaining content isn't processed and therefore isn't indexed.
Indexed managed property size	512 KB per searchable/queryable managed property	Threshold	This is the default value for the maximum size of a managed property that is set to either "searchable" or "queryable". You can configure this limit by using PowerShell cmdlets and the schema object model to set the MP.MaxCharactersInPropertyStoreIndex attribute. Enter the value in bytes. The maximum value for this maximum size is 2,097,152 bytes. If you increase this limit you enable indexing of more data per managed property. Indexing more data per managed property uses more disk space and increases the overall load on the search system.
Retrievable managed property size	16 KB per managed property	Threshold	This is the default value for the maximum size of a retrievable managed property. You can configure this limit per managed property by using PowerShell cmdlets and the schema object model to set the P.MaxCharactersInPropertyStoreForRetrievalattribute. Enter the value in bytes. The maximum value for this maximum size is 2,097,152 bytes. If you increase this limit you enable indexing of more data per managed property. Indexing and retrieving more data per managed property increases the overall load on the system and uses more disk space.
Sortable and refinable managed property size	16 KB per managed property	Boundary	This is the maximum size of a sortable and refinable managed property.
Token size	Variable	Boundary	Search can index tokens of any length. But the word breaker that search uses to produce tokens can limit the token length. Word breakers are language-aware components that break content into single words (tokens). You can also create custom word breakers. The token size limit therefore depends on the word breaker. Here's the limit of the word breaker for western languages: The word breaker only considers the first 1000 characters of a token for splitting, it ignores any remaining characters. The word breaker splits tokens that are longer than 300 characters into two or more tokens where no token has more than 300 characters. For example, a 612 character token is split into two 300 character tokens and one 12 character token.

Search: dictionary limits

The dictionary limits safeguard memory, content processing efficiency, and query results.

Limit	Maximum value	Limit type	Notes
Number of entries in a thesaurus	1 million	Supported	The thesaurus contains synonyms for query terms. Exceeding this tested limit may result in increased use of memory and an increased query response time.
Number of entries in a custom entity extraction dictionary	1 million	Supported	Exceeding this tested limit may result in increased use of memory, slower indexing, and an increased query response time.
Number of entries in a custom search dictionary	5,000 terms per tenant	Boundary	This limits the number of terms allowed for inclusions and exclusions dictionaries for query spelling correction and company extraction. You can store more terms than this limit in the Termstore, but search only uses 5000 terms per tenant.

Search: schema limits

The schema limits safeguard memory resources and keep the management operation overhead at an acceptable level.

Limit	Maximum value	Limit type	Notes
Crawled properties	500,000 per Search service application	Supported	The contents and metadata of the items that you crawl are represented as crawled properties. You can map these crawled properties to managed properties. If the number of crawled properties exceeds this supported limit, this reduces indexing speed.
Managed properties	50,000 per Search service application	Supported	Search uses managed propertied in queries. Crawled properties are mapped to managed properties. Exceeding the supported limit for managed properties reduces indexing speed.
Managed property mappings	100 per managed property	Supported	Crawled properties can be mapped to managed properties. Exceeding this limit might decrease crawl speed and query performance.
Values per managed property	1000	Boundary	A managed property can have multiple values of the same type. This is the maximum number of values per managed multi-valued managed property per document. If this number is exceeded, the remaining values are discarded.
Metadata properties recognized	100,000 per crawled item	Supported	This is the maximum number of metadata properties that the crawl component can determine when crawling an item. These metadata properties can be mapped or used for queries. Approaching this number of crawled properties might result in a low crawl rate.

Search: crawl limits

Limit	Maximum value	Limit type	Notes
Start addresses	500 per content source	Supported
Length of machine host name	15 characters	Threshold	NetBIOS limits the maximum machine host name length to this value.
Crawl databases	15 per Search service application	Supported

Search: query and result limits

The limits for queries and results safeguard the search engine against executing very large query expressions and returning very large result sets. Preventing the search engine from executing very large query expressions and returning very large result sets prevents Denial-of-service (DoS) attacks and makes sure that results return timely. If you have to retrieve more results we recommend that you use paging.

Limit	Maximum value	Limit type	Notes
Text length for queries using Keyword Query Language	4 KB (4,096 characters)	Supported	This is the tested and default value for the maximum text length for a query built by using Keyword Query Language, except for Discovery queries. For Discovery queries 16 KB (16,384 characters) is the default maximum value. The default value for the maximum text length can be increased up to the boundary of 20 KB (20,480) for all query types.
Number of rows in a result set	500 rows	Supported	This is the tested and default value for the maximum number of rows in a result set, except for a Discovery query. For Discovery queries 10,000 rows is the default value. To display the entire result set, issue more paging queries. You can change the value for the maximum number of rows in a result set by using PowerShell cmdlets to change the Search service application property MaxRowLimit. MaxRowLimit defines the maximum value of the query property RowLimit and the Discovery query property RowLimit. RowLimit defines the number of rows each page contains in a result set. You can increase MaxRowLimit up to 10,000 rows, this is the supported boundary.
Results removal	No limit	Supported
Search alert quota	100,000 alerts per Search service application	Supported	End-users can set search alerts for the result set of a query. When the results are changed or updated, search notifies the end-user. This is the tested limit for a Search service application that has a mix of end-user queries (75%) and alert queries (25%). The limit for a Search service application that has only alert queries is 400,000 alerts. These limits are based on a system with five queries per second (QPS).

Search: ranking limits

The ranking limits safeguard application server memory, query latency, and the size of the index.

Limit	Maximum value	Limit type	Notes
Ranking models	1,000 per tenant	Boundary	Approaching this limit can adversely affect the overall system performance.
Unique contexts used for ranking	15 unique contexts per rank model	Boundary	This is the maximum number of unique contexts per rank model.
Authoritative pages	1 top level and minimal second and third level pages per Search service application	Supported	Use as few second- and third-level pages as possible while still achieving the desired relevance. The boundary is 200 authoritative pages per relevance level per Search service application. If you add more pages, you may not achieve the desired relevance. Add the key site to the first relevance level. Add more key sites at either second or third relevance levels, one at a time. Evaluate relevance after each addition to make sure that that you have achieved the desired relevance effect.

Search: index limits

The index limits safeguard the index from growing out of bounds and exceeding the available resources.

Limit	Maximum value	Limit type	Notes
Unique terms in the index	2^31 (>2 billion terms)	Boundary	This is the maximum number of unique terms that can exist in the index of a Search service application.
User defined full text indexes	10	Boundary	This is the maximum number of full text indexes.
Indexed items	10 million per index partition	Supported	Each index partition contains a subset of the whole search index. If the number of indexed items is high in relation to how much memory the server has, affects the query response time negatively. For SharePoint Foundation 2013, the maximum number of indexed items is 2 million items per index partition. For SharePoint Foundation 2013, the maximum number of indexed items is 2 million items per index partition, before applying the June 2016 Public Update. The June 2016 Public Update, increases this limit to 10 million items per index partition.

User Profile Service limits

The following table lists the recommended guidelines for User Profile Service.

Limit	Maximum value	Limit type	Notes
User profiles	2,000,000 per service application	Supported	A user profile service application can support up to 2 million user profiles with full social features functionality. This number represents the number of profiles that can be imported into the people profile store from a directory service, and also the number of profiles a user profile service application can support without leading to performance decreases in social features.
Social tags, notes and ratings	500,000,000 per social database	Supported	Up to 500 million total social tags, notes and ratings are supported in a social database without significant decreases in performance. However, database maintenance operations such as backup and restore may show decreased performance at that point.

Content deployment limits

The following table lists the recommended guidelines for content deployment.

Limit	Maximum value	Limit type	Notes
Content deployment jobs running on different paths	20	Supported	For concurrently running jobs on paths that are connected to site collections in the same source content database, there is an increased risk of deadlocks on the database. For jobs that must run concurrently, we recommend that you move the site collections into different source content databases. > [!NOTE]> Concurrent running jobs on the same path are not possible. If you are using SQL Server snapshots for content deployment, each path creates a snapshot. This increases the I/O requirements for the source database. For more information, see About deployment paths and jobs.

Blog limits

The following table lists the recommended guidelines for blogs.

Limit	Maximum value	Limit type	Notes
Blog posts	5,000 per site	Supported	The maximum number of blog posts is 5,000 per site.
Comments	1,000 per post	Supported	The maximum number of comments is 1,000 per post.

Business Connectivity Services limits

The following table lists the recommended guidelines for Business Connectivity Services.

Limit	Maximum value	Limit type	Notes
ECT (in-memory)	5,000 per web server (per tenant)	Boundary	Total number of external content type (ECT) definitions loaded in memory at a given point in time on a web server.
External system connections	500 per web server	Boundary	Number of active/open external system connections at a given point in time. The default maximum value is 200; the boundary is 500. This limit is enforced at the web server scope, regardless of the kind of external system (for example, database, .NET assembly, and so on) The default maximum is used to restrict the number of connections. An application can specify a larger limit via execution context; the boundary enforces the maximum even for applications that do not respect the default.
Database items returned per request	2,000 per database connector	Threshold	Number of items per request the database connector can return. The default maximum of 2,000 is used by the database connector to restrict the number of result that can be returned per page. The application can specify a larger limit via execution context; the Absolute Max enforces the maximum even for applications that do not respect the default. The boundary for this limit is 1,000,000.
Response latency	600 seconds	Threshold	Timeout used by the external data connector per request. The default value is 180 seconds, but applications can be configured to specify a larger value up to the maximum of 600 seconds.
Service response size	150,000,000 bytes	Threshold	The upper volume of data per request the external data connector can return. The default value is 3,000,000 bytes, but applications can be configured to specify a larger value up to the maximum of 150,000,000 bytes.
Filter Descriptor (in-store)	200 per ECT method	Boundary	The maximum number of Filter Descriptors per ECT method is 200.
ECT Identifier (in-store)	20 per ECT	Boundary	The maximum number of identifiers per ECT is 20.
Database Item	1,000,000 per request	Threshold	The default maximum number of items per request the database connector can return is 2,000, and the absolute maximum is 1,000,000. The default max is used by the database connector to restrict the number of results that can be returned per page. The application can specify a larger limit via execution context; the absolute max enforces the allowed maximum even for applications that do not respect the default such as indexing.

Workflow limits

The following table lists the recommended guidelines for workflow.

Limit	Maximum value	Limit type	Notes
Workflow postpone threshold	15	Threshold	15 is the maximum number of workflows allowed to be executing against a content database at the same time, excluding instances that are running in the timer service. When this threshold is reached, new requests to activate workflows will be queued to be run by the workflow timer service later. As non-timer execution is completed, new requests will count against this threshold. This is limit can be configured by using the Set-SPFarmConfig PowerShell cmdlet. For more information, see Set-SPFarmConfig. Note: This limit does not refer to the total number of workflow instances that can be in progress. Instead, it is the number of instances that are being processed. Increasing this limit increases the throughput of starting and completing workflow tasks but also increases load against the content database and system resources.
Workflow timer batch size	100	Threshold	The number of events that each run of the workflow timer job will collect and deliver to workflows. It is configurable by using PowerShell. To allow for additional events, you can run additional instances of the SharePoint Foundation Workflow Timer Service.
Workflow associations	100 per list	Supported	Exceeding this limit will degrade browser performance due to the large volume of data that is loaded for more than 100 associations and their status columns.
List items or documents that can be bulk created or uploaded to start workflow instances	5,000 items	Supported	Testing has verified that all workflow activation events are processed for an on-item-creation workflow association when up to 5,000 items are created in a single bulk upload. Exceeding this limit could cause workflow initiation to time out.
Published workflow definitions per web site	1,000 per web site	Supported	The maximum supported number of published workflow definitions per web site is 1,000.
Total workflow associations per site	1,799 per site	Boundary	The Service Bus supports a maximum of 1,799 subscriptions per scope. This maximum value includes the sum of both published and unpublished associations.
Maximum workflow definition (xaml) size	5,120 KB	Boundary	Attempts to publish xaml files that exceed the size limit will fail.
Maximum depth of a workflow sub-step in xaml (workflow complexity)	121 levels	Boundary	There is a hard limit of 125 for node depth in xaml. The maximum value of 121 levels accounts for the default activities (stage, sequence, etc.) that SharePoint Designer inserts automatically.
Workflow instance activations per second per web server	6 per second	Threshold	Testing has confirmed that a SharePoint web server can activate a maximum of 6 workflow instances per second. This number is cumulative, and therefore scales with the number of web servers in the farm. For example, 2 web servers can activate 12 workflow instances per second, and 3 web servers can activate 18.
Rest calls from SharePoint workflow per second per web server	60 per second	Supported	Testing has confirmed that a SharePoint web server can effectively process up to 60 rest calls per second from SharePoint workflow. If this level of volume will be exceeded, we recommend that an additional load-balanced web server be added to the SharePoint farm. In testing, 120 rest calls per second against a single web server resulted in sustained 90-100% CPU utilization. Adding a second web server reduced CPU utilization to 30-40% on both servers. Adding a third web server enabled processing of 180 calls per second, with 30-40% CPU utilization on all three servers, and so on. The servers used for this test were Hyper-V virtual machines with 16 core processor and 24 GBs RAM each.
Workflow variable value size	256 KB	Boundary	The maximum amount of data that can be stored in a single workflow variable is 256 KB. Exceeding this limit will cause the workflow instance to terminate.
Maximum list size for workflow lookups to non-indexed fields	5,000 items per list view	Threshold	This limit is a result of the maximum view size limit. When this limit is exceeded, workflow lookups to non-indexed fields will fail for non-administrative users. At this threshold, an index must be created for the field, in order for workflows to be able to successfully perform lookups against the field.
Maximum list size for auto-start workflow associations	10 million items per list	Supported	Testing has confirmed that the performance of auto-start workflow associations is not affected when list size grows to 1 million items. Because response time doesn't change as list size scales, the effective limit is the same as the maximum number of items in a non-workflow list.

Managed Metadata limits

The following table lists the recommended guidelines for managed metadata configuration.

Limit	Maximum value	Limit type	Notes
Number of folders with location-based defaults	1,000 folders per site, or data file size of 256 Mb	Boundary	Location-based default metadata allows you to set default values for list columns per folder. You can only apply location-based default values on up to 1,000 folders per site, or up to the point at which the data file in which location-based default metadata is stored for the site (client_LocationBasedDefaults.html) reaches 265 Mb. When the number of folders in the data file exceeds 1,000, or the data file size exceeds 256 Mb, default values added for additional folders will be ignored.
Number of links in or file size of a document that are updated when the target location changes	1,000 links or file size of 256 Mb per document	Boundary	When a document containing links is added to a folder, SharePoint Foundation 2013 will update links automatically when the link target is moved to a new location. In a document with more than 1,000 links, or a document with a file size that exceeds 256 Mb, the document is treated as though it contains no links, and updates to link targets are ignored for the entire document.

Managed Metadata term store (database) limits

The following table lists the recommended guidelines for managed metadata term stores.

Limit	Maximum value	Limit type	Notes
Maximum number of levels of nested terms in a term store	7	Supported	Terms in a term set can be represented hierarchically. A term set can have up to seven levels of terms (a parent term, and six levels of nesting below it.)
Maximum number of term sets in a term store	1,000	Supported	You can have up to 1,000 term sets in a term store.
Maximum number of terms in a term set	30,000	Supported	30,000 is the maximum number of terms in a term set. > [!NOTE]> Additional labels for the same term, such as synonyms and translations, do not count as separate terms.
Total number of items in a term store	1,000,000	Supported	An item is either a term or a term set. The sum of the number of terms and term sets cannot exceed 1,000,000. Additional labels for the same term, such as synonyms and translations, do not count as separate terms. > [!NOTE]> You cannot have both the maximum number of term sets and the maximum number of terms simultaneously in a term store.
Number of Variation Labels	209 per term store	Supported	The maximum number of Variation Labels per term store is 209.
Number of terms in managed navigation term set	2,000	Supported	The maximum supported number of terms in a managed navigation term set is 2,000.

Visio Services limits

The following table lists the recommended guidelines for instances of Visio Services in SharePoint.

Limit	Maximum value	Limit type	Notes
File size of Visio web drawings	50 MB	Threshold	Visio Services has a configuration setting that enables the administrator to change the maximum size of web drawings that Visio processes. Larger file sizes have the following side effects: Increase in the memory footprint of Visio Services. Increase in CPU usage. Reduction in application server requests per second. Increase overall latency. Increase SharePoint farm network load
Visio web drawing recalculation time-out	120 seconds	Threshold	Visio Services has a configuration setting that enables the administrator to change the maximum time that it can spend recalculating a drawing after a data refresh. A larger recalculation time-out leads to: Reduction in CPU and memory availability. Reduction in application requests per second. Increase in average latency across all documents. A smaller recalculation time-out leads to: Reduction of the complexity of diagrams that can be displayed. Increase in requests per second. Decrease in average latency across all documents.
Visio Services minimum cache age (data connected diagrams)	Minimum cache age: 0 to 24hrs	Threshold	Minimum cache age applies to data connected diagrams. It determines the earliest point at which the current diagram can be removed from cache. Setting Min Cache Age to a very low value will reduce throughput and increase latency, because invalidating the cache too often forces Visio to recalculate often and reduces CPU and memory availability.
Visio Services maximum cache age (non-data connected diagrams)	Maximum cache age: 0 to 24hrs	Threshold	Maximum cache age applies to non-data connected diagrams. This value determines how long to keep the current diagram in memory. Increasing Max Cache Age decreases latency for commonly requested drawings. However, setting Max Cache Age to a very high value increases latency and slows throughput for items that are not cached, because the items already in cache consume and reduce available memory.

SharePoint Web Analytics service limits

The SharePoint Web Analytics service has been deprecated in SharePoint Server 2013.

PerformancePoint Services limits

The following table lists the recommended guidelines for PerformancePoint Services in SharePoint.

Limit	Maximum value	Limit type	Notes
Cells	1,000,000 per query on Excel Services data source	Boundary	A PerformancePoint scorecard that calls an Excel Services data source is subject to a limit of no more than 1,000,000 cells per query.
Columns and rows	15 columns by 60,000 rows	Threshold	The maximum number of columns and rows when rendering any PerformancePoint dashboard object that uses a Excel workbook as a data source. The number of rows could change based on the number of columns.
Query on a SharePoint list	15 columns by 5,000 rows	Supported	The maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SharePoint list as a data source. The number of rows could change based on the number of columns.
Query on a SQL Server data source	15 columns by 20,000 rows	Supported	The maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SQL Server table data source. The number of rows could change based on the number of columns.

Word Automation Services limits

The following table lists the recommended guidelines for Word Automation Services.

Limit	Maximum value	Limit type	Notes
Input file Size	512 MB	Boundary	Maximum file size that can be processed by Word Automation Services.
Frequency with which to start conversions (minutes)	1 minute (recommended) 15 minutes (default) 59 minutes (boundary)	Threshold	This setting determines how often the Word Automation Services timer job executes. A lower number leads to the timer job running faster. Our testing shows that it is most useful to run this timer job once per minute.
Number of conversions to start per conversion process	For PDF/XPS output formats: 30 x MFor all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)	Threshold	The number of conversions to start affects the throughput of Word Automation Services. If these values are set higher than the recommended levels then some conversion items may start to fail intermittently and user permissions may expire. User permissions expire 24 hours from the time that a conversion job is started.
Conversion job size	100,000 conversion items	Supported	A conversion job includes one or more conversion items, each of which represents a single conversion to be performed on a single input file in SharePoint. When a conversion job is started (using the ConversionJob.Start method), the conversion job and all conversion items are transmitted over to an application server which then stores the job in the Word Automation Services database. A large number of conversion items will increase both the execution time of the Start method and the number of bytes transmitted to the application server.
Total active conversion processes	N-1, where N is the number of cores on each application server	Threshold	An active conversion process can consume a single processing core. Therefore, customers should not run more conversion processes than they have processing cores in their application servers. The conversion timer job and other SharePoint activities also require occasional use of a processing core. We recommend that you always leave 1 core free for use by the conversion timer job and SharePoint.
Word Automation Services database size	2 million conversion items	Supported	Word Automation Services maintains a persistent queue of conversion items in its database. Each conversion request generates one or more records. Word Automation Services does not delete records from the database automatically, so the database can grow indefinitely without maintenance. Administrators can manually remove conversion job history by using the PowerShell cmdlet Remove-SPWordConversionServiceJobHistory. For more information, see Remove-SPWordConversionServiceJobHistory.

Excel Services limits

The following table lists the recommended guidelines for Excel Services in SharePoint.

Limit	Maximum value	Limit type	Notes
Maximum workbook size	10 MB	Supported	The maximum size of a workbook that can be opened in Excel Services is 10 megabytes.

Machine Translation Service limits

The following table lists the recommended guidelines for the Machine Translation Service.

Limit	Maximum value	Limit type	Notes
Input file size for binary files	524,288 KB per file	Threshold	Files larger than the limit take too long to transfer and process, decreasing the throughput of the service.
Input file size for text files	15,360 KB per file	Threshold	Files larger than the limit have too much text to translate, decreasing the throughput of the service.
Maximum character count for Microsoft Word Documents	10,000,000 per document	Threshold	Documents with more characters than the limit have too much text to translate, decreasing the throughput of the service.
Total concurrent translation processes	5	Threshold	Using more processes than the limit does not increase throughput because there is a limit to how much text can be translated at a time. Using more processes increases the demands on the server resources.
Delay between translations	59 minutes	Threshold	Starting translations at a larger interval than the limit causes the time taken to translate documents to grow too large and can cause the number of queued translations to grow too large.
Number of translations per translation process	1,000 per process	Threshold	Starting more translations than the limit causes translations to fail due to timing out because they cannot be processed before the timeout period.
Maximum concurrent translation requests	300	Threshold	More than 300 concurrent translation requests could cause translations to time out because requests are queued for longer than the timeout period.
Files per translation job	100,000 files	Supported	Submitting jobs with a number of files that exceeds the limit causes job submittal time and processing time to be too long.
Machine Translation Service database size	1,000,000 files	Supported	Operations to maintain the queue of jobs become slow if the database grows beyond the maximum number of files in the database.

Office Web Application Service limits

The following table lists the recommended guidelines for Office Online. Office client application limits also apply when an application is running as a web app.

Limit	Maximum value	Limit type	Notes
Cache size	100 GB	Threshold	Space available to render documents, created as part of a content database. By default, the cache available to render documents is 100 GB. We do not recommend that you increase the available cache.
Renders	One per document per second per CPU core per application server (maximum eight cores)	Boundary	This is the measured average number of renders that can be performed of "typical" documents on the application server over a period of time.
OneNote concurrent merge operations	8 per document	Threshold	OneNote merges combine changes from multiple users who are co-authoring a notebook. If too many concurrent merges are already in progress, a conflict page is generated instead, which forces the user to perform the merge manually.

Project Server limits

The following table lists the recommended guidelines for Project Server. For more information about how to plan for Project Server, see Planning and architecture for Project Server 2010.

Limit	Maximum value	Limit type	Notes
End of project time	Date: 12/31/2149	Boundary	Project plans cannot extend past the date 12/31/2149.
Deliverables per project plan	1,500 deliverables	Boundary	Project plans cannot contain more than 1,500 deliverables.
Number of fields in a view	256	Boundary	A user cannot have more than 256 fields added to a view that they have defined in Project Web App.
Number of clauses in a filter for a view	50	Boundary	A user cannot add a filter to a view that has more than 50 clauses in it.

SharePoint Apps limits

The following table lists the recommended guidelines for apps for SharePoint.

Limit	Maximum value	Limit type	Notes
Maximum Access/SharePoint App Package size	100 Mb	Boundary	100 MB is the limit for an app package created in the Access client. > [!NOTE]> Access compresses the database when it creates the app package, so the app package may include more than 100 MB of data.
Maximum Access app database storage size in SQL Azure	1 Gb	Boundary	Each Access app created on SharePoint Online creates a database on SQL Azure. 1 GB is the limit for the database storage on SQL Azure. In an on-premise installation, the administrator controls the size of the associated SQL database.
Apps displayed in Manage Licenses page	2,000	Boundary	Up to 2,000 apps (purchased from the store) can be displayed on the Manage Licenses page. You can still manage the license of any app by going to the All Site Contents page of the site where the app is installed and clicking on Licenses, or by searching for the app using Marketplace Search.
Number of app licenses per tenant	1,000,000	Supported	The maximum supported number of licenses (purchase of apps from the store) for a single SharePoint deployment, either on-premises or SharePoint Online. Exceeding this limit might cause severe performance degradation.
Number of apps displayed in the Add an App page	240	Boundary	After this limit is reached, only the first 240 apps are displayed, and a message guiding you to search to find your app is displayed.
Number of managers per app license	30	Boundary	Only 30 people can manage a license. License managers can add or remove users or delete a license.
Number of app licenses assigned to a user viewable by that user	2,000	Boundary	When more than 2,000 licenses are assigned to a user, that user will no longer see any apps in the default Add an App view. Instead, a message guiding you to search the app catalog or the SharePoint Store will appear.
Number of apps in the corporate catalog viewable by a single user	500	Boundary	When more than 500 apps from the corporate catalog are available to a single user, that user will no longer see any apps in the default Add an App view. Instead, a message guiding you to search the app catalog or the SharePoint Store will appear.

Distributed cache service limits

The following table lists the recommended guidelines for the distributed cache service.

Limit	Maximum value	Limit type	Notes
Number of followable entities (users, documents, sites and hashtags) per cache host	400,000	Supported	The total number of entities that can be followed by a single user on a distributed cache host with 16GB RAM assigned to the distributed cache service is 400,000.
Number of cache hosts in a cluster	16	Boundary	The total number of cache hosts a single distributed cache cluster can support is 16.
Maximum amount of memory dedicated to a cache host	16GB	Boundary	The total amount of memory that can be dedicated to the distributed cache service on any one cache host in a cluster is 16GB.

Miscellaneous limits

The following table lists limits and recommended guidelines for services and features not covered in other sections.

Limit	Maximum value	Limit type	Notes
Number of User agent substrings per device channel	150	Boundary	The maximum number of user agent substrings per mobile device channel is 150.
Number of SharePoint sources per EDiscovery case	100	Boundary	The maximum number of SharePoint sources that can be added to an EDiscovery case is 100.
Number of Exchange sources (mailboxes) per EDiscovery case	1,500	Boundary	The maximum number of Exchange sources (mailboxes) per EDiscovery case is 1,500.
Maximum size of EDiscovery Query	16K characters or 500 keywords	Boundary	The size of an EDiscovery query is limited to 500 keywords or 16,000 characters, whichever is reached first.

Active Directory Distribution Groups Unavailable in People Picker

2018-05-16T22:56:00.000+05:30

We had a issue wherein the user is using infopath form in Sharepoint 2013 ( consider any version of Sharepoint ) where the user tries to resolve a Distribution group in the form however it doesnt resolve.

So we explained the user that the distribution group doesnt get resolved it has to be converted to a security group . Its by Design .

For reference :

https://support.nintex.com/SharePoint/Workflow/Active_Directory_Distribution_Groups_Unavailable_in_People_Picker

https://social.technet.microsoft.com/Forums/lync/en-US/35aa5e72-521c-416d-961c-d00d426c54e4/people-picker-and-infopath?forum=sharepointgeneral

1.What is the difference between a security group and a distribution group?
Ans. Security groups can be used to assign security rights on resources inside your Windows 2003 Active Directory network. By using a security group, we can collect a group of user accounts in a department and assign them access to a shared folder. ... A distribution group can be used for sending emails to a group of users.

Content database limits suggested by Microsoft in SharePoint 2013

2018-05-16T00:13:00.002+05:30

The following table lists the recommended guidelines for content databases.

Limit
Maximum value
Limit type
Notes

Number of content databases
500 per farm
  The maximum number of content databases per farm is 500. With 500 content databases per web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use PowerShell to manage the web application when a large number of content databases are present, because the management interface might become slow and difficult to navigate.
With 200GB per content database, and 500 content databases per farm, SharePoint Server 2013 supports 100TB of data per farm.

Content database size (general usage scenarios)
200 GB per content database
  We strongly recommended limiting the size of content databases to 200 GB, except when the circumstances in the following rows in this table apply.
If you are using Remote BLOB Storage (RBS), the total volume of remote BLOB storage and metadata in the content database must not exceed the 200GB limit.

Content database size (all usage scenarios)
4 TB per content database
  Content databases of up to 4 TB are supported when the following requirements are met:
Disk sub-system performance of 0.25 IOPS per GB. 0.2 IOPS per GB is recommended for optimal performance.
You must have developed plans for high availability, disaster recovery, future capacity, and performance testing.
You should also carefully consider the following factors:
Requirements for backup and restore may not be met by the native SharePoint Server 2013 backup for content databases larger than 200 GB. It is recommended to evaluate and test SharePoint Server 2013 backup and alternative backup solutions to determine the best solution for your specific environment.
It is strongly recommended to have proactive skilled administrator management of the SharePoint Server 2013 and SQL Server installations.
The complexity of customizations and configurations on SharePoint Server 2013 may necessitate refactoring (or splitting) of data into multiple content databases. Seek advice from a skilled professional architect and perform testing to determine the optimum content database size for your implementation. Examples of complexity may include custom code deployments, use of more than 20 columns in property promotion, or features listed as not to be used in the over 4 TB section below.
Refactoring of site collections allows for scale out of a SharePoint Server 2013 implementation across multiple content databases. This permits SharePoint Server 2013 implementations to scale indefinitely. This refactoring will be easier and faster when content databases are less than 200 GB.
It is suggested that for ease of backup and restore that individual site collections within a content database be limited to 100 GB. For more information, see Site collection limits.

IMPORTANT We do not recommend the use of content databases that exceed 4 TB, except in document archive scenarios (described in the next row in this table). If, in the future, you need to upgrade your SharePoint Server 2013 installation, upgrading the site collections within the content databases can be very difficult and time consuming. > It is strongly recommended that you scale out across multiple content databases, rather than exceed 4 TB of data in a single content database.

Content database size (document archive scenario)
No explicit content database limit
Supported
Content databases with no explicit size limit for use in document archive scenarios are supported when the following requirements are met:
You must meet all requirements from the "Content database size (all usage scenarios)" limit earlier in this table, and you should ensure that you have carefully considered all the factors discussed in the Notes field of that limit.
SharePoint Server 2013 sites must be based on Document Center or Records Center site templates.
Less than 5% of the content in the content database is accessed each month on average, and less than 1% of content is modified or written each month on average.
Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint Server 2013 objects in the content database.
Note: Document archive content databases can be configured to accept documents from Content Routing workflows.
For more information about large-scale document repositories, see Estimate performance and capacity requirements for large scale document repositories in SharePoint Server 2010, and the Typical large-scale content management scenarios section of the article Enterprise content storage planning (SharePoint Server 2010).

Content database items
60 million items including documents and list items
Supported
The largest number of items per content database that has been tested on SharePoint Server 2013 is 60 million items, including documents and list items. If you plan to store more than 60 million items in SharePoint Server 2013, you must deploy multiple content databases.

Site collections per content database
10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone)
Supported
We strongly recommended limiting the number of site collections in a content database to 5,000. However, up to 10,000 site collections in a database are supported. Note that in a content database with up to 10,000 total site collections, a maximum of 2,500 of these can be non-Personal site collections. It is possible to support 10,000 Personal site collections if they are the only site collections within the content database.
These limits relate to speed of upgrade. The larger the number of site collections in a database, the slower the upgrade with respect to both database upgrade and site collection upgrades.
The limit on the number of site collections in a database is subordinate to the limit on the size of a content database that has more than one site collection. Therefore, as the number of site collections in a database increases, the average size of the site collections it contains must decrease.
Exceeding the 5,000 site collection limit puts you at risk of longer downtimes during upgrades. If you plan to exceed 5,000 site collections, we recommend that you have a clear upgrade strategy to address outage length and operations impact, and obtain additional hardware to speed up the software updates and upgrades that affect databases.
To set the warning and maximum levels for the number of sites in a content database, use the PowerShell cmdlet Set-SPContentDatabase with the -WarningSiteCount parameter. For more information, see Set-SPContentDatabase.

Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS)
Time to first byte of any response from the NAS should remain within 40 milliseconds 95% of the time.
Boundary
When SharePoint Server 2013 is configured to use RBS, and the BLOBs reside on NAS storage, consider the following supported limit.
From the time that SharePoint Server 2013 requests a BLOB, until it receives the first byte from the NAS, 95% of the time no more than 40 milliseconds can pass.

Reference : https://docs.microsoft.com/en-us/sharepoint/install/software-boundaries-and-limits

SharePoint 2016: Build Numbers

2017-10-23T17:20:00.001+05:30

Finding your Build Number

To find the build version of the SharePoint farm using Windows PowerShell:

1. Open the SharePoint Management Shell

2. Type the following command:

(Get-SPFarm).BuildVersion

Build Number Table:

Please see the table below:

Schema Version	Build Number	Schema Change	LPs	Released Month	Compon ent	KB	Download Link	Issue Fixed
16.0.4327.1000	16.0.4351.1000	N/A	No	RTM	SP 16		RTM
16.0.4327.1000	16.0. 4366. 1000	No	No	April 2016 CU	SP 16	KB 2920721	April 2016 CU	Link
16.0.4378.1000	16.0.4378.1000	Yes	No	May 2016 CU	SP & Proj 16	KB 3115088	May 2016 CU	Link
16.0.4378.1000	16.0.4378.1000	Yes	Yes	May 2016 CU	SP & Proj 16	KB 2920690	May 2016 Cu +LP	see above link
16.0.4393.1000	16.0.4393.1000	Yes	No	June 2016 CU	SP & Proj 16	KB 3115181	June 2016 CU	Link
16.0.4393.1000	16.0.4393.1000	Yes	Yes	June 2016 CU	SP & Proj 16	KB 3115184	June 2016 CU+LP	Link
16.0.4405.1000	16.0.4405.1000	Yes	No	July 2016 Cu	SP & Proj 16	Kb 3115299	July 2016 CU
16.0.4405.1000	16.0.4405.1000	Yes	Yes	July 2016 Cu	SP & Proj 16	Kb 3115304	July 2016 CU +LP
16.0.4417.1000	16.0.4417.1000	Yes	No	Aug 2016 CU	SP & Proj 16	KB 3115437	Aug 2016 CU	Link
16.0.4417.1000	16.0.4417.1000	Yes	Yes	Aug 2016 CU	Sp & Proj 16	KB 3115441	Aug 2016 CU & Lp	Link
16.0.4432.1003		Yes	Yes	Sep 2016 CU	SP & Proj 16	Kb 3118295	Sep 2016 CU +LP
16.0.4432.1003		Yes	No	Sep 2016 CU	SP & Proj 16	Kb 3118289	Sep 2016 CU
16.0.4444.1004	16.0.4444.1000	Yes	No	Oct 2016 CU	SP & Proj 16	Kb 3118372	Oct 2016 CU
16.0.4444.1000	16.0.4444.1000	Yes	Yes	Oct 2016 CU	SP & Proj 16	Kb 3118376	Oct 2016 CU +LP
16.0.4456.1002	16.0.4456.1000	Yes	No	Nov 2016 CU	SP & Proj 16	Kb 3127940	Nov 2016 CU
16.0.4456.1002	16.0.4456.1000	Yes	Yes	Nov 2016 CU	SP & Proj 16	Kb 3127942	Nov 2016 CU +LP
16.0.4471.1000	16.0.4471.1000	Yes	No	Dec 2016 CU	SP & Proj 16	Kb 3128014	Dec 2016 CU
16.0.4471.1000	16.0.4471.1000	Yes	Yes	Dec 2016 CU	Sp & Proj 16	Kb 3128017	Dec 2016 CU + LP
16.0.4483.1001	16.0.4483.1001	Yes	No	Jan 2017 CU	SP & Proj 16	Kb 3141486	Jan 2017 CU
16.0.4483.1001	16.0.4483.1001	Yes	Yes	Jan 2017 CU	SP & Proj 16	Kb 3141487	Jan 2017 CU + LP
16.0.4498.1002	16.0.4498.1002	Yes	No	Feb 2017 CU	SP & Proj 16	Kb 3141515	Feb 2017 CU
16.0.4498.1002	16.0.4498.1002	Yes	Yes	Feb 2017 CU	SP & Proj 16	Kb 3141517	Feb 2017 CU + LP
16.0.4510.1001	16.0.4510.1001	Yes	No	March 2017 CU	SP & Proj 16	Kb 3178672	March 2017 CU
16.0.4510.1001	16.0.4510.1001	Yes	Yes	March 2017 CU	SP & Proj 16	Kb 3178675	March 2017 CU + LP
16.0.4522.1000	16.0.4522.1000	Yes	No	April 2017 CU	SP & Proj 16	Kb 3178718	April 2017 CU
16.0.4522.1000	16.0.4522.1000	Yes	Yes	April 2017 CU	SP & Proj 16	Kb 3178721	April 2017 CU + LP
16.0.4534.1000	16.0.4534.1000	Yes	No	May 2017 CU	SP & Proj 16	Kb 3191880	May 2017 CU
16.0.4534.1000	16.0.4534.1000	Yes	Yes	May 2017 CU	SP & Proj 16	Kb 3191884	May 2017 CU + LP
16.0.4549.1001	16.0.4549.1001	Yes	No	June CU 2017	SP & Proj 16	KB 3203432	June 2017 CU
16.0.4549.1000	16.0.4549.1000	Yes	Yes	June CU 2017	SP & Proj 16	Kb 3203433	June 2017 CU +LP
16.0.4561.1000	16.0.4561.1000	Yes	No	July CU 2017	SP & Proj 16	Kb 3213544	July 2017 CU
16.0.4561.1000	16.0.4561.1000	Yes	Yes	July CU 2017	SP & Proj 16	Kb 3213543	July 2017 CU & LP

Please read below for further explanation of each column:

Schema Version: This version number you will see from central admin (home page or going to Central admin > System Settings > Manager Server in Farm) or you can get the same from PowerShell as well: (Get-SPFarm).BuildVersion
Build Number: Now onwards, MSFT is not changing the schema version with every CU as they change the practice so this number represents the patch level you are. You can get by going Central Admin > Upgrade and Migration > Check Product and patch Installation Status.
Schema Change: This column will tell if Schema was changed or not for a specific CU
LPs: This column will tell if they included the Language Pack fix or not.
Release: This Column will tell the release month of the CU
Component: What SharePoint or Project component this CU is for. Most probably it will be SharePoint 2016.
KB: Link to MSFT KB Articles
Download Link: Download link for the CU
Issue Fixed: This will list all the issues fixed in this CU.

Factors affecting performance and capacity in Project Server 2013

2017-05-11T19:12:00.002+05:30

Entity	Description/Notes	Small	Medium	Large
Projects		20	100	5000
Project Sites		20	100	5000
% Projects in Managed Mode		0%	10%	80%
Tasks		1250	25000	1250000
Average Tasks Per Project		62.5	250	250
Task Transaction History	The number of times status tends to be submitted and approved for any given task	10	10	100
Assignments		1625	32500	1625000
Average Assignments Per Task		1.3	1.3	1.3
Average Tasks per My Site User		50	250	5000
Approvals	Pending updates per manager	5	50	600
Resources		50	1000	10000
Average Resources Per Project		2.5	10	20
Average Assignments Per Resource		32.5	32.5	162.5
Users		50	1000	10000
Calendars		3	26	100
Issues		20	400	20000
Risks		20	400	20000
Deliverables		20	800	40000
Enterprise Project Types			5	50
Workflows			2	30
Average Projects Per Workflow			50	167
Phases			5	50
Phases Per Enterprise Project Type			20	20
Stages			15	150
Stages Per Workflow			20	40
PDPs			10	100
Custom Fields Per PDP			10	10
Number of Departments				100
Average Projects Per Department				50
Average Resources Per Department				100
Timesheets Per Year	The more you utilize timesheets, the more resource demands will be placed on SQL Server.	2600	52000	780000
Status Reports Per Year			26000	260000

Social features - SP 2013

2016-04-19T11:18:00.003+05:30

Social features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Ask Me About	No	Yes	Yes
Blogs	Yes	Yes	Yes
Communities Reputation, Badging, and Moderation	No	Yes	Yes
Community	Yes	Yes	Yes
Company Feed	Yes	Yes	Yes
Follow	No	Yes	Yes
Microblogging	No	Yes	Yes
Newsfeed	No	Yes	Yes
One Click Sharing	No	Yes	Yes
People, Sites, Document Recommendations	No	Yes	Yes
Personal Site	No	Yes	Yes
Photos and Presence	Yes	Yes	Yes
Profile	No	Yes	Yes
Ratings	No	Yes	Yes
Site Feed	Yes	Yes	Yes
Skydrive Pro	Yes	Yes	Yes
Tag profiles	No	Yes	Yes
Tasks integrated with Outlook	No	Yes	Yes
Trending Tags	No	Yes	Yes
Wikis	Yes	Yes	Yes

Sites features - SP 2013

2016-04-19T11:17:00.000+05:30

Sites features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Change the look	Yes	Yes	Yes
Connections to Microsoft Office Clients	Yes	Yes	Yes
Cross Browser Support	Yes	Yes	Yes
Custom Managed Paths	Yes	Yes	Yes
Governance	Yes	Yes	Yes
Large List Scalability and Management	Yes	Yes	Yes
Mobile Connectivity	Yes	Yes	Yes
Multi-Lingual User Interface	Yes	Yes	Yes
My Tasks	Yes	Yes	Yes
OOTB Web Parts	Yes	Yes	Yes
Permissions Management	Yes	Yes	Yes
Project functionality for team sites	Yes	Yes	Yes
Project site template	Yes	Yes	Yes
Project Summary web part	Yes	Yes	Yes
Project workspace	Yes	Yes	Yes
Public Website (SPO)	N/A (SharePoint Online only)	N/A (SharePoint Online only)	N/A (SharePoint Online only)
SharePoint Lists	Yes	Yes	Yes
SharePoint Ribbon	Yes	Yes	Yes
Task list	Yes	Yes	Yes
Team Site: Drag & Drop	Yes	Yes	Yes
Team Site: Notebook	Yes	Yes	Yes
Team Site: Simplified Access	Yes	Yes	Yes
Templates	Yes	Yes	Yes
Themes	Yes	Yes	Yes
Work Management Service	Yes	Yes	Yes
Usage Analytics	Yes	Yes	Yes

Insights features SP 2013

2016-04-19T11:16:00.000+05:30

Insights features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Business Intelligence Center	No	No	Yes
Calculated Measures and Members	No	No	Yes
Data Connection Library	No	No	Yes
Decoupled PivotTables and PivotCharts	No	No	Yes
Excel Services	No	No	Yes
Field list and Field Support	No	No	Yes
Filter Enhancements	No	No	Yes
Filter Search	No	No	Yes
PerformancePoint Services	No	No	Yes
PerformancePoint Services (PPS) Dashboard Migration	No	No	Yes
Power View	No	No	Yes
PowerPivot	No	No	Yes
Quick Explore	No	No	Yes
Scorecards & Dashboards	No	No	Yes
SQL Server Reporting Services (SSRS) Integrated Mode	Yes	Yes	Yes
SQL Server Reporting Services (SSRS) Web Part	Yes	Yes	Yes
Timeline Slicer	No	No	Yes
Visio Services	No	No	Yes

Content features - SP 2013 comparision

2016-04-19T11:11:00.000+05:30

Content features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Accessibility Standards Support	Yes	Yes	Yes
Asset Library Enhancements/Video Support	Yes	Yes	Yes
Auditing	No	Yes	Yes
Auditing & Reporting (e.g. doc edits, policy edits, deletes)	No	Yes	Yes
Auditing of View Events	No	Yes	Yes
Content Organizer	No	Yes	Yes
Design Manager	Yes	Yes	Yes
Document Sets	No	Yes	Yes
Document Translation in Word Web App	Yes1	Yes1	Yes1
eDiscovery	No	No	Yes
External Sharing: External Access	No	No	No
External Sharing: Guest Link	No	No	No
Folder Sync	No	Yes	Yes
Information Rights Management (IRM)	No	Yes	Yes
In-Place Hold	Yes	Yes	Yes
Managed Metadata Service	No	Yes	Yes
Metadata-driven Navigation	No	Yes	Yes
Multi-stage Disposition	No	Yes	Yes
Office ProPlus (Osub)	No	No	No
Office Web Apps (edit)	Yes1	Yes1	Yes1
Office Web Apps (view)	Yes1	Yes1	Yes1
Office Web Apps Server integration	Yes	Yes	Yes
PowerPoint Automation Services	No	Yes	Yes
Preservation hold library	No	No	Yes
Quick Edit	Yes	Yes	Yes
Related Items	Yes	Yes	Yes
Rich Media Management	No	Yes	Yes
Shared Content Types	No	Yes	Yes
SharePoint Translation Services	No3	Yes	Yes
Site mailbox	No	Yes2	Yes2
Unique Document IDs	No	Yes	Yes
Video Search	No	No	Yes
WCM: Analytics	No	Yes	Yes
WCM: Catalog	No	No	Yes
WCM: Cross-site publishing	No	No	Yes
WCM: Designer Tools	No	Yes	Yes
WCM: Faceted navigation	No	No	Yes
WCM: Image Renditions	No	No	Yes
WCM: Mobile and Device Rendering	No	Yes	Yes
WCM: Multiple Domains	No	No	Yes
WCM: OOTB Recommendations Webparts	No	Yes	Yes
WCM: Search Engine Optimizations (SEO)	No	Yes	Yes
WCM: Topic Pages	No	No	Yes
Word Automation Services	No	Yes	Yes

Search Features 2013 comparision

2016-04-19T11:06:00.002+05:30

Search features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Advanced Content Processing	Yes	Yes	Yes
Content Search Web Part	No	No	Yes
Continuous crawl	Yes	Yes	Yes
Custom entity extraction	No	No	Yes
Deep links	No	Yes	Yes
Event-based relevancy	No	Yes	Yes
Expertise Search	Yes	Yes	Yes
Extensible content processing	No	No	Yes
Graphical refiners	No	Yes	Yes
Hybrid search	Yes	Yes	Yes
Managed navigation	No	Yes	Yes
On-premises search index	Yes	Yes	Yes
Phonetic name matching	Yes	Yes	Yes
Query rules—Add promoted results	No	Yes	Yes
Query rules—advanced actions	No	No	Yes
Query spelling correction	Yes	Yes	Yes
Query suggestions	No	Yes	Yes
Query throttling	No	Yes	Yes
Quick preview	Yes	Yes	Yes
Recommendations	No	Yes	Yes
Refiners	Yes	Yes	Yes
RESTful Query API/Query OM	Yes	Yes	Yes
Result sources	Yes	Yes	Yes
Search connector framework	No	Yes	Yes
Search results sorting	Yes	Yes	Yes
Search vertical: “Conversations”	No	Yes	Yes
Search vertical: “People”	No	Yes	Yes
Search vertical: “Video”	No	No	Yes
Tunable Relevancy	No	No	Yes

IT Professional features - Sharepoint 2013

2016-04-19T10:59:00.000+05:30

IT Professional features	Foundation 2013	Server 2013—Std	Server 2013—Enterprise
Active Directory Synchronization	Yes	Yes	Yes
Alternate Access Mapping (AAM)	Yes	Yes	Yes
Analytics Platform	No	No	Yes
Claims-Based Authentication Support	Yes	Yes	Yes
Configuration Wizards	No	Yes	Yes
Deferred Site Collection upgrade	Yes	Yes	Yes
Distributed Cache	Yes	Yes	Yes
Host Header Site Collections	Yes	Yes	Yes
Improved Permissions Management	Yes	Yes	Yes
Improved Self-Service Site Creation	No	No	Yes
Managed Accounts	Yes	Yes	Yes
Minimal Download Strategy (MDS)	Yes	Yes	Yes
OAuth	No	Yes	Yes
Patch Management	Yes	Yes	Yes
Quota Templates	Yes	Yes	Yes
Read-Only Database Support	Yes	Yes	Yes
Remote Blob Storage	Yes	Yes	Yes
Request Management	Yes	Yes	Yes
Request throttling	Yes	Yes	Yes
Resource throttling	Yes	Yes	Yes
Service Application Platform	Yes	Yes	Yes
SharePoint Health Analyzer	Yes	Yes	Yes
SharePoint Online Admin Center	N/A (SharePoint Online only)	N/A (SharePoint Online only)	N/A (SharePoint Online only)
Shredded Storage	Yes	Yes	Yes
Site Collection Compliance Policies	No	Yes	Yes
Site Collection Health Checks	Yes	Yes	Yes
State Service	Yes	Yes	Yes
Streamlined Central Administration	Yes	Yes	Yes
System Status Notifications	Yes	Yes	Yes
Unattached Content Database Recovery	Yes	Yes	Yes
Upgrade evaluation site collections	Yes	Yes	Yes
Usage Reporting and Logging	Yes	Yes	Yes
Windows PowerShell Support	Yes	Yes	Yes

Developer Features of SP 2013

2016-04-19T10:55:00.000+05:30

Developer features	Foundation 2013	Server 2013- Std	Server 2013—Enterprise
Access Services	No	No	Yes
App Catalog (SharePoint)	No	Yes	Yes
App Deployment: Autohosted Apps	No	No	No
App Deployment: Cloud-Hosted Apps	No	Yes	Yes
App Deployment: SharePoint-Hosted Apps	No	Yes	Yes
App Management Services	No	Yes	Yes
BCS: Alerts for External Lists	No	Yes	Yes
BCS: App Scoped External Content Types (ECTs)	No	Yes	Yes
BCS: Business Data Webparts	No	Yes	Yes
BCS: External List	Yes	Yes	Yes
BCS: OData connector	No	Yes	Yes
BCS: Profile Pages	No	Yes	Yes
BCS: Rich Client Integration	No	No	Yes
BCS: Secure Store Service	Yes	Yes	Yes
BCS: Tenant-level external data log	No	No	Yes
Browser-based customizations	Yes	Yes	Yes
Client Object Model (OM)	Yes	Yes	Yes
Client-side rendering (CSR)	Yes	Yes	Yes
Custom Site Definitions	No	Yes	Yes
Custom Site Provisioning	No	No	Yes
Developer Site	No	No	No
Forms Based Applications	No	Yes	Yes
Forms on Spreadsheets	No	Yes	Yes
Full-Trust Solutions	Yes	Yes	Yes
InfoPath Forms Services	No	No	Yes
JavaScript Object Model	Yes	Yes	Yes
List and Library APIs	Yes	Yes	Yes
Remote Event Receiver	Yes	Yes	Yes
REST API	Yes	Yes	Yes
Sandboxed Solutions	Yes	Yes	Yes
SharePoint Design Manager	No	Yes	Yes
SharePoint Designer	Yes	Yes	Yes
SharePoint Store	Yes	Yes	Yes
Workflow 2010 (.NET 3.5)	Yes	Yes	Yes
Workflow 2010 (out of the box)	No	Yes	Yes
Workflow 2013	No	Yes	Yes
Workload API: ECM APIs	No	Yes	Yes
Workload API: Search APIs	Yes	Yes	Yes
Workload API: Social APIs	No	Yes	Yes

Features of NLB

2016-04-19T10:40:00.004+05:30

Features in Network Load Balancing

NLB includes the following features:

Scalability

Scalability is the measure of how well a computer, service, or application can grow to meet increasing performance demands. For NLB clusters, scalability is the ability to incrementally add one or more systems to an existing cluster when the overall load of the cluster exceeds its capabilities. To support scalability,

NLB can do the following:

Balance load requests across the NLB cluster for individual TCP/IP services.

Support up to 32 computers in a single cluster.

Balance multiple server load requests (from either the same client or from several clients) across multiple hosts in the cluster.

Support the ability to add hosts to the NLB cluster as the load goes up, without bringing the cluster down.

Support the ability to remove hosts from the cluster when the load goes down.

Enable high performance and low overhead through fully pipelined implementation. Pipelining allows requests to be sent to the NLB cluster without waiting for response to the previously sent one.

High-availability :

A highly available system reliably provides an acceptable level of service with minimal downtime. To provide high availability, NLB includes built-in features that can automatically:
Detect and recover from a cluster host that fails or goes offline.

Balance the network load when hosts are added or removed.

Recover and redistribute the workload within ten seconds.

Manageability :

NLB provides the following manageability features:
You can manage and configure multiple NLB clusters and the cluster hosts from a single computer by using NLB Manager.

You can specify the load balancing behavior for a single IP port or group of ports by using port management rules.

You can define different port rules for each Web site. If you use the same set of load-balanced servers for multiple applications or Web sites, port rules are based on the destination virtual IP address (using virtual clusters).

You can direct all client requests to a single host by using optional, single-host rules. NLB routes client requests to a particular host that is running specific applications.

You can block undesired network access to certain IP ports.

You can enable Internet Group Management Protocol (IGMP) support on the cluster hosts to control switch flooding (when operating in multicast mode).

You can remotely start, stop, and control NLB actions from any networked computer that is running Windows by using shell commands or scripts.

You can view the Windows event log to check NLB events. NLB logs all actions and cluster changes in the event log.

Ease-of-use

NLB provides many features that make it convenient to use:

NLB is installed as a standard Windows networking driver component.

NLB requires no hardware changes to enable and run.

NLB Manager enables you to create new NLB clusters.

NLB Manager enables you to configure and manage multiple clusters and all of the cluster's hosts from a single remote or local computer.

NLB lets clients access the cluster by using a single, logical Internet name and virtual IP address—known as the cluster IP address (it retains individual names for each computer). NLB allows multiple virtual IP addresses for multihomed servers.

Note
In the case of virtual clusters, the servers do not need to be multihomed to have multiple virtual IP addresses.
NLB can be bound to multiple network adapters, which allows you to configure multiple independent clusters on each host. Support for multiple network adapters differs from virtual clusters in that virtual clusters allow you to configure multiple clusters on a single network adapter.

You do not have to modify server applications to run in an NLB cluster.

If a cluster host fails and then is subsequently brought back online, NLB can be configured to automatically add that host to the cluster. The added host will then be able to start handling new server requests from clients.

You can take computers offline for preventive maintenance without disturbing cluster operations on the other hosts.

What is Network Load Balancing ?

2016-04-19T10:37:00.000+05:30

The Network Load Balancing (NLB) feature in Windows Server 2008 R2 enhances the availability and scalability of Internet server applications such as those used on Web, FTP, firewall, proxy, virtual private network (VPN), and other mission-critical servers. A single computer running Windows Server 2008 R2 provides a limited level of server reliability and scalable performance. However, by combining the resources of two or more computers running one of the products in Windows Server 2008 R2 into a single virtual cluster, NLB can deliver the reliability and performance that Web servers and other mission-critical servers need.

The diagram above depicts two connected Network Load Balancing clusters. The first cluster consists of two hosts and the second cluster consists of four hosts. This is one example of how you can use NLB.

Each host runs a separate copy of the desired server applications (such as applications for Web, FTP, and Telnet servers). NLB distributes incoming client requests across the hosts in the cluster. The load weight to be handled by each host can be configured as necessary. You can also add hosts dynamically to the cluster to handle increased load. In addition, NLB can direct all traffic to a designated single host, which is called the default host.

NLB allows all of the computers in the cluster to be addressed by the same set of cluster IP addresses, and it maintains a set of unique, dedicated IP addresses for each host. For load-balanced applications, when a host fails or goes offline, the load is automatically redistributed among the computers that are still operating. When a computer fails or goes offline unexpectedly, active connections to the failed or offline server are lost. However, if you bring a host down intentionally, you can use the drainstop command to service all active connections prior to bringing the computer offline. In any case, when it is ready, the offline computer can transparently rejoin the cluster and regain its share of the workload, which allows the other computers in the cluster to handle less traffic.

The hosts in an NLB cluster exchange heartbeat messages to maintain consistent data about the cluster’s membership. By default, when a host fails to send heartbeat messages within five seconds, it has failed. When a host has failed, the remaining hosts in the cluster converge and do the following:

Establish which hosts are still active members of the cluster.
Elect the host with the highest priority as the new default host.
Ensure that all new client requests are handled by the surviving hosts.

During a convergence, the surviving hosts look for consistent heartbeats. If the host that failed to send heartbeats begins to provides heartbeats consistently, it rejoins the cluster in the course of the convergence. When a new host attempts to join the cluster, it sends heartbeat messages that also trigger a convergence. After all cluster hosts agree on the current cluster membership, the client load is redistributed to the remaining hosts, and the convergence completes.

Convergence generally takes only a few seconds, so interruption in client service by the cluster is minimal. During convergence, hosts that are still active continue handling client requests without affecting existing connections. Convergence ends when all hosts report a consistent view of the cluster membership and distribution map for several heartbeat periods.

Upload multiple photos is missing - SharePoint 2010

2016-04-19T10:33:00.000+05:30

Situation : I Was not able to find a option to upload multiple photos and documents the option was missing in upload dialog box

Resolution:

Normally Upload Multiple Files is missing when you don't have any local Office clients installed.

You need to check on the below

1. The 32 bit version of Internet Explorer.
2. Office 2003 /Office 2007 / Office 2010 / Office 2013 or newer on the client
3. Client integration will need to be enabled for the web app.
4. The STSUpld.UploadCtl IE add-in must be enabled.

Note : Does not work with other browsers or 64 bit IE

There is an ActiveX control that is used to support multiple file uploading - that ActiveX control is installed with office.

Once you install any of the client (i.e. any office version ) then your issue will be resolved.

Sharepoint 2013 Latest Updates

2016-03-29T19:17:00.001+05:30

SharePoint 2013

Build Number	Build Name	Component	Information Link
15.0.4128.1014	Beta	SharePoint Foundation 2013
15.0.4128.1014	Beta	SharePoint Server 2013
15.0.4128.1014	Beta	Project Server 2013

15.0.4420.1017	RTM	SharePoint Foundation 2013
15.0.4420.1017	RTM	SharePoint Server 2013
15.0.4420.1017	RTM	Project Server 2013

15.0.4433.1506	December 2012 Hotfix	SharePoint Server 2013	KB2752058
15.0.4433.1506	December 2012 Hotfix	SharePoint Server 2013 (coreserver)	KB2752001

15.0.4481.1005	March 2013 Public Update	SharePoint Foundation 2013	KB2768000
15.0.4481.1005	March 2013 Public Update	SharePoint Server 2013	KB2767999
15.0.4481.1005	March 2013 Public Update	Project Server 2013	KB2768001

15.0.4505.1002	April 2013 CU	SharePoint Foundation 2013	KB2751999
15.0.4505.1005	April 2013 CU	SharePoint Server 2013	KB2726992
15.0.4505.1005	April 2013 CU	Project Server 2013	KB775426

15.0.4517.1003	June 2013 CU	SharePoint Foundation 2013	KB2817346
15.0.4517.1005	June 2013 CU	SharePoint Server 2013	KB2817414
	June 2013 CU	Project Server 2013	KB2817415

15.0.4535.1000	August 2013 CU	SharePoint Foundation 2013	KB2817517
	August 2013 CU	SharePoint Server 2013	KB2817616
	August 2013 CU	Project Server 2013	KB2817615

15.0.4551.1001	October 2013 CU	SharePoint Foundation 2013	KB2825674
15.0.4551.1005	October 2013 CU	SharePoint Server 2013	KB2825647
	October 2013 CU	Project Server 2013

15.0.4551.1508	December 2013 CU	SharePoint Foundation 2013	KB2849961
15.0.4551.1511		SharePoint Server 2013	KB2850024
15.0.4551.1508		Project Server 2013	KB2837668

15.0.4569.1000*	Service Pack 1	SharePoint Foundation 2013	KB2817439
		SharePoint Server 2013	KB2817429
		Project Server 2013	KB2817434

15.0.4571.1502*	Service Pack 1 Mark 2	SharePoint Foundation 2013	KB2880551
		SharePoint Server 2013	KB2880552
		Project Server 2013	KB2880553

15.0.4605.1000	April 2014 CU	SharePoint Foundation 2013	KB2863892
		SharePoint Server 2013	KB2878240
		Project Server 2013	KB2880484

15.0.4615.1001	MS14-022	SharePoint Foundation 2013	KB2952166
		SharePoint Server 2013	KB2952166
		Project Server 2013	KB2952166

15.0.4617.1000	June 2014 CU	SharePoint Foundation 2013	KB2881063
		SharePoint Server 2013	KB2881061
		Project Server 2013	KB2881062

15.0.4631.1001	July 2014 CU	SharePoint Foundation 2013	KB2882999
		SharePoint Server 2013	KB2882989
		Project Server 2013	KB2882990

15.0.4641.1001	August 2014 CU	SharePoint Foundation 2013	KB2883081
		SharePoint Server 2013 (1/5)	KB2760213
		SharePoint Server 2013 (2/5)	KB2880559
		SharePoint Server 2013 (3/5)	KB2883078
		SharePoint Server 2013 (4/5)	KB2883085
		SharePoint Server 2013 (5/5)	KB2883086
		Project Server 2013	KB2883083

15.0.4649.1001	September 2014 CU	SharePoint Foundation 2013	KB2883087
		SharePoint Server 2013	KB2883068
		Project Server 2013	KB2883072

15.0.4659.1001	October 2014 CU	SharePoint Foundation 2013	KB2889946
		SharePoint Server 2013 (1/3)	KB2899469
		SharePoint Server 2013 (2/3)	KB2880962
		SharePoint Server 2013 (3/3)	KB2880485
		Documentum Connector	KB2752098
		Project Server 2013	KB2889959

15.0.4667.1000	November 2014 CU	SharePoint Foundation 2013	KB2899468
		SharePoint Server 2013	KB2889944
		Project Server 2013	KB2889949

15.0.4675.1000	December 2014 CU	SharePoint Foundation 2013	KB2910945
		SharePoint Server 2013	KB2910938
		Project Server 2013	KB2910911

15.0.4693.1001	February 2015 CU	SharePoint Foundation 2013	KB2920801
		SharePoint Server 2013	KB2920804
		Project Server 2013	KB2920796

15.0.4701.1001	March 2015 CU	SharePoint Foundation 2013	KB2956159
		SharePoint Server 2013	KB2956166
		Project Server 2013	KB2956162

15.0.4711.1000	April 2015 CU	SharePoint Foundation 2013	KB2965261
		SharePoint Server 2013	KB2965266
		Project Server 2013	KB2965263

15.0.4719.1002	May 2015 CU	SharePoint Foundation 2013	KB3039747
		SharePoint Server 2013	KB3039780
		Project Server 2013	KB3039753

15.0.4727.1001	June 2015 CU	SharePoint Foundation 2013	KB3054864
		SharePoint Server 2013	KB3054866
		Project Server 2013	KB3054865

15.0.4737.1001	July 2015 CU	SharePoint Foundation 2013	KB3054931
		SharePoint Server 2013	KB3054937
		Project Server 2013	KB3054933

15.0.4745.1001	August 2015 CU	SharePoint Foundation 2013	KB3055004
		SharePoint Server 2013	KB3055009
		Project Server 2013	KB3055005

15.0.4753.1000	September 2015 CU	SharePoint Foundation 2013	KB2975894
		SharePoint Server 2013	KB2986213
		Project Server 2013	KB2986195

15.0.4763.1000	October 2015 CU	SharePoint Foundation 2013	KB3085488
		SharePoint Server 2013	KB3085492
		Project Server 2013	KB3085489

15.0.4771.1000	November 2015 CU	SharePoint Foundation 2013	KB3101368
		SharePoint Server 2013	KB3101373
		Project Server 2013	KB3101369

15.0.4779.1000	December 2015 CU	SharePoint Foundation 2013	KB3114339
		SharePoint Server 2013	KB3114345
		Project Server 2013	KB3114341

15.0.4787.1000	January 2016 CU	SharePoint Foundation 2013	KB3114492
		SharePoint Server 2013	KB3114497
		Project Server 2013	KB3114493

15.0.4797.1000	February 2016 CU	SharePoint Foundation 2013	KB3114722
		SharePoint Server 2013	KB3114726
		Project Server 2013	KB3114723

15.0.4805.1000	March 2016 CU	SharePoint Foundation 2013	KB3114822
		SharePoint Server 2013	KB3114827
		Project Server 2013	KB3114823

Workflow History Purge After 60 days

2014-02-28T02:07:00.000+05:30

Hi Readers ,

Today i came across a department in the organisation which wants all the old workflow history for Audit purpose .

By default the workflow history gets purged after 60 days . For the same there is a Timer job which runs .

You could also disable the automatic cleanup of workflow history by the following steps:

1. From Central Administration, click the Operations tab on the top navigation bar.

2. On the Operations page, in the Global Configuration section, click Timer job definitions.

3. On the Timer Job Definitions page, click Workflow Auto Cleanup to edit the appropriate timer job.

4. On the Edit Timer Job page, click Disable and then click OK to disable the Workflow Auto Cleanup feature.

Reference :
Disable automatic cleanup of workflow history (SharePoint Server 2007)

Disable preservation of workflow history (SharePoint Server 2010)

check this too

Huge MOSS Workflow Issue… What is Microsoft Thinking!!!!

Slipstream version of SharePoint 2010 Foundation with SP2 included

2013-12-14T07:52:00.000+05:30

SharePoint Foundation 2010 is the new version of Microsoft Windows SharePoint Services. It is the essential solution for organizations that need a secure, manageable, web-based collaboration platform. SharePoint helps teams stay connected and productive by providing easy access to the people, documents, and information that they need to make well-informed decisions and get work done. Use SharePoint Foundation to coordinate schedules, organize documents, and participate in discussions through team workspaces, blogs, wikis, and document libraries on the platform that is the underlying infrastructure for SharePoint Server.

Search Server 2010 Express: If you’re using SharePoint Foundation, you can easily add search capabilities to your collaboration environment across SharePoint sites, file shares, web sites, Exchange Public Folders, and third party repositories using Microsoft Search Server 2010 Express.

Sharepoint 2010 with SP2 Click here to download

December 2013 CU for SharePoint 2010 has been released

2013-12-14T07:36:00.000+05:30

The product group released the December 2013 Cumulative Update for the SharePoint 2010 product family.
Be aware that the December Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix. It is recommended to have SP2 installed before installing the December CU.
The KB articles for December CU are available at the following locations:

KB 2849990 - SharePoint Foundation 2010
KB 2849971 - SharePoint Server 2010
KB 2849972 - SharePoint Server 2010 with Project Server
As you see there is a separate Full Server Package for SharePoint Server 2010 with Project Server which simplifies patching of this common installation.

The Full Server Packages for December 2013 CU are available through the following links:

Download SharePoint Foundation 2010 December 2013 CU
Download SharePoint Server 2010 December 2013 CU
Download SharePoint Server 2010 with Project Server December 2013 CU
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU. And the SharePoint Server 2010 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.

Thanks Stefan for Sharing this Information

Spell Check is not working in SharePoint 2010

2013-12-06T10:43:00.003+05:30

Issue : Recently I got to know issue from my customer mentioning that spell check is not working on SharePoint 2010 site while editing the item in any lists and was giving around 105 errors when there was no spelling errors.

Resolution : Analyzed the whole list item edit form and found that one column which was People picker was giving spelling errors against it.
Clicked on the spelling errors found that Spell checker does its spell check against the query written to resolve the name from Active Directory which was resulting in 105 errors being displayed.
So in all we can say that this bug in SharePoint 2010 hopefully will be corrected in future versions.

Please let me know if you have any questions or need more information.

Your feedback is welcome :)

October 2013 CU for SharePoint 2010 has been released

2013-10-11T07:29:00.001+05:30

The product group released the October 2013 Cumulative Update for the SharePoint 2010 product family.

Be aware that the October Cumulative Update for SharePoint 2010 is a Post-SP1 hotfix. That means that you should ensure that SP1 is installed before the October CU.

The KB articles for October CU are availabe at the following locations:

KB 2825824 - SharePoint Foundation 2010

KB 2825786 - SharePoint Server 2010

KB 2825793 - SharePoint Server 2010 with Project Server

As you see there is a separate Full Server Package for SharePoint Server 2010 with Project Server which simplifies patching of this common installation.

Download SharePoint Foundation 2010 October 2013 CU

Download SharePoint Server 2010 October 2013 CU

Download SharePoint Server 2010 with Project Server October 2013 CU

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

That means only one package has to be installed for the SharePoint 2010 product family.

The Full Server Packages for October 2013 CU are available through the following links:

http://blogs.technet.com/b/stefan_gossner/archive/2013/10/09/october-2013-cu-for-sharepoint-2010-has-been-released.aspx