Windows Server 2008 R2 Thread, Moving to a new DHCP scope in Technical; This school has a /24 subnet but as we have run out of addresses I've been given a new /23 ...
7th June 2013, 05:03 PM #1
Moving to a new DHCP scope
This school has a /24 subnet but as we have run out of addresses I've been given a new /23 subnet and told that we can still use the old addresses while we move over. What is the recommended method of changing scopes? The school closes in five weeks but I could really do with getting the scope moved before that as I'm very low on free addresses and more machines are on the way.
The server has free NIC ports so could one be set to the new subnet so clients can see the server regardless of which subnet they are on or is it best to just hold fire and wait till the summer close down?
7th June 2013, 07:17 PM #2
Get a list of all your devices with static IPs.
Get a list of all services which access the Static IPs rather than the DNS names. Printer Servers ->network printers are one headache, firewall publishing rules are another, gpo proxy settings are another.
Also look in DNS at all your static entries.
Figure out how long it will take to manually update to the new subnet. This will determine the downtime window for services.
For your DHCP / Dynamic DNS environment, you could set a short lease time, and wait for all clients to have picked this up, then over-night deactive one scope and enable the new one. In the morning everything should be one the new subnet. Obviously your DCs and servers are going to be static, so they need to move over as the first action of the evening.
And don't forget about your default gateway and any other routing that may be going on.
7th June 2013, 07:25 PM #3
You can be lazy if you like, depending on your current scope.
Moved one of my primaries to a /22. The /24 they were using was unfortunately at the wrong end, so expanding it means that the server, router and printers etc are all at the end of the scope rather than beginning as would be nice (without changing those too). Not a problem though - router updated, server subnet changed, printers on statics had their subnets changed to 255.255.252.0 and that was absolutely it. DHCP scope moved lock stock to the start of the /22 and doesn't even touch the old /24.
15th June 2013, 12:23 AM #4
Thanks guys but getting this done before the holidays is looking like a non starter as Capita haven't sorted out the filtering for the new scope yet, but that said it's probably better for me to wait and take my time anyway.
15th June 2013, 10:02 AM #5
What a surprise there! (It's no help to you but just a brief anecdote - when we changed our DHCP scope *massively* (i.e. went from 1000 addresses to 16,000 for one scope and another couple of thousand for the statics; nothing like planning ahead!) as well as implementing a complex VLAN infrastructure our new ISP were on it within half an hour. It's good to be with someone who actually want's your business!
By kaphc in forum How do you do....it?
Last Post: 3rd March 2011, 09:00 PM
By sidewinder in forum ICT KS3 SATS Tests
Last Post: 27th February 2009, 02:20 PM
By contink in forum Comments and Suggestions
Last Post: 24th September 2008, 12:07 AM
By edie209 in forum MIS Systems
Last Post: 16th November 2007, 07:22 PM
By pshuttle in forum General Chat
Last Post: 17th March 2006, 07:14 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)