NT4 system partition cloning-effects of NOT using sysprep
Posted on 2004-04-17
i just upgraded an old NT4 box that was still running a 40gb drive with a FAT32 system partition at 2gb. this is the primary domain controller for a small (12 users) office.
my upgrade was basically a new 80gb drive with an 8gb NTFS system partition.
for a little background on the steps i took:
on another box running W2KPro, i installed the new 80GB drive and partitioned out 8gb as FAT32, and 35gb, 5gb, 32-ish GB as NTFS. i pulled the 40gb master drive from the NT4 box, popped it into this W2KPro box as a slave. booted into W2KPro, i then ghosted the 2gb FAT partition to another external drive. then i restored the image to the new 8GB FAT32.
note: i'm not sure if i could have ghosted the FAT32 image to an NTFS partition, hence the FAT32->FAT32. the convert command didnt take that long, so i figured i'd save myself a potential headache.
so, as inferred above, i ran c:\> convert e: /fs:ntfs (where e: was the 8GB FAT32 partition i just restored from a ghost image)
i pulled the new 80GB drive from the W2KPro box and put it back in the NT4 box as PRI-MAS. hit the power button and everything booted up fine.
so, my question is: what are the ramifications of not running sysprep.exe as ms suggests?
i noted a line in the sysprep readme.doc that specifically stated that sysprep is NOT for use with a primary domain controller. this is what prompted me to see what happened by cloning on another machine.
any insights as to why i should not trust this partition now will be welcome. thanks.