Udostępnij za pośrednictwem

How to migrate SPS 2003 My Sites to MOSS 2007 using the same web app hosting the Portal site

  • Artykuł

During my customer's migration from SPS 2003 to MOSS 2007 testing environment, we encountered some challenges while migrating My Sites. With Bill's help, I was able to fix the My Sites in testing environment. During the actual production upgrade, My Sites were sucessfully migrated.

Here's a recap of the fix I did in the MOSS testing environment:

1. Migrate the portal content db first.

stsadm -o addcontentdb -url https://sharepoint07uat.corproot.com/ -databaseserver dbserver -databasename portal_SITE

2. Create a web named something like “my” using My Site Host template under the portal

stsadm -o createweb -url https://sharepoint07uat.corproot.com/my -sitetemplate SPSMSITEHOST -title "MySite Host"

3. Then restore SSP from the old PROF db:

stsadm -o restoressp -title Restored_SSP -url https://adminserver:11111 -ssplogin DOMAIN\sharepoint -mysiteurl https://sharepoint07uat.corproot.com/my -indexserver
indexservername -indexlocation "d:\index” -keepindex -sspdatabaseserver dbserver -sspdatabasename portal_PROF -ssppassword pwd

4. Execute iisreset 

Then go into the SSP admin, check My Site settings, search settings, User profiles to make sure they all look good.

5. Now as a user, when I click on My Site in portal home page, I’m brought to https://sharepoint07uat.corproot.com/personal/userid and when I click on My Profile (or others click on my name) I’m brought to https://sharepoint07uat.corproot.com/my/person.aspx?accountname=DOMAIN\userid

6. To see the old SPS2003 MySite home page, just type https://sharepoint07uat.corproot.com/MySite . The Web Part error in this page is expected due to the retirement of My Alerts summary web part in MOSS 2007. Other web parts from your old MySite home page should show up here. This link can be pinned at either SSP or site level.

I'm also linking Bill's blog here for further reference:

https://blogs.technet.com/wbaer/archive/2007/02/19/co-hosting-team-and-personal-site-collections-within-an-individual-web-application.aspx

Comments

  • Anonymous
    February 26, 2007
    A good TechNet article on Design My Sites Architecture in MOSS 2007 http://technet2.microsoft.com/Office/en-us/library/97a22c4e-6fc0-4745-9a03-0bfa500a4ca51033.mspx?mfr=true

  • Anonymous
    March 12, 2007
    Hi. I'm trying to restore a PROF database from a SPS2003, and keep getting an error when running the following stsadm command: stsadm -o restoressp -title Restored_SSP -url http://mosskurs2007:11111 -ssplogin MOSSKURS2007administrator -mysiteurl http://mosskurs2007/mysites -indexserver MOSSKURS2007 -indexlocation "c:index” -keepindex -sspdatabaseserver MOSSKURS2007 -sspdatabasename Laerdal1_PROF_OLD -ssppassword passord The error I keep getting is this: "The following required arguments are missing: sspdatabase Any idea what this might mean? I've tried supplying this argument, but the same error keeps coming up. Thanks, Frank

  • Anonymous
    March 12, 2007
    sspdatabase is not even a valid parameter for stsadm -o restoressp The only database related parameter is searchdatabasename, if you don't pass a value for that it'll just use the default name, something like SharedServices1_Search_DB

  • Anonymous
    March 12, 2007
    Thank you for your feedback. I know sspdatabase is not a valid parameter. When the error is displayed, so is the parameter list, and sspdatabase is not one of them. However, can you tell me if you see any of the other parameters are wrong, resulting in this error? Thank, Frank

  • Anonymous
    March 13, 2007
    frankok: I have never seen the error you described before and I don't see any problems in your command. The url should be the SSP admin site and a subsite should have been created at http://mosskurs2007/mysites using My Site Host template. I think indexlocation needs to exist already.

  • Anonymous
    March 13, 2007
    Hi again. I found out the error. I downloaded the stsadm windows gui tool for MOSS 2007(http://blogs.msdn.com/ronalus/comments/1411643.aspx) and ran the command from there. I saw in the composed command that all parameters were quoted ("..."). Thank you for you help.

  • Anonymous
    July 25, 2007
    Hey Jingmei Both this post and Baer's reference the stsadm -o addcontentdb approach. How would one approach this using the gradual upgrade method? How would the steps differ? Thanks

  • Anonymous
    July 26, 2007
    The comment has been removed

  • Anonymous
    August 15, 2007
    Hi Jingmeili：   after migrate my sites to Moss 2007, I can't see any "My alerts" but "My links" is fine. How is this normally done.? thank you

  • Anonymous
    August 15, 2007
    eniky: Check this out about the alert not migrated... http://support.microsoft.com/?id=936759 Jingmei

  • Anonymous
    October 09, 2007
    Hi I am attempting to migrate my existing SSP (in which users have creates their MySites)  to a new farm. I have followed the steps mentioned in the article and I can see that all the user profiles are migrated successfully, I can also see the /personal/{uid}/ in the personal site attribute of the user profiles. However when I login to the site and click on the MySite, it tries to create the MySite for the user and fails with an error "Personal site cannot be created for the user, a site already exists, contact your administrator". Any help is appreciated. Thanks in advance Shekhar

  • Anonymous
    October 10, 2007
    Shekhar: The scenario I described in this post has 1 web app to co-host both the portal and my sites. Double check your my site web app location and make sure it's pointing to the same web app.

  • Anonymous
    February 27, 2008
    My question is how to migrate SPS 2003 My Sites to MOSS 2007 using a different web app(not the same web app hosting the Portal site)? Since it is recommended by Microsoft to deploy my sites to a seperate web app for medium to large deployment. Thanks,

  • Anonymous
    February 27, 2008
    ASMariner: One approach you could try is to move the SPS 2003 My Sites into a separate content database if that's not the case already, then in MOSS 2007, you just create a separate web app and attach the content db that contains the 2003 My Sites to it to upgrade. You could host them in the same web app initially for the migration and once they are over in MOSS 2007, you can migrate the My Sites into a separate Web App using stsadm commands (backup/restore or export/import).

  • Anonymous
    February 29, 2008
    I tried the backup/restore approach, but it seems that the personal sites on the new web app are not working, only see empty sites. Could you elaborate a little bit more on that?

  • Anonymous
    February 29, 2008
    Will the backup of the MySites from the migrated MOSS web sites have all the data needed for the MySites on the new Web App dedicated for the MySites?