NS

Thank you for this opportunity to allow me to engage in your companies networking solutions. To dive right in, I see that you have added two new branches in addition to your regional office.
Considering the size of your branch I suggest we use a Class A IP addressing scheme with the regional office as 192.168.1.x as it is the main branch, and 192.168.2.x for the second branch, and 192.168.3.x for the third branch. This will allow us to keep track of what building an IP address is transmitting from in order to help us better analyze the network for things such as trouble shooting. In the recent years you have switched over to a DHCP solution which is better suited for your company so that was the right move.
 I do notice that there are several nodes using static IP addresses. Some of these are computers that had issues getting network connectivity at a certain point in time and rather then properly fix the issue, manual IP addresses were assigned as temporary fixes. We will be addressing the issues with those computers and update them to the DHCP configuration via Control Panel > Network and Internet Settings > Network and sharing center > Change Adapter Settings > Selecting the correct adapter and right clicking and going to Properties > Selecting TCP/IPv4 and select Properties > select automatically assign IP addresses.
I realize you are unsure about updating the network with the cost of time it will take to update those static IP addresses but this is an important matter to address as there are some issues that can arise from leaving them static. Such issues can be conflicting IP addresses which will cause one of the nodes with the same IP address to not be able to access the network. Another issue that can arise from having static IP addresses are they can be set to bad IP’s such as the IP address of the server or as the gateway, this can cause issues with other computers trying to reach the gateway or server and instead hitting your node that was statically set.
However there are some nodes on the network that are set as static that do not need to be changed such as the network printers and server nodes. If those IP addresses are dynamic, when the IP address lease is up and the IP changes, all computers that are setup to print to that printer IP or use that server that has a network share will no longer see it and will not be able to print or be able to access the files on the network share.
To save money, these networking schemes could be done remotely but I would not recommend it as it may cost more money in the future. When updating IP schemes remotely there are issues you can run into. For one, when you update an IP address on a node, as soon as it is updated your remote connection will drop. The issue with this is that if there is a problem with the IP settings after the first change, you may not be able to reconnect. Now you are stuck with possibly having to plan a trip to that location where the computer is located to fix the issue. The other issues are you are not 100% sure what device you are interfacing with, and could make a change to a static IP device that should remain static like a server node.