Exchange 2007 Installation

So this was kinda enlightening … the AD boys have setup for forest for me and schema / domain prepped too.

But when I went to Install Exchange I kept getting:

setup /mode:install /role:mt,mb,ca,ht

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be installed
    Management Tools
    Hub Transport Role
    Client Access Role
    Mailbox Role

Performing Microsoft Exchange Server Prerequisite Check

    Organization Checks              ……………………. FAILED
     The Active Directory Schema must be modified and this user account has insufficient permissions. It must be a member of both the ‘Schema Admins’ and ‘Enterprise Admins’ groups.

     Global updates need to be made to Active Directory, and this user account is not a member of the ‘Enterprise Admins’ group.

     The local domain needs to be updated. You must be a member of the ‘Domain Admins’ and ‘Exchange Organization Administrators’ group, or ‘Enterprise Admins’ group to continue.

    Hub Transport Role Checks        ……………………. COMPLETED
 Setup cannot detect an SMTP or Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.
    Client Access Role Checks        ……………………. COMPLETED
    Mailbox Role Checks              ……………………. COMPLETED

The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.

Exchange Server setup encountered an error.
 

WTF, i checked permissions and tried a milion and one different things before the penny dropped.  yeah you got it, the AD boys had use Exchange 2007 RTM and not SP1 ! … Doh!

The tell tail sign was the objectVersion on the Organization container in the Active Directory Configuration partition, it was set to 10666. 

After an SP1 forest prep I was still getting this:


setup /mode:install /role:mt,ca,ht,mb

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be installed
    Management Tools
    Hub Transport Role
    Client Access Role
    Mailbox Role

Performing Microsoft Exchange Server Prerequisite Check

    Organization Checks              ……………………. FAILED
     Global updates need to be made to Active Directory, and this user account is not a member of the ‘Enterprise Admins’ group.

     The local domain needs to be updated. You must be a member of the ‘Domain Admins’ and ‘Exchange Organization Administrators’ group, or ‘Enterprise Admins’group to continue.

    Hub Transport Role Checks        ……………………. COMPLETED
 Setup cannot detect an SMTP or Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.
    Client Access Role Checks        ……………………. COMPLETED
    Mailbox Role Checks              ……………………. COMPLETED

The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.

Exchange Server setup encountered an error.

Intersting, the objectVersion didn’t change to 11221 until the domain prep was run?!

Check this out for info on the objectVersion

440 Login Timeout when using OWA 2007

If you try and access OWA 2007 you may see this error
 
440 Login Timeout
 
It would appear that this error happens if the IUSR_ and / or IWAM_ accounts are disabled on the server.
 
Using Computer Mangement on the server, navigate to Local Users and Groups and select the disabled acount and using right click select properties
 
Now uncheck “Account is disabled”
 
Once you have done this for the IUSE and IWAM account run and IISReset
 
All should be back to normal!

Blackberry & Exchange 2007 OoO Issue

Okay so just for everyone (and for me to blow the dust off a few brain cells .. and what I understand the issue to be) .. This is a problem introduced with Exchange 2007, and affects any BES or Outlook 2003 user that is on Exchange 2007.

Essentially, a users Exchange 2007 OoO is actually stored at the top of the information for a users mailbox, and comprises of two messages in the folder. One has a message class of IPM.Microsoft.OOF.Log where the message body as a log of any OOF changes. The other is IPM.Microsoft.OOF.UserOofSettings, and this contains your Exchange 2007 OoO setting.

BTW, you cannot see these messages if you are using Outlook Cache Mode, you must connect direct to the server ;-)

All previous versions of Exchange and Outlook older than Outlook 2007 use a different mechanism for OoO.  The OoO settings are stored in a users mailbox under IPM_SubTreeInbox and is a hidden associated message with a message class of: IPM.Note.Rules.OofTemplate.Microsoft.

When you use Outlook 2007 or OWA 2007, any updates to OoO are changed in IPM.Microsoft.OOF.UserOofSettings and IPM.Microsoft.OOF.Log.  Then for the “legacy” purposes, Exchange 2007 writes a IPM.Note.Rules.OofTemplate.Microsoft to a users IPM_SubTreeInbox.

So you’re on Exchange 2007 and set and OoO using Blackberry, two IPM.Note.Rules.OofTemplate.Microsoft objects appear in the users mailbox. One is the original one set using Outlook and one the new OoO set using a Blackberry.  For a small period of time, the new OoO may work, but after a few minutes, the Exchange 2007 Store finds these two messages and runs the “legacy” process and makes the “IPM.Microsoft.OOF.UserOofSettings” the “master” OoO.

For RIM to fix this, they will need to rewrite the OoO bit to use the new Exchange 2007 methods, that is as long are the users mailbox is on an Exchange 2007 server.

So the workaround is to set the OoO using OWA 2007 or Outlook 2007 … or as I suspect some Microsoft folk will want you to migrate to Windows Mobile & ActiveSync ;-)

It doesn’t looks like BES 4.1 SP5 fixes the issue, and we will all have to wait for BES 5.0

KB15155: Out Of Office text is not synchronized to Microsoft Exchange 2007 when updated from the BlackBerry smartphone

So at last RIM confirm they have a problem! .. Rumour control has the fix scheduled for BES 5.0 … god knows when that will hit the streets!.

So esentially you when you migrate a Blackberry user to Exchange 2007 they shouldn’t set an OoO from the BES device!?


Source: http://www.blackberry.com/btsc/article/458/KB15155_f.SAL_Public.html

Environment
BlackBerry® Enterprise Server software version 4.1 Service Pack 4 (4.1.4) for Microsoft® Exchange
BlackBerry smartphone
Microsoft® Exchange 2007
SDR145355

Problem
BlackBerry smartphone users with a Microsoft Exchange 2007 mailbox are unable to update Out Of Office text from their BlackBerry smartphones.

Cause
Microsoft Exchange 2007 provides the ability to set Out Of Office text for internal and external email messages. When internal Out Of Office text is set in Microsoft® Outlook® 2007, the Out Of Office text is updated on the BlackBerry smartphone. When setting or updating Out Of Office text on the BlackBerry smartphone, the internal Out Of Office text in Microsoft Outlook 2007 is not updated.

Resolution
This is a previously reported issue that has been escalated internally to our development team. No resolution time frame is currently available.

Workaround
Set or update Out Of Office text in Microsoft Outlook 2007 or using Microsoft® Outlook® Web Access 2007.

Microsoft Exchange Monitoring service failed to start following installation of Exchange 2007 or Service Pack or Rollup

Thanks to Ari for this nugget ;-)

The following events are visible:
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Description:
The Microsoft Exchange Monitoring service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion. 

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Description:
Timeout (30000 milliseconds) waiting for the Microsoft Exchange Monitoring service to connect.

Reference: Exchange 2007 managed code services do not start after you install an update rollup for Exchange 2007 (KB944752)

RESOLUTION To resolve this problem, verify that the computer can reach the following Microsoft Web site to download the CRL: http://crl.microsoft.com/pki/crl/products/CSPCA.crl Configure server to uses a proxy server for HTTP and for HTTPS, you must configure the proxy server so that HTTP-enabled CRL validation works. Additionally, make sure that the proxy settings are configured correctly for the Exchange Server services to access the Internet.

The simplest way to configure WinHTTP is to use ProxyCfg.exe. ProxyCfg.exe is a command-line tool that is included in the %System32% directory on all Windows Server 2003-based computers. You can use ProxyCfg.exe to set WinHTTP configurations and to view WinHTTP configurations. For more information about how to use the Proxycfg.exe tool to modify WinHTTP proxy settings, click the following article number to view the article in the Microsoft Knowledge Base: 936707

FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start Microsoft Knowledge Base article 841641 describes how to configure a specific proxy setting if you are running services as a noninteractive account. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 841641 IIS returns a “403.13 Client Certificate Revoked” error message after you install MS04-011 because of Wininet proxy settings.