Chris Schwab

Determining your own SharePoint Farm Deployment

Best Practices

#SPSBE

#SPSBE22

Uhh…Who are you?

• I’m glad you asked…

• SharePoint Engineering Director at Fpweb.net

• @chrisrschwab

• cschwab@fpweb.net

• Leo

A big thanks to our sponsors

Venue Sponsor

Platinum Sponsors

Gold Premium Sponsors

Gold Sponsors

Agenda• What are “Best Practices” anyway?

• Planning – Pre Install

• Recommended Specs

• PowerShell Scripting

• Install/Configuration

• Script #1

• Service Accounts

• Script #2

• Choose your own adventure

• Smaller Tweaks

WHAT ARE “BEST PRACTICES” ANYWAY?

• Best practices are conditional• YOU must come up with your own,

someone can’t give them to you.

• Not just for initial deployments.

• …but how do you do that?! Yeah, let’s talk about that.

PLANNING – PRE INSTALLRECOMMENDED SPECS

• Why are these recommended?

• Room for growth

• How do we determine our own?

• Analysis of existing activity

• So what's the big picture?

PLANNING – PRE INSTALLPOWERSHELL SCRIPTING

• Database Names

• Documentation

• Consistency

• Time

INSTALL/CONFIGURATIONSCRIPT #1

INSTALL\CONFIGURATIONSERVICE ACCOUNTS

• Service accounts

• Naming

• Password management

INSTALL\CONFIGURATIONSCRIPT #2

LESS TALK, MORE ACTION!

CHOOSE YOUR OWN ADVENTURE…

Possible discussion points:

• Versions: OS, SQL, SharePoint• Security: AD, NTLM, Kerberos,

Claims• SQL: configuration, maintenance,

alias• Infrastructure: Virtual, Physical, Cloud• Naming conventions• Post Install: Backups, Performance,

Monitoring• Quantifying user impact• Database: Sizing, RBS, Security

SMALLER TWEAKS

• SMTP

• HA Rules

• Permissive File Handling

REFERENCES\FURTHER READING

• SharePoint Saturday NZ Best Practices for SharePoint 2010 Infrastructure Deployments

• SharePoint 2010 Performance and capacity management

• Capacity Management for SharePoint Server 2010

• Microsoft SharePoint 2010 Unleashed

We need your feedback!

Scan this QR code or visit http://svy.mk/sps2012be

Our sponsors: