Yammer Redirection in SharePoint Server 2013 Service Pack 1

In previous articles I discussed redirecting OneDrive for Business to Office 365 in SharePoint Server 2013 Service Pack 1.  In addition to new functionality that allows IT administrators to redirect OneDrive for Business and Sites pages to Office 365, Service Pack 1 also allows IT administrators to activate Yammer as the default social experience for SharePoint Server 2013.

When activated, the Newsfeed link in the navigation bar is replaced with a Yammer link that directs users to the organizations’ Yammer network. 

Yammer Configuration page in Central Admin

While a simplified Activate/Deactivate configuration is provided in Service Pack 1, proper identity management planning is required to deliver a consistent and integrated user experience.

For organizations with an established Active Directory and identity management infrastructure and practices

Directory Synchronization with Office 365 is a distinct configuration that provides an integrated identity solution for applications within the Office 365 suite with the exception of Yammer.  Integrated identity with Yammer requires a separate implementation of a directory synchronization solution provided by Yammer, Yammer Directory Sync (DSync).

Similar to Directory Synchronization, Yammer Directory Sync (DSync) is a Windows application that automates user provisioning in your Yammer network by querying your Active Directory (AD) host(s).


Sites Page

The Sites page introduced in SharePoint Server 2013 is designed to provide users a unified location to create new sites and view sites they are following.

Managing Sites Page Redirection

Service Pack 1 also includes within OneDrive for Business redirection the option to redirect users Sites page to Office 365.

Example 1 C#

        static void Main(string[] args)
                SPWebApplication webApp = SPWebApplication.Lookup(new Uri("http://sharepoint.spc.com.co"));
                foreach (SPSite site in webApp.Sites)
                    foreach (SPWeb web in site.AllWebs)
                        if (web.Features != null)
                            web.Features.Remove(new Guid("{043C4BDD-9745-441a-A9A7-0BCD9B910319}"));

Example 1 Windows PowerShell

This example can be used to deactivate a specific Feature across all sites within the specified Web application.

$webApp = Get-SPWebApplication -Identity http://sharepoint.contoso.com

$webApp | Get-SPSite -limit all | ForEach-Object {Disable-SPFeature -Identity “FeatureName” -Url $_.Url}

The Uninstall-SPFeature cmdlet removes the specified feature definition from the collection of feature definitions in the farm.

Uninstall-SPFeature –Identity

Other Social Capability Considerations

In addition to addressing scenarios such as Following Content you should also consider the management of other SharePoint Server 2013 social capabilities such as:

  • Removing the SharePoint Server social web parts from My Sites and Team Sites.
  • Hiding user interface controls that provide social functionality.

For additional information on replacing the social features in SharePoint Server 2013 with equivalent Yammer features in a SharePoint Server 2013 on-premises deployment see also http://technet.microsoft.com/en-us/library/dn270535(v=office.15).aspx.


Add Yammer to the navigation bar for SharePoint 2013 [http://technet.microsoft.com/en-us/library/dn627521(v=office.15).aspx]

Service Pack for SharePoint Server 2013 1 Recalled [Updated]

Service Pack 1 update is now available.  Refer to the information below to acquire the updated Service Pack for your product:

NOTE For a list of previously published KB’s refer to the recall information in the original post below.



SharePoint Foundation


SharePoint Server


Project Server


SharePoint Server Language Pack


SharePoint Foundation Language Pack


Office Web Apps Server


Customers with Service Pack 1 Deployed

For customers who have previously deployed Service Pack 1, download the updated Service Pack 1 and install over the existing Service Pack 1 running PSConfig or PSConfigUI immediately following.

Customers without Service Pack 1

For customers without Service Pack 1 deployed, download the updated Service Pack 1 package and deploy as per the KB documentation.


There is no update to the integrated ISO on MSDN as it was not affected by the issue.

A potential issue with the following Service Pack 1 packages may prevent customers with Service Pack 1 from deploying future Public and/or Cumulative Updates.  As a precautionary measure we have deactivated the download page until a new package is published.



SharePoint Foundation


SharePoint Server


Project Server


SharePoint Server Language Pack


SharePoint Foundation Language Pack


Office Web Apps Server


Customers with Service Pack 1 Deployed

For customers who have deployed Service Pack 1 there is no action; however, an update will be released to resolve a potential issue when deploying subsequent Public and Cumulative updates.

Customers with Service Pack 1 Downloaded

For customers who have downloaded Service Pack 1, but have not deployed Service Pack 1, we recommend you postpone deployment until an updated package is delivered (date is TBD).


The integrated ISO with SP1 on MSDN is not affected by this issue.  Service Pack 1 on MSDN is a full build release.

What’s new in the User Profile Service Application

The User Profile Service Application stores information about users in a centralized location used by SharePoint’s social computing features to support natural collaboration.  The User Profile Service Application is also required when provisioning My Site personal sites, enabling certain social computing features such as newsfeeds, and the creation and distribution of user profiles across server farms or sites.

To learn more about the User Profile Service Application see also http://technet.microsoft.com/en-us/library/ee662538.aspx.

The User Profile Service Application is based on technologies provided through ForeFront Identity Manager which provides a comprehensive solution for identity and credential management and identity-based access policies.

To learn more about ForeFront Identity Manager see also http://www.microsoft.com/en-us/server-cloud/forefront/identity-manager.aspx.

Since RTM the User Profile Service Application has been incrementally improved through Cumulative Updates and Service Packs to improve both its performance and resiliency.  Recent improvements include:

  • Parallel SharePoint, Active Directory, and Business Connectivity Services import and export support
  • ForeFront Identity Manager performance improvements
  • Reduction of full table scans and indexing specific user properties
  • Batch import of Business Connectivity Services user properties
  • Removed automatic provisioning of users and groups to ILM MA
  • Programmatic cleanup of large run histories
  • Resolution of AD-Contact objects in ForeFront Identity Manager as opposed to SharePoint Server 2010

As a result of these improvements there has been a dramatic reduction of the time required to import user information into SharePoint.  For example, inside of Microsoft on the RTM version of SharePoint Server 2010 with 100,000 users our profile import duration for full synchronization commonly required 2 weeks to complete and 2-3 days to support an incremental synchronization.  This same scenario on SharePoint Server 2010 with the December 2011 Cumulative Update has been reduced to 120-140 for a full synchronization and 6 hours for an incremental synchronization.

If you’re experience delays in importing users and properties or are just looking to improve the security, reliability, and performance of your SharePoint 2010 environment we recommend installing the latest Cumulative Update or Service Pack.


Download SharePoint Server 2010 Service Pack 1
Download the SharePoint Server 2010 February 2012 Cumulative Update

Site Recycle Bin (Service Pack 1 and CodePlex) FAQs

Do I need to uninstall the Site Recycle Bin from CodePlex if I plan to use the Site Recycle Bin in Service Pack 1?

It depends on what you’re looking for.  The Site Recycle Bin available through CodePlex will capture deleted Site Collections and Sites to disk, Site Recycle Bin in Service Pack 1 copies the Site Collections and Sites to an auxiliary SQL table until they are permanently deleted at which point are managed by Gradual Site Deletion.  Once a Site Collection or site enters this Garbage Collection phase it will be managed by the Site Recycle Bin on CodePlex and copied to disk.  In theory you could have both.  The CodePlex Site Recycle Bin to provide archival and the Site Recycle Bin in Service Pack 1 to provide quick recovery and enable Site Collection administrators to perform self-service restores.

What happens to deleted Site Collections?  Do they ever get deleted?

These objects are purged.

There already is Web application property that controls the retention period for the Site Collection level Recycle Bin.  The same property is used for the deleted Site Collections themselves; when the Site Collection was deleted prior to a specified period (30 days), the timer job permanently removes it from the Content Database.  A Site Collection in the process of being permanently removed can no longer be restored.

Service Pack 1 Move-SPSite w/ ‘shallow copy’

Service Pack 1 introduces a new method of moving Site Collections between Content Databases where RBS is used known as ‘shallow copy’.


What is ‘shallow copy’?

‘Shallow copy’ refers to moving structured content without moving the underlying unstructured content.  With SharePoint 2010 Products ‘shallow copy’ moves the structured Site Collection data across Content Databases without moving the unstructured data which is comprised of user created content such as PowerPoint Presentations, Word Documents, etc.

What is a ‘shallow copy’ migration?

‘Shallow copy’ migration refers to a migration technique in which structured Site Collection data is moved across Content Databases while the unstructured BLOB data remains untouched in its originally configured BLOB store.

What is a deep copy migration?

Deep copy refers to a migration technique is which unstructured BLOB data is passed through the Object Model when its associated Site Collection is moved across Content Databases, I.e. download and upload of BLOB data.


‘Shallow copy’ capabilities provide a number of benefits, for example, shallow copy migration enables seamless movement of Site Collections across Content Databases while improving performance through enabling the unstructured data to remain in the originally configured BLOB store.  In scenarios where the same RBS provider is configured in both the source and destination Content Database the structured Site Collection data is moved without copying the underlying BLOB data – transferring only the ownership information between Content Databases.

In many SharePoint 2010 Products deployments unstructured BLOB data comprises 80% or more of the total content, ‘shallow copy’ helps administrators avoid deep copy migration significantly reducing the time required to move Site Collections between Content Databases.


The following prerequisites are required to implement ‘shallow copy’ migrations.

SQL Server 2008 R2 Public Cumulative Update
SharePoint Server 2010 Service Pack 1

Administrators can leverage ‘shallow copy’ functionality in Service Pack 1 through both the Object Model and Windows PowerShell using the Move-SPSite Windows PowerShell CmdLet with the -RbsProviderMapping parameter.  The -RbsProviderMapping parameter defines the mapping between the RBS providers in the source and destination Content Databases.

Move-SPSite -Identity siteUrl -DestinationDatabase databaseName -RbsProviderMapping
    @{"sourceProvider1"="targetProvider1", "sourceProvider2"="targetProvider2"}

When using the -RbsProvideMapping parameter the ownership of the RBS pool (subset of the BLOB store documents) used by the specified Site Collection is transferred from the source to the destination Content Database without moving the underlying unstructured data associated with that Site Collection.

‘Shallow copy’ is also an efficient migration method when moving from EBS to RBS.  In an EBS to RBS scenario the EBS token is moved from the source to the destination Content Database.

For additional information on Remote BLOB Store Architecture see http://msdn.microsoft.com/en-us/library/gg316769.aspx.

For additional information on the Move-SPSite CmdLet see http://technet.microsoft.com/en-us/library/ff607915.aspx.