VMware vSphere

 View Only
  • 1.  Clone production Windows 2003 server

    Posted Aug 01, 2013 06:52 PM

    I would like to clone a domain joined windows 2003 server, but I'm unable to run sysprep on the clone because it's domain joined, and I don't want to take it out of the domain and effect the production server.

    I need to do some testing and don't want to mess up the production server so basically I need another copy of the server added to to the domain with a different name/sid etc.

    Thanks for your help.



  • 2.  RE: Clone production Windows 2003 server

    Posted Aug 01, 2013 06:56 PM

    What happens if we run a sysprep on cloned machine ? Which option of customization you are selecting.

    Refer this VMware vSphere 4 - ESX and vCenter Server

    VMware KB: Windows SID needs to be changed after copying a virtual machine directory  



  • 3.  RE: Clone production Windows 2003 server

    Posted Aug 01, 2013 07:07 PM

    I'm selecting

    Reseal, and Shut Down. 

    Don't reset grace period for activiation, don't regenerate security identifiers, and detect non-plug and play hardware are unchecked.

    I get a message saying sysprep is unable to run because it's joined to a domain.



  • 4.  RE: Clone production Windows 2003 server

    Posted Aug 01, 2013 08:03 PM

    I ran SP2 on the machine, it ran fine.  After the reboot I ran the Sysprep from the Deploy.CAB on the SP2 cd, and now it's saying

    "There is an incompatibility between this tool and the current operating system.  Unable to continue"



  • 5.  RE: Clone production Windows 2003 server
    Best Answer

    Posted Aug 01, 2013 08:18 PM

    Wow, it's running now...

    I had to remove File and Print Sharing for Microsoft Networks service, then restart the server service, and then sysprep ran !

    finally