| Author | Messages | |
Johnchristie11
Posts:16
 | | 09/08/2008 4:15 PM |
| Chaps...
We're in the process of migrating our network to a new network address
range. We have a hub and spoke network design and so far we've managed to
migrate all branch offices to the new address range.
We're planning on migrating our 3 core hub sites that host our
infrastructure (MS DNS, DHCP, DC's, WINS) servers and approx 80 application
servers that service the rest of the network. MS DHCP servers are used to
dynamically assign IP's and DNS/WINS config to approx 2500 workstations.
This is where I need advice, when we migrate the DNS/WINS servers to the new
address range, the application servers and workstations will be pointing to
the old address. To migrate the application servers, I'll use a script, but
whats is the best approach to update the DNS/WINS configuration on
the workstations?
I was thinking of updating the DHCP scopes with the DNS/WINS information and
then rebooting all workstations to update but some sites are 24/7 so would
be a problem.
Also, I want to minimise the impact to users, can I do anything fancy in DNS
to redirect requests to the old IP to the new DNS/WINS servers?
JC
| | | |
| kevinbrunson
Posts:40
| | 09/08/2008 4:17 PM |
| I've gone through this process several times, and when possible, I try to set up both sets of addresses on the gateway. Then it can route between the 2 subnets, so workstations can talk to servers whether they have the new IP address or not. Once you get the last of your devices on the new subnet, you can remove the old subnet from your router/firewall/whatever.
Kevin
From: ActiveDir-owner@mail.activedir.org [mailto:ActiveDir-owner@mail.activedir.org] On Behalf Of John Christie
Sent: Tuesday, August 26, 2008 2:15 PM
To: activedir
Subject: [ActiveDir] OT Migration to new network address range
Chaps...
We're in the process of migrating our network to a new network address range. We have a hub and spoke network design and so far we've managed to migrate all branch offices to the new address range.
We're planning on migrating our 3 core hub sites that host our infrastructure (MS DNS, DHCP, DC's, WINS) servers and approx 80 application servers that service the rest of the network. MS DHCP servers are used to dynamically assign IP's and DNS/WINS config to approx 2500 workstations.
This is where I need advice, when we migrate the DNS/WINS servers to the new address range, the application servers and workstations will be pointing to the old address. To migrate the application servers, I'll use a script, but whats is the best approach to update the DNS/WINS configuration on the workstations?
I was thinking of updating the DHCP scopes with the DNS/WINS information and then rebooting all workstations to update but some sites are 24/7 so would be a problem.
Also, I want to minimise the impact to users, can I do anything fancy in DNS to redirect requests to the old IP to the new DNS/WINS servers?
JC
| | | |
| bdesmond
Posts:357
| | 09/08/2008 4:17 PM |
| John-
I would suggest you trim your DHCP lease time down (e.g. to 8 hours), wait until your existing lease period expires, and then move towards this change. DHCP clients will renew their lease at 50% of the lease length, so every 4 hours in this scenario. You make the IP swaps and DHCP change at 2200 hours, by 0600 all your clients using DHCP will have renewed.
A more conservative approach (which I would recommend) is that you do half the name server swaps one maintenance window and the other half the next. That way you won't break clients who aren't using DHCP or other oddball things out there. Believe me you will find them.
You can then put your DHCP lease duration back where it belongs. 2500 clients will not hurt a DHCP server of any recent vintage even if they are hitting it every 4 hours.
Thanks,
Brian Desmond
brian@briandesmond.com
c - 312.731.3132
From: ActiveDir-owner@mail.activedir.org [mailto:ActiveDir-owner@mail.activedir.org] On Behalf Of John Christie
Sent: Tuesday, August 26, 2008 2:15 PM
To: activedir
Subject: [ActiveDir] OT Migration to new network address range
Chaps...
We're in the process of migrating our network to a new network address range. We have a hub and spoke network design and so far we've managed to migrate all branch offices to the new address range.
We're planning on migrating our 3 core hub sites that host our infrastructure (MS DNS, DHCP, DC's, WINS) servers and approx 80 application servers that service the rest of the network. MS DHCP servers are used to dynamically assign IP's and DNS/WINS config to approx 2500 workstations.
This is where I need advice, when we migrate the DNS/WINS servers to the new address range, the application servers and workstations will be pointing to the old address. To migrate the application servers, I'll use a script, but whats is the best approach to update the DNS/WINS configuration on the workstations?
I was thinking of updating the DHCP scopes with the DNS/WINS information and then rebooting all workstations to update but some sites are 24/7 so would be a problem.
Also, I want to minimise the impact to users, can I do anything fancy in DNS to redirect requests to the old IP to the new DNS/WINS servers?
JC
| | | |
|
|