Win2k Domain Merging

[C M]

Hi,

I need to merge two networks, they are both Win2k & Active Directory.
One uses fixed IP Addresses (Domain1) and the other uses DHCP (The PDC is a DHCP Server - Domain2)

I am planning on demoting one PDC (Domain2) to a Member Server then placing it into the main Domain (Domain1).
Then configuring it's clients to look at Domain 1 i am thinking that because this thing is a DHCP Server the clients and Server can still use DHCP whilst in the Fixed IP Domain?

Or do i need to give the PDC of Domain2 a fixed IP then it's clients can use DHCP from there?

Any Suggestions?

I hope what i have explained makes sense.lol.

Thanks,

CM

[ZOT]

You can go either way, but converting all to DHCP would be a bit easier and most likely faster.

DHCP Servers need a fixed defined address.
In fact, it is good practice to define addresses for all servers on DHCP network (and add reservations for others <- what I mean is you don't need reservation for self).

Any system set for DHCP should have no problem obtaining an address from the DHCP server.

Fixed addressing on all is a real pain to keep up with.

Depending on IP schemes, should be an easy conversion either way you decide to go.



WOW - Junior Member Status Again!, 4th time since 1998

[Silicon Scream]

This post was also made in the networking forum. Since it should be here (the 2K forum), here's a copy of what I typed over there should C M never have another look.

Okay, this is a good question, but overall...pretty easy to answer and implement.

Before merging...

1) Make sure that you migrate your user accounts from domain 2 into domain 1 so they will still be able to logon after the migration. If you don't have many users, you may just want to make all new user accounts for any users coming over from domain two.

2) What are the users IP Addresses in Domain 1 now, (before you migrate) ? Static or Dynamic? Would you like to use all dynamic addresses for ALL clients after the migration? You didn't specify this in your question. I RECOMMEND ALL DHCP (except for any reservations you need to make on say another member server etc...). Oh, and obviously the DHCP server needs to be static along with the domain controller as well.

a) If yes, Ready all Domain1 clients to use DHCP.
b) If no, simply leave the domain one clients as
they are now, and you should be fine

Merging...

3) After reducing the Domain2 domain controller to a 'Member Server' and adding it into Domain1, you need to make sure the IP Addresses that you're handing out from the DHCP server are on the same subnet as your other computers already in domain 1. Be sure to RESERVE any static IP Addresses of computers on your network so none of your DHCP clients will get them issued. Otherwise, you're looking at IP Address conflicts. Also, don't forget to setup the new DHCP settings to reflect the new domain controller etc... Keep in mind, if you start using multiple subnets on the same network, things can get complicated quick depending on how you're setting up routing etc..

In a nutshell, that's pretty much it. Of course, there's other things that are involved depending on how much you want of what you had in Domain2 to be carried over into Domain1 ie. group policies etc...

Perhaps a little more info on the amount of users, computers and your present location setup ie two offices, to countries etc...

[C M]

want all the current machines in the Domain1 to keep Static IP Addresses as they have now...but the new machines to use DHCP can this be done?

Thanks

[C M]

There are no policies to worry about, just merging.

There are 30 users in domain one & 8 in domain 2.

They are in offices next to each other, they will all be physically on the same hubs & patch panels e.t.c.

Thanks.