Renaming a domain is tricky. One method you could consider would be to install one of your new machines initially as an NT machine (BDC in your AD domain) and follow the instructions in Technet article 292541. This will only work, however, if yourcurrent Win2K DC is in mixed mode rather than native mode. The other way would be to migrate your current domain into a new one. In this case, you would set up one of your new servers as the first DC in the new domain, then migrate your user and computer accounts to the new domain. Then, you would demote the old DC from its old domain and then promote it again as a DC in the new domain.
In either case, the best way to preserve user profiles would be first to change to roaming profiles so that all your current user profiles are stored on the server. Then after migration, continue to use the roaming profiles or, if you don't want to do that, at the least you will have a copy of all your user profiles on the server and can return them tolocal profiles by copying them back down to the workstations under the new domain user IDs. If you start out with roaming profiles, they will be automatically cached to the local workstation profiles folders the first time the user logs on to the workstation with the new domain user ID. To return to local profile use, you would first remove the setting for roaming profiles from the user IDs. Then at each workstation log on as the user, creating a new local profile; then log on as Administrator and copy the locally cached copy of the roaming profile to the newest profile folders for that user on the local workstation.