reference articles

sysprep on esx	link
changing the SID on a clone	Link sysinternals

Background;

Virtualization and disaster ecovery have driven the need for cloning machines. Often this is done to simplify provisioning of new servers as well. When cloning machines for this purpose, it is necessry to change key components to prevent software and network issues:

1. Active directory conflicts
2. MAC address issues
3. Software licensing issues

In a cases where the clone is done for disaster recovery, the system should be kept intact, with as few changes as possible. It should be noted that most P2V tools (vmware, symantec, acronis , provide a means to support  keeping the orginal server identity, but here are some guidelines and hints;

1. when working with clones machines, do not start them on the network. (this will prevent software problems when application access network resources)
2. If a machine will be used for DR, make sure processro identification, mac addresses and SID 's are preserved.
3. Document NIC card/network configs prior to cloning. Unless you convert to the exact same hardware, the network config will be lost when the driver for the NIC card changes.
4. Drivers; pre-install drivers for the destination hardware if possible.
5. Do not clone accross architectures; CISC to RISC, AMD to intel (particularly for 64 bit)
6. In most cases, systems with OEM OS licenses will not clone. The licenses must be upgraded to retail or volume 1st.

Notes;

• For Vmware cloning of windows machines, use sysprep (for 64bit OS's, the Newsid tool will work better)
• sysprep install for vmware;
  • for esx, the sysprep files go in this directory; " C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep "
  • for vmware virtual center ; " C:\Program Files\VMware\VMware VirtualCenter\resources "

notes; sysprep tools from msft;

1. System Preparation tool for Windows Server 2003 Service Pack 2 Deployment
2. Windows XP Service Pack 2 Deployment Tools
3. System Preparation tool for Windows Server 2003 Service Pack 2 Deployment (x64)
4. Windows Server 2003 Service Pack 1 32-bit Deployment Tools
5. Windows 2000 Service Pack 4 Network Install for IT Professionals