Category Archives: SharePoint

I’m Presenting at SharePoint Fest Chicago on October 7th

SharePoint

On October 7th, I’m teaming up with Michael Blumenthal to give a half day workshop on using PowerShell with SharePoint.  Michael’s got some great material and between the two of us you should walk away with a firm introduction as well as a walk through on a few of the more useful scripts from this site.

The Workshops are optional and are the day before the official conference begins (Workshops are on Monday, Conference is Tuesday and Wednesday)  Although there is an extra cost for the workshops, I think you get more for your money on workshop day as the sessions benefit in 2 big ways:

  • Workshops are Longer – basically a half day vs 1 hour sessions during the conference.
  • Workshops are more intimate – where there might be 100 people in a 1 hour session, expected attendance for workshop sessions is typically half that.

I hope to see you there!

http://www.sharepointfest.com/Chicago/

UPDATE: the presentation, scripts and handout PDF are available for download here: SPFestHandout.zip

 

SharePoint 2010 SP2 installation trouble

SharePoint,

“let no good deed go unpunished”

I’m not sure who said that, but it certainly seems true with SharePoint Patching – It’s Sunday night and I thought I would “be nice” and upgrade our development environment over the weekend so the developers don’t loose a day during the week.

What was I thinking…

My install:

2 SharePoint boxes plus one FAST box.

I had downloaded 4 updates:

– SharePoint Server SP2

– Language Packs for office products SP2

– Office Web Apps SP2

– Fast Server SP2

Progress:

The FAST server SP2 installed on the fast server pretty quickly – it asked for a reboot no trouble there – I didn’t see any indication that there were any post setup tasks to run, but then again I don’t know that I looked very hard.

The Problem Children: my two SharePoint boxes.

I ran setup on the 3 remaining SP2 installers in this order: Server, Language, OWA. The installs went pretty quick thanks to a tip I had heard on Todd Klindt’s netcast last week about stopping a bunch of services prior to launching setup.  Luckily, I had also run a script I had leftover from SP1 that backed up key files and took an inventory of running services, content databases, etc…

With the 3 binaries installed, It was time to run the Dreaded “SharePoint Products Configuration Wizard”.  I say dreaded, because looking back, I can’t think of a single time it’s ever worked the first time after an upgrade. Something has always gone wrong and this Do-gooder’s Sunday night was no exception.

At stage 9 of 10, it threw an error saying the SharePoint Admin Service (SPADMINV4)  wasn’t started.
Piece of cake, I’ll just start it. Wait, no I can’t – it won’t start.

A few searches on the internet and I found this article:

http://support.microsoft.com/kb/2756815

It mentioned the Claims to Windows token service not starting either – hmm, that seemed to be the case too.

I checked a different environment that hadn’t been patched with SP2 and sure enough the claims to windows token service was running on that one, but it wasn’t running on my dev environment. Hmmm.

Do you remember above where I mentioned I had an inventory of what services were running before the upgrade??? Guess what – Claims to windows token service (C2WTS) was not running BEFORE my Upgrade, yet SP 2010  PRE SP2 seemed to be working just fine.

So perhaps there is something in SP 2010 SP2’s admin service that requires the C2WTS service.  Or maybe that came with SP1, and I thought I had SP1 but was running RTM. Who knows.

Anyhow back to the fix, I used the second solution in KB 2756815 – My servers are behind a proxy server, and can’t get out to the internet so the C2WTS service gets mad when it can’t check the internet for the latest and greatest gossip about what certificates have fallen out of favor. In fact C2WTS gets so mad, it refuses to start – which is where KB2756815 comes in – I was able to change a local policy setting and after I did that, C2WTS started right up and after that, The SharePoint Admin Service (SPAdminV4) started as well.

As I write this, the Farm is in upgrade task step 9 of 10 and its 41.17% done- Hopefully it will finish up, then I can run it on my second box, and start upgrading content databases and be on my merry way.

But of course not…

Somewhere after about 44% I stepped away only to return and be greeted by the “Configuration Failed” screen – again.

2 problems seen in the logs:

    • The user profile sync service would not start – I actually saw this flash across the screen during the operation of the wizard – it nicely said that I could/should start that after the install was done.
    • The second issue: A timeout, Looks to be related to the user profile service.

The error mentioned setting the USP Sync Service Instance to Offline, so maybe I’ll get lucky and it will work the second time I run the wizard.

For Kicks, I’m running the wizard once on the second machine to see if it fairs any better. The second machine isn’t running User Profile Sync, which I don’t think should matter as much of the upgrade work is done via timer jobs and should work across all nodes in the farm, but just in case, it’s worth trying – I could use a success.

And, I got one! The second node finished ok, so now back to the first node.

Success again! Re-running the Products config wizard on the first node a second time also worked! Now all I need to do is start that user profile service… I tried it from windows services, but it didn’t start – not a big deal since I know that quite a bit goes on when provisioning User Profile Sync and remember above, SharePoint mentioned that it put UPS offline.

Next I try to Central Admin->”Services on Server” I find the service, click start and am asked for the farm account password – on the password screen in nice red letters, it says that after I provision the service I need to do an IIS reset. I think to myself “I haven’t done anything yet” and I enter the needed password and click OK.
I am immediately greeted by one of those SharePoint error screens with a correlation ID on it. Off to look at the ULS logs.

System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 – An existing connection was forcibly closed by the remote host.)

Hmm, makes me wonder if something else is wrong.

I checked a few other SP Service Apps and they seemed fine.

Is it worth trying again? I go back to services on server and click start – I see the Red IISreset message and figure it can’t hurt to do it BEFORE – so I give that a shot, and guess what, I am able to click OK and not get an error – the service now shows as “Starting”

This doesn’t bother me – I’ve done User profile sync in 2010 a few times and I know it takes something like 10 minutes to finish setting up FIM in the background, but it’s taking a long time and I’m getting nervous…

I check the windows services – FIM Sync is started, FIM itself is still disabled. Hmm – I can’t say I’ve ever watched it so I don’t know which one gets put up first, so I wait a while longer, then I try a reboot, still no luck. Time for some powershell

I look at the user profile sync services in powershell with this command:

Get-SPServiceInstance | where { $_.typename -like ‘User Profile Synchronization *’ }

I get a line back that shows it is “Provisioning” – I’ve seen this before so it’s time to Kill that and try again.

I did a Stop-SPServiceInstance followed by the ID of the “Stuck” Sync Service.

Now back to Central admin for another try at starting it.

Still no luck.

Spencer Harbar is pretty much the expert on this and his blog says that if we’re in the situation we’re in, that we should just go ahead and rebuild the user profile service from scratch.  There is only one problem here – we use Newsgator, a 3rd party add in, that relies heavily on User Profiles – So I’ve got a support ticket open with them to find out if UPS gets reset, if it will break a bunch of associations.

I’ll hopefully have an update tomorrow.

Update:

The issue turned out to be related to Duplicate Certificates for ForeFront.

Here are a few steps I took to get from Problem to Resolution.

  • Enabled verbose logging for User Profile Service in Central Admin
  • Looked at the Windows Event logs
  • Reset the SharePoint Timer Cache
  • Started the User Profile Sync Service on a different Node.

I noticed a few additional things:

In the Event Log, Event ID 234 from “ILM Web Service Configuration”

ILM Certificate could not be created: Cert step 2 could not be created: C:\Program Files\Microsoft Office Servers\14.0\Tools\MakeCert.exe -pe -sr LocalMachine -ss My -a sha1 -n CN=”ForefrontIdentityManager” -sky exchange -pe -in “ForefrontIdentityManager” -ir localmachine -is root

ILM Certificate could not be created: Cert could not be added: C:\Program Files\Microsoft Office Servers\14.0\Tools\CertMgr.exe -add -r LocalMachine -s My -c -n “ForefrontIdentityManager” -r LocalMachine -s TrustedPeople

I also noticed that the UPS Sync worked just fine on the other node, so that was good news.

MS had suggested that the FIM certs might have been messed up so I looked at certificates on both the working and non-working systems

What I found was that the Non-working system had more than one certificate.

MS said it was safe to delete all the forefront certs so that’s what I did, but it still didn’t work.

As it turned out, there was more than one place the certificates

The FIM certificates were found in two locations:

  • Certificates (Local Computer) -> Personal -> Certificates -> ForefrontIdentityManager
  • Certificates (Local Computer) -> Trusted Root Authority -> Certificates -> ForeFrontIdentityManager

I had deleted the ones from Personal, but not the Trusted Root Authority

http://www.cleverworkarounds.com/2010/08/15/more-user-profile-sync-in-sp2010-certificate-provisioning-issues/  Does a great job explaining the certificates so no need to rehash it here.

So in summary, Extra ForeFront certificates in the certificate store were the reason I couldn’t start the User Profile Sync Service.

 

 

 

 

Powershell to find all the Access Database Sites on your Web Application in SharePoint

PowerShell, SharePoint

I needed to track down all the access DB’s and wasn’t sure how to do it.

One of our developers came up with a script which I modified a bit.

Original credit goes to Ravi Konaparthi for the script.

This script will look for Access Services DB’s in a SharePoint 2010 Farm.
(This version only looks at a given Web application, but you can easily modify it to search everything – have a look at the comments)

$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) 
{
	Write-Host "Loading SharePoint Powershell Snapin"
    Add-PSSnapin "Microsoft.SharePoint.Powershell"
}

#Foreach loop to loop through all webs, and compare the web template and write findings to .csv file.

function Get-AccessDB()
{
    log "In Get-AccessDB"
    $url = getURL
    #NOTE - if you want to look at ALL Sites and not just a specific web application, just remove -webapplication $url from the line below.
    $sites=Get-SPSite -webapplication $url  -limit all
    foreach($Site in $sites)
	{
		log "Inspecting Site $($site.url)"
		foreach($web in $site.AllWebs)
		{
			log "inspecting web $($web.url)"
			if ($web.WebTemplate -like "*ACCSRV*")
			{
				log "Found Access DB in $($web.url)" "Green"
				$hash = @{"[URL]"=$web.Url;}
				New-Object PSObject -Property $hash | Sort-Object
			}
		}
	$site.Dispose()
	}
}

function log($txt, $color)
{
  if ($color -eq $null) { $color = "White" }
  write-host $txt -foregroundcolor $color
}

function getURL()
{
    switch(hostname)
	{
		"SPDEVPC" {$machineURL = "http://yourDevURL.yoursite.com"}
		"SPStagePC" {$machineURL = "https://yourStgURL.yoursite.com"}
		"SPProdSrv" {$machineURL = "https://yourProdURL.yoursite.com"}
		default {write-host "This should be run from either SPDEVPC, SPSTAGEPC or SPPRodSRV - Press any key to exit this script"; read-host; exit}
	}
	return $machineURL
}

Get-AccessDB | Export-csv D:\accessdb.csv

 

SharePoint 2010 Service Pack 2 (SP2) download links

SharePoint

SharePoint 2010 Service Pack 2 was released this month.

I’ve seen a few posts on blogs, but none so far were complete.

Here’s a list, I gathered this from: http://support.microsoft.com/kb/2687524
Note: This page took forever to load – in fact I almost closed it since it didn’t seem to have any relative information, then data showed up – they must build the page with an AJAX callback – it has quite a lot of detail!

I’ve organized the list below by product configurations so a few items are repeated (ie you’ll see the language packs in both the SP standard and Project server section)

Foundation / Free:

SharePoint 2010 Foundation SP2: wsssp2010-kb2687464-fullfile-x64-en-us.exe KB article: 2687464

SharePoint 2010 Foundation Language Pack SP2: wsslpksp2010-kb2687466-fullfile-x64-en-us.exe KB article: 2687466

Standard and Higher:

SharePoint 2010 Server (includes Foundation) SP2: oserversp2010-kb2687453-fullfile-x64-en-us.exe  KB article: 2687453

MS 2010 series Server products Language Pack SP2: oslpksp2010-kb2687462-fullfile-x64-en-us.exe  KB 2687462

Office Web Apps SP2: wacsp2010-kb2687470-fullfile-x64-en-us.exe  KB article: 2687470

FAST search for SP2010 SP2: fsserversp2010-kb2687446-fullfile-x64-en-us.exe  KB article: 2687446 (Fast search was a separate product offering, higher end than what came bundled with SharePoint 2010)

Project Server:

SharePoint/Project Server 2010 SP2: svrprjsp2010-kb2687452-fullfile-x64-en-us.exe KB article: 2687452

MS 2010 series Server products Language Pack SP2: oslpksp2010-kb2687462-fullfile-x64-en-us.exe  KB 2687462

“Other” servers/connectors etc:

FAST search for SP2010 SP2: fsserversp2010-kb2687446-fullfile-x64-en-us.exe  KB article: 2687446 (Fast search was a separate product offering, higher end than what came bundled with SharePoint 2010)

Microsoft Search Server 2010 SP2: sserversp2010-kb2687461-fullfile-x64-en-us.exe KB article: 2687461
(Note: Search Server 2010 SP2 was a separate offering by MS to allow search without needing sharepoint – if you are using the search features of SharePoint, you’ll just use either the foundation or server versions of SP2 above)

Microsoft Groove Server 2010 SP2: grssp2010-kb2687448-fullfile-x64-en-us.exe KB: 2687448

SharePoint 2010 Indexing Connector for Documentum SP2: dctmsp2010-kb2687459-fullfile-x64-en-us.exe KB: 2687459

MS Duet Ent. for SP2010 and SAP SP2: duetsrvsp2010-kb2687445-fullfile-x64-en-us.exe KB: 2687445

Installation tips: 

Much has been written about this, and I’ve seen some conflicting advice. I don’t have a “right answer” here – but I will say it’s a good idea to be prepared:

    • Practice on a test environment first.
    • take a backup of your IIS directory, especially the web.config files on your web front ends
    • Take a backup of your “hive” (c:\program files\common files\microsoft shared\web server extensions\14\*) there may be customization here.
    • Take backups of every DB, especially the content DB’s
    • Don’t forget about 3rd party DB’s like newsgator, K2, etc.

When possible:

    • If your SharePoint infrastructure is Virtualized, you can get a fool proof backup by doing this:
      • Shut down all your VM’s and then take a snapshot in the powered off state.
      • Take SQL backups while the VM’s are off.

The above steps might be a bit extreme, and maybe aren’t necessary, but they do give the best option of pain free recovery if you have to roll back. The logic being you can restore it to the exact same state (that of a shutdown system) – Every other backup method involves backing up (and subsequently restoring) a moving target…

Update:

This might be a good technique to follow when patching – basically it proposes shutting down the IISAdmin and SPTimerServces, and stopping or pausing the Search Services prior to patching then starting them back up afterwards.

http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx

– Jack

 

 

 

 

 

 

 

First steps – How to get an office 365 account to start learning SharePoint in the cloud

O365, SharePoint, SP2013

I’ve been playing around with Office 365 a little bit. I signed up for the preview a while back and have been using that free of charge since then…

If you’re a SharePoint person then I’m sure you’re aware that SharePoint in the cloud Aka Office 365 is where things are heading. At first this can be a little scary, especially if your company doesn’t currently subscribe to Office 365. Office 365 subscriptions come in a variety of flavors, and a variety of per month costs! – how do you get involved, how do you learn it, without breaking the bank?

It turns out there are a few ways to get involved, that you can have 100% control of, without needing a corporate account, and you can do it right n o w.

Step1: Visit Dev.office.com

On this page as of this writing Click the Big Start Button:
dev.office.com

Step2: On this page we have a few options:
dev.office.com_step2

Expand “Sign up for an Office 365 Developer Site”
Now:

This last option is the most interesting one… I’ve had my free trial for at least 6 months now. In talking with various Microsoft people at the SharePoint Conference last year, several of them mentioned that it’s possible to renew the free trial, and that if your company has a Microsoft TAM (Technical Account Manager) then that person can assist on getting this extended. I got the impression they could extend it pretty much forever, and that’s certainly been the case with my trial, It’s still live 6 months later and I’ve not even called my TAM yet!

Summary:
There are a few ways to sign up for a test account on Office 365, most of them are free, but worst case scenario, you’re only out $99/yr ($8.25 a month)

Tip:
All the office 365 accounts are tied to “Microsoft Accounts” – these have had different names throughout the years (Windows Live, LiveID, Zune, xbox, etc) So… you probably already have one of these and if so you may run into a few problems, as I did, so I want to share a few tips…

When you log in to any Microsoft service using a Microsoft Account, you have the option to “remain logged in” If you do this, a Cookie is saved in your browser – this can cause confusion if you have multiple accounts, which you’re likely to have once you sign up for the services above. So here are a few tips-

  • It’s always helpful to save the URL to sign in with – this is typically sent in a welcome email for the service in question. I’ve found that if I go to my o365 site and am unable to sign in using the sights “Sign in” page, I can always use that original URL to sign in, and that works every time.
  • Almost all problems with sign on are cookie related – meaning you can fix them easily by deleting all your cookies
  • If you have lots of work to do and need to be logged in to two accounts at once, you can try one of these approaches:
    • Use different browsers ie one ID is logged into IE and another into Chrome.
    • Sign in but don’t check the “remember me” option.

Ok so now that the mechanics are out of the way, You probably can’t wait to get started. There is a cool Development environment in the browser called Napa, which you’ll want to install. Step 2 in the above screenshot outlines it, but you might run into trouble (I did) and if so this article by Krunal Patel might be helpful: Enable Napa App for Office Online Development with SharePoint

With that installed and out of the way, here’s an article to get you started developing your first app for SP2013 in Office 365:

How to: Create a basic app for SharePoint by using “Napa” Office 365 Development Tools

Powershell to check SSL certificates Expiration dates

PowerShell, SharePoint

SSL certificates expire every now and again.

After getting caught off guard about an expired SSL certificate, I thought I’d search and see if I could find a powershell script I could run on the web front ends where the certs are installed.

I found a post on stack overflow that was a good starting point:
http://stackoverflow.com/questions/16181725/powershell-script-to-find-currently-bound-expiring-certificates-in-iis

I made a few simple modifications, formatting the output slightly differently, and adding email to the script, but basically what you see below is mostly from the above post, credit goes to Ansgar Wiechers for posting the solution I used.

You’ll want to test the script as is, then change the $DaysToExpiration to something more reasonable such as 30.

import-module webadministration
$DaysToExpiration = 700 #change this once it's working

$expirationDate = (Get-Date).AddDays($DaysToExpiration)

$sites = Get-Website | ? { $_.State -eq "Started" } | % { $_.Name }
$certs = Get-ChildItem IIS:SSLBindings | ? {
           $sites -contains $_.Sites.Value
         } | % { $_.Thumbprint }

$body = Get-ChildItem CERT:LocalMachine/My | ? {
  $certs -contains $_.Thumbprint -and $_.NotAfter -lt $expirationDate
}
$body | select friendlyname, Subject, @{Name="Expiration"; Expression = {$_.NotAfter}} | fl | out-string

$PCName = $env:COMPUTERNAME
$EmailFrom = "$PCName@yourdomain.com"
$EmailTo = "YourEmail@yourdomain.com"
$EmailBody = $body | select friendlyname, Subject, @{Name="Expiration"; Expression = {$_.NotAfter}} | fl | out-string
$EmailSubject = "Certificates Expiring within $DaysToExpiration days"
$SMTPServer = "yoursmtpserver.yourdomain.com"

if ($EmailBody.Length -gt 1)
{
  Write-host "Sending Email"
  Send-MailMessage -From $EmailFrom -To $EmailTo -Subject $EmailSubject -body $EmailBody -SmtpServer $SMTPServer
}

I added this script to the “Scripts” folder on my Web servers, and then created a windows “Scheduled task” to run PowerShell along with the script, scheduled nightly. I let it run a few times with $DaysToExpiration set to 700 (to confirm I would actually get the email.) After I knew that it worked I changed the number to a more reasonable 45.

Powershell to add a user to a group on remote machines

PowerShell, SharePoint

Problem:
A new Developer is brought on board and needs access to the ULS logs on 10 different machines.

2 part solution:
Part 1:
This only has to be done once, so I did this manually, A powershell script would be great for this, but I don’t have one – Sorry!

  • Create a local group on each server called “LogReaders”
  • Share the ULS logs folder on each server
  • Add “read” permissions to the “LogReaders” group to the share/NTFS permissions for the ULS log folder

Part 2:
Use the following script, updating values to match your environment –
Run the script as needed, each time a new developer needs access to the log folders

#AddUserToLogs.ps1
#this script is an adaptation of a forum post by jrv: http://social.technet.microsoft.com/Forums/en-US/ITCG/thread/35b8022e-7c0e-49fb-b4c7-346b83ed3fd0/
#jrv (http://social.technet.microsoft.com/profile/jrv/?ws=usercard-mini) provided the function Add-LocalUser
# I added the wrapper to make it work for my needs
function main {

	$user = "userIDneededtobeadded"
	$domain = "yourdomain"
	$Group = "LogReaders"
	$computers = @("computernanme1", "computername2", "computername3", "etc..") 

	foreach ($Computer in $Computers) {
		write-host $computer -foregroundcolor green
		Add-LocalUser -Computer $Computer -group $group -userdomain $domain -username $user
	}
}

function Add-LocalUser{
     Param(
        $computer=$env:computername,
        $group="LogReaders",
        $userdomain=$env:userdomain,
        $username=$env:username
    )
        ([ADSI]"WinNT://$computer/$Group,group").psbase.Invoke("Add",([ADSI]"WinNT://$domain/$user").path)
}

main

Powershell to check if an application pool has stopped

SharePoint

I had an oddball situation where the app pool of a given site would keep stopping. No one visits this site with a browser, it’s used just for search crawling. So when it goes down, we never know.

In theory SCOM can tell us this, but SCOM produces so much noise that it’s easy to miss things.

import-module webadministration

	function main{
	#get-command -module webadministration will show all the IIS stuff
	$appPoolName = "SharePoint - www.mysite.com443"
	
	$dt = get-date
	$ComputerName = $env:computername
	If((get-WebAppPoolState -name $appPoolName).Value -eq "Stopped")
	{
		write-host "Failure detected, attempting to start it"
		start-webAppPool -name $appPoolName
		start-sleep -s 60
		
		If((get-WebAppPoolState -name $appPoolName).Value -eq "Stopped")
		{
			write-host "Tried to restart, but it didn't work!"
			sendmail "AppPoolRestart Failed" "App Pool $appPoolName restart on $ComputerName failed - this will effect search `n $dt"
			#log to event log
		}
		else
		{
			write-host "Looks like the app pool restarted ok"
			$subjectString = "AppPool Restart was needed"
			$body = "A routine check of the App Pool $appPoolName on $ComputerName found that it was not running, it has been started. `n $dt"
			sendmail $subjectString $body
			#log to event log?
		}
	}
	else
	 {
	 write-host "app pool $appPoolName is running"
	 }
 } #end main function
 
 function sendmail($subject, $body)
 {
    
    write-host "in Sendmail with subject: $subject, and body: $body"
	
	$EmailFrom = "WEBMONITOR@mydomain.com"
	$EmailTo = "jack@mydomain.com"
	$EmailBody = $body
	$EmailSubject = $subject
	$SMTPServer = "DNS.name.of.your.internal.smtp.server.com"
 
	Send-MailMessage -From $EmailFrom -To $EmailTo -Subject $subject -body $EmailBody -SmtpServer $SMTPServer
	"Emailed $subject on $dt to $EmailTo" | out-file -filepath "CheckSearchAppPools.log" -append 
 }
 
 #call main function
 main

PowerShell Cheat Sheet V2.00

PowerShell, SharePoint

CheatSheetP1

For years I’ve had this handy PowerShell Cheat Sheet at my desk, the original came from:  http://blogs.msdn.com/b/powershell/archive/2007/01/25/powershell-cheat-sheet-redux-the-pdf-version.aspx

I’ve looked a few times for an update, but never found one so I created my own.

I emailed the original author, Ben Pearce from Microsoft to ask his permission to post my updated version online. Ben replied it was ok:

Hi Jack

Thanks for sending me this.  It’s really nice to hear that you found the cheat sheet useful.  I’ve stopped working so closely with PowerShell now and actually manage a team of Premier Field Engineers.  So, I haven’t updated the sheet and I`m not aware of new version circulating.

Thanks for taking the time to update it yourself and feel free to post this on your blog.
Thanks

Ben

That said here’s the updated version – it adds a 3rd page with a few extra tips and there is a bit thrown in about $true and $false on page 1.

PowerShell Cheat Sheet V2.00

I created a new 3 page cheat sheet for SharePoint to supplement the above sheet:

SharePoint PowerShell Cheat Sheet

If you want both in the same file they can be found here:

Combined PowerShell and SharePoint Cheat Sheet

I’ve introduced co-workers to PowerShell and the Cheat Sheet is always very popular:

CheatSheetwall