TechNet “Get ready for Windows Server 2008”

Yesterday I was on the TechNet “Get ready for Windows Server 2008” seminar with one of my collegues. We’ve had a great day with much technical information about the ins and outs of Microsoft Server 2008. A very nice presentation and demonstration was given by speaker Gerald van Grootheest. What we’ve seen was:

– Terminal Server 2008
– TS Gateway
– TS RemoteApp
– TS Easy Print
– RODC (Read Only Domain Controller)
– NAP (Network Access Protection)
– Server 2008 Core Edition
– Hyper-V
– PowerShell

To download the presentations of the “Get ready for Windows Server 2008” seminar, go to the skydrive of Gerald van Grootheest. 

Session Broker in Windows 2008 Server

On of the great new features within Windows 2008 is the Session Broker feature. Actually you don’t call it a feature. The Terminal Server is a role, and you can install the Session Broker in the same windows, so let’s call it a Role Service. This new role service is responsible for the Load Balance between the different Terminal Servers in your farm. The great thing is that this role service it is included in the Windows 2008 Server Standard Edition, so you don’t have to buy the Enterprise Edition to use it.

The installation of the new Session Broker takes four steps:

  1. Install the TS Session Broker role service on a Server
  2. Populate the Session Directory Computers local group
  3. Join the Terminal Servers to the Session Broker and make them participate in the Load Balancing
  4. Add DNS entries for all Terminal Servers in the same farm.



When you install the Session Broker role service, this can be installed on the same server as the TS Licensing role service.

After installing this role service, there’s a new local security group called Session Directory Computers. Here you’re going to add all of the Terminal Servers that are member of the new Terminal Server Farm.

Next you have to configure all the Terminal Server to join the new Session Broker. This can be done using the following command: TSCONFIG.MSC

Now you are going to configure the group policy on the OU that includes the Terminal Servers.

The last step is to create new DNS entries for all the terminal server in the same farm. Now you are able to connect to the new Terminal Server Farm.

Here’s a great overview how this new Session Broker Role Service works.



Set the default logon domain

When you are using a terminal server 2008 environment, and the users connecting to this servers, you want the domain name is automatically filled in. Most of the time the local computer is filled in, for example SRV-TS01 or TS001. Users have to change this manually to the domainname.

Windows 2003 Server:

In Server 2003 you had the option to do this with a registry tweak:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Add a new REG_SZ called DefaultDomainName and fill in your DomainName.

Windows 2008 Server:

In Server 2008 this setting is included in the Group Policy structure.
Computer Settings\Administrative Templates\System\Logon\Default domain for logon
Here you can fill in your domain name.

Configure this option for your terminal server environment and you’ll save a lot telephone calls of users that are able to login, possibly because the domain is standing on locally this computer. 😉

Windows 2008 Server Core Configurator

With this great free tool you can configure your Windows 2008 Server Core Edition. Such as:

Product Licencing
Networking Features

DCPromo Tool
ISCSI Settings
Server Roles and Features
User and Group Permissions
Share Creation and Deletion
Firewall Settings
Display Settings
Add & Remove Drivers
Screensaver Settings
Windows Updates (Including WSUS)






Download the Windows 2008 Server Core Configurator