Archive for October, 2008

Create a custom Address List for all recources

Default in Exchange 2007 there are a copple of Address Lists available.

All Contacts
All Groups
All Rooms
All Users
Default Global Address List
Public Folders

We can find everything in this lists within Outlook 2003/2007, exept one thing, the Equipment Recourse. You can find the equipment recourse in the All Users address list. So, let’s make a new custom address list for all our Recourse Mailboxes (included: Room and Equipment)

Open the EMC (Exchange Management Console), Organization Configuration, Mailbox, Address Lists.

Richt-click on New Address List. Lets call it All Recources.

       

Now we have created a new Address List. Let’s open the Outlook Web Access (or Outlook client) to check if it is available.

   

As you can see, there’s our new created custom Address List that includes all the Resource Mailboxes as shown in the preview. Make it easy for your users in the environment to search a resource. ;)

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

Exchange 2007 Component Architecture Poster

This poster gives you an overview of the different architectures of Exchange 2007.

  • Management and Monitoring
  • High Availability
  • Client Access, Edge Transport, Hub Transport, Mailbox, and Unified Messaging server roles
  • Download the Exchange Server 2007 Component Architectur Poster

    Prepare Windows 2008 server for Exchange 2007

    With the following script, you can prepare Windows 2008 server for installing Exchange 2007. This will save a lot of time… :)

    Script: Exchange2007_pre_2008.cmd

    ServerManagerCmd -i PowerShell
    ServerManagerCmd -i Web-Server
    ServerManagerCmd -i Web-ISAPI-Ext
    ServerManagerCmd -i Web-Metabase
    ServerManagerCmd -i Web-Lgcy-Mgmt-Console
    ServerManagerCmd -i Web-Basic-Auth
    ServerManagerCmd -i Web-Digest-Auth
    ServerManagerCmd -i Web-Windows-Auth
    ServerManagerCmd -i Web-Dyn-Compression
    ServerManagerCmd -i RSAT-ADDS
    Shutdown -r  -t 5

    The reboot is needed for the last command ServerManagerCmd -i RSAT-ADDS (Active Directory Domain Services Tools). The server is now ready for installing Exchange 2007.

    Adding a disclaimer

    One of the new features of Exchange 2007 are the Transport Rules. In this article i’m adding a disclaimer to outgoing e-mail with a transport rule.

    Open the EMC (Exchange Management Console), Organization Configuration, Hub Transport, Transport Rules, New Transport Rule

             

           

           

    So lets see if everything is working. We are sending an e-mail to Administrator@e2k7.nl

    When we open the mailbox from Administrator, there’s one new e-mail…

    And you will see, there’s our custom made disclaimer! You can make so much configurations whitin these transport rules, so check all these options, it’s a real great feature…

    Passed the 70-624…

    Yesterday I passed the 70-624 exam. TS: Deploying and Maintaining Windows Vista Client and 2007 Microsoft Office System Desktops.

    • Deploying desktop operating systems
    • Automating and customizing deployments by using scripts and answer files
    • Deploying applications during and after operating system deployments
    • Deploying upgrade packages
    • Using Business Desktop Deployment (BDD) tools
    • Using Windows Preinstallation Environment (PE)
    • Upgrading existing systems

    So now I will receive a new certificate from Microsoft :) and i’m proud to say that i’m now Microsoft Certified Technology Specialist (MCTS): Business Desktop Deployment.