MOSS 2007 Site Directory Sharepoint 2010 what do we do.

I have a MOSS 2007 deployment for a school to Shared Services with students and staff seperated across them and their my sites as well.

Both Web Applications are setup with the Default Template Enterprise --> Site Directory. Now I have worked really hard great help from others on migrating databases upgrading creating proxies to support the Shared Services we had have got it working and check my sites and they work.

But now with the staff and or student web applications it is completely broken at the root because I know site directory is not working and is not available I can browse directly to applications under there for example a blog or a wiki but the root just gives you the standard error. My question is moving forward what do I do to replace the Site Directory so that I can get everything up and running I have been to the code plex site to look at the solution of a site directory I am more looking at just rebuilding a directory or page to link to blogs and wiki's, but how do you clean up this mess with the site directory and get it gone so that all I am left with is the resources under there. Is it at MOSS 2007 you do this or at Sharepoint 2010.

Who is Participating?

there are features that are missing in the upgrade. For instance
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:41 AM]: File [Features\S2SearchAdmin\ActiveCrawls.dwp] is referenced [1] times in the database

this feature is not installed - its needed
Features\S2SearchAdmin\ActiveCrawls.dwp

Im not sure what you are attempting to do so I have a couple of questions.
1.It appears you are migrating from MOSS 2007 to Sharepont 2010 is this correct? Or are you trying to integrate a MOSS 2007 instance with a 2010 instance?

0

balwynhighAuthor Commented: 2011-04-03

I am migrating from a MOSS 2007 enviroment where the Default Site Directory was the foundation of the site with categories and sites linking from there, I want to migrate to 2010 but the main default page throws an error and the only way to get to all sites is directly for example everything sits on the url staff.domain.com.au etc.. I need to know how to get rid of the default page so I can start building a new site directory either from scratch or by using something else.

I guess what I am asking is how do I migrate the MOSS 2007 and then remove the junk that is left from the default site directory with out deleting all the other stuff below that.

the site directory is just a special type of site collection. are all of your sites subsites of the site directory? if they are they don't have to be. If you move them then you can just recreate the site directory

How do you move the subsites from the site directory. Is this something that should be done before upgrading or is best done after the upgrade.

The upgrade approach I am taking is a database attached as I am building front end web servers and seperated database. Our MOSS 2007 system is pretty much the default configuration on a single server with SQL 2005 and because the use has grown and escalated i need to do it now before it gets out of control.

So the migration using the database attached way should be pretty straight forward because there is not much to do. Just this damn site diretory and the error it throws up because it is not supported any more.

0

balwynhighAuthor Commented: 2011-04-04

I have been asking the wrong thing the whole time. It is the Collaboration Portal that our entire system is based on and this is failing to upgrade, the subsites are ok to get to but the collaboration portal just comes up with see screen shot for idea. I re-enable the template in the 1033 directory as did i enable the site directory there too before upgrading the entire system.

How can I get rid of the collaboration portal and either replace it with something new or what ever else. I just need to access the subsites nothing else.

Thanks.

0

balwynhighAuthor Commented: 2011-04-05

Screen Shot for last comment. This is the screen of the Collaboration Portal.

[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:41 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:41 AM]: File [Features\S2SearchAdmin\ActiveCrawls.dwp] is referenced [1] times in the database [WSS_Content_StudentUpgrade], but is not installed on the current farm. Please install any feature/solution which contains this file.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:42 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:42 AM]: One or more setup files are referenced in the database [WSS_Content_StudentUpgrade], but are not installed on the current farm. Please install any feature or solution which contains these files.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:42 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:42 AM]: File [Features\S2SearchAdmin\CompletedCrawls.dwp] is referenced [1] times in the database [WSS_Content_StudentUpgrade], but is not installed on the current farm. Please install any feature/solution which contains this file.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:43 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:43 AM]: One or more setup files are referenced in the database [WSS_Content_StudentUpgrade], but are not installed on the current farm. Please install any feature or solution which contains these files.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:43 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:43 AM]: File [Features\S2SearchAdmin\SearchAdministration.aspx] is referenced [1] times in the database [WSS_Content_StudentUpgrade], but is not installed on the current farm. Please install any feature/solution which contains this file.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:43 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:43 AM]: One or more setup files are referenced in the database [WSS_Content_StudentUpgrade], but are not installed on the current farm. Please install any feature or solution which contains these files.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:44 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:44 AM]: File [Features\S2SearchAdmin\Subsystems.dwp] is referenced [1] times in the database [WSS_Content_StudentUpgrade], but is not installed on the current farm. Please install any feature/solution which contains this file.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:45 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:45 AM]: One or more setup files are referenced in the database [WSS_Content_StudentUpgrade], but are not installed on the current farm. Please install any feature or solution which contains these files.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:45 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:45 AM]: File [Features\S2SearchAdmin\SystemStatus.dwp] is referenced [1] times in the database [WSS_Content_StudentUpgrade], but is not installed on the current farm. Please install any feature/solution which contains this file.
[STSADM] [SPContentDatabaseSequence] [INFO] [4/5/2011 11:57:46 AM]: SPContentDatabase Name=WSS_Content_StudentUpgrade
[STSADM] [SPContentDatabaseSequence] [WARNING] [4/5/2011 11:57:46 AM]: One or more setup files are referenced in the database [WSS_Content_StudentUpgrade], but are not installed on the current farm. Please install any feature or solution which contains these files.

0

balwynhighAuthor Commented: 2011-04-06

Above warning are the only 10 warnings in the entire upgrade, i am guessing they must have something to do with the Collaboration Portal displaying the error it does in the screen shot above. Couls someone please direct me in what these errors are about as I have googeld them and come up with nothing.