Cloning Windows/XP: Difference between revisions
From DWIKI
No edit summary |
m (→frisbee) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Steps to take = | = Steps to take = | ||
* Remove system to clone from domain | *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 = | ||
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. | 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. | ||
| Line 12: | Line 31: | ||
*[http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999070716282425 Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer] | *[http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999070716282425 Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer] | ||
*[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://www.dominok.net/en/it/en.it.clonexp.html Forking a XP-installation] | |||
*[http://gparted.sourceforge.net/ gparted] | |||
=Notes= | |||
==fetch <url> | tar xf -C /ntfs== | |||
==partimage== | |||
==frisbee== | |||
*[http://www.cs.utah.edu/flux/papers/frisbee-usenix03-base.html Fast, Scalable Disk Imaging with Frisbee] | |||
Latest revision as of 19:10, 20 October 2008
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
- Windows XP Cloning or Universal system installation
- Deploying Windows XP Using Windows Product Activation
- Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer
- Using sysprep
- Using partimage for cloning
- Forking a XP-installation
- gparted
