About one month ago (April 30th 2008) Zach Rosenfield (SharePoint Program Manager - Infrastructure) announced on his blog about the availability of the SharePoint Administration Toolkit. The Toolkit is the first in a series of updates that you should consider to be deployed into your SharePoint farm deployment. I haven't had the time to test this out hence the delayed post.
This update will add the following capabilities to your SharePoint farm.
- A new menu named "Batch Site Manager" with a link to "Move, Lock and Delete Site Collections"
- A new STSADM command to update user alerts to a new URL when a site has been moved
Let me explain what these mean and what you'll need to consider for deploying this update to your farm.
There are two installers available for x86 and x64 and you can download the correct version of the SharePoint Administration Toolkit from the following locations.
Before you hit the install button after your download you should read the release white paper for SharePoint Administration Toolkit (MS Word) about known issues and how to install this on your farm. There are differences between the x64 install and x86 install.
Here are some basics you should know when installing and using the new updates.
- You must be a local administrator of the server and also belong to the SharePoint farm administrator group in your SharePoint farm to install this update (Most common for updates)
- You should run the "Move, Lock and Delete Site Collections" option from the server where the "Central Administration Service" is running. Basically this is your primary server in your farm
- If your farm has not been updated to Service Pack 1 of SharePoint you should first consider upgrading (Although you can still use the commands you *may* encounter Timer job errors)
- For x64 edition first run the "MicrosoftSharePointAdministrationToolkit.exe" from your download location and then you will need to manually run the following commands.
From a command prompt, navigate to the following location:
%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin
Type the following commands (without the quotation marks):
“psconfig –cmd applicationcontent –install”
“stsadm –o installfeature –name BatchSiteManagerLinks”
- When you first navigate to the "Move Lock and Delete Site Collections Screen" you will need to "Update Statistics Aggregation". (Would have been nice if the link was on the actual word than on click here.)
The Move Lock and Delete Site Collections Screen once statistics have been updated. In this demo server I have two content databases for my Web Application. One for My Sites content and the other for a single site collection.
- The Move Lock and Delete Site Collections option only shows 100 site collections. So if you are doing more than 100 site collection moves soon as you move to 101 you'll lose what you selected in the previous screen. In any case you should not Move hundreds of site collections on one go since that will put quite a heavy load on your farm as well as SQL server. Make sure that you schedule these after hours according to your SLA requirements. Users will lose access to your sites when the Move site operation is running. Attempting to access the sites will result in a failed Move operation. So it is required that you should "lock" the sites prior to the planned move.
- You can only Move Site Collections within the same web application. So this means you can only go from Single web app to multiple content databases. To move from one web application to another consider using the STSADM -o export command.
- You can only run one move operation at a time. Don't run multiple and make sure that the previous operation was successful before running the next. Do not attempt to remove already running timer jobs for move operations.
- Make sure you backup your sites prior to doing any of the operations to ensure recoverability to previous state in case something goes wrong.
- Once a site collection move has been finalised use the "STSADM -o updatealert" command to change the Alert URL's of the site collections existing alerts.
- Updatealert operation will only work correctly if the URLs specified with the url and oldurl parameters reside in the same site collection. This is necessary to allow proper updating of alerts in a specific zone. Zones are defined when you create your SharePoint farm. This is when you have different URL's for accessing your sites via alternate access mappings (AAM). If you don't know what AAM's are I highly recommend this article titled "What Every SharePoint Administrator Need to know about Alternate Access Mappings" . SharePoint needs to update these on it's own.
Most of what I highlighted above is available on the Release white paper for SharePoint Administration Toolkit.
If you are installing on a x86 platform you will see a similar screen if your install was successful.
Posted by Chandima Kulathilake
| 2 Comments
| Bookmark with:
, SharePoint 2007