Changing Domain in W2k Clients

Well, you can run the old NET COMPUTER command to add machine names to a Domain Controller.
You could put the names of the machines in a spreadsheet, all in a single column. Then, in the column in front of these names, put in:
NET COMPUTER

And in the column after the computer names, put in:

/ADD

Then Save As the whole thing as a Unicode TXT file.

Ok, now you have a text file with all of this info. The problem is that the file will be Tab delimited. That is easy to fix also.

Open the file in Notepad. Highlight one of the tabs (just Shift+Right Arrow key between COMPUTER and the \\machinename in the first row to hightlight a TAb) and Copy it.
Ok, now go to Edit -> Replace.
Paste the Tab in the Find What box. In the REplace With box, put a single Space.

Click Replace All.

Watch it run!!!!

When done, you should have something similar to this:

NET COMPUTER \\MACHINE1 /ADD
NET COMPUTER \\MACHINE2 /ADD
NET COMPUTER \\MACHINE3 /ADD
etc.

Save the file as a .BAT file (replacing the .TXT extension).

Now, copy/paste this new BAT file onto your domain controller.

Now, double-click it!

Voila! That's it.

hope this helps

Thank you for your help ,the other problem is how can i change the domain on the w2k clients ,now they part of x domain ,want it to be part of y domain ,is there a way to automate that ,local groups settings to have new domain damins in the local admin group of the client.
Thanks again

When you change the domain on the clients, the Domain Admins group for the new domain will automatically update on the client's Administrators local group. However, it sounds like the only (and best) way to automate this (so you don't have to sit down at EVERY client and make the change) is to purchase a Windows scripting program. Our company uses WinBatch. It's fairly easy to use, it does require some self-training though. If you can successfully create and test a script, you can then deploy it using domain login scripts (ntuser.bat). Of course, you'll first want to build and run the batch file Mr. Moore wrote about, to first add the machines to the new domain. Hope this helps.

This question was auto closed due to inactivity