STSADM

I’m working on a project which involves scripting, via batch files, an intranet portal. We wanted to script the creation of the various division and department sites along with several lists that would be needed in each site.

It’s been a little while since I’ve released any new commands so I decided to throw one together real quick. Fellow MVP, Matthew McDermott, was working on a scripted install and had asked if I had anything to set the path for the ULS logs.

If you’re a WSS v3 user this will hopefully make you happy – I’ve reworked my custom extensions so that there is now a WSS specific build. This means that you can download the source and debug in a pure WSS environment and you will also no longer be plagued by commands being available but not working either at all (because they’re just for MOSS) or only partially because I had one small MOSS specific feature that’s not necessary for WSS.

On a recent project I had a need to relate one list to another. The first list was a document library which stored project specs and the second was a list that contained user provided scores that were used to rank the projects.

I just saw a couple of posts from AC and Spence regarding the release of the Content Deployment QFE Pack: http://andrewconnell.com/blog/archive/2008/05/20/MOSS-2007-Content-Deployment-QFE-Pack-Now-Available-via-MSFT.aspx http://harbar.net/archive/2008/05/21/MOSS-2007-Content-Deployment-QFE-Pack-Now-Available-via-MSFT.aspx I won’t reiterate what they’ve already done a good job stating.

In my last post I mentioned a project which required me to move documents from one list to another list in a different farm one folder at a time. Along with that was a requirement to set various field values (metadata) based on patterns in the folder name and/or filename.

I was recently trying to debug some issues that I was having with the people picker that is shown when creating audiences and I found that I needed a way to manually trigger the distribution list import quickly but I didn’t always want to have to wait for the user profile import to finish.

Those familiar with my commands know that I’ve got a few commands that I created to handle the exporting and importing of list items and lists using the content deployment API.

I’ve pushed out a minor update to my code which affects several commands. Any command that took in an URL to a list view will now work with an URL to the list folder or the list view.

This is something that I put together a while ago but I’m only just now getting to the point where I can document it. I was looking for a solution to a common problem of propagating changes to content types deployed via a Feature and I came across a post by Søren Nielsen.