0.53 Alpha

Rating: No reviews yet
Downloads: 109
Released: Oct 21, 2006
Updated: by
Dev status: -not yet defined by owner-

Recommended Download

Application RC2 Compatible SharePoint PSProvider
application, 43K, uploaded Nov 2, 2006 - 109 downloads

Release Notes

PowerShell RC2 Build:

Installation Instructions

PS c:\temp> InstallUtil Nivot.PowerShell.SharePoint.dll
PS c:\temp> Add-PSSnapin Nivot.PowerShell.SharePoint
PS c:\temp> New-PSDrive wss SharePoint http://mywss/
PS c:\temp> cd wss:
PS wss:\>

What now?

It now supports infinitely complex paths (including circular ones), and copy/move/delete:


# clear all alerts for the 'username' found in the contributor role
remove-item wss:\site\subsite\!roles\contributor\username\!alerts\*

# make the cross-site group 'crosssitegroup' part of the administrator role
copy !groups\crosssitegroup !roles\administrator\

# upgrade perms for 'crosssitegroup' from reader to contributor
move !roles\reader\crosssitegroup !roles\contributor

Of course, wildcards work too, so let loose!

pseudo containers (will tab complete, but not show up in get-childitems):

!alerts, !groups, !roles, !lists, !users

When in the context of certain containers, only a subset of these will appear. For example, when in the user container, only !groups and !alerts are available


user, group, role, list


alert, listitem

I've implemented a handful of what I call "adders" and "removers" to allow basic copy/move/delete functionality between different types of compatible (and incompatible) paths. So, what do I mean by "incompatible?" For example, it is currently possible to do:

move-item \!users\oisin \!roles\contributor\

So, what happens is the user oisin gets copied to the contributor role (ok) and then is removed from the source (not ok). In sharepoint terms, this makes oisin a contributor, and then removes him from the site users -- which also removes him from contributors :)

Reviews for this release

No reviews yet for this release.