Architecting and Building Your Farm Using PowerShell Part 2

This is a live blogging post from the International SharePoint Conference London 2012. So don’t expect well-written proza here.

Session by Gary Lapointe, Chandima Kulathilake, Spencer Harbar

Note: live blogging PowerShell code isn’t exactly easy, so this abstract primarily contains snippets of some takeaways

PowerShell Remoting

  • You can join servers to your farm remotely by using PowerShell Remoting
  • ExecutionPolicy should be ByPass when running command remotely (Unrestricted is not enough)
  • You will not get it right the first time probably, but that goes for scripting in general

Service Applications & Topology

  • Running all your service app endpoints in only one application pool is a good practice
  • A highly available SharePoint farm has a minimum of 6 servers (4 SharePoint, 2 SQL)
  • Only install what you need
  • Treat your scripts as production code. Don’t just copy a script from the internet and run it.
  • Provisioning pattern: start service instance, create app pool, create service app, create service app proxy, grant permissions
  • Service application proxies are a pain to create/manage via PowerShell, many inconsistencies
  • Know the difference between service app, service app proxy, service instance, windows service
  • There is no generic way to create and instantiate each service app: know the differences
  • Separate service accounts and managed accounts because automatic pwd changes might break your farm