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 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)
- I am able to click the LB Service link, which brings me to the settings page
- But when I click Start I get redirected to this error page:
- UPDATE – As mentioned in the comments by Tuppence Weix, this can be fixed with the following PowerShell command:
PowerShell123New-ItemProperty "HKLM:\Software\Microsoft\Office Server\15.0\LauncherSettings" -Name "AcknowledgedRunningOnAppServer" -Value "1" -PropertyType "DWORD"New-ItemProperty "HKLM:\Software\Microsoft\Office Server\15.0\LoadBalancerSettings" -Name "AcknowledgedRunningOnAppServer" -Value "1" -PropertyType "DWORD"
- Also, apparently Yammer and OneDrive for business are critical issues (You can just click the X to close)
- When creating a new User Profile Service Application you are presented with the option to use Yammer for Social Collaboration!
- This adds the following entry to the navigation bar (Starting to look more and more like O365):
- 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.
- 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
- I did some testing by typing in my trial Office 365 tenant so I could play around here.
- 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).
- Clicking OneDrive and Sites Redirected Perfectly!
- 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.
- 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.