I would suggest reconfiguring a single machine and then
taking note of the Registry changes.
Depending on the order that you carry out the task - there
are two options to you.
1) Boot them onto the NT server, and use the system
policies to change the domain at the next logon. I can't
say for certain wether there is an actual ADM (probably
not), so running a script to change the appropriate
registry entry would be just as simple. If you want a "one-
hit wins" approach - then that's the way to do it.
2) My preferred method. Do the same as above but create a
script and a batch file to run it. Either copy the files
to the C: drive on each machine and reboot or run around
with a floppy disk. Because I have so many different sites
that I have to do things like this with different types of
networks, it's fool-proof.
As an aside, just remember to change the system policy
User-level access setting to the new domain with the
windows.adm file.
I hope this is useful to you.
John
>-----Original Message-----
>I'm just about to re-configure our network in a week or
>so and have just about everything in order to do so. But
>I have a question that maybe someone can answer. I'll be
>changing our Domain name and network OS from WinNT to
>Win2K. What I need to know is if there's an easier way to
>join all my machines to the NEW Domain other than
>physically going to each machine and doing so. The
>majority of my clients are Win98 but also have a few
>WinXP. Any help/advice is appreciated. Thanks in advance.
>.
>
|
Similar Threads
Linear Mode
