Search has become the primary means in the Enterprise for surfacing and locating information, as a result, it has become a mission critical component of SharePoint deployments. The rise in adoption of SharePoint 2010 in organizations has led to more customers seeking to leverage the benefits of the new search architectures, whether Enterprise Search in SharePoint 2010 or FAST Search Server 2010, as part of their topologies. In either scenario…read more on the SharePoint Team Blog.
One of the most challenging aspects of maintaining a SharePoint deployment is understanding why certain events have transpired in the environment, often IT Professionals and Developers only have access to when an event occurred and are tasked with parsing Performance Counters, Event and Diagnostic logs, or executing Transact-SQL statements against the Usage database to put the what and why to the when. These tasks are typically accomplished through an array of tools such as Excel, Log Parser, SQL Server Management Studio…read more on the SharePoint Team Blog.
We’ve recently released the first administration toolkit for SharePoint Foundation and SharePoint Server 2010. The toolkit includes a new User Profile Replication Engine, a new Security Configuration Manifest, a new Content Management Interoperability Services (CMIS) Connector, and the Load Testing Kit (LTK).
User Profile Replication Engine
The User Profile Replication Engine was first introduced as a standalone application in later adminisration toolkits for Office SharePoint Server 2007 to replicate profiles between Shared Services Providers (SSP). The User Profile Replication Engine for SharePoint Server 2010 was built on Windows PowerShell and now enables the replication of Profile and Social data between the User Profile Service Application in SharePoint Server 2010, in addition to backwards compatibility with Office SharePoint Server 2007 SSPs. These improvements enable replication between SSP’s or User Profile Service Application services, as well as across versions. Note Replication is limited to Profile data, SSP’s in Office SharePoint Server 2007 contains no Social activity tracking.
Security Configuration Manifest
The Security Configuration Manifest is an attack surface reduction feature in Windows Server products. The manifest inlcuded in the administration toolkit adds roles for SharePoint 2010 to Windows Server 2008 with SP2 or Windows Server 2008 R2.
Content Management Interoperability Services Connector
The Content Management Interoperability Services (CMIS) Connector enables consumers of SharePoint to interact with content stored in any repository that has implemented the CMIS standard and in additional enables SharePoint 2010 content to be available to any application that has implemented the CMIS standard.
Load Testing Kit
The Load Testing Kit (LTK) generates a Visual Studio Team System 2008 (VSTS) load test based on Windows SharePoint Services 3.0 Internet Information Services logs. Load test can be used to generate synthetic load against SharePoint 2010 as part of a capacity planning exercise or a pre-upgrade stress test.
The Microsoft SharePoint 2010 Administration Toolkit v1.0 can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en.
Microsoft SharePoint 2010 Administration Toolkit v1.0 documentation for SharePoint Foundation 2010 can be downloaded from http://technet.microsoft.com/en-us/library/cc508986.aspx and for SharePoint Server 2010 from http://technet.microsoft.com/en-us/library/cc508851.aspx.
The 4th release of the Microsoft SharePoint Administration Toolkit is now available for download and includes improvements in the SharePoint Diagnostics Tool (SPDiag), a new Permissions Reporting Tool, a new bulk Quota processing tool, in addition to the Security Configuration Wizard Manifests. The Microsoft SharePoint Administration Toolkit is an excellent suite of utilites aimed at the system administrator to assist in both isolating issues, understanding the overall environment they support, and making common administrative tasks more efficient and reliable.
To learn more about improvements about this release see http://blogs.msdn.com/sharepoint/archive/2009/08/27/announcing-the-fourth-release-of-the-microsoft-sharepoint-administration-toolkit.aspx.
To download the Microsoft SharePoint Administration Toolkit for x64 environments see http://go.microsoft.com/fwlink/?LinkID=142035.
To download the Microsoft SharePoint Administration Toolkit for x86 environments see http://go.microsoft.com/fwlink/?LinkId=141504.
I completely missed this one; the SharePoint Diagnostics Tool was recently released (included in the Microsoft SharePoint Administration Toolkit v3.0). The SharePoint Diagnostics Tool enables an administrator to simplify troubleshooting by gathering pertinent information about a farm and displaying it in a meaningful way providing a programmatic approach to locating and isolating issues in your environment. Find it and other great tools and utilities under Tools.
The Microsoft SharePoint Administration Toolkit contains functionality to help administ
rateer (good catch A Mondale) and manage Office SharePoint Server 2007 and Windows SharePoint Services version 3.0. This toolkit contains two new functions – the ability to perform bulk operations on site collections and a Stsadm operation to update alert emails after a Web application has changed URLs.
I was recently asked to deploy the ProClarity Viewer 6.3 for SharePoint Web Part – after downloading the package I realized that it was not offered in a deployable package, but rather a compressed archive of the .dwp, assembly, and resource files. The challenge became offering a user experience similar to the previous ProClarity Viewer version so I decided to package the Web Part into a reusable solution. For those interested or looking to create a deployable Web Part package I’ve documented the steps below:
Step 1 Create a Manifest
The Manifest file is a required configuration file that describes the contents and overall structure of the cabinet file. STSADM will use the Manifest file to deploy the contents of the cabinet file when executing the addwppack operation.
<SafeControl Assembly=”SPSPageViewer, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Namespace=”SPSPageViewer” TypeName=”*” Safe=”True” />
The <Assemblies> node contains the overall definitions for each of the assemblies being deployed, the child <Assembly> node uses the FileName attribute to define the assembly file name, in this case SPSPageViewer.dll, and contains the definitions for the class resources in addition to the XML for the SafeControls list. The XML for the SafeControls list can be found in the ProClarity Viewer Web Part Setup Guide or optionally copied from the example above. This information will be written to the web.config for the Web application(s) when the solution is deployed to the SharePoint Products and Technologies server farm using the SharePoint administration tool (STSADM).
The <ClassResources> node contains the base definitions for each class resource that will be deployed, the child <ClassResource> node uses the FileName attribute to define the class resource file name, in this case each of the images accompanying the Web Part are defined in a <ClassResource> node with their path relative to wpresources at a global or localized level.
The <DwpFiles> node contains the definitions for each .dwp file being deployed, the child node <DwpFile> uses the FileName attribute to define the file name of the .dwp file, in this case the .dwp file name accompanying the downloaded Web Part archive is PasPageViewer.dwp.
The complete Manifest file should appear as follows:
<SafeControl Namespace=”SPSPageViewer” TypeName=”*” />
Step 2 Create a MakeCab Directives File
The MakeCab directives file controls how files are compresses in a cabinet.
Create a logical file structure by copying Book.gif, Library.gif, Page.gif, TPMax.gif, TPMin.gif, Unknown.gif, and up.gif to /images. *You will need to create the images directory in your cabinet directory. The directives file is also used to define the name of the cabinet file.
;*** <the end>
Step 3 Create the Cabinet
To create the cabinet file execute MakeCab.exe /F <filename>.ddf where <filename> is the name of your directives file. The cabinet file when a source destination is not specified is commonly created under C:Documents and Settings<user>.
Step 4 Deployment
To deploy the Web Part package, copy <cabinet>.cab to a location on one Web front-end server.
Execute STSADM -o addwppack -filename <cabinet>.cab [-globallinstall].
Step 5 Verify Deployment
The Web Part package will be listed in the list of available/deployed solutions to the SharePoint Products and Technologies server farm under SharePoint 3.0 Central Administration | Operations | Solutions Management (see image).
To review deployment details, retract, or remove the solution click <cabinet>.cab (see image).
Step 6 Add the ProClarity Viewer to a Page
To add the ProClarity Viewer Web Part to a page, navigate to a site collection and select Site Actions | Edit Page.
Select a Web Part zone and click Add Web Part.
Select ProClarity Viewer from the list of available Web Parts and click Add.