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.


Exploding TFS Groups For User Investigation

When users are using Team Explorer and viewing the group membership for a particular project (Team Project Settings -> Group Membership) it’s pretty easy because explicit users and groups are listed. However, this becomes a problem when you want to view all the users of that particular group. This is very, very evident when the groups are chained, i.e. Group X contains Group Y, which contains Group z, and so forth. This becomes an issue because viewing the security information for a particular security group becomes very limited.

Fortunately, to get around this limitation you can use the TfsSecurity tool, specifically the TfsSecurity /imx command, to get the direct members of the specified group.

It is important to remember that TfsSecurity.exe comes from Team Explorer, not the Visual Studio shell.


TFS Proxy Server Unexpected Shutdowns

TFS Proxy Servers are essential for my current client’s TFSenvironment because they allow the disparate SharePoint development environment to experience improved network performance by caching copies of VC files. Since this particular environment is geo-distributed, this is a necessary architectural requirement in order to maintain appropriate developer efficiency.

Recently, a strange issue was occurring with my clients geo-environment where the proxy servers would start shutting down repetitively. The exact error you may run into is:

The VSTF Proxy Server stopped at [server]. The application is being shutdown for the following reason: HostingEnvironment. For more information …..”

Now this can happen for a variety of reasons, but first thing is you should enable proxy server tracing to get some more relevant error information by opening the web.config in the VersionControlProxy folder by setting the traceDirectoryName to a familiar storage location and changing traceWriter to true. For this particular error, one of the error returns can be:

Detailed Message: TF53002: Unable to obtain registration data for application VersionControl.
TF30055: Visual Studio could not find or read the Team Foundation Server server name in the configuration file. Contact your Team Foundation Server administrator. (type VstfNotConfiguredException)

If you get this error, the TfsNameUrl appsetting is not configured in the web.config file for the proxy server. Locate the:


element and change it. After, check your IIS app pool setting and check that the recycle interval or memory limit. After, you should be good to go!