How to create integrated NIC Teaming with Windows Server 2012 via GUI

One new and big feature in Windows Server 2012 is the integrated NIC Teaming. In the past when you want to team network interfaces in Windows, you need special 3rd party software e.g. like Broadcom Advanced Control Suite (BACS). But this brought us some problems e.g. when you run Group policies against teamed devices. Mostly the policy was not executed, I will explain this maybe in a later blogpost. Microsoft has also published some Hyper-V Scenarios where NIC Teaming is not supported.

Now this is no problem anymore.

With integrated NIC Teaming in Windows Server 2012 you can team NIC or even LOM. You can also Team different Vendors (e.g. Intel or Broadcom) together in one Team. In the past this was very difficult, unstable and also not supported. The only software that is able to do this, is Intel Advanced Networking Services (ANS) Teaming Software.

Let me show you how to configure it via GUI.

 

1. Open the Server Manager and click on “Configure this local Server”.

2. Now click on “disabled” at the point NIC Teaming to start the Wizzard.

3. Now you the Wizzard starts and you have a few options to add NICs to a team.

4. How to add a NIC to a Team.

Selection over NIC box:

 

a. Mark all NICs you want to use in your team by selecting them out of the right box with shift+click.

 

b. click “Tasks” and  “Add to new Team”

c. Now you see that the NICs that you selected before, are marked with a hook.

Type in a Team name.

After this open “Additional properties” and go on with Step 5 will popup.

Selection over Team box:

 

a. In the left box click on “Tasks” and than select “New Team”.

b. select all NICs that should be part of the Team.

Type in a Team name.

After this open “Additional properties” and go on with Step 5 will popup.

5. In the Additional properties you can configure more options.

Teaming Mode

switch-dependent modes: require switch ports teaming setting, must on same switch.
switch-independent modes: not require switch ports teaming setting, could on same switch or different switch.

Load balancing mode

Hyper-V switch port: use MAC address of the virtual machine across the team members, bandwidth will be 2 Gbit.

Adress Hash: use hash based on components of the packet on one team member, bandwidth will be 1 Gbit to one traffic, bandwidth will be balanced to other team member for more than one traffic.

Standby mode

Active/Active: failover to other team members
Active/standby: failover to standby team member (you can select on standy adapter)

 

6. By clicking on Primary team Interface: Team1: default VLAN.

Here you can set a Specific VLAN if you need.

7. Click “OK” to close the wizzard and save the configuration.

8. After this you should see the NIC Teaming in you Server Manager.

 

 

How to add other Windows Server 2012 System to Server Manager for remote management via IP

In the new Server Manager from Windows Server 2012 you can add other Windows 2012 (and also Windows 2008 and 2008 R2 Servers) to manage. This is an easy way to consolidate and simplify your management environment.

 

1. Open the Server Manager on the Server that should be your management station.

 

2. In Server Manager click on “Manage” and than on “Add Servers”

 

3. A wizzard will open where you can search after the Servers you want to add. You can choose between search in AD, DNS or Import via CSV sheet. In my example I will search my Server via DNS / IP. For this please click on DNS.

 

4. Type in the name of your server and than click on the magnifying glass.

 

5. now the Server should be listed in the left box. Doubleclick on the servername to move it in the selction list. You can also mark the server and click on the error between both tables, to select them.

You are able to select as many server as you want.

 

6. When you finished with selection click “OK” and go to “all Servers” in the Server Manager. Now you should see all selected and added servers.

 

 

How to Configure DHCP Faileover Cluster on Windows Server 2012

All of you know that we didn’t have any Failover option for DHCP in the past. So must of us created different DHCP scopes for one IP range on different servers. This was needed to get a partly redundant DHCP option. This was working but any changes for reservations, scope changes or configuration changes must be done manually or with scripts. This took time or wasn’t really successful.

Now with Windows Server 2012, we get a real Failovercluster including configuration replication. Please notice, the only available options are load balanced and hot standby. I will explain you later when you should use which option.

So let us start to configure our cluster.

 

1. You need to install the first DHCP Server and configure the DHCP Scope. This DHCP Server has to be Windows Server 2012 Standard or Datacenter.

http://datacenter-flo.de/?p=350

In this scenario I configured the first DHCP Server on Flo-SVR-DC01.

 

2. Next install a new server with Windows Server 2012 or take one other free server from your existing Windows Server 2012 Systems as Windows Server 2012 DHCP Failover Clusterpartner.

How to install a Windows Server 2012 http://datacenter-flo.de/?p=203

First Configuration of a Windows Server 2012 http://datacenter-flo.de/?p=222

In my case I installed a fresh Windows Server 2012 VM as Failover Partner.

 

3.  Now your could add the new node to your Server Manager, if you want to manage the Server remote. You can also configure the Failover Setup without this, but it helps to manage both Servers later.

http://datacenter-flo.de/?p=496

 

4. When the DHCP role was installed correct on the second host and you added the server for management to your management host, than you should see both systems under DHCP.

5. In the next step open the DHCP MMC.

6. In the DHCP MMC please add the second DHCP Server first. You can do this via right click on “DHCP” and than “Add Server”.

http://datacenter-flo.de/?p=689

7. Now you should see both DHCP Servers in the list.

12. In the next step we authorize the DHCP server to our Domain.

http://datacenter-flo.de/?p=688

13.  Now click right on the scope that you want to cluster and select “Configure Failover”.

14. When the Wizzard starts, you see the Scope that can be clustered.

If you see no available Scope, you have to check if DHCP Service is up, DHCP Server is complet configured and there are no issues with DNS and ADDS.

 

15. Next step is to selecte the failover partner.

16. When you authorized the second DHCP server before, you see it in the second list. Otherwise you have to select “This Server:” and “Browse”.

17.  Now you type in the name of the server.

18. When you entered the name click “Check Names”. When the wizzard found the server, click “ok”.

19. Click “ok” and the server will attached to DHCP MMC.

20. Now you see the selected Server with complet FQDN in the Patern Server field.

Click “Next” to go on.

 

21. Now you have to set the clusterconfiguration.

Load Blanced:

Relationship Name: Name of your Failover Cluster

Maximum Client Lead Time: Defines the amount of time the surviving server will wait before assuming control of the entire scope.

Mode: Load Balanced – When the cluster is configured in Load Balance mode, this results in an active-active setup of the two DHCP Servers.

You should use when you have big networks with many clients or you want to deploy the cluster in different branch offices.

Load Balance Percentage: Means how the work is splitted up between both hosts. The percentages together can only be 100%. The node with the highest percentage gets the highest workload.

State Switchover Interval: automatically change state to partner down after <time>.

Enable Message Authentification: enables authentification from clusternodes.

Shared Secret:Validation Passwort that identifies the node as partners against each other.

 

Standby:

Relationship Name: Name of your Failover Cluster

Maximum Client Lead Time: Defines the amount of time the surviving server will wait before assuming control of the entire scope.

Mode: Hot Standvy – When the cluster is configured in Hot Standby mode, one node is active and the second is standby and will only take over when the primary DHCP Server failes.

You should use when you need the partner as fault tolerance.

Adresses reserved for standby server: Means how many adresse the standby can lease before he takes over the entire scope and becomes active.

State Switchover Interval: automatically change state to partner down after <time>.

Enable Message Authentification: enables authentification from clusternodes.

Shared Secret: Validation Passwort that identifies the node as partners against each other.

 

22. After klicking “Next” you see a short summary of your configuration.

23.  Klick “Finish” and the cluster configuration starts.

24. In the DHCP MMC click right on the Scope and force a replication by clicking on “Replicate Failover Scope” and than on the refresh  button or press F5.

25. On the failover node check the config. If the config is right your finished.

 

 

 

 

How to add second Server to MMC (example DHCP Server)

1. Right click on “DHCP” and than “Add Server”.

2. Now you can add the server. You will not see the new DHCP Server in the list of authorized DHCP server because we didn’t authorize the server yet.

Mark “This server:” and click “Browse”.

 

3.  Now you type in the name of the server.

4. When you entered the name click “Check Names”. When the wizzard found the server, click “ok”.

5. Click “ok” and the server will attached to DHCP MMC.

6. Now you should see both DHCP Servers in the list.

Free Windows 8 eBooks and learning materials

Hi Community,

I found some free Windows 8 eBooks and Jumpstarts that I want to share with you.

———-

free eBooks:

Introducing Windows 8: An Overview for IT Professionals (preview Edition) by Microsoft Press

Programming Windows 8 Apps with HTML, CSS, and JavaScript by Microsoft Press

Windows 8 for Dummies: Dell Pocket Edition by Dell

Windows 8 Accessibility Tutorial Guide by Microsoft

———-

Windows 8 Jumpstarts: 

Link to all 8 Modules

———-

Windows 8 Hands on Labs: 

Windows 8 labs for JavaScript and HTML

Windows 8 labs for C# and XAML

———-

Training and Demonstrations

Windows 8 Training and Demonstrations