This project is read-only.

Current Release 0.61 Beta August 26, 2007

January 31, 2008

I've just started a big contract with MOSS 2007. Expect some movement finally on the wss3/sps3 bits in the near future. I'll be posting to my blog with progress reports.

October 24, 2007

It appears that in some environments, it's impossible to mount local instances. I'm investigating the problem.

Glitches in 0.60 fixed, Binaries now available. Root is URL format again.


For Windows PowerShell v1.0 RTM only. Please ensure you are not running a beta version; you should have a System.Management.Automation version in your GAC if you are running the RTM version of PowerShell.

What is it?

A full PowerShell provider for exposing WSS/SPS 2003 (support for 2007 coming) as a filesystem. Administer your SharePoint installation with familiar copy/move/rename/delete and new-item metaphors. Move users between roles, copy users between webs; use the full power of the shell to script away the pain of GUI based mass-management.


At the moment, you can only install this onto a machine that has a local installation of Windows SharePoint Services 2.0 (WSS) and/or SharePoint Portal Server 2003. So, you need:
  • WSS 2.0 and/or SPS 2003 (SP2 recommended)
  • Windows Powershell 1.0

Known Issues

Manipulation of SPS 2003 is very flakey due to the fact that SPS 2003 itself is not supported with .NET 2.0, which of course powershell uses. However, I have been able to manipulate WSS sites under a portal instance without much problem.


First ensure you have the .net 2.0 sdk in your path, extract the release zip into an empty directory, then:

PS > InstallUtil Nivot.PowerShell.SharePoint.dll
PS > Add-PSSnapin Nivot.PowerShell.SharePoint
PS > New-PSDrive wss SharePoint http://localserver[:port]/[site/name]
PS > cd wss:
PS wss:\>

After that, you can read about some of the Features.


Oisin Grehan is from Dublin, Ireland, now living in Montreal. Author's blog at Nivot Ink

Last edited Feb 28, 2008 at 11:52 PM by oisin, version 32