SPSBE 2012 - PowerShell and SharePoint

Adam Burcher

PowerShell your SharePoint environment from setup to finish

#SPSBE

#SPSBE20

About me

• Adam Burcher

• http://www.thesharepointbaker.co.uk

• #sharepointbaker

• [email protected]

• SharePoint Developer & IT

A big thanks to our sponsors

Venue Sponsor

Platinum Sponsors

Gold Premium Sponsors

Gold Sponsors

Agenda

• PowerShell – what, why and who?

• Out of the Box

• Writing custom functions

• Demo

• Build a SharePoint Farm

• Configure a site

• Deploy code and then content

PowerShell – what?

• Scripting language/framework

• Configuring Server technologies – SharePoint, Windows, Active Directory, Exchange....

• Blurs the lines between scripting (e.g. MS DOS) and code (e.g. C#)

PowerShell – why?

• Automation – if its scripted, you can run it again

• Documented – scripts can form documentation

• Simplified rolls outs – scripts do all the work

• Distinction between ‘Code’, ‘Content’ and ‘Configuration’

• Code = WSP, C#, DLL

• Content & Configuration = PowerShell

PowerShell – who?

• IT Admins & Dev

• One option – IT Admin manage scripts for server, farm and web app setup. Dev everything else.

• “Befriend a Dev”

• If SharePoint offers collaboration across a business, PowerShell is collaboration between IT Admins and Dev

Out of the box

• SharePoint comes with a number of very useful cmdlets

• New-SPWebApplication

• Get-SPSite

• Typically you can interchange the ‘verb’ – New, Get, Set

• Extend by wrapping custom logic – ifs, loops, etc

$managedAccount = Get-SPManagedAccount | ?{$_.UserName –eq “tsb\appPoolAccount”}

if (-not $managedAccount){

New-SPManagedAccount –credientials $credientials}

Writing custom scripts

• You can write custom cmdlets in code and compile

• Custom functions don’t require “code” (& compiling)

• Good news is you can access the SharePoint OM

• Bad news is you can access the SharePoint OM

• Good C# Code...can make good PowerShell

• Bad C# Code...will make bad PowerShell

• Treat PowerShell as Production Code

The Scripts

Create the Farm &

Central Admin Create our Web App &

Site CollectionDeploy

Features Deploy Content

• Deploy-me.ps1 {args}

deploy

webapp

farmsetup

content

Demo

Building our Farm & Site

What’s next?

• Extend scripts for other elements –

• Service Applications – search, meta data etc

• Other content – new Webs (site hierarchy)

• Permissions, users, documents etc

• Create EnvVars for UAT, Prod etc

• Write a Release Note & Document!

• Test Scripts!

• Remember, anytime you go to Central Admin or your site to make a change, think – should you script it?

Q&A

Any questions…?

We need your feedback!

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

Our sponsors: