First demote ur bravo and join it in workgroup anname it bravo1 , now change kilo name as bravo , and promote it as a DC . ok now join bravo1 to domain and copy all files and folders as u mentioned above .

As long as do not touch permissions they will remain intact . and in the end u can the ip address as u mentioned above between kilo and bravo which is now bravo1 .

IF you're running Server 2003, AND your domain is running in Server 2003 functional level, you CAN rename a DC (you can just use the GUI as usual, not even a need for netdom).
Just make sure you rename the sysvol member object to avoid later confusion:
You Must Rename the SYSVOL Member Object to Rename a Windows Server 2003 Domain Controllerhttp://support.microsoft.com/?kbid=316826
The best method to actually do this depends on whether you want to keep the old bravo (future lima if I understood you correctly) as DC, or if you want it to be just a member server.

amitspeedstar,
if bravo is arahming's only DC, your advice will cost him his domain ...

My comment about "The best method to actually do this depends on whether you want to keep the old bravo (future lima if I understood you correctly) as DC, or if you want it to be just a member server." was actually a question.
Anyway, since this is your only DC (and probably running DNS), I'd recommend the following:
1. let kilo point to bravo as the only DNS server in TCP/IP; install DNS on kilo, but do NOT create any zones.
2. if you haven't done so already, change the DNS zones on bravo to AD integrated.
3. dcpromo kilo; the AD integrated DNS zones should appear automatically on kilo.
4. change the DNS settings in TCP/IP on bravo and kilo to point to itself as primary, the other one as secondary.
5. run netdiag and dcdiag to make sure everything is okay.
6. Make kilo a GC, and move the FSMO roles to kilo (see links below)
7. run netdiag and dcdiag to make sure everything is okay.
8. for the sake of completeness, transfer the Licensing server to kilo (AD Sites and Services, right-click "License Server" in the right pane, choose Properties, move it to kilo).

If you do NOT want to keep bravo as DC:
9. change the DNS settings in TCP/IP on bravo to point to kilo as only DNS.
10. dcpromo down bravo (which will remove the AD integrated DNS zones from bravo), rename it to lima.
11. check AD sites and services and remove bravo entries; remove any SRV entries in DNS referring to bravo that might have survived.
12. rename kilo to bravo, rename the sysvol object.

If you *want* to keep bravo as DC:
9. rename bravo to lima, rename the sysvol object.
10. rename kilo to bravo, rename the sysvol object.

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server.
We would only need to create and run scripts using thi…

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …

In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…

In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB.
To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…