Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Just received snapshots vms from production (3 vm, 1 for app/ca/index, 1 for sql and 1 for wfe). They will be on same domain. (the new vm pc names are different than the one in production)

I ran the sp config wizard and it's still shows the production sql server.

What are the steps (either gui based or powershell) i need to go through in order to make this new dev instance to work.

share|improve this question
add comment

3 Answers

up vote 1 down vote accepted

I would say that creating a dev by cloning production environment, especially having the dev in the same domain, is not possible. You will have multiple servers with same SIDs in the domain, SharePoint can't tell which one is which...well, the domain cannot do it either.

What you can do is take database dumps from production, recreate the dev farm from scratch - then restore the content databases. Best step-by-step for setting up the environment is the installation manual/memo of the current production environment.

After (and before that) please review the Recovery guide from MSDN. It will instruct how to restore the farm databases, amongst other things.

share|improve this answer
    
the dev server named differently. would the above still apply? –  M. Todd Jan 24 '12 at 21:09
    
Can you specify how can it be different if it is a clone? I mean, the computer name and the unique identifier of the computer, SSID. –  Jussi Palo Jan 24 '12 at 21:18
    
Yes, the dev vm pc name is different. Actually, just learned it was a snapshot. –  M. Todd Jan 24 '12 at 21:20
    
The name of the dev VM host pc is irrelevant in this scenario. What matters is that you cannot have duplicate servers (virtual machines in this case) in the domain with same computer name. So, setting up dev environment as described in my answer is the way to go. –  Jussi Palo Jan 24 '12 at 21:38
    
Computer Names are different too. so does above still apply... –  M. Todd Jan 24 '12 at 21:47
show 1 more comment

If the setup you are running matches what I have, when you run the Configuration Wizard there should be an option in one of the first steps to disconnect from the farm. You would want to do that and then the next time you run the wizard it should allow you to specify a new farm to connect to.

Unfortunately I have seen in some instances where this option for one reason or another isn't available (I'm guessing stand alone versus farm install). Hopefully yours is a configuration where this option is available. Let me know if this works for you.

share|improve this answer
    
config wizard does not even give me disconnect from farm option. it gives me the sql server window (everything grayed out so i cant change the sql to new machine) then click next and config fails. –  M. Todd Jan 24 '12 at 21:07
    
In that case I would follow the advice given @Jussi Palo - provisioning new servers and restoring backups is the way to go. –  ToddersLegrande Jan 24 '12 at 22:14
add comment

Cloning an environment like this is harder than provisioning a new environment. You will need to get the servers detached from the existing farm and configuration database. You can then go through the process to provision a new farm.

share|improve this answer
    
Careful! Don't detach servers from the existing farm unless you're certain SharePoint doesn't get upset and think you've detached the real production server. I mean, will it know that you detached the clone and not the production server? –  Jussi Palo Jan 24 '12 at 20:59
    
Is there a good link that shows step by step process? –  M. Todd Jan 24 '12 at 21:05
1  
@JussiPalo One of the many reasons why I do not support this process. –  Mike Oryszak Jan 24 '12 at 22:17
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.