Leaving a Yammer Network

I recently decided to leave my first Yammer network…I joined too many networks to keep up with so something had to give. It took me a while to find the “Leave Network” option so I figured I’d post it out there for you/me to reference in the future :) Pretty simple stuff, but I couldn’t find a blog or article that was high in Bing search results

  1. Click the Ellipses (. . .)
  2. Click Edit Profile
  3. Click Networks
  4. Click Leave Network
  5. Wave Goodbye




SharePoint 2013 SP1 – Windows Server 2012 R2 Prereq Install Error

So I got my hands on the SharePoint 2013 w/ SP1 ISO as well as a shiny new Windows Server 2012 R2 ISO and decided to give it a go! I installed Server 2012 R2 (Return of the shiny “start” button in the lower left), then installed SQL 2012 w/ SP1, and then moved on to SharePoint 2013 SP1. I fired up the splash screen and chose to install the Prerequisites…Good news is IIS installed/configured on the first attempt. In Server 2012 RTM there was a bug where sometimes IIS would fail to configure and you would have to install IIS manually and then let the prerequisite installer configure it appropriately. I DID get an install error though! This time the culprit is the Microsoft Information Protection and Control Client. I tried rebooting a few different times and could not get it to install so I decided to give an offline install a whirl.

You can download the install file for the Protections and Control Client here: http://go.microsoft.com/fwlink/p/?LinkID=219568

After downloading setup_msipc_x64.msi save it somewhere on the SharePoint server.

Then open CMD and type the following commands (If the CD drive is different than D change the directory to that drive letter):

After this you will be all set!


Also, my last post talked about installing SP1 after installing RTM + March 2013 PU…I did find one other difference with the ISO. The yellow bar at the top for Yammer/Office 365 is green if you install with the SP2013 SP1 Iso! Check it out:



SharePoint 2013 – Service Pack 1

SharePoint 2013 SP1 has been released! I’m a day late…so this isn’t exactly hot off the press


Check out the new addition to the Central Administration menu! SharePoint got Yammered..



Testing Notes: I setup a SharePoint 2013 Server (Windows Server 2012 RTM/SQL Server 2012 SP1) Farm to test out Service Pack 1 and what it brings to the table. This was a fresh installation – installed the Server OS > installed SQL 2012 > installed SP2013 RTM bits > upgraded to March 2013 PU bits > upgraded to SP1 bits > ran config wizard.

The Bad:

  1.  The Document Conversions Load Balancer Service appears to be in a state where it will NOT start: (NOTE: This also happened using a SP2013 SP1 ISO)ServicesOnServerErrorLB
    1. I am able to click the LB Service link, which brings me to the settings page
    2. LBSettings
    3. But when I click Start I get redirected to this error page:
    4. Error Starting Load Balancer
  2. Also, apparently Yammer and OneDrive for business are critical issues (You can just click the X to close)
  3. YammerO365CriticalError

The Good:

  1. When creating a new User Profile Service Application you are presented with the option to use Yammer for Social Collaboration!
  2. SP1UPSCreation
  3. This adds  the following entry to the navigation bar (Starting to look more and more like O365):
  4. SP1NavBarYammer
    1. Clicking Yammer Redirects to http://webappurl/_layouts/15/Yammer.aspx
    2. sp1clickyammer
    3. Clicking TAKE ME TO YAMMER redirects to https://www.yammer.com/?trk_event=sp_landing
  5. By clicking the Office 365 link on the left (Current) navigation in Central Administration you can configure Yammer (Which is just an activate/deactivate functionality for the link in the navigation bar..discussed above) and you can configure Office 365 settings for the OneDrive and Sites links in the top navigation bar.
  6. This is the screen you are presented with..pretty cool! I actually just worked on a project where we deployed an IIS HTTP Handler to rewrite URL’s to an Office 365 tenant…now this functionality is baked into SharePoint
  7. OneDriveConfigSP1
  8. I did some testing by typing in my trial Office 365 tenant so I could play around here.
  9. After clicking OK the change was nearly instant (I did need to clear browser cache in IE..but I tested in Firefox/Chrome right away which I wasn’t previously authenticated to the SharePoint site and the links were updated within a matter of seconds).
  10. Clicking  OneDrive and Sites Redirected Perfectly!
  11.   OneDriveO365Redirect
  12. For every good thing there is a bad thing though. The About Me link still redirects to the On Premise MySite Host…This is OK because most of the content here is directly synchronized from Active Directory, which makes the profile pages On Prem/Office 365 very similar (minus manually typed in information – Skills, About Me, Ask Me About, etc.). If the user had permissions within the UPS to create a personal site and has ALREADY done so..the links to that On Prem personal site collection will still show as links on the left-hand side. If you are looking for a truly hybrid environment there will need to be settings adjustments to lock down users being redirected to Office 365 (UPS Permissions settings, Decide if you want to use audiencing/targeting to send some user on prem/some users to Office 365, etc.
  13. Just note setting these features in Central Admin to redirect users to an Office 365 tenant will not change user permissions settings in the UPS (This is very similar to using Trusted MySite Locations pre-SP1…and then using audiencing to route specific users to the MySite Tenant. In the past you could point a MySite Location at an Office 365 tenant, but the About Me link would be broke (User Not Found) and when clicking on a people column containing that user it would give the same error (Because the URL structure after person.aspx is different for on premise and Office 365..Hence the need for a HTTP Handler or some other form of URL redirect). Otherwise you may end up managing personal site collections on prem, when these users actually have storage in Office 365.
  14. MyProfile

SharePoint Server Licensing – Failover Rights

I was working on a SharePoint installation where we would be using VMWare vCenter Site Recovery Manager to failover from the primary datacenter to a secondary datacenter for DR purposes. There would be identical infrastructure in the secondary datacenter, but it would be on standby. This got me thinking about licensing…I called Microsoft and they indicated that a SharePoint Server license by itself does NOT include failover rights and that you would need to purchase Software Assurance to be supported in this scenario. Good thing I called..


Fixing the Windows App Store after Windows 8.1 In-Place Upgrade

After an in-place upgrade of Windows 8.1 the app start would not start. It stayed on the loading screen for long periods of time and would never load. After some searching I found this article: http://blogs.msdn.com/b/notime/archive/2013/10/18/fix-store-app-in-windows-8-1.aspx

The fix for me was to open command prompt (CMD) as an admin and running the following command to re-register the Store App:

SharePoint 2013 – Search Service Application Not Provisioning Correctly After Server Rename

OK so here’s a fun one! I had a server that originally had SharePoint installed on it and the server was eventually renamed. After the rename I went and re-installed SharePoint because the new environment was to have a new name, use new service accounts, and have a different database naming scheme. After re-installing the SharePoint bits and running PSConfig almost everything was working correctly…Search on the other hand was not able to provision. I was getting the following error consistantly in the eventvwr application log:

The Execute method of job definition Microsoft.SharePoint.Administration.SPServiceInstanceJobDefinition (ID 7588c6ba-6e23-4712-aff4-8c1f53d2d4ec) threw an exception. More information is included below.

Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))

I checked folder and registry permissions and other than the fact that both the old service accounts and new service accounts were applied, everything seemed fine. I was not able to start the search service instance on this single server environment until I ran the following stsadm command:

SharePoint PowerShell Tip – Save a deployed farm solution

Ever deployed a SharePoint farm solution and then lose the WSP file? Good news – there is PowerShell to grab that WSP file and save it off somewhere for DR purposes.

Migrate lists/doc libraries/sites from WSS 3.0 to 2010 using stsadm

There may be certain scenarios where you need to migrate content from a WSS3.0 SharePoint farm to a 2010 or even a SharePoint 2013 farm. I’d almost always recommend using DB backup/restore or even utilizing the unattached database recovery option in Central Admin. The following post is for times when that is not an option. Times like require good ole stsadm. NOTE: This has a 2GB limit and has had mixed results in testing

1 – Export the list from WSS 3.0

Notation: This is done using Gary LaPointe’s custom sts commands, which is a more functional sts command index (See here for a list of all possible commands: http://blog.falchionconsulting.com/index.php/stsadmpowershell-commands/)

Run the following command on the WSS3.0 server:

Working example:

The number for versions can vary depending on the user needs:
1 – Last major version for files and list items
2 – The current version, either the last major or the last minor
3 – Last major and last minor version for files and list items
4 – All versions for files and list items (default)

2 – Modify files to make the backup SP 2010 compatible

  • Open the folder you backed up and open the following 2 files:
    • Manifest.xm
    • SystemData.xml
  • Open SystemData.xml this file with a text editor (Notepad ++ is preferred)
  • Change the Version from “” to “” (Or if this is 2013)
  • Change the build to be the same as the 2010/2013 SharePoint farm. This can be checked in Central Admin  > System Settings > Manage Servers in this farm
  • image
  • clip_image020
  • Open Manifest.xml with a text editor (Notepad ++ is preferred, but if the file is very large Notepad may be better as it won’t crash)
  • Run a find and replace all
    Find “” and replace it with “14.0.6117.5002” (This is Feb 2012 CU. Change to your build found above)


  • If there is an entry for ProductVersion change the value to 4 (2010)

3 – Repackage the file using makecab.exe

  • Open notepad and create a new text file. Include the following lines of text into this file:

This is the directive file that tells makecab what to compress into the cabinet file. This is all of the files in the folder you exported earlier. All of the XML files should be consistent for all exports, but the .dat files will change. These filenames can be copied easily by running the following command (after all filenames are copied, paste them below the XML files):

  • Open command prompt (CMD)
  • Navigate to the folder where all of the files exist and type:
    • Save this text file as makecab.ddf and copy it to the directory where all of the XML/DAT files exist
    • Open the command prompt and type the following command (First, navigate to the directory with all of the files in it using cd):
    • Makecab.exe /F makecab.ddf
    • You will now have a fileexport.cab file in the folder you exported earlier. Rename this file to whatever seems fit with the extension of .cmp. For example: WSSList.cmp

    4 – Import the list into SP 2010

    • Create the new site under the correct site collection, for STS Templates:
      • STS#0 = Teamsite
      • STS#1 = Blank
    • Run the following PowerShell to import the list into the site/site collection of your choosing
    • Working Example:

    import-spweb -identity http://sharepointsite.com -path C:\temp\test.cmp -includeusersecurity -includeversions all