What is the point in authorising a Windows DHCP server. If I have client machines joined to a domain, they will obviously retrieve DHCP addresses from the authorised DHCP server. If someone puts a rogue DHCP server on the network will my client machines get an IP from the rogue machine or how should I stop this. thanks
The client doesn't know which to use, it just sends out a broadcast request and waits for a reply from whichever DHCP server replies first.
The way it works is that when a Windows DHCP server starts up, it checks if it's authorised. If its not authrorised then it won't serve any clients. This way, in theory, the only DHCP servers that are active will be ones you've authorised in AD.
As i mentioned above though, non-windows DHCP servers don't check for authorisation, so this is only effective at preventing rogue Windows DHCP servers.
It basically prevents unwanted Windows DHCP servers from running on your network. Unfortunately this doesn't apply to non-windows DHCP servers so it's usefulness is somewhat limited.
The way it works is that when a Windows DHCP server starts up, it checks if it's authorised. If its not authrorised then it won't serve any clients. This way, in theory, the only DHCP servers that are active will be ones you've authorised in AD.
As i mentioned above though, non-windows DHCP servers don't check for authorisation, so this is only effective at preventing rogue Windows DHCP servers.