This is easily the most important module. Without SharePoint installed properly nothing else matters. Here at SharePoint911 we have a unique perspective on installing SharePoint because we have installed it for over 100 different customers. So in this module we will not talk about hypothetical install but actual client installs. This module will walk you through doing a SharePoint install the exact same we do it for customers on their production systems. And then during the hands on lab you will do just that. We won’t be installing SharePoint as one account because that is easier, instead we will explain a proper, least privilege install. With a least privilege install each account only has the permissions it needs. This makes your farm less susceptible to attack and is also more impressive to show off to your coworkers. Also, the lab is written so you could easily apply the same steps to your production server when you get back to the office.Hardware for SharePoint VirtualizationTopologies and farm designFour stages of SharePoint installationPrerequisitesSharePoint bits installSharePoint bits configureFarm Configuration A professional installRid the world of unnecessary GUIDsUsing PowerShell to create the farmUsing PowerShell to create State and Usage service appsUsing Power or Central Admin to configure the restCovered more in module 3
Need 24 GB for SharePoint Server dev environment“SharePoint 2013 does not support installation on to a domain controller in a production environment. “From http://www.microsoft.com/en-us/download/details.aspx?id=30384 http://technet.microsoft.com/en-us/library/cc262485.aspx
Need to fix the image
This is from SharePoint 2010. Information is mostly the same for SharePoint 2013, but I couldn’t find the comparable docs.
Transcript of "Part I: SharePoint 2013 Administration by Todd Klindt and Shane Young - SPTechCon"
Admin StuffShane Young and Todd Klindt
Who is this Todd guy?• WSS MVP since 2006• Speaker, writer, consultant, Aquarius, President of Shane Young fan club• Personal Blog www.toddklindt.com/blog• Company web site www.sharepoint911.com• E-mail todd.Klindt@Rackspace.com• Twitter me! @toddklindt• NETCAST!!!!!!!!!!!!!!!!!!!!!!!!• http://www.toddklindt.com/netcast RACKSPACE® HOSTING | WWW.RACKSPACE.COM
Who Am I?• Shane Young• SharePoint911, a Rackspace Company• Microsoft Office SharePoint Server MVP• Consultant, Trainer, Writer, & Speaker • Shane.Young@Rackspace.com • Blog • http://msmvps.com/shane • SharePoint Consulting • http://www.sharepoint911.com • Twitter @ShanesCows RACKSPACE® HOSTING | WWW.RACKSPACE.COM
Three tiers of SharePoint • These are servers that host the IIS sites (web applications) that your users interact with • You have to setup your own load balancing to direct web traffic • Catch all for the servers in your farm that run the various services • SharePoint is very flexible, you can spread the load any way you want • SharePoint does the load balancing of service for you • Search needs some extra lovin’ • Can be any supported version of SQL • Can be cluster or mirrored or any other cool SQL trick you know • You can have multiple SQL servers
SharePoint production hardware • Windows • SharePoint root • All of those hotfixes & service packs for the next few years • Some SharePoint operations spool here • Move all possible files here (logs, etc.) • All servers must have the same drive letters • 12 GB for production servers in 3 tier topology • 24 GB for all-in-one test or dev • 8 GB for test or dev Foundation
Virtualization and Hardware requirements • Web front ends – Sure • Application – Be careful • SQL – Be very, very carefu • http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx http://technet.microsoft.com/en-US/sqlserver/gg429826.aspx
Different workloads different hardware • http://www.microsoft.com/en-us/download/details.aspx?id=12768 • http://technet.microsoft.com/en-us/library/ff758647.aspx