Cloning Windows/XP: Difference between revisions

From DWIKI
No edit summary
No edit summary
Line 7: Line 7:
*copy sysprep.exe, setupcl.exe, setupmgr.exe, factory.exe, deploy.chm and ref.chm to C:\Sysprep
*copy sysprep.exe, setupcl.exe, setupmgr.exe, factory.exe, deploy.chm and ref.chm to C:\Sysprep
*run C:\Sysprep\setupmgr.exe
*run C:\Sysprep\setupmgr.exe
*select "sysprep setup"
**create new
**sysprep setup
**not fully automate
**prompt end user for admin pass
**log in as admin 1 time
**after filling everything in the dialog hangs, this is normal, just cancel
 
*run sysprep
**Use mini-setup
**make sure it will regenerate security identifiers
**reseal




Line 22: Line 32:
*[http://www.geocities.com/kilian0072002/sysprep/sysprep.html Using sysprep]
*[http://www.geocities.com/kilian0072002/sysprep/sysprep.html Using sysprep]
*[http://pittman.ws/articles/howto/partimage.html Using partimage for cloning]
*[http://pittman.ws/articles/howto/partimage.html Using partimage for cloning]
*[http://www.dominok.net/en/it/en.it.clonexp.html Forking a XP-installation]
*[http://gparted.sourceforge.net/ gparted]

Revision as of 10:25, 13 September 2006

Steps to take

  • Remove system to clone from domain
  • turn off Encrypting File System (EFS)
  • create a folder named C:\Sysprep
  • find SUPPORT\TOOLS\
  • doubleclick on DEPLOY.CAB
  • copy sysprep.exe, setupcl.exe, setupmgr.exe, factory.exe, deploy.chm and ref.chm to C:\Sysprep
  • run C:\Sysprep\setupmgr.exe
    • create new
    • sysprep setup
    • not fully automate
    • prompt end user for admin pass
    • log in as admin 1 time
    • after filling everything in the dialog hangs, this is normal, just cancel
  • run sysprep
    • Use mini-setup
    • make sure it will regenerate security identifiers
    • reseal


Sysprep

sysprep is needed to ensure uniqueness of SID ( Security IDentifier). If these are duplicated only one system would be able to join a domain. Another solution is using SID changer.


Links