Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have a Windows Server 2008 R2 machine that ends up being replicated multiple times a week for development purposes.

Each time the server is replicated, the machine name changes. This completely kills SharePoint, and since the alternate access mappings are no longer correct--fixing it is no easy task.

Is there a good way to sysprep/replicate a server that is running SharePoint without having to fix everything each time?

Thanks

share|improve this question

3 Answers 3

up vote 3 down vote accepted

Short answer: no.

SharePoint is very intollerant to host name changes. What you can do is install the binaries, service packs and language packs. As long as you don't run psconfig.exe you will be able to sysprep and clone that machine. After cloning script psconfig to ease provisioning.

share|improve this answer

I would script an unattended install of SharePoint that gets called from the answer file rather than trying to cram it into the image and work around whatever blows up. It's more scalable and agile that way.

share|improve this answer

I just did this and would like to document it for others.

  1. Using Hyper-V I copied a working SP VM VHD and created a new VM.
  2. Boot the new VM and change the computer name.
  3. Change the SP computer name.
  4. Connect to Central Administration.
  5. Rename Alternate Access Mappings

If on the other hand you would like to set up a SP VM for duplication, don't run the SharePoint 2010 Products Configuration Wizard. After you clone the VM for use, run the wizard. The wizard will create the configuration database. Reference

share|improve this answer

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.