The DHCP server in Windows Server 2008 R2 has invested in the areas of security, reliability, manageability and usability. Similarly on the DHCP Client in Windows 7 has invested on certain optimization for obtaining IP Address.
The following changes are available in DHCP server in Windows Server 2008 R2:
· Supports MAC address based network access control mechanism, with the Link Layer based Filtering feature. With this feature DHCP Administrator can control issuance/denial of DHCP leases/IP addresses.
· Supports prevention of name squatting issues caused due to non-Windows OS machines, with the Name Protection feature. Using this feature one could prevent registration of non-Windows OS machine with a same name that is already registered for another machine in DNS Server.
· Supports prevention of exhaustion of IP addresses at scope level especially for the deployments catering to redundancy/high-availability scenarios like Split-Scope. This feature is available only for IPv4 network and not for IPv6 network as in case of latter exhaustion of addresses is not an issue.
· Supports DHCP activity logging, allows DHCP Administrators to monitor the configuration changes of the DHCP Servers. DHCP Administrators would use this feature for network security / IT compliance auditing purposes.
· Supports migration of DHCP Server role using Windows Server Migration Tool (WSMT).
· DHCP Server service is moved under Network Service account from Local Service account. With this the DHCP Server service that runs in the context of the Network Service account presents the computer's credentials to remote servers. Also the advantage with Network Service is it has very few privileges and can do less damage on the server if compromised.
· Usability and operability enhancements of DHCP Server like:
- Auto-population of certain network interface fields like DNS Server addresses (both IPv4 and IPv6), WINS Server addresses, during installation and configuration of scope.
- Interpretive Icons for better readability.
- Wizard based split-scope configuration for ease and error free split-scope deployment.
- Address leases to filter (multiple select supported) for ease of Link Layer based filter configuration for leased clients.
- Address leases to reservation (multiple select supported) for ease of reservation configuration for leased clients.
- In the product scenario/task based help content for Windows Server 2008 R2 features.
· Supports DHCPv6 Option 15 (User Class). This is used by client to identify the type or category of user or application it represents. It involves both DHCP Server and Client side implementation.
· Support of DHCPv6 Option 32 (Information Refresh Time). This specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6. It involves both DHCP Server and Client side implementation.
· Better performance and scalability achieved through lease database caching. Read more about it here.
The DHCP client of Windows 7 has support for optimization to obtain IP Address using SSID caching.
· Supports SSID caching so that, laptop devices with Windows 7 could get IP Address in a lesser time in a Wireless LAN network during revisits to the same.
· Extended NDF and unified tracing to support additional scenario.
· Broadcast bit flag behaviour is updated to toggle between ‘0’ and ‘1’ and also would cache the last successful broadcast bit setting for which the client received IP Address. This way it would ensure the client to acquire the address properly, irrespective of the support for the flag by the 3rd party DHCP Server \ Relay Agent.
· Support of DHCPv6 Option 32 (Information Refresh Time). This specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6.
You mention that you don't have IP address exhaustion protection for IPv6. Does this mean that a client can request an unlimited number of IA_NA leases? If that's the case, isn't this a potential DOS attack, since the server has to maintain state for each lease?
The DHCP server in Windows Server 2008 R2 has invested in the areas of security, reliability, manageability
Windows Server 08 R2 has Clustering and 80:20 (with secondary server delay)support for Higher availability .
214 Microsoft Team blogs searched, 101 blogs have new articles in the past 7 days. 237 new articles found
>>Address leases to reservation (multiple select supported) for ease of reservation configuration for leased clients.
We have been wanting this for years!!!!! There is no reason I shouldn't be able to right-click a lease and convert it to a reservation!
You can convert your active leases into reservations, starting with Windows Server 2008 R2.
I know this query is way off topic but was wondering if there is a posssibility to give preference to a particular DHCP server [maybe using Server IP in the DHCP Offer]? This is purely for use in a lab environment? Any suggestions would be greatly helpful!
In Dhcpv4 u can configure a delay on the scope which you want to give lesser preference. You can get more information here http://blogs.technet.com/teamdhcp/archive/2009/01/22/how-to-prevent-address-exhaustion-from-secondary-server-in-split-scope-deployment.aspx
In DHCPv6, there is provision at the protocol level for a server preference field which is supported by Windows DHCP server. For DHCPv4 however, there is no such provision at the protocol level. Configuring delay at the scope level would be the way to go.
Are there any options to use Windows Server 2008 to issue classless static routes?
This feature is available in Windows Server 2003 DHCPs
I dun see that its configurable in WIndows Server 2008... please advice any workaround in R2?
Windows Server 2008 as well as Windows Server 2008 R2 support option 121 classless static routes. This can configured as a server or scope option. Is that what you were looking for.
Will DHCP in 2008R2 be FULLY controllable from Powershell? In all previous versions there has not even been so much as a MOF to allow queries/control via WMI.
DHCP in 2008R2 won't be controllable from powershell. Please let us know what are the queries/control that you think will be simple if implemented using powershell but difficult to implement currently.
Please send the mail at dhcpblog AT microsoft DOT com
I've read a post some time ago that contained VB code to compile a DLL that should be registerred on the Windows 2003 DHCP server of which you want to delay the DHCP offer by for example 5 seconds.
Do you know about this article? It's something I want to implement at this moment because we don't have the opportunity to implement 2008R2 at this moment (yet) but still require a stand-by DHCP server that should respond a few seconds after the primary server.
I hope you know about this.