Hello, just started as the network administrator at a small - medium business not having a huge amount of experience in this size and complexity of network before I have a few questions i hope you can help with.
I understand the concept of Superscopes and how they work, and in my situation it seems the best option, my current IP addressing pool is not large enough for the number of systems that on the network. we heavily use VMWARE and have a number of virtual servers and physical servers and developer servers in use on Static IP's, Lync, SharePoint and forefront servers also on static IP's, the gateway to the internet is all managed by a watchguard XTM 5 firewall with rules and VPN's allowing traffic in and out to access Lync and SharePoint.
my plan was to leave the current network pool of 192.168.254.1 - 192.168.254.254 in places due to all the existing NAT, VM Systems and static IP's in use and In server 2008 R2 use DHCP to create a second Scope with a new pool on 172.16.0.1 - 172.16.15.254 giving me ample usable address's so I wont have any conflicts, when I make a superscope what do I need to consider and what are the risks involved, will the original scope provide the options to the new scope or will i need to duplicate them?, and what are the chances my whole network will collapsing and, finally for the new scope to access the internet what sentry in the firewall will i most likely have to make.
Thank You for any assistance.
Gordon - BPDZenith UK