OK, here's a question. I created a superscope, and within that superscope was a number of scopes. I probably didn't follow best practice here, since the child scopes were bascially all over the place as far as IP addresses go.
But anyway, one day we noticed that one of the scopes, when clients would attempt to renew their address, DHCP would assigned them an address from the first scope of the superscope instead of the scope that they should be in. And when this happens, the client cannot connect to anything, since it gets an IP that belongs to another subnet.
So, in order to try and remedy this situation, I removed the scope from the superscope, deleted the invalid client from the incorrect scope, and everything's hunk-dory. However, the next time the server is rebooted, or the DHCP Server service is restarted, the scope I removed from the superscope is right back in that superscope again. In fact, even if I remove all the scopes from the superscope, and delete the superscope completely, the next time the DHCP Server service is started, that damn superscope, along with all of the child scopes I removed, are right back in it again.
Note: This is happenping on both a 2003 and 2008 server.