I just realised that there are quite a few custom solutions installed on my 2007 farm that have been deployed globally to all site collections, even though not all of them require it. As a result I have solutions in the Site Collection I want to move that I don't really need. So I simply want to delete the 2007 solutions out of my Site Collection. Sounds simple, I thought. However, there seem to be problems in this: I have removed most of the custom solutions from my 2007 site collection, yet they still show up in the log as missing features when I run test-spcontentdatabase. Is there something else I have to do other than retract the solutions from the site collection? Or do I really have to remove the entire solution off the farm? I don't want to do that because I am only migrating a single Site Collection at this point. All other site collections still need the features that are installed on the SP 2007 farm. Thanks for the feedback.

So that means I have to remove the solutions from all Site Collections Is there any workaround for this? Thanks

Mike, when you remove my "references to 2 010" the whole question doesn't make sense anymore! That's why I posted in the "Upgrade" forum: I want to upgrade my 2007 Sharepoint site. It's not a 2010 question, it's just the background. The reason I am required to remove web parts from this one particular site collection is that I want to upgrade only the one site collection and not the others. So, for this reason, is there a way in SharePoint 2007 to remove the solutions entirely just from one Site Collection but not the others?

> Mike, when you remove my "references to 2 010" the whole question doesn't make sense anymore! I was very very careful when I edited the post that it still made sense. This wasn't a hatchet job. The reason you want to do this is irrelevant. Any mention of 2010 in the pre-2010 forums will encourage people to post (even more) SP 2010 questions here. We are already plagued by people who think it is a great idea to add a post to a MOSS 2007 thread saying how things are done in 2010 (and by over ten people every day who post 2010 questions here). My editing 2010 out of posts is to avoid encouraging even more. MikeSP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

If these solution have been globally deployed, then they are active throughout the farm in all site collections. The only control you have ta the site collection level is disabling the feature for that site collection which does not necessarily remove th reference. In this case, the best way out seems to be to retract the solution, do the upgrade for this site collection and then redeploy the solution. Just curious to know, how did you manage to remove a globally deployed solution from the site collection? Do you mean just disabling the feature?