SPSiteManager update coming soon
As I noted in my previous post The Next Big Thing - The SharePoint Configuration Analyzer V.Next, we'll be combining the functionality of SPSiteManager with the SharePoint Configuration Analyzer, and incorporating SPUserUtil as well.
In the mean time, we've found some immediate additions we need to make to SPSiteManager based on overwhelming customer requests and feature requests. Thus, I'm working on an update to SPSiteManager to include the following before moving forward.
First I'll note what is complete, and then what is in progress to go into this version before I release it. This of course, is not an all encompassing feature request list :).
What's Complete
-
Fix for removefromdirectory and removefromcrawl operations
-
I found that my comparison was literal, and if you created the site via the Portals Create Site link, then we only stored the relative path to the site in the directory. So I updated the comparison logic to do a literal comparison, and then a relative comparison.
-
New site directory targeting via -sitedirectoryurl switch
-
New enumsitecrawl operation
-
New enumsitedirectory operation
-
New adddatabase operation
-
This operation can be used to enumerate over the <contentdatabases> section of a Site Distribution Document to create Content Databases. This is extremely helpful if you are mirroring a farm with lots of content databases, and want to match database names, etc on a target system.
-
Theoretically speaking, you could run an analysis on one farm, then use SPSiteManager to create the necessary databases, then restore sites. (In the future, I hope to be collecting enough information in the Site Distribution Document, that you could basically replay and duplicate your entire farm settings if needed)
-
New site owner attributes reported in <site> elements for analysis.
-
New Version Purging
What's In Progress
I hope to have these changes complete and tested by the end of the week. Once they're done, I'll post again with an update.
- Keith