I've inherited a Windows network that has a number of locations with Windows 2003 and Windows 2008 servers. One of the DCs is running Windows 2008 R2 server is also serving DNS and DHCP.
The DHCP environment was showing several servers that had been decommissioned years ago. I used the tip in http://blogs.technet.com/b/networking/archive/2009/02/27/old-dhcp-servers-appear-in-the-list-of-authorized-servers-after-a-domain-rename.aspx
to remove the obsolete servers.
My issue now is that when I'm connected to this particular Windows 2008 R2 server, I can bring up DHCP, but I can't see the locally defined scope. I can access this server's scope from other systems, and from that perspective, it appears to be operating normally. The other unusual thing I've noticed is that when accessed locally, instead of the server's name showing at the top of the list, the name of one of the software apps on this server is displayed. The icon is a server with a red circle and a horizontal white line, which I find to be defined as "DHCP server connected but current user does not have the administrative credentials to manage the server."
The same username can remotely access that server's DHCP setup without problems.
So the questions are (1) why can't I access DHCP locally and (2) why isn't the server name used?