Time to re-read my article about migration vs upgrade. This is a classic case of a scenario where you should migrate - create a new environment, and use migration tools (hello AvePoint) to move the content, leaving custom solutions behind.
[Description: Description: C:\Users\Brian\Pictures\EXD Logos\Extelligent logo no text.jpg]Ishai Sagi | Solutions Architect 0488 789 786 | [email protected]<mailto:[email protected]> | www.sharepoint-tips.com<http://www.sharepoint-tips.com/> | @ishaisagi<http://twitter.com/ishaisagi> | MVP Profile<https://mvp.support.microsoft.com/profile/Ishai> From: [email protected] [mailto:[email protected]] On Behalf Of Web Admin Sent: Tuesday, 21 May 2013 11:03 AM To: ozMOSS Subject: MOSS to SP2010 Upgrade issue due to missing features Hi all, I have a significant public website I am trying to migrate. While I have managed to get the site functional I have a big clean-up job to perform. We do not have the 2010 solutions these features and fields belong to and have been unsuccessful in removing them via the UI or PowerShell. Is there anyway to force delete: * Features where the definition is missing/unknown? * Content Types (and other objects) which are part of a missing feature? A typical PS error when attempting to delete a content type is: Exception calling "Delete" with "1" argument(s): "The content type "$Resources:NWResource,_ContentType_MultiOutcomeTask_Name;" is part of an application feature." Or is the safer path to deactivate all (non-upgradeable) features in the source site before taking a DB backup? My main issue here is that it would render the source site unusable. Any advice appreciated. Regards, Paul
<<inline: image001.jpg>>
<<inline: image002.jpg>>
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
