SP1 is the latest release to SharePoint Server 2013 on-premises. The service pack includes performance, reliability, and security fixes. It also helps IT address some of the most common scenarios faced when moving to the cloud, helping them deploy cloud-based workloads in their organization faster and with less complexity, while providing them with the control they demand. In this session, you will learn some of the new features in SharePoint Server 2013 Service Pack1, how to set them up, how to upgrade your SharePoint environment to SP1 and what you need to need to be aware of before the upgrade.
3. Knut Relbe-Moe
Senior Solution Architect
Technical Lead SharePoint
Steria AS
Oslo
Norway
Contact:
Twitter:@sharePTkarm
Email: knutrelbemoe@outlook.com / kirm@steria.no
Blog: http://www.sharepointblog.no
Skype: knutik.net
Mobil: 0047-98224609
4. Working for Steria Norway
Lives just outside of Oslo, the capital of Norway
Married
2 Children.
About me
SharePoint evangelist, mentor, speaker
Old developer, turned Architect / ITPro
Have worked with SharePoint since the
2003 version.
Worked with several clients upgrading their
solution from 2007/2010 to 2013.
Worked with several clients upgrading from
2013 to 2013 SP1
Works as a Lead Architect and advisor
creating SharePoint Farm
architecture/infrastructure on many
projects. With up to 25.000 users.
Experience
9. • Includes fixes designed to improve your experience with SharePoint 2013.
• All cumulative updates through December 2013
• Public updates through February 2014.
Fixes
10. Included fixes and updates in SP1:
• Security and Non-Security Updates for January 2014–Released January 14, 2014
• Office 2013 December 2013 Cumulative Update (KB 2912738)–Released December 10, 2013
• Security and Non-Security Updates for December 2013 (KB 2916204)–Released December 10, 2013
• Security and Non-Security Updates for November 2013–Released November 12, 2013
• Office 2013 October 2013 Cumulative Update (KB 2887714)–Released October 8, 2013
• Security and Non-Security Updates for October 2013 (KB 2892139)–Released October 8, 2013
• Security and Non-Security Updates for September 2013–Released September 10, 2013
• Office 2013 August 2013 Cumulative Update (KB 2873346)–Released August 13, 2013
• Non-Security Updates for August 2013–Released August 13, 2013
Fixes and updates
11. • Security and Non-Security Updates for July 2013–Released July 9, 2013
• Office 2013 June 2013 Cumulative Update (KB 2855356)–Released June 11, 2013
• Security and Non-Security Updates for June 2013–Released June 11, 2013
• Security and Non-Security Updates for May 2013–Released May 14, 2013
• Office 2013 April 2013 Cumulative Update (KB 2832224)–Released April 9, 2013
• Security and Non-Security Updates for April 2013–Released April 9, 2013
• Security and Non-Security Updates for March 2013–Released March 12, 2013
• Office 2013 February 2013 Cumulative Update (KB 2802843)–Released February 12, 2013
• Non-Security Updates for February 2013 (KB 2810076)–Released February 12, 2013
• Security and Non-Security Updates for January 2013–Released January 8, 2013
• Security and Non-Security Updates for December 2012–Released December 11, 2012
Fixes and updates
12. • So you should get a more secure and stable enviroment if you upgrade to
SharePoint 2013 SP1.
Summary
14. SharePoint Saturday
Gulf
Live Online
#SPSGulf
14
Seamless connection to OneDrive
for Business in Office 365
What’s great about this is that it
makes it so much easier for SharePoint 2013 on-
premises customers to use OneDrive for Business in
the cloud alongside their existing SharePoint
deployment.
OneDrive for business in the cloud gives every user
25GB of storage, which is a good reason to use this
hybrid setup.
New functionality allows IT administrators to
selectively configure redirection of OneDrive for
Business, sites, and pages to the cloud.
SP1 – provides you with a hybrid
setup of OneDrive from Office 365
with a OnPremise SharePoint
Solution.
Microsoft gives every user a 25gb
OneDrive setup, which is pretty
awsome
Microsoft tries to «push» the users
to the cloud with this setup, by
giving the users good reasons to do
this move.
16. SharePoint Saturday
Gulf
Live Online
#SPSGulf
16
Seamless connection to OneDrive
for Business in Office 365
Just remember if you choose to Redirect the Sites
pages to Office 365 – the sites users follow on
premise will not appear on the page
17. • OneDrive now replaces SkyDrive in the top link bar. Included with this is
Yammer, if you activate the Yammer feature on-premesis via Central
Administration.
OneDrive integration
18. SharePoint Saturday
Gulf
Live Online
#SPSGulf
12/04/2014
Yammer
Organizations of all sizes are using Yammer. SP1 makes it easy
for IT to replace the out-of-the-box SharePoint 2013 social
experience (Newsfeed) with Yammer.
Using simple controls in SharePoint 2013 Central
Administration, IT can choose to activate (or deactivate)
Yammer, redirecting users to their established Yammer
network.
SP1 – provides you with a hybrid
setup of Yammer with a OnPremise
SharePoint Solution.
This redirect the users to
established yammer network, but
requires that the onPremise servers
are connected to the wire
Microsoft tries to «push» the users
to the cloud with this setup, by
giving the users good reasons to do
this move.
19. • When you click on the Yammer link, you’ll be directed to
/_layouts/15/Yammer.aspx and be asked to log in. That’s about it…
Yammer integration
20. • Once Yammer is activated, the SharePoint “newsfeed” will now display this
message when you visit your MySite.
Yammer integration
21. • When creating a new User Profile
Service Application you are
presented with the option to use
Yammer for Social Collaboration!
Yammer integration
22. SharePoint Saturday
Gulf
Live Online
#SPSGulf
22
JSON Light
SP1 includes notable improvements that support
developers.
SP1 introduces support for JSON Light, allowing
developers to choose which level of metadata they would
like in a response: no metadata, minimal metadata, or full
metadata (previously the only option in SharePoint 2013).
24. SharePoint Saturday
Gulf
Live Online
#SPSGulf
12/04/2014
On April 3, this announcement appeared on the
Knowledge Base article attached to SharePoint 20013
SP1, KB 2817429:
“ We have recently uncovered an issue with this
Service Pack 1 package that may prevent customers
who have Service Pack 1 from deploying future
public or cumulative updates. As a precautionary
measure, we have deactivated the download page
until a new package is published. ”
Sorry – the update packagde of
SharePoint 2013 SP1 is currently
unavailable
Only way to upgrade now is a
new install with the
slipstreamed version.
25. SharePoint Saturday
Gulf
Live Online
#SPSGulf
25
At the same time, the version number of the KB article
was increased to 4.0.
Since then, we've had a more detailed (but not
particularly enlightening) explanation posted on
TechNet:
«We have recently uncovered an issue with the following
Service Pack 1 packages that may prevent customers with
Service Pack 1 from deploying future public updates. As a
precautionary measure we have deactivated the download
pages until new packages are published.»
• SharePoint Foundation SP1: KB 2817439
• SharePoint Server 2013 SP1: KB 2817429
• Project Server 2013 SP1: KB 2817434
• Office Web Apps Server 2013 SP1: KB 2817431
• SharePoint Server Language Pack SP1: KB 2817438
• SharePoint Foundation Language Pack SP1: KB 2817442
27. 1. Install SharePoint 2013 service-pack 1 on all servers.
2. Install SharePoint 2013 Language pack service pack 1 on all servers
3. Complete the upgrade with psconfig/config-wizard to complete on all servers
4. Install Windows 2012 R2 on all servers
Alternative 1:
28. 1. Patch SharePoint 2013 Farm to SP1
2. Install SharePoint 2013 service-pack 1 on all servers if not already done. Without SP1 we can’t run Windows
2012 R2 with SharePoint 2013 (and be supported at least).
3. Next, complete the upgrade with psconfig/config-wizard to complete the upgrade process. If a server hasn’t
been fully patched done yet you’ll see a warning about software version mismatches.
Upgrade to SP 1
29. • Windows 2012 is perfectly capable of mounting local ISO files as a virtual disc. Click the ISO,
then run setup when the ISO is mounted.
29
Prepare Windows 2012
R2 ISO
31. SharePoint Saturday Gulf
Live Online
#SPSGulf
31
Make sure you install the GUI Windows only. SharePoint doesn’t support
server core.
Make sure you select “upgrade” as it’s pretty much the entire point of this
article/process.
32. SharePoint Saturday
Gulf
Live Online
#SPSGulf
12/04/2014 32
Windows Upgrade Compatibility
Check
The compatibility check will point
out the Hyper-V device drivers
might not work after the upgrade.
We don’t mind. If you need to
restart for any reason, setup will
insist you do that 1st too here.
Ifyourserver has 4 million apps
installed, these may cause
problems with the upgrade.As this
is my “production” environment,
there is just SharePoint +
prerequisites so this is what I see:
33. SharePoint Saturday Gulf
Live Online
#SPSGulf
Running Setup & Upgrading
Windows 2012 to R2
Once passed the compatibility checks, Windows setup should basically keep itself busy for the rest of the process
without any interruption needed
33
Setup will restart a
couple of times.
34. SharePoint Saturday Gulf
Live Online
#SPSGulf
Verify SharePoint Functionality & Fixing Errors
As mentioned earlier, the upgrade to Windows
2012 R2 can leave SharePoint rather broken by
default.
Specifically the Security Token Service can break
because of a problem with then SharePoint farm
certificate.
Click on “view these issues” and you might see
something like this:
35. SharePoint Saturday Gulf
Live Online
#SPSGulf
How to fix it!
STS is likely broken and the cache-cluster probably needs a reboot to get it working again.
Fix the cache cluster by removing and then re-adding each cache server in turn
For STS errors, a simple psconfig upgrade command per failing server (psconfig -cmd upgrade -
inplace b2b) should fix that problem up.
If not run the following commands to rebuild your environment
35
psconfig -cmd services install
psconfig -cmd installfeatures
psconfig -cmd secureresources
36. 1. Reinstall the Servers.
2. Install Windows 2012 R2 on all servers
3. Install SharePoint 2013 service-pack 1 on all servers.
4. Install SharePoint 2013 Language pack service pack 1 on all servers
5. Join the SP1 servers to the farm
6. Complete the upgrade with psconfig/config-wizard to complete on all servers
7. Remove the old 2013 servers from the farm
Alternative 2:
My recommendation
37. SharePoint Saturday Gulf
Live Online
#SPSGulf
Upgrade process
Project Start
Upgrade code to
2013 if possilbe
IF not possible put
the 2010 code in
the 14 hive
Install and
configure 2013
farm
Do a test
upgrade /
test run
Clean up
2007/2010
environment
Analyze todays
solution up
against new
solution
Success?
Yes or No
Error handling Analyse resultsTest the
systemet
Migrate Migrate content
38. SharePoint Saturday Gulf
Live Online
#SPSGulf
How to succeed upgrading SharePoint
Test upgrade of all contents
Test, test and test again
Involve the business owners to early identify if the upgrade was a success
Create a log of activities and prioritize the error handlings
Repeat the process with upgrading until end result is acceptable.
Expect that mistakes will happen, upgrade is never straight forward. Make sure to have a plan
to resolve the problems. Or consider not upgrading at all, recreate the site instead
39. Scripted install of cumulative updates/SP1
To save a lot of time during installation of cumulative updates / service pack,
take a look at Russ Maxwell powershell script to script the installation. This will
save you a lot of time.
http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-
cumulative-update-takes-5-hours-to-install.aspx
Another note