Monthly Archives: March 2010

Friday Tip #3 – DNS/Spamcheck


This is the third Friday tip and maybe the best of them all J
To have a complete check on the customers external DNS when doing a mail project is maybe the best thing to do.

Very often I see that “everything” looks OK but when checking for PTR records they doesn’t exists.
This can be a problem, some receivers doesn’t accept the mail if the PTR records doesn’t match the mx record and the banner on the server.

With this link below you can search for the domain and check for blacklists, SMTP check and also the PTR check.

Entourage Issues with Exchange 2007 on Windows 2008


Using Entourage for Mac (2004 or 2008) while connecting to an Exchange 2007 mailbox on a Windows 2008 Server, user cannot download any e-mail message which has a plus sign in the subject line, like ‘Mail + Issue’.

Entourage’s request to download this e-mail message goes thru IIS 7 on Windows 2008 Server, which is configured (by default) to deny ‘double escape sequences’ in any HTTP request and thus it rejects the request with a ‘404.11’ error.

As Entourage talks to ‘Exchange’ virtual directory (for mailbox access) under ‘Default Website’ on IIS, thus you can use the following procedure to allow the use of ‘double escape sequence’ only at that level to address this issue. This will minimize the risk you will be taking to enable the usage of double escape sequence. Enabling the use of ‘double escape sequence’ does carry some risk, please go thru the links below under ‘More Info’ section to get yourself educated on the issue & involved risks before you work on the steps below.

Manual Steps
1. Bring up Notepad : File : Open, type %windir%\System32\inetsrv\config\applicationHost.config in the ‘File name’ box, and then click ‘Open’.

2. Locate the section titled as: <location path=”Default Web Site/Exchange”>

3. Under that section locate </authentication> tag

4. Just after that insert the following text on a new line: <requestFiltering allowDoubleEscaping=”true” />

5. Save the file and ‘Exit’ Notepad

No restart of any service is required.

As Entourage talks to ‘Public’ virtual directory (for public folder access) under ‘Default Website’ on IIS, thus you will need to follow the same procedure for ‘Public’ virtual directory as well. Same instructions apply; just replace ‘Exchange’ with ‘Public’ in all steps mentioned above.

This text was found and copied from a blog, don’t remember which one (sorry) and some editing in the text has been done.

Databases doesn’t show up


This error came up to me after installing an Exchange 2010 CAS/HUB server and a Mailbox server.
The server doesn’t show any databases; by default the server itself creates an “example” database like Mailbox Database 4385492.
But it didn’t show up!

After running ExBPA I found out that the ‘homeMDB’ value for System Attendant service was missing. This caused the error.

By following this article on technet the error went away:

In addition to what I wrote earlier in the post, I’ll update it here with a picture of the path in adsiedit because of the comments to the post.
Hope it will help to find it.

Recover failed Exchange 2007/2010 server installation

A time ago I had a little problem with an Exchange 2007 (SP1) installation.
The server I was using was prepared with Windows 2008 R2 Standard and I was told that this should be supported if Exchange 2007 is using SP2.
Well, with that said I could install Exchange 2007 including SP1 if I used Compatibility mode. But when I should update it to SP2 it wouldn’t run the installation even if I used the Compatibility mode.

The only option that was available for me was to uninstall Exchange 2007, but the uninstallation told me that this wasn’t supported and failed right away.

I did that dramatic thing to power off the server, reinstall Windows and this time it was with Windows 2008 including SP2 because I knew this is working really well.
The nice thing here is that I reinstalled the server, gave it the same hostname and ip address, joined it to the domain.

But what about Exchange?
In Active Directory it already exists so it cannot be installed again?

Maybe you know this but if you don’t, it’s a really nice feature to recover an Exchange server using /recoverserver
(This recovery switch could also be applied on Exchange 2010)

It will then checks Active Directory for the information and recover almost all information, so in maybe 2 hours I was back on track J

An article that describes the installation problem of Exchange 2007 on a Windows 2008 R2 server