Gizmodo has additional info here: http://gizmodo.com/5140434/win-7-tip-windows-explorer-preview-pane-works-much-better-than-vistas

Enjoy!

DECLARE @DatabaseNames TABLE
(
	name varchar(255)
)

INSERT INTO @DatabaseNames
SELECT name FROM sys.databases WHERE
name NOT IN ( 'master', 'model', 'msdb', 'tempdb' )

DECLARE DatabaseCursor CURSOR FOR
SELECT * FROM @DatabaseNames

OPEN DatabaseCursor

DECLARE @DatabaseName varchar(255)
DECLARE @LogFileName varchar(255)
DECLARE @SqlStatement varchar(2000)

FETCH NEXT FROM DatabaseCursor INTO @DatabaseName

WHILE @@FETCH_STATUS=0
BEGIN
	PRINT '----------------------------------------------------------'
	PRINT 'Processing database ' + @DatabaseName
	PRINT '----------------------------------------------------------'

	SET @SqlStatement = 'ALTER DATABASE [' + @DatabaseName +
		'] SET RECOVERY SIMPLE'

	PRINT @SqlStatement
	EXEC (@SqlStatement)

	SET @LogFileName =
		(
			SELECT b.name
			FROM sys.databases a
			INNER JOIN sys.master_files b ON
				a.database_id = b.database_id
			WHERE
				a.name = @DatabaseName
				AND b.name LIKE '%log')

	PRINT @LogFileName

	SET @SqlStatement = 'USE [' + @DatabaseName +
		'] DBCC SHRINKFILE(N''' + @LogFileName + ''', 1)'

	PRINT @SqlStatement
	EXEC (@SqlStatement)

	SET @SqlStatement = 'ALTER DATABASE [' + @DatabaseName +
		'] SET RECOVERY FULL'

	PRINT @SqlStatement
	EXEC (@SqlStatement)

	FETCH NEXT FROM DatabaseCursor INTO @DatabaseName
END

CLOSE DatabaseCursor
DEALLOCATE DatabaseCursor

Open the registry editor. Browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications”. Here you will find a key for each SSP in the farm. Drill down to "\Gather\ProfileImport\ContentSources\0" (which is the Full Import) and check the key “CrawlNumberInProgress”. If it´s not “0xffffffff” then the number displayed corresponds to a key under the branch “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\\Gather\ProfileImport\Crawls”.
I changed the number in the key “CrawlNumberInProgress” to “0xffffffff” and then restarted the “Office SharePoint Server Search” service for the settings to be applied.

Tackling the job of migrating from subsites to new site collections is no trivial task.  There are however, some COTS products specifically tailored to this case:

• Metalogix Site Migration Manager
• Quest Software Migration Manager for SharePoint

Unfortunately, I did not have the luxury of using one of these purpose-built tools for this endeavor.  Instead, I have relied on Gary Lapointe’s fantastic stsadm extensions.  Specifically, the following:

• gl-convertsubsitetositecollection – this one does all of the heavy lifting, using the SharePoint Content Migration API.
• gl-replacewebpartcontent – this allows you to use regex patterns to search and replace links that are in content editor web parts
• gl-copynavigation – because the new site collections create their own global navigation, I set the global navigation of the root (/) site collection to be all manual links, and use this extension operation to copy that navigation to the new site collection
• gl-addsiteadmin – add site collection administrators to the site collections easily

These commands have been grouped into a batch file which will handle each step of the migration process.  This has worked pretty well.  The batch file is executed through a Scheduled Task as the process often can exceed 24 hours in runtime so executing through RDP is not an option. 

The last utility I have made use of for this effort is bmail from Beyond Logic.  This is a simple command-line SMTP mailer which is used at the end of the conversion batch file to notify me that the process is complete.  This saves me the trouble of having to login to the server several times a day to check on progress.

Have I missed any utilities that you find useful for similar work?  If so, please comment!

SharePoint Content Deployment Wizard

http://spdeploymentwizard.codeplex.com/

The SharePoint Content Deployment Wizard is a tool for SharePoint 2007 which provides the means to deploy the following content:
- site collections
- webs
- lists
- folders
- list items (including files)
Content is exported using the Content Migration API (PRIME) as a .cmp file (Content Migration Package) which can be copied to other servers for import. Unlike the out-of-the-box tools, the Wizard allows *granular* selection of content via a treeview.

 

SharePoint Access Checker Web Part

http://accesschecker.codeplex.com/

Quickly check what objects within a Sharepoint site hierarchy a user has access to.

The Access Checker Web Part is a Windows Sharepoint Services Web Part, for use within Windows Sharepoint Services v3 and Microsoft Office Sharepoint Server 2007, that displays a tree view showing permissions on objects for a user scoped to a Site hierarchy. It also has a second mode which will show the permission inheritance of objects within a Site hierarchy.

 

SharePoint ULS Log Viewer

http://ulsviewer.codeplex.com/

A windows application for viewing SharePoint ULS log files more easily. Supports filtering and easy viewing of data.

SLAM! SharePoint List Association Manager

http://slam.codeplex.com/

Most developers who have used SharePoint as an application development framework have run into the realization that SharePoint is NOT a relational database. In fact, the accepted wisdom is if you need relational tables, use ASP.NET/SQL straight-up, not SharePoint.

Enter SharePoint List Association Manager (SLAM). In short it allows you to define relationships (one to one, one to many, many to many) between SharePoint lists (or Content Types) and then leverage those relationships in webparts or custom field types using familiar and straight forward SQL queries.

Have I missed any?  Please comment if there is a “must have” (except WSPBuilder of course, everyone knows that ) I have omitted!

And this is what it looks like after:

Much better!  In any event, if you haven’t seen it yet, here is the new VS2010 start screen:

Pretty clean looking.  One of the very first things I looked for in this version is to make sure it can target the 2.0 Framework, and sure enough, support for 2.0, 3.0, 3.5, and 4.0.  Very cool.  Stay tuned for more updates as I get a chance to play around with this some more.

We are working to release a hotfix to automatically fix this issue. A manual work-around is currently available and involves customers re-entering their Product ID number (PID) on the Convert License Type page in Central Administration.  For more information and detailed steps please read this KB article.

In addition, Microsoft is working on a hotfix to be released shortly.  More information can be found on the Microsoft SharePoint Team Blog:

Microsoft SharePoint Team Blog : Attention: Important Information on Service Pack 2