Kong Kong de World

Upgrade is always painful. SharePoint is no exception. Microsoft has suggested two ways of upgrade: inplace and database upgrade. All articles suggest database upgrade, which is also my choice. I don't trust third party migration tools. They will mess up the whole thing as I tried the most famous one, and missed a lot of things. However I don't trust Microsoft either, maybe SharePoint itself too. Firstly I exported content database to new farm. The PowerShell window in SharePoint 2010 menu must be opened as Administrator. Run Test-SPContentDatabase in the new farm then it reported some error. Check the log it says some features are missing. Those features have already deleted but some elements still reference to them. After some search I found a tool that claims to remove even the toughest features. It's called WssRemoveFeatureFromSite written by an MS guy. Still one feature can't be deleted. My colleage suggested me to create a dummy feature using the same GUID. It&#

The stsadm command was replaced by PowerShell cmdlets in 2010. To deploy on a Produciton, QA or DEV server you may probably need PowerShell scripts (with .ps1 suffix). However if you prefer GUI, you'll thank to Visual Studio 2010 as development and deployment is as simple as a few clicks.