mvozila
asked on
Moving SharePoint 2007 SSP
In my production environment my Sharepoint 07 SSP is currently living on our main SharePoint 07 Portal. The central admin site is on a completely seperate site. In my dev environment I have both the Central Admin and SSP on seperate sites. The question is should I move it to a different site? I would like to keep it seperate from my main portal site, but is this risky. Now, the second part of this is I am upgrading SharePoint this weekend from 07 to 2010 (using the database attach method). So if I keep the SSP as is do you forsee me having any issues?
When you upgrade to 2010, there are no longer any SSPs. Everything that the SSPs provided in 2007 are now simply services of the main 2010 farm. The only thing you would then separate out is the My Sites, which you can put on their own site or under another site, that would be up to you (http://mysite vs http://mainsite/mysite). Here are the upgrade instructions for the SSP portion: http://blogs.msdn.com/b/alimaz/archive/2009/11/08/upgrading-moss-2007-ssp-user-profiles-and-mysite-content-to-sharepoint-server-2010-using-db-attach-method.aspx.
ASKER
That's right. So I am creating a new service and upgrading the old SSP database. I am not actually associating it with a website anymore. I know this is only losely related to the orginal question, but can I choose not to upgrade the mysite database, but instead just create a new one. We haven't allowed folks to use it in 2007, but they will be using more social computing features in 2010.
Yes, you can create a new 2010 farm and simply attach the content databases for the site collections and skip the SSP all-together.
ASKER
What data will I lose by doing this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This has been very helpful