Monday, November 15, 2010

Cloning Windows Server 2008 R2: Use Sysprep (no more NewSID)

Changing SID does matter, as you will learn reading this: Cloning Windows Server 2008 R2: Use Sysprep (no more NewSID): "It is not uncommon for system administrators to clone virtual servers or take an image of physical servers running Windows Server 2008 these days. There are plenty of tools to do that these days (Ghost, Acronis, Platespin for P2V conversions, etc.) If this is something you do regularly then you won’ ..."


  1. When running Sysprep on Windows Server 2008 R2 Enterprise Edition with windows updates and Microsoft updates turned on and .NET 3.5 sp1 installed and McAfee installed with all updates until 30/1/2011 set to generalize it just reboots on restart.

  2. Have you done a sysprep on virtual machine running off a SAN before? Ever notice how long it takes?

  3. I may need a bit of help. My system appears to have blown up after running OOBE. I thought I was fowling the steps outlined on the site.
    1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
    2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
    3) Tick the ‘Generalize’ option (this resets the SID)
    4) Select ‘Shutdown’ from the Shutdown Options.
    5) Once the machine has shutdown, take your image and you are good to go!
    I ran it and it appeared to be working until the reboot. It restarted and said ( Setup is starting services) then I get the install windows error ( Windows could not complete the installation. To install Windows on this computer, restart the installation. ) Hit OK then screen says.
    (Setup will continue after restarting your computer.)
    Then I get the same install windows error.
    So what did I miss? I have no server anymore. How do I recover?
    Please help. I really need this system to work. Or at least reboot into its normal server mode.

  4. Anonymous: depends on the san and other hardware of course.

    Tim: I am getting this error too. There must be a log file in there somewhere that will show what's going wrong.


Related Posts Plugin for WordPress, Blogger...