Understanding Feeds In SharePoint 2013

With the use of site feeds, you have the function to offer newsfeed to specific users of a group. They are available for team sites as well. In your planning for site feeds, the web application that contains them must exist in the same server farm as the web application that is host of My Site Host site collection.

With SharePoint Server 2013, it is recommended that the same service account issued for My Site Host Web Application and the web application for hosting those team sites. My Site Host Site Collection also has to be a SharePoint Server 2013 My Site Host. The user must have a SharePoint Server 2013 My Site in order to use the site feed feature.

It is recommended to enable Self Service Site Creation on the web application that hosts the team sites. This allows the users an easy way to create team sites from My Site. With SharePoint Server 2013, the About Me pages don’t have My Sites. However, the site feeds are still accessible to the users.

Should an administrator upgrade team sites from SharePoint Server 2010, they have to activate the site feeds on the upgraded team site first. This is done by enabling Following Content then enabling Site Feeds on the team site.

Should users begin to follow the site before they have been enabled in Site Feeds, then the upgrade team won’t appear in the Share With menu. The user needs to stop following the site, allow the upgrade to be done, and then follow the site again so that it will appear in the Share With menu.

It is possible for a user to include images in microblog postings. When there is such an image in the post, SharePoint Server 2013 will upload that image to a folder that is private on the My Site of that user. The image will be reduced in file size automatically to dimensions that optimize the space that remains available.

Assigning quota limits for My Sites allows the administration to plan for additional storage of those images. If a user doesn’t have any remaining storage on their My Site, they won’t be able to post a message that includes an image. Instead, they will get an error message.


It is possible for the system to generate email messages that notify the user of various activities. This can be when they have contributed to a thread or even when someone new is following them. These notifications are set by configuring the outgoing email settings in SharePoint Server 2013.


The newsfeeds from SharePoint Server 2010 have to be upgraded if they are going to be used in SharePoint Server 2013 . Administration has to perform various steps to configure this access and upgrade to occur.

With the use of Outlook Social Connector, the feed can be displayed with information about meetings, messages, and more. This increases the load for the server farm with SharePoint Server 2013. It is the result of Outlook Social Connector accessing My Site features and pushing that information into Outlook. The overall performance of the SharePoint Server 2013  farm has to be considered.

Public conversations including posts and replies are part of the Everyone and Newsfeed options. All users are able to access them. These public elements are added to the search index offered by SharePoint Server 2013. It allows users to look for and view results of such public information.

There aren’t any permissions assigned to these conversations. Any users that require trimming for specific conversations must have that configured by administration. With a team site, the assigned permissions for the group of users in the conversation have to be allocated. Then what is trimmed will be determined based on those assigned permissions.

That should be taken into consideration when you configure the crawl schedule for indexing. It will also affect how fast the conversations are going to appear in those search results for users. You want the use of the microblog to be effective in regards to the posts and replies so they should be able to see those search results as quickly as possible. This is why you want to set up short intervals for those updates to occur.


SharePoint Security And Authentication Part 4 Choosing The Right Authentication Strategy

When Designing authentications strategies for SharePoint 2010, there are guidelines to be aware of with the process for authentication with SharePoint Server 2010. So let's just get down to it. The authentication process is configured through the web application. A server farm may be configured to host sites for many organizations. However, the authentication is configured on an individual level for each of the organizations. It is possible for web applications in SharePoint Server 2010 to be configured with up to five different methods being used. Authentication for internal employees can be completed through one of the standard Windows methods. When a partner organization is involved, their employees can be authenticated with the identity management system that is in place for that particular organization. In order to be able to configure a web application so that it can be accessed by at least two systems of authentication, the additional zones must be configured in the web application. Each of the zones is a representation of a different path for accessing the same application. Typically when there is a partner application, the employees of a partner company are going to gain access to the application through the internet. Internal employees will be able to do so through intranet.  The zone type is a category for naming purposes but it won’t affect the overall configuration of a zone. Once you have successfully extended the web application, you can move on to configuring a new method of authentication for that zone. The default zone that will be in place should only be used by the internal employees. Partner access can be used by configuring the internet zone for forms based authentication.

If you are planning to implement more than one method of authentication for a web application, you will need to plan how to create those zones. There is some best practices to follow. The default zone can be use to implement secure settings for authentication. If a request isn’t able to be associated with a given zone then the settings and security policies of the default zone will apply. The default zone is one that is going to be created when you first initialized the web application. The secure authentication settings are to be used by end user access. Therefore, end users are the most likely to be the ones accessing the default zone. Use the least number of zones that are required by any given applications. Each of the zones will be associated with a new IIS site and domain. They will be used when a user is accessing that web application. You should only add new points of access when they are required. In order for content from the web application to be included in search results you need to make sure there is at least one zone configured with NTLM authentication. This requirement is going to result in the crawl content being indexed. Only create a dedicated zone for that indexing if it is necessary.

There are some methods of authentication that you need to consider when you are planning which of them you will use. Ensure that the methods of authentication are compatible with the browsers that your users will be accessing, understand the methods use for your user accounts to be managed, understand how credentials of users and identity are cached in SharePoint Server 2010, evaluate the pros and cons of each method of authentication available, and evaluate the security of the web applications to be used in SharePoint Server 2010.

Security should be a huge factor that you consider when you are looking at authentication methods for your applications. There are some common security environments for you to evaluate. External anonymous implementations allow for some access without authentication occurring. However, the permission is a read only basis. There isn’t the ability to modify. Authentication can be used to allow access to specific materials. External secure collaboration requires configuring a separate zone for each partner organization that will be connecting to the site. Once a user is no longer employed they won’t be able to continue accessing the application. Intranet implementations are used to protect the credentials of users from being in plain sight.

There are some significant advantages to using certain authentication methods. However, there are also some tradeoffs that occur as well. Exploring both sides of this issue will help you to determine which ones are best for your organization. The advantages of claims include the implementation being a collection of materials for the security token to determine if the user has permission to access a network. These types of materials can include a user name, password, role, or employee ID. All of which can determine the authorization as well as the level of permission.

The tradeoff is that the configuration to manage it all takes a great deal of planning and training. It can be a complex process that a person needs time to fully understand. Windows allows for the authentication of existing Active Directory Accounts to be used. This makes managing any given user simple to take care of. There is no need to write custom code either. Active Directory groups can be beneficial when you complete the configuration in SharePoint Server 2010. The trade off is that not all of the IIS authentication protocols offered are supported by the various web browsers. Therefore you will have to make sure those browsers users are going to use are going to be compatible with it. With forms based authentication, the environment doesn’t use AD DS or Windows accounts. It is possible to have more than one authentication method in place that can help with Identity Management Systems for partner applications to be completed. Authentication users come from the internet. It is possible to customize the authentication process to based on specific criteria. The trade off is that this also requires the web.config file to be customized. It can also be risky if the SSL is in place for an additional layer of security.


Implementing List Governance With Performance Consideration In SharePoint 2010 – Part 2

Managed Metadata – With Managed metadata you will have a new set of features that add information to the architecture of the SharePoint Server. The managed metadata will offer a shared service known as the managed metadata service. This can be used for storing term sets and it can also be used to deploy the SharePoint environment. Elements of this feature include terms that can support both deep and flat hierarchies, managing metadata column type, and term sets that are open or restricted.

The use of managed metadata columns and terms that are set for organizing content allow you to use the features of content querying. Both metadata and the Content Query Web Part navigation help a user to find content. With managed metadata there is also the regular search queries available. This allows for keywords to be added to classified documents. It also allows for managed metadata to be used in the search panel.

Limits and Throttles – Through SharePoint Server 2010 there are various limits that can be configured for farm performance to be maintained. The Web application level is configured with limits and throttles. They were added to offer more operations for individual users or processes. However, they don’t affect the overall farm performance. The list view threshold is a limit that stops queries from affecting a given number of list items.

Compound Index – One of the important elements of large lists is the use of indexes. With SharePoint Server you will be able to create a compound index. These are useful for queries that will be performed on two columns versus just one. When you only have one, it may not be selective enough. A compound index allows for utilization of various views but they can still be accessed with metadata navigation. A throttle condition will occur when they metadata attempts to retry and then indexing is based on the various filters that apply.

Developer Dashboard – With the developer dashboard display there is a diagnostic detail for each page that loads. The default can be left on if you like. The developer will allow you to get information about load times, errors, and database queries. The metadata navigation is visible in the developer dashboard.

This means that large lists and throttle conditions are for the list of indexes. They are used to retry and for partial results that can appear in the operation tree. This is on the left side. The SQL Server queries are found on the right side. The developer dashboard allows for debugging the custom Web Parts and queries.

Content Iterator – The content Iterator is developed for API and it simplifies the writing code for large lists. This is important when there is a new list view limit. The content iterator offers a way for retrieving content and performing operations on small sets. This is different than performing operations on the entire set as before. The result is that you don’t have to worry about exceeding the threshold for a give list view.

Remote BLOB Storage – The SharePoint default results in files stored as Binary Large Objects (BLOB). This is in the SQL Server database. There is a large amount of content found in the database. BLOB storage also allows for more to be stored outside of the SQL Server. This allows for less cost to be involved with storing the options. At the same time this reduces the content database size. Remote BLOB storage is a library API set for the add on pack with the SQL Server 2008. There can be a 3rd party remote BLOB storage provider required for the remote BLOB storage API.