Ghosting Win2K3 to new disc (AD error)

[Stu]

My windows 2003 server had a 12Gb disc. I needed more space so bought a
150Gb disc. I had thought that all I would need to do is ghost (v 2002) the
entire old disc to the new disc and then plug in the new disc as the pri
master. But after booting from new disc I get:
ISASS.exe
Security Accounts Manager initialisation failed because of the following
error: Directory Service cannot start. Error Status 0xc00002e1. Please
click OK to shutdown this system and reboot into Directory Services Restore
Mode, check the event log for more detailed information.

So I reboot and choose DSR mode. I logon....wait.....status says rebuilding
active directory indices.....wait......status says applying
settings......wait......status says logging off.....wait.....presented with
logon screen again (repeat last sentence as often as you like).

Ive read that this problem is likely caused by insufficient permissions on
%windows_drive%, but I cant logon to fix it! I have granted admin full
control from my workstation (thru mapped drive). I have granted admin full
control from win2k3 server with old disc as pri master. Neither worked!

Any ideas?

Cheers
Stu

 

[Guest]

I had a problem ghosting Win2K disk to disk once, when I swapped to the new disk I got errors which basically amounted to an inability to find the C Drive

I think my mistake was to connect the new drive and format it with NTFS from my existing Win2K system, which also wrote a signature to the disk, then I shutdown and use ghost to transfer to the new partition. When I removed the original disk and put the new one in the system, the OS recognised the hard drive from the previous run, probably via the signature and decided it was the D: drive and not the C:, so I couldn't log in as the system couldn't find the SAM files and I got lots of rebuilding file messages too

I put the original system back in without the new drive, then shut down, added the new drive again and used a win98 boot disk to startup, wrote a new MBR and blew away all the partition info on the new disk then used ghost to copy the data and let it create it's own partition. Then I removed the original disk and put the new one in it's place

On reboot it worked fine but it had me pulling my hair out for a few hour

Don't know if this will solve your problem but it might help

 

[Stu]

I put the original system back in without the new drive, then shut down,
added the new drive again and used a win98 boot disk to startup, wrote a new
MBR and blew away all the partition info on the new disk then used ghost to
copy the data and let it create it's own partition. Then I removed the
original disk and put the new one in it's place.

Sounded promising, but just tried it and get same error message!

Any other suggestions?

Cheers
Stu

 

[Guest]

oh well it was worth a try, sorry it didn't work ou

You could try with a disk copy instead of a partition copy, clutching at straws a bit now tho

 

[Stu]

I actually have not tried a partition copy! Ive only tried mirroring the
entire disc. Is it even worth trying partition copy if disk copy doesn't
work?

Cheers
Stu

oh well it was worth a try, sorry it didn't work out

You could try with a disk copy instead of a partition copy, clutching at

straws a bit now tho

 

[Stu]

I put the original system back in without the new drive, then shut down,
added the new drive again and used a win98 boot disk to startup, wrote a new
MBR and blew away all the partition info on the new disk then used ghost to
copy the data and let it create it's own partition. Then I removed the
original disk and put the new one in it's place.

How did you create a new mbr? fdisk/mbr ? How do you specify which disk?

Chers
stu

 

[Stu]

Just thought: With my old drive the windows drive was G: If I do a ghost
disk image will the new windows partition still be G:? What if ISASS is
looking for AD on C:? Anyone any ideas?

Cheers
Stu

 

[anonymous]

Hi Stu,

When I use Ghost to clone my 3 partition drive, which are C/D and E, to
a second drive, the backup drive is "temporily" given the letters G/H
and I. When I take the backup drive and swap its jumpers so it's the
primary, its letters change to C/D and E just like the drive I cloned.
Everything works just as it did before swapping the drives. A clone
seems to be exactly that, an exact copy of the originating drive.

---==X={}=X==---


Jim Self
AVIATION ANIMATION, the internet's largest depository.
http://avanimation.avsupport.com

Your only internet source for spiral staircase plans.
http://jself.com/stair/Stair.htm

 

[Stu]

Everything works just as it did before swapping the drives. A clone

seems to be exactly that, an exact copy of the originating drive.

Thats what I expected! Thats what usually happens! Any ideas why I would
get the problems described?

Stu

 

[joust in jest]

Stu:
You need to visit an Active Directory newsgroup for answers to this problem.
AD is never happy about having the HAL changed in mid-stream.

steve

 

[Stu]

Trying AD newsgroups.

Stu:
You need to visit an Active Directory newsgroup for answers to this problem.
AD is never happy about having the HAL changed in mid-stream.

steve

permissions

 

[Jason Robarts [MSFT]]

Imaging of DCs is not supported. You should restore from backup.

Jason

 

[Jetro]

Stu,
Connect the registry remotely, delete everything from
HKLM\System\CCS\MountedDevices, and reboot.

 

[Stu]

Imaging of DCs is not supported. You should restore from backup.

I take it DC = Domain Controller?

Ok. Is there a way to get round the error? I dont mind loosing the domain
setup since it is only for 3 users.

Cheers
Stu