Project Plan to change subnet mask

I am evaluating a change in the subnet mask on my networks.  I have an all Windows Server 2012 R2 server domain network.  Clients obtain their IP addresses via DHCP.  Servers and other devices have static IP addresses.  I have one point to point VPN that connects a remote office to the domain.  Please provide references to documentation that could provide the basis for a project plan to accomplish this migration.
Who is Participating?
nociConnect With a Mentor Software EngineerCommented:
Now if you want to grow you network by doubling, Lets assume this because of lack of info in the Question,
netmask from /24 -> /23 ( ->
For a transistion it is needed to know 2 of the next 3 things..... (Starting situation, Ending situation, Difference between start & end).....
Ok work break down....

Doubling the range means... the base range of will become 192.168.0/23  it will also invade
Therefore you will need to move the remote network from the address range to something else ( or beyond. Moved to *.9.0 or higher so you can do this doubling trick again.
So that is the first task.  This can be done cold turkey or by using alias addresses as in between on the remote site.
and moving systems one by one.  and finaly remove all reference on remote.

After that you can on a quiet moment adjust all netmasks on the main site. (DHCP by adjusting the netmask provided and all static configs by hand/script etc. Dont forget to also update the remote router if needed.

Now you have to take inventory and determine the time all tasks consume and start making a planning.
And define intermediate stable states you can leave your network in if the planning is not met in time.
Also make a plan how to undo parts of changed to ge back to a previous stable state. and the time it takes.
Determine the windows of opportunity the network is quiet.  
During many of the steps in  the change the network will NOT be stable prepare for that.
bbaoIT ConsultantCommented:
better to know more details about the existing and projected IP plans. e.g. DHCP scope and its subnet mask, servers' IP scope with their existing and projected masks.

if the situation meet some criteria, you may work out a smooth plan to deploy the new mask in steps while keeping all servers accessible to the client computers.
BeurmannPrincipalAuthor Commented:
The existing network has the standard subnet mask:  DHCP scope is 101 to 200.  The static IP range of the servers and ancillary equipment is 002 to 100.  The IP address range is  The IP address of the remote office that is
Mike Beurmann
The new generation of project management tools

With’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

bbaoIT ConsultantCommented:
what about the new mask?
BeurmannPrincipalAuthor Commented:
I hadn't selected the new subnet mask, as I had anticipated that I would include its selection in the planning, much as noci indicates.
BeurmannPrincipalAuthor Commented:
Thanks NOCI.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.