Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Would a Powershell Provider for SharePoint 2007 be worthwhile or is stsadm.exe sufficient?

share|improve this question
up vote 4 down vote accepted

There is a PowerShell provider that I've heard some good things about. It's available on CodePlex; however, it doesn't yet support MOSS 2007. That said, I've found using the SharePoint object model sufficient. If you don't want to dig into the object model, though, I recommend both Gary LaPointe's stsadm extensions, and his newer PowerShell cmdlets for SharePoint. Both are available via his blog.

share|improve this answer
Unfortunately the codeplex project does not yet support 2007 – Chris Ballance Apr 30 '09 at 17:28
Oh, wow. Good point, Chris. I'll edit to reflect that. – Abs Apr 30 '09 at 23:08

Given how pervasive PowerShell has been for the Exchange servers, it's probably a good assumption that the other Office servers won't be too far behind. So, while you're probably better off just calling stsadm from PowerShell for now, knowing how it's used and taking advantage of Gary LaPointe's extensions during your learning will probably be a worthwhile use of your time.

share|improve this answer

I am the ashamed author of the aforementioned SharePoint Provider - the current source will build a 2007 compatible provider that can even be used from a non-sharepoint box but it is a bit primitive still. I hope to get back onto this soon.

I already am a bit overstretched over several powershell projects, so apologies again.

share|improve this answer

Here are three posts from Karine Bosch, an employee of U2U which cover some operations with PowerShell and SharePoint.

Depending on the level of coding skills known you can do anything with PowerShell and SharePoint since PowerShell can use and .NET assembly so the object model is completely usable.

share|improve this answer

I would recommend sticking with stsadm.exe unless you have a strong business need for using PowerShell.

share|improve this answer

I believe that STSADM will be the main administration tool for quite some time. Nothing prevents you from using STSADM from PowerShell environment.

share|improve this answer

Stsadm is still alive and well, but judging by the developments in Exchange and SQL server powershell skills might soon (2-3 years) be nessisary in the SharePoint world. PowerShell skills makes updates to existing sites soooo easy especially once the tools catch up with visual studio intellisense-wise :-)

share|improve this answer

There is quite a bit of work already happening with PowerShell and SharePoint. Check out Gary Lepointe's blog. He is Mr. STSADM in the SharePoint MVP world.

I think Gary has developed a set of cmdlets (is that the right word?) for Powershell.

In general I am not a big fan of PowerShell b/c I have solid devleopment skills and feel more comfertable writing what I need in C# with the SharePoint API.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.