<?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>Microsoft Windows DHCP Team Blog : Split Scope</title><link>http://blogs.technet.com/teamdhcp/archive/tags/Split+Scope/default.aspx</link><description>Tags: Split Scope</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How to configure split-scope using wizard</title><link>http://blogs.technet.com/teamdhcp/archive/2009/01/22/how-to-configure-split-scope-using-wizard.aspx</link><pubDate>Thu, 22 Jan 2009 11:59:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3189673</guid><dc:creator>teamdhcp</dc:creator><slash:comments>9</slash:comments><comments>http://blogs.technet.com/teamdhcp/comments/3189673.aspx</comments><wfw:commentRss>http://blogs.technet.com/teamdhcp/commentrss.aspx?PostID=3189673</wfw:commentRss><wfw:comment>http://blogs.technet.com/teamdhcp/rsscomments.aspx?PostID=3189673</wfw:comment><description>Split-scope configuration (Widely known as 80/20 Configurations) is typically considered as high-availability deployment scenario for the DHCP Server. It involves configuring scopes with the same subnet address and subnet mask and configuration on two...(&lt;a href="http://blogs.technet.com/teamdhcp/archive/2009/01/22/how-to-configure-split-scope-using-wizard.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3189673" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/teamdhcp/archive/tags/Split+Scope/default.aspx">Split Scope</category></item><item><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><pubDate>Thu, 22 Jan 2009 10:09:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3189544</guid><dc:creator>teamdhcp</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/teamdhcp/comments/3189544.aspx</comments><wfw:commentRss>http://blogs.technet.com/teamdhcp/commentrss.aspx?PostID=3189544</wfw:commentRss><wfw:comment>http://blogs.technet.com/teamdhcp/rsscomments.aspx?PostID=3189544</wfw:comment><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...(&lt;a href="http://blogs.technet.com/teamdhcp/archive/2009/01/22/how-to-prevent-address-exhaustion-from-secondary-server-in-split-scope-deployment.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3189544" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/teamdhcp/archive/tags/Split+Scope/default.aspx">Split Scope</category></item></channel></rss>