Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Moving Sharepoint WSS3.0 from old domain to new domain

Posted on 2013-01-03
33
Medium Priority
?
1,515 Views
Last Modified: 2013-01-06
Hello experts!

I have  a virtual machine that was running sharepoint wss3.0 on a win2003 std guest.
This sharepoint site was in a domain that no longer exists  called domain A (so we dont get confused) it had an ip address of 192.168.0.22

I'm trying to get the sharepoint site to work in a new domain called domain B (hopefully on 192.168.1.22)

I've setup a new domain and installed vmware workstation 9 on a physical win 2008 r2 server.
I've then managed to start the virtual machine on this host.
I can login to the guest using the old domain A username and password.

whats the best procedure to get sharepoint accessible in the new domain B?
and how do i link it to the new AD in Domain B?
0
Comment
Question by:ukwebdzine
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 20
  • 13
33 Comments
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38740309
I might have found the answer!

http://sharepointapplied.com/2009/02/04/move-sharepoint-to-a-new-domain/

Any tips and hints when performing a sharepoint domain move?
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38740340
the previous link needs you to setup sharepoint from scratch  and then migrate the data.

Is there a way to do it like move to workgroup, then add to new domain and connect ? or am i dreaming?
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741006
I assume everything, including SQL is on this machine?  

You could either create a new farm on a server in the new domain, and migrate your databases over.

Or you could disjoin the current server from the current domain, and add it to the new domain.  This would require that you go in and adjust all your SQL level security and SharePoint service accounts to be accounts in the new domain.  

Either way, lots of work ahead of you.
0
Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741060
Yes Everything is on this virtual machine

I've never installed sharepoint and my SQL knowledge is zero.  
The new domain is already setup with all the same usernames as the old domain. so if I get some SQL techie to help then this should be the easiest route?
0
 
LVL 38

Accepted Solution

by:
Justin Smith earned 2000 total points
ID: 38741082
There will still be work to do on the SharePoint side as well.  You'll have to adjust service accounts then run a command to migrate all the users on your site to the new domain.

I'd make sure you have a local account that is specified in SQL as a sysadmin, so you'll have a backup account to log in as after you move domains (just in case you couldn't log in with an account from the new domain).

Here is a good guide: http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741374
Thanks ACH1LLES working on that guide right now
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741477
I'm at this stage in the above guide

1. stsadm -o updatefarmcredentials -userlogin CONTOSO\ServiceAccount -password NewPassword

I understand that I change CONTOSO\ServiceAcount to MYDOMAIN\MyNewServiceAccount
but what is the password NewPassword refering too?
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741482
The password for your service account
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741505
aha this worked

stsadm -o updatefarmcredentials -userlogin MYDOMAIN\MyServiceAccount -password MypasswordforMyServiceAccount

but I got this msg

To ensure that all credential caches in IIS have updated, you must run the comma
nd "IISRESET /NOFORCE" on all servers in the farm.  This should be done after all credential updates have been completed.
Operation completed successfully.

looking good?
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741513
yes.  So thus far you've changed the server's domain, updated SQL permissions, and updated service accounts in SharePoint?
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741526
Yes, but . . . . .

stsadm.exe -o spsearch -farmcontentaccessaccount MYDOMAIN\MyServiceAccount –farmcontentaccesspassword MyServiceAccounPassword

gets a command line error????
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741538
Don't worry about that one, you can change it in Central Admin.
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741548
phew!!

skipping step 5.5 and 5.6 as Im using wss3.0

onto Step 6: Confirm Site loads:
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741574
I can open the Sharepoint 3.0 central administration webpage no problem

http://mysharepoint:4527/default.aspx


but  when going to http://mysharepoint/

I get

Go back to site  
Error: Access Denied
 
 Current User  
You are currently signed in as:  MYDOMAIN\administrator  
 
Sign in as a different user
Request access
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741582
if I click sign in as a different user and use MYDOMAIN\MyServiceAccount I can get to the sharepoint site hooraaaahh!!!!1
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741593
Step 7: Migrating User Accounts:

Warning: Before you begin ensure that we have migrated all the AD user accounts to the new domain


This cannot be achieved as the old domain and AD is long gone

I have setup all the old domain usernames in the new domain with same passwords and usernames.

will this get me through step 7??
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741621
Go ahead with STep 7, it doesn't matter if the old domain is gone.  This command is change account names in the content database, it doesn't even contact the old domain.

If you need to run it for lots of users, this blog can help:  http://blogs.msdn.com/b/sowmyancs/archive/2012/01/07/migrate-users-groups-powershell-script.aspx?PageIndex=2
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741670
ok

I'm working through the 30 users I need sorting ASAP

There are old users in the old domain and in sharepoint that have left the company.

Do I need to recreate their accounts in the new domain and perform:-

stsadm -o migrateuser -oldlogin DOMAIN\user -newlogin DOMAIN\user -ignoresidhistory

for them to tie in their posts and reports??
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741676
If they no longer exist, I wouldn't worry about it.  THe content will still be there.
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741695
ok thanks

Just setting up groups in AD and then I'll execute

stsadm –o migrategroup –oldlogin Domain\group –newlogin Domain\group

this is worth more than 500 points !!
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741701
LOL, I hope it works out for you.  If you ever need remote support, I'm available for hire.


______________________________________________________________________
Follow me on Twitter!  @justinsmith317
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741721
all the group i set up in new AD Domain match the ones in Sharepoint but the

stsadm –o migrategroup –oldlogin MyDomain\group –newlogin MyNewDomain\group

gets a command line error
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741724
Also is there anything i need to do in central admin to finalise this?
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741739
What is the command line error?  This command didn't come around till the August 2009 CU.  Possibly you don't have this installed.  In Central Admin go to Operations - Servers in Farm and tell me the Farm Build Number.

In Central Admin you need to verify all your service accounts and web app pool accounts are running as accounts in the new domain.  This is in Central Admin - Operations - Service Accounts.  You should also go to Central Admin - Operations - Services on Server, click on the Search Service, and assure all is well there.
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741788
Farm build number = 12.0.0.6421


In central admin - Operations -service accounts

I have a  dot  in  Windows service. but nothing to pick from in the drop down box

In web application pool  I can select  'windows sharepoint services web application' from the dropdown box

and 'application pool' drop box I can pick sharepoint -80

then select an account
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741819
i can access the site from a user on the new domain

the search facility brings up no items for things i know are there

in central admin the Service Account is set to the new account I used in the guide MYDOMAIN\MyNewAccount

in central admin the Content Access Account is set to the new account I used in the guide MYDOMAIN\MyNewAccount

the search database uses windows authentications and the database server and database name look good too



* going back to the group migration error - it doesnt give any error just says Commandline error. then gives every usage of stsadm.exe under the sun!
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741836
Leave search to last. Verify that your users can access their stuff first.
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741844
they can access everything :)

just no search results
0
 
LVL 1

Author Comment

by:ukwebdzine
ID: 38741854
time to head home now as I've been working for 13 hours

Will be back tomorrow  


many thanks for your awesome help ACH1LLES  \o/\O/\o/
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741857
Run crawl. Stsadm -o spsearch -action startfullcrawl
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741922
Correction:        Stsadm -o spsearch -action fullcrawlstart


____________________________________________________________________
Follow me on Twitter!  @justinsmith317
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 38741946
Yeah you are on SP2, which doesn't have the migrategroup command.  You'd need at least the August 09 CU, or you could just deploy SP3.



__________________________________________________________________
Follow me on Twitter!  @justinsmith317
0
 
LVL 1

Author Closing Comment

by:ukwebdzine
ID: 38749531
many thanks for your excellent knowledge and prompt replies.
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question