How to removing forcibily child domain in win2003 Active Dir

Hey Smurf
As I mentioned that I fromat the child domain server before removing the entries so when i followed the steps given in link
support.microsoft.com/kb/230306
I was able to do the steps howeve when i reached to step 5 and 6 (5. Type: metadata cleanup, and then press ENTER.
6. Type: connections, )
I was unable to go beyond this is and got an error
'Connections' is not recognized as an internal or external command,
operable program or batch file.
(may be becoz the child domain did not exist at this poin of time )
so I was unable to go beyont this step and was stuck .

Hmm thats strange i have never come across that problem before.

Atleast you got it fixed

Thanks for sharing

Wayne

ANYTIME Smurf :lol:

'Connections' is not recognized as an internal or external command,
operable program or batch file.
(may be becoz the child domain did not exist at this poin of time )
so I was unable to go beyont this step and was stuck .

On what basis did you come to the conclusion that because 'Connections' is not recognized as an internal or external command, operable program or batch file, that it could be because the child domain did not exist at this point of time?

Hey FallenZer0
I appriciate ur question but i would like to inform u that I faced this situation in production enviroment and SLA was 2 hrs. and at that point of time I was the only person to work upon this issue (My Administratior is on vacation) so I did not get enough time to try and research on this issue .
I followed all the above mentioned sites but was unable to resolve the situation ..... I believe it was too early to reach to conclusion
I will try this is my lab and will share the results with u guys ....and if u cn try this and get to know any thing new plz share with us

Hi Kingofzombis,

I think what FallenZer0 was a little confussed about (as was i) is that the error that you indicated is that of when you try to run a program from the command prompt and its not a recognised file to execute.

The only thing i could have thought would account for this is if you somehow went out of the ntdsutil command shell back into the dos prompt.

Since its fixed now suppose it doesn't really matter but please do let us know how you get on in your test environment.

Regards

WAyne