Archive for the ‘Windows 2008 R2 DHCP Cluster’ Category

Powershell Network Load Balancing

Teched 2010 Berlin #TEE10 #Teched

For Demo and learning Sites you need often thing that takes only a minute but when you play with it it takes more time than you want. So with this in my mind I created 3 powershell scripts that you can use for building a cluster , NLB Cluster and a MSTDC cluster resource.

This powershell script is fully unattended an yes it is not complete it can be improved.  But you can always adjust this. Similar scripts are there for creating Exchange NLB.

This script runs on node 1 and is creating the NLB on the two or more nodes. ( tested only on two nodes )

You can find the Scripts Here : Powershell Scripts

Powershell Create NLB

The first thing you might want to change is the network adapter name I used adapter 3 and renamed it to NLB later in the NLB name is used as parameter,

#Set IP for NLB Write-Host "Set NLB IP and change Network adapter" -ForegroundColor yellow Netsh interface ip set address name="Local Area Connection 3" static Netsh interface set interface name="local area connection 3" newname="NLB"

The Ip adress is needed to set the NLB don’t worry the IP will be removed when the NLB is complete.

The other part is the powershell script is connecting thrue powershell to the other node.

First give the netbios name from the second node ( make sure your DNS is OK )

#Adding additional cluster nodes based on user input
Write-Host "Give Second NLB host" -ForegroundColor yellow
$Node2Fqdn = Read-Host "Enter 2e NLB node"

Here with the “function EndPSS { get-pssession | remove-pssession } “
and “endpss “ I connect and disconnect to the other node. the problem here was. in the basic security you can only use 5 remote connections. I can adjust this or make a workaround so the script works in the default security template.

Now I connect from node 1 to node 2 and placed a IP and renamed the NIC

function EndPSS { get-pssession | remove-pssession }
#Set Network Adapter
#Enter-PSSession -ComputerName $Node2Fqdn
invoke-command -computername $Node2Fqdn -scriptblock { Netsh interface ip set address name="local area connection 3" static}
invoke-command -computername $Node2Fqdn -scriptblock { Netsh interface set interface name="local area connection 3" newname="NLB"}
Write-Host "Placed NLB IP and changed NIC to NLB" -ForegroundColor yellow

#Import-Module NetworkLoadBalancingClusters
Write-Host "Import-Module NetworkLoadBalancingClusters On Remote Node" -ForegroundColor yellow
Enter-PSSession -ComputerName $Node2Fqdn
invoke-command -computername $Node2Fqdn { Import-Module NetworkLoadBalancingClusters}

#Add Remote Node To NLB
Write-Host "Adding cluster node $Node2Fqdn" -ForegroundColor yellow
Get-NlbCluster | Add-NlbClusterNode -NewNodeName $Node2Fqdn -NewNodeInterface NLB

#Remove Old IP
Remove-NlbClusterNodeDip -Hostname $Node2Fqdn -force
Write-Host " Remove old IP node " -ForegroundColor yellow

Here I removed the IP that was needed to create the NLB.

You can find the Scripts Here : Powershell Scripts

Powershell Create NLB

Microsoft sends invitations to testers for Windows 7, Server 2008 R2 SP1


You are receiving this invitation based on the quality of feedback you have provided on previous Windows programs and the Microsoft Windows release team would like you to participate in the Microsoft Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) release program, to be available shortly, as announced at the Microsoft’s TechEd conference.

Accepting this invitation will allow you to access pre-release versions of the Service Pack for the purposes of validating the release readiness. We highly value your past feedback and know we can count on you again to help us build a great new version of Windows!

The SP1 release version is not available quite yet but we need to assemble a great team of program peers early so you are ready to go when we are! If you accept this invitation you’ll be notified when the release version becomes available.

What you will get if you choose to participate

• Early access to downloadable Windows 7 SP1 and Windows Server 2008 R2 SP1 releases
• Access to private newsgroups to share information about the release with other program peers and with Microsoft staff
• The ability to report bugs and track their status
• An opportunity to help us build a better Windows by validating the release readiness

What we will ask of you if you choose to participate

• Download and install Windows 7 SP1 or Windows Server 2008 R2 SP1 on at least one PC each
• File bugs if you encounter them as well as respond to surveys as you can.
• Validation we are seeking
o Set-up and installation
o Application Experience/Compatibility
o Device Experience/Compatibility
• We ask that you actively participate in discussions on the newsgroups and share your opinions with us and others


Read more :

Deploying Remote Desktop Connection Broker with High Availability


This guide is intended for IT professionals, and tells how to configure Remote Desktop Connection Broker in a failover cluster. The configuration provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection

A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service. This guide describes the steps for configuring Remote Desktop Connection Broker (RD Connection Broker) in a failover cluster, as part of a configuration that provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection. As you work with the configuration in this guide, you can also learn about failover clusters and familiarize yourself with the Failover Cluster Manager snap-in in Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter.

Deploying Remote Desktop Connection Broker with High Availability  click here: Start download

Failover of clustered RD Connection Broker






Servers providing a virtual desktop


1. The user requests a connection to a virtual desktop, either a personal virtual desktop or one from a virtual desktop pool.

2. The RD Gateway receives the request.

3. The RD Gateway sends the request to a virtual machine redirector (that is, RD Session Host running in virtual machine redirection mode). The virtual machine redirector informs RD Connection Broker, and then waits for the IP address of a virtual machine.

4. RD Connection Broker requests information about a virtual machine from the RD Virtualization Host.

5. RD Connection Broker receives information about a virtual machine and then provides that information to the virtual machine redirector.

6. The virtual machine redirector communicates through the RD Gateway, providing the client with the IP address and connection information for a virtual desktop.

7. The client connects to a virtual desktop.

8. The virtual desktop is displayed on the client.

The following illustration shows the same sequence of events occurring despite the failure of one node of the cluster. Because a second cluster node is still running, it can respond to client requests as they occur.

Figure 3   Servers providing a virtual desktop after a failure


Cluster Screen Shots




RDP Connection Options



Additional Links

· Remote Desktop Services (

· What’s New in Remote Desktop Services (

· Install the RD Session Host Role Service (

· About Dedicated Farm Redirection and Virtual Machine Redirection (

· Remote Desktop Connection Broker (

· Verify Connection broker cluster configuration (

· Remote Desktop Services Script Repository (

  • Tag