We have cloned the SharePoint 2010 Production environment(Company Portal, around 3500 users) using VMWare clone feature. The purpose is to Create a Test environment for Restructuring the content, Quality assurance etc.,
The Prod environment consist of WFE, APP server and Database Server.
All the 3 Machines are assigned a new names and IP Address re-configured. These machines are also isolated in VLAN so they don't communicate to any machines on the network but they can communicate with each other in VLAN. I have also got RDP access so that I can do my configuration work.
What steps do I need to follow to configure these machines and start the portal.
1) The service accounts used by service application & app pools are still referring to the domain and since the machines are disconnected from domain app pool is not starting.
2) Do I need to create a new Domain controller, Service account within the isolated VLAN and connect these machines or Should I bring a copy of Domain Controller, Active directory and use it in VLAN. My system admin told that it's not best practice to clone DC, AD and use it in VLAN.
3) How do I configure the SQL Server machine.
4) How Should I configure the Central admin, WFE and Service Application and point to the cloned Database server. Can this be done in CA or do I need any powershell scripts. Do I need to run Rename-SPServer command to rename the server? Does it change the database server name as you can see here it still refers to the Actual prod database. How do I change this.
5) Once reconfiguration is completed we have plans to connect this machines back to the Domain.
Your help is much appreciated.
I'm going to remove the clone machines from VLAN and follow these steps to configure the Cloned server. The reason is i'm unable to get the copy of the cloned AD or access to AD from VLAN.
Shut down production servers
Join the cloned machines to Domain and reconfigure IP Address. Port should be opened from WFE, App Server to the SQL Server machine.
Do I need to run Rename-SPServer or Stsadm command on both WFE and App Server. Not sure at this stage. Is the "oldservername" attribute is the name of the Database Server or App server... I tried this command in my development VM and it actually changes the DataSource connection string to the new Database Server. (Search for configdb in windows registry using regedit command)
Run the configuration wizard on App Server(Central admin) again and provide the clone sql server details and configuration database name.
Take a backup of content database and restore with different name.
Run the configuration wizard on WFE and join the WFE to the Clone server farm(App Server) 6.1) Repeat step 3 here… Not sure???
Mount the new content database.
Change alternate access mappings.