Home / server / Questions / 327975
Accepted
Brad
Asked: 2011-11-05 13:21:54 +0800 CST

SharePoint crashed after sysprep

  • 772

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

sharepoint windows-server-2008-r2 sysprep

3 Answers

  1. Best Answer

    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.

    • 3

  2. 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.

    • 0

  3. 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

    • 0