Move WSS 3 site/content to another domain
We currently have WSS 3.0 running in domain A.Will bring up a new WSS 3.0 in domain B.Need to move site/content from WSS 3.0 domain A to WSS 3.0 domain B.No common user accounts between domain A and domain B.Just want to move the site/content over so that the admin in domain B has rights to all content. Then we will asign rights to user accounts in domain B to the content.I've tried using the stsadm utility with the -o export and -o import command. Basically, the admin account in domain B has no rights to the imported content, and I am locked out.Any ideas on how to make this work?
May 29th, 2008 6:54pm
Disclaimer: I am not aware if this works on WSS 3.0 - it was written for MOSS 2007 to move sites between site collections:
A quick and dirty solution could be to simply save the site as a template with content and create a new site based on it on the newweb application:
Step 1: Create Site Template
1. On the site that should be moved, navigate toSite Actions -> Site Settings
2. In the Look and Feel section, select Save site as template
3. Enter File Name, Template Name and Template Description
4. Make sure the Include Option is checked if site content should be included in the template
5. Click OK
6. When the template is saved, go to the site template gallery
7. Click the new site template and save it do disk
Step 2: Import Site Template
1. In the Site Collection that the site should be moved to, natigate to Site Actions -> Site Settings
2. In the Galleries section, select Site templates
3. Click Upload
4. Browse to the site template previously created
5. Select the site template and click Open and then OK
6. Review the Title and Description and click OK.
Step 3: Create a New Site
1. In the Site Collection that the site should be moved to, natigate to Site Actions -> Create
2. In the Web Pages section, select Sites and Workspaces
3. Enter Title, Description and URL
4. In the Template Selection section,select theCustum tab and select the imported site template
5. Make the appropriate Permissions and Navigation choices and click Create
Step 4: Test and Delete
1. Test the new site
2. If everything is correct, delete the site template in both site collections and delete the old site.
Cheers,
Christian
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2008 9:06pm
Disclaimer: I am not aware if this works on WSS 3.0 - it was written for MOSS 2007 to move sites between site collections:
A quick and dirty solution could be to simply save the site as a template with content and create a new site based on it on the newweb application:
Step 1: Create Site Template
1. On the site that should be moved, navigate toSite Actions -> Site Settings
2. In the Look and Feel section, select Save site as template
3. Enter File Name, Template Name and Template Description
4. Make sure the Include Option is checked if site content should be included in the template
5. Click OK
6. When the template is saved, go to the site template gallery
7. Click the new site template and save it do disk
Step 2: Import Site Template
1. In the Site Collection that the site should be moved to, natigate to Site Actions -> Site Settings
2. In the Galleries section, select Site templates
3. Click Upload
4. Browse to the site template previously created
5. Select the site template and click Open and then OK
6. Review the Title and Description and click OK.
Step 3: Create a New Site
1. In the Site Collection that the site should be moved to, natigate to Site Actions -> Create
2. In the Web Pages section, select Sites and Workspaces
3. Enter Title, Description and URL
4. In the Template Selection section,select theCustum tab and select the imported site template
5. Make the appropriate Permissions and Navigation choices and click Create
Step 4: Test and Delete
1. Test the new site
2. If everything is correct, delete the site template in both site collections and delete the old site.
Cheers,
Christian
May 29th, 2008 9:27pm
You can set the primary site collection administrator in Central Administration. This will let you specify an account that has site collection administrator rights to the imported site.
In domain B, open the Central Administration site. In Application Management, under SharePoint Site Management, click Site Collection Administrators. Enter an account from domain B as the primary site collection administrator. This account should now be able to browse to the site. Once there, you will need to set the permissions accordingly in Site Actions/Site Settings.
In addition to creating the site as a site template and moving it or exporting/importing, you can try performing a site collection backup and restore, and then modifying the permissions.
Backup the site collection in domain A:
Code Snippetstsadm -o backup -url http://server.domaina.com/sitecollection -filename sitecollectiona.bak
Create a web application and site collection on a farm in domain B.
Copy the site collection backup to an accessible place in domain B.
Restore the site collection backup to the farm in domain B:
Code Snippetstsadm -o restore -url http://server.domainb.com/newsitecollection -filename sitecollectiona.bak -restoremethod overwrite
Create a web application and site collection on a farm in domain B.
Copy the site collection backup to an accessible place in domain B.
Restore the site collection backup to the farm in domain B:
Code Snippetstsadm -o restore -url http://server.domainb.com/newsitecollection -filename sitecollectiona.bak -restoremethod overwrite
Set a site collection administrator: In Central Administraion, Application Management under SharePoint Site Management, click Site Collection Administrators. Enter an account from domain B as the primary site collection administrator.
Log onto the new site collection as the primary site collection administrator. Click Site Actions -> Site Settings (-> Modify all Site Settings depending on template). Modify permissions using the Site Permissions link.
Hope this helps.
Please don't hesitate to contact me if you have any questions.
Jason
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2008 11:30pm
Thanks guys. Did what Jason suggested, and it worked!!!I am now working on giving the new users in domain B access.David
May 30th, 2008 2:02am
Hey this worked fine, but when I try to setup Permissions it seems that I only have read-only permission. I'm not able to add or modifi access, any ideas?
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2010 4:16pm
Disregard my previous message. I was locking the site before backing it up, just to prevent users on doing modification while the backup was running. When I did the restored the lock was restored. I just went and unlock the site and it worked fine.
Thanks
April 5th, 2010 5:49pm
Hi Jason,
Thanks for your post, I followed all your steps and eventually stuck in while coping and pasting the commands into the command prompt but thanks to the other thread which advise
me to type the command by hand rather pasted from the notepad:-
Now I have taken up the back up of my intranet site i.e.
http://intranet.domainA.com which is 1.4MB in size (surprised me) which I successfully restored on my
http://servername.domainB.com
Then I realise that is not the actual intranet site which I had to move. Later I discovered
http://intranet.domainA.com is redirected to the
http://intranet.domainA.com/SITES/GWL
I took the backup of the site
http://intranet.domainA.com/SITES/GWL which is 3GB in the size.
I tried to restore the newback.dat (3GB) to the old
http://servername.domainB.com which ask me to create a new content and –overwrite in the end of our command, which I followed
But I didn’t get success..
the site got restored successfully but it didn’t get open, open with error some thing “Could not load file or assembly 'EasyTabParts PublicKey dependencies “
could you please help me ??
also do i need to follow these steps
SOLUTION:
1. Open a command prompt and navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
2. Run 'stsadm- o preparetomove -Site <http://whatevertheguiltysiteis/> -OldContentDb <GUID of the contentdb listed in event
log error>'
3. Run 'stsadm -o sync -deleteolddatabases 0'
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2010 10:56am