Windows 2008

All posts tagged Windows 2008

Windows 2008 R2 contains a new version of the file server resource manager (FSRM) which has been improved a lot. One of the options this tool has is to send notifications for example when an alert is activated. Normally this is really easy to configure, the only thing you need is a mailserver which will accept the traffic and will deliver the e-mail. 

But let’s assume you have an Exchange 2010 Server in your environment and you use the default receive connectors. In most situations the default receive connector is configured to accept mail which is send from the internet, this can be done by adding the anonymous permission group to the receive connector. 

However this connector can’t be used by FSRM. When pressing the test button the following event is logged in the application event log: 

 

As you can see the event will tell you that the account you are using is not allowed to send e-mail as the alert account.

When enabling SMTP logging you will see the following entries in your log:

 

The FSRM will authenticate using the computer account from the system on which FSRM is running, in this case LAB-DC-01. But how do you need to configure Exchange so it will accept the message and send the alert e-mail? To accomplish this, a seperate receive connector needs to be created. This because we don’t want everybody can use this receive connector.  

But what are the correct settings for the receive connector? The receive connector will need to accept basic authentication and the anonymous permission group needs to be added to the connector. By performing the following Powershell cmdlet the connector is created: 

New-ReceiveConnector -Name FSRM -Usage Custom -Bindings 192.168.1.30:25 -RemoteIPRanges 192.168.1.24AuthMechanism BasicAuth -PermissionGroups Anonymous 

Now when performing the test again it will succeed: 

Exchange and using the ä in an e-mail address

Last week I found a nice issue on a forum. A user who managed an Exchange server in a Scandinavian country had issues with using the letter ä in an e-mail address. When a user had this name the e-mail address was generated with an ae instead of the ä.

After some troubleshooting we found out that it had nothing to do with the Exchange settings. I searched further and found a knowledge base article from Microsoft which described the same issue. The problem is caused by incorrect regional settings before installing .NET 2.0. Make sure these are correct before installing .NET. to fix the issue stop the Exchange services, remove the .NET version(s), correct the regional settings and reinstall .NET.

In case of Windows 2008 it’s a little bit more complicated as it already contains .NET 2.0 by default. As soon as I found a solution for it I will let you know. There is a workaround, don’t use the letter ä in the e-mail address, but in some countries this is not an option.

open

A while ago …

It has been a while but since this week I am back online thanks to my neighbour.  My own provider hasn’t been able to arrange the new connection despite several phone calls and a letter which mentioned the line should be working on 21-7.

Nevertheless, last week Rollup 9 for Exchange 2007 SP1 which contains several fixes. One of the fixes is to improve the performance of ESEUtil when running it on a Windows 2008 R2 system.

Besides this SP2 for Exchange 2007 will be released soon, so a lot of news about Exchange.

For a full overview of fixes in Rollup 9 visit the site below.

open

Technet Page

 

 

 

 

 

I discovered this  page via a link in the Microsoft Exchange team website

The site contains several templates which can be used to install the Exchange 2007 rolles on both Windows 2003/Windows 2008 including a list of recommended hotfixes  and things you should keep in mind.  A really nice start for your implementation plan.

open

Just as like Windows 2003 you need to add some components to Windows 2008 before you can install Exchange 2007. In this tutorial I will explain which need to be installed on which server and made some scripts for it, that’s far more easier then typing the commands one by one ;-).

When you gone prepare the AD for Exchange 2007 from a Windows 2008 server you first need to install the Active Directory Domain Services remote management tools. These tools make it possible to modify the schema and domain so that Exchange 2007 can be installed.

This can be done by executing the following script:

prepad4ex07.cmd

ServerManagerCmd -i RSAT
shutdown -r

After the installation of the tools the server will be  rebooted, this last thing is optional and is not always needed.

After the tools have been installed the next step is the CAS server. First we will install Powershell, this is a prerequisite for Exchange 2007. Next fase is installing several IIS components for the web applications such as: OWA and AutoDiscovery that will be hosted on the CAS.  When you are going to use Outlook Anywhere you also need to install the RPC over HTTP proxy, this will be done in the last step.

CASpreex07.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 RPC-over-HTTP-proxy
shutdown -r

After installing the components the server will be rebooted, this again is optional.

When the CAS server is prepared it’s time for the HUB server. If you want to use a script for it, it’s your own decission, this because just one component will be installed.

HUBpreex07.cmd

ServerManagerCmd -i PowerShell
shutdown -r

Now that the CAS and HUB server are prepared it’s time for the mailbox server.

MBpreex07.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-Windows-Auth
shutdown -r

As you can see IIS is installed besides Powershell. Exchange 2007 doesn’t use the SMTP and NNTP from IIS anymore, some other components do need IIS.

When you want to build a cluster of mailbox servers you will need to add an extra line of code to the script.

MBCpreex07.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-Windows-Auth
ServerManagerCmd -i Failover-Clustering 
shutdown -r

A next step could be installing the Edge Sync server.

Edgpreex07.cmd

ServerManagerCmd -i PowerShell
ServerManagerCmd -i ADLDS
shutdown -r

This script will install Powershell again, besides this Active Directory Lightweight Directory Services will be installed. This services have the same functionality as the Active Directory Application Mode (ADAM) as it was known in Windows 2003.

When you would like to use the auto attendant and voicemail functionality of Exchange 2007 you will need to install the UM role.

UMpreex07.cmd

ServerManagerCmd -i PowerShell
ServerManagerCmd -i Desktop-Experience
shutdown -r

This script will install the codecs for audio/video from the Windows Media Player.

When you have a dedicated management station it may be necessary to install the manegement tools on it. For this only Powershell and two IIS components are needed.

Mgpreex07.cmd

ServerManagerCmd -i PowerShell
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console

I think we have talked about all the prerequisites for all rolles now. Below there are some links to some resources that contain extra information about this.

How to Install Exchange SP1 Prerequisites on Window Server 2008 or Vista
Speeding up installation of Exchange Server 2007 SP1 Prerequisites on Windows Server 2008

Windows 2008 workstation

Windows 2008 Workstation??  does it exist. I will help you rapidly out of  your dream there is no Windows 2008 Workstation indeed. But someone has again been creative and has turned Windows 2008 server in Windows 2008 workstation. It seems that it is a lot of work to get it running but there is a complete step-by-step plan to get it working. You want to try it, then have a look at this site.

Remote Server Administration Tools makes it possible to manage a Windows 2008 server from you workstation. This tool is the Windows 2003 Administration Tools, which was available for Windows 2003, for Windows 2008. This tool is only available for 32 and 6 bits Vista systems.

32-bit download

64-bit download