Sharepoint 2013 Topology Broke Down

Question

Almost three years ago i installed Sharepoint 2013 Enterprise for test purposes and i didn't planned very well the topology so i prepared one server as a web server and used TFS database server as database server. Everything had worked well and we started to use it instead of just testing.

One month ago our windows administrators created another Active Directory domain and moved our clients and users. But all other systems like TFS and Sharepoint were left at legacy domain. Both of the systems were working like a charm, only we had to use our legacy domain accounts to login them.

Two days ago i decided to move TFS from legacy domain to new domain, i followed the instructions and moved. But i forgot that Sharepoint was using same database server. Due to SQL Server login problems Sharepoint stopped working. Now i have been strugling with Sharepoint to bring back it life.

I tried to update connection string manually via registry or stsadm but it didn't worked. Then, I moved Sharepoint web server to new domain too and changed the service accounts and application pool accounts according to the new domain but it didn't helped me.Also I changed SQL Server logins and rights according to the new domain in database server.

Now i cannot find a way to recover Sharepoint. There are lots of data and files in databases so it is very important for me. I am not sure that if i install a new instance of Sharepoint 2013 and attach old conent databases with configuration database.

I hope you can guide me to solve my problem.

PS: Full system backups of TFS and Sharepoint before moving new domain are existing.So I planned to restore backups to new servers and try to backup data in Sharepoint, if i cannot find a way to fix this problem.

Answer 1

I think you miss the train and now the only option is rebuild the farm on new domain.For rebuilding you have to two options.

Options 1 as you TFS DB server still have all the content DBs..

• build a new farm on new domain
• Create & configure all the web application & service applications
• Now attach the old content DB to right web app.
• Now you have to run the migrate user against each user, because all the ids belong to old domain. But if you have trust between old and new domain then ids will work.

Option #2

• Build new farm on new domain.

• restore the farm backup you had before the moving the server.

.