Configuring Windows Server 2008 R2 DHCP Split-Scope

At last with Windows Server 2008 R2 Microsoft have introduced an easy way to provide some form of redundancy for DHCP servers with the new Split-Scope Wizard. Administrators have always had to provide some form of DHCP redundancy in larger networks, this was usually done by manually splitting scopes across more than one server, and if a lot of scopes are required this can be a laborious job, and not the easiest to manage.
So what have Microsoft introduced now? Lets presume that you have 2 DHCP servers configured on your network. On server 1 you go ahead and configure your DHCP scope as you always have, include any Scope Options, server options etc. When you define your scope, include all the range that you will be wanting to split, for example a new scope;
IP Range 10.1.1.100 – 10.1.1.200
So, nothing new so far, once you scope is configured, right click on the new scope, select advanced, and then Split-Scope,

Windows Server 2008 IIS7 HTTP Redirection

In IIS6 to redirect a virtual directory within a website to another URL, local or remote, was a nice and simple process. It was just a case of right clicking on the virtual directory, selecting properties and on the Directory Tab selecting “A Redirection to a URL” and entering the required address.

With the introduction of IIS7 in Windows Server 2008 this was published as an improved feature. So when asked to move a virtual directory, and forward all requests to the original address to the new URL I presumed this would be just as straight forward.

So first things first, HTTP Redirection is not included in the standard IIS7 setup, when you add it as a Role. So to start with using Server manager, add the Role Service to IIS (I will presume you know how to do this).