In this session, we cover what’s new in SharePoint 2013. First, we cover installing SharePoint 2013 and configuring your new farm. This session provides what to need to start planning your new SharePoint 2013 farm and dovetails nicely into Part 2, which covers changes in SharePoint 2013 the SharePoint administrator should know about. We cover changes to how you’ll plan your farm topology. We also cover the changes to the Search service application and how that impacts scale. Finally, we spend some time talking about everyone’s favorite part of SharePoint Server, the User Profile Service.
That’s quite a lot for one session – but Todd is a fast speaker. The session also includes cheap jokes about SharePoint Developers, guaranteed!
So here are my session notes:
Performance – Performance – Performance!
Performance come from SQL server, so implement the best practices. Don’t be cheap on hardware!
I love to quote this one:
The cost of overinvestment in hardware is almost always far less than the cumulative expenses related to troubleshooting problems caused by under sizing.
Virtualization is more common nowadays, but its tough to virtualize SQL Server / SharePoint – the good thing, there is a webcast about how to set things up correctly. Note: I will attend to that session tomorrow.
Access Service creates a lot of databases, Todd’s recommendation is to provision this service to a different SQL Server instance. I think that’s a good one.
User Profile Service has not changed that much in SharePoint 2013 – is it FIM RC under the hood again? If there is a question concerning User Profiles, I always check Spence Harbar’s blog – if someone figured it out, its him.
Web Frontend, Application Server, Database Server – the first two tiers are flexible enabled/disabled via the Web Role.
Search: There is a gang on the box stealing all the resources
Nice one, so true. Search loves RAM.
Then the two IT-Pros showed us how to scale SharePoint from two servers to three servers – and then it got bigger and bigger. Finally a session about big installations. By the way, where is the level 400 session for scaling SharePoint?
Search is a killer: Don’t underestimate the hardware requirements for bigger installations.
4 times patches killed SharePoint 2010 and they were pulled right afterwards. Todd has two lists, he is my reference for the current recommended version (SharePoint 2010 and SharePoint 2013). Too bad there is no “If I were you, I would install this patch flag” on the page. Important: There is no uninstall – install the patches on a TEST environment and to quote Dan Holme:
You always have a TEST environment – without it you don’t have a PROD environment
Slides & 60 Minutes Entertainment
Laughing and learning – that’s why I love Todd’s sessions for years now. I even bought his book at TechEd, but he took it from me to shamelessly promote it in the session:
The Todd and Corey combo worked very well, I (and I assume the 100 attendees) had a very good time! Thanks!
Max has led SharePoint implementations for Dax 30 companies since 2009.
Max’s free time is spent on twitter mostly with a good coffee in his hands.
Latest posts by Max Melcher (see all)
- He’s dead, Jim: SharePoint 2013 Search Troubleshooting - October 13, 2014
- Create SharePoint 2010/2013 Search Content Sources – one script to rule them all - July 14, 2014
- What happened to ‘the’ ULSViewer and how to still get it? - June 4, 2014