<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to prevent address exhaustion from Secondary Server in split-scope deployment</title><link>http://blogs.technet.com/teamdhcp/archive/2009/01/22/how-to-prevent-address-exhaustion-from-secondary-server-in-split-scope-deployment.aspx</link><description>DHCP secondary server is configured with 20% of address leases and if it serves the clients at the same pace it would run out of address leases and would be useless if the primary DHCP server is down. To avoid address range depletion on the secondary</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>