STSADM does not include the capability to enumerate Web Parts per site collection. You could design nn extension object to allow STSADM to include a new command that would enable this capability.

An STSADM command extension is composed of configuration information in an XML file that is parsed by STSADM, and code that is called whenever the new command is executed by STSADM. The configuration XML file contains each command name with a reference to a class that implements the command.

The following is an example of an STSADM command extension from the stsadmcommands.sps.xml file included with Microsoft Office SharePoint Server 2007.

<commands>
   <command name="setsitedirectoryscanschedule" class="Microsoft.SharePoint.Portal.SiteDirectory.LinksCheckerJobCommand
   Line, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral,PublicKeyToken=71e9bce111e9429c"/>
   <command name="getsitedirectoryscanschedule" class="Microsoft.SharePoint.Portal.SiteDirectory.LinksCheckerJobCommand
   Line, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral,PublicKeyToken=71e9bce111e9429c"/>
</commands>

The configuration XML file for an STSADM command extension is stored in the following path:

%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\CONFIG

The assemblies for an STSADM command extension are normally installed in the global assembly cache.

Implementation of an STSADM command extension would require some code and configuration information to be installed on each server running Office SharePoint Server.

Because this is an administrator-level enhancement that is available only to someone with server administrative access, it is supported.