You run into issues installing Exchange 2007 SP2 on SBS 2008 until you add the following key and DWORD to the registry.

To create the E12SP2READY registry value, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Exchange

   Note If the Exchange subkey does not exist, you must create it. To do this, follow these steps:

   1. Right-click SmallBusinessServer, point to New on the Edit menu, and then click Key.
   2. Type Exchange and then press ENTER.
3. After you select the Exchange subkey that is specified in step 2, point to New on the Edit menu, and then click DWORD Value.
4. Type E12SP2READY, and then press ENTER.
5. Right-click E12SP2READY, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. On the File menu, click Exit to exit Registry Editor.

Full article at Microsoft - http://support.microsoft.com/kb/973862

There are additional steps to get Exchange 2007 SP2 installed on SBS 2008, below are the steps to complete from Microsoft Support

http://support.microsoft.com/default.aspx?scid=kb;EN-US;973862

How to update the GAL manually

Update-GlobalAddressList -Identity <GlobalAddressListIdParameter> -DomainController

For most it would be Update-GlobalAddressList -Identity “Default Global Address List”

How to check the logging in Exchange 2007

get-EventLogLevel

See which certificates Exchange 2007 are using

Get-ExchangeCertificate

Get-ExchangeCertificate |fl  (for more information)

Enable Exchange services for certificate

Enable-exchangecertificate -services IMAP, POP, UM, IIS, SMTP -Thumbprint BCF9F2C3D245E2588AB5895C37D8D914503D162E9

See what URL the CAS server has for autodiscover

Get-ClientAccessServer -Identity CASServer | FL

Change the autodiscover URL

Set-ClientAccessServer -Identity CASServer -AutoDiscoverServiceInternalUri https://mail.yourdomain.com/Autodiscover/Autodiscover.xml

Configure all the InternalURLs for each web distributed service

Set-OABVirtualDirectory -Identity “CASServer\OAB (Default Web Site)” -InternalURL https://mail.yourdomain.com/OAB

Enable-OutlookAnywhere -Server CASServer -ExternalHostname “mail.yourdomain.com” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “CASServer\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalURL https://mail.yourserver.com/Microsoft-Server-Activesync

Find out your inbound/outbound message limits

get-transportconfig

You may have trouble sending mail to certain domains while using Exchange Server 2007 on Windows Server 2008. The Queue Viewer displays the following status error for the domain in question:

“451 4.4.0 primary target IP address responded with “421.4.4.2 unable to connect.”attempted failover to alternate host, but that did not succeed.Either there are no alternate hosts, or delivery failed to all alternate hosts.”

This problem occurs because routers do not support the TCP autotuning settings in Windows Server 2008.

To disable autotuning, follow these steps:

Run CMD as Administrator

At the command prompt, type the following command, and then press ENTER:

netsh interface tcp set global autotuninglevel=disabled

This command disables the Receive Window Auto-Tuning feature.

Exit the Command Prompt window.

Restart the computer.

In the situation I came across, Outlook 2007 clients were constantly prompting for a password eventhough the users were on the LAN, members of the domain, and logged in to the PC with domain credentials.  While I found several potential causes, the solution ended up being an SSL setting in IIS on the mail server. 

The solution was to allow client certificates on the virtual directory for Exchange Autodiscover.  It turns out the clients were attempting to use the Autodiscover service with Exchange 2007 to detect settings and the website wasn’t accepting their client certificate.  The client certificates are apparently used for encryption between the client and the server.  Disabling the checkbox to enable that type of communication may also have been a solution, but this is a better one because it maintains the security of an encrypted channel.  Here are the instructions:

1. Using IIS6 - Click Here
2. Using IIS7 - Open the IIS manager.  Expand the Sites group and expand down to the Autodiscover virtual directory.  Select this virtual directory then selec “SSL Settings” from the center pane.  In the settings window, select “Accept Client Certificates”.

In addition, the authentication settings on this virtual directory can also cause this to happen if not configured correctly.  Just make sure that Integrated Windows Authentication is checked.

After installing the latest version of Trend Micro Scanmail 8.0 on an SBS 2008 server, the Exchange Transport service kept stopping and reporting the following errors in the Application event log:

Event ID: 16023 Source: MSExchangeTransportMicrosoft Exchange couldn’t start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type ‘TrendMicro.SMEX.hookE12TransportAgent.hookE12RoutingAgentFactory’ from assembly ‘D:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll’ due to error ‘Invalid agent assembly path.’ …

Event ID: 1052 Source: MSExchange Extensibility

The creation of an agent factory for the agent ‘ScanMail Routing Agent’ failed with error ‘Failed to create type ‘TrendMicro.SMEX.hookE12TransportAgent.hookE12RoutingAgentFactory’ from assembly ‘D:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll’ due to error ‘Invalid agent assembly path.’.’. Verify that the corresponding transport agent assembly and dependencies with the correct version are installed.

The issues turned out to be a permission issue on the SMEX program file directory.  Exchange uses the Network Service account for the Transport Service credentials but this account didnt get security permissions to the Trend Micro SMEX program folder after install.  Adding the appropriate read permissions did the trick.

With the newer versions of Backup Exec and Exchange 2007, Granular Recovery Technology (GRT), a requirement of the Microsoft Exchange Server MAPI Client and Collaboration Data Objects needs to be downloaded and installed on the Exchange/Media server. Microsoft has updated the Mapi and CDO to 1.2.1 to include Windows Server 2003 and Windows Server 2008. 64bit servers have no problem installing.

Link to download.

http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx

Situation: Exchange 2007 has a contact (not a mailbox) within the GAL that end-user uses to email instead of using the actual non-exchange email address. The non-exchange (network solutions) user does not get attachment sent (Word, Excel, etc.), but does get a winmail.dat file attached.

Fix: Launch Exchange Management Console, goto Recipient Configuration/Mail Contact container, open up contact you’re having the issue with, on the ‘general’ tab change the ‘Use MAPI rich text format’ drop-down to ‘Never’ and test.

I recently came across a client’s backup that was completing successfully daily but not flushing the transaction logs for Exchange as it should.  In the job properties of Backup Exec, the Exchange section declares that it will perform a full backup and flush the comitted logs but it simply never happens.

After some research, Veritas article 280659 had the answer…and it was a simple one.  In the job properties, review the options under Advanced Open File and make sure the option “Process Logical Volumes for backup one at a time” is not checked.   As its explained in the article, if this is unchecked, Backup Exec will use a different open file option (VSS) for the Exchange logs to allow it to flush them afterwards.