In Windows 2012R2 and Windows 8.1 there is a command “Test-NetConnect” which tests a TCP port. That is a life saver. To be able to do that in Windows 2012 I created a small function.
I did create a DHCP scopes a couple of days ago. Something happened after the creation and a some scopes had a range of leases that got higher than 240, which was my top lease. The DHCP service had 70 scopes on two servers. This meant that I needed to check 140 scopes. First thing I rerun the script in previous post and set the top lease to 240, again, and Second I created a script to look for leases over 240 for me. It is not pretty, but it does its job.
I just want to point out a time saver.