CTX: Exchange is unavailable error on Citrix or Terminal Server

When a user opens Outlook on Citrix XenApp (or Terminal Server) running on Windows 2008, he received an error: “Exchange is unavailable”.

They are several reasons for this issue:

1) Network issues:

Check network connection. Check if network gateway is ok. Reset the network connection.

2) Cached Profiles:

• Check the date of cached profile folder for the user on the C:\Users folder. If the date is from previous days, ask user to log off and delete the cached profile. Also delete any temp folder, they are corrupted profiles.
• Check Profile List and delete key with .bak at the end in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Compare users in task manager and delete profiles from not connected users too.

Note: you can enable a GPO to delete profiles when users log off from a session.

Open Group Policies Management console. Expand Computer Configuration, expand Administrative Templates, expand System, and then expand User Profiles.
Double-click Delete cached copies of roaming profiles, click Enabled

This GPO not always is working properly. A process lock the profile and some pieces of the profile still on folder. You can enable a GPO to delete profiles older than XX days when server is rebooted, to delete these profiles.

Open Group Policies Management console. Expand Computer Configuration, expand Administrative Templates, expand System, and then expand User Profiles. Double-click Delete user profiles older than a specified number of days on system restart and type amount of days.

EXCHANGE: Apply to Mailbox Retention Policy to Security Group Members

This powershell script will apply a Mailbox Retention Policy to a Active Directory Security Group Members

This script require Quest ActiveRoles Management Shell for Active Directory, available for FREE at http://www.quest.com/powershell/

To add the ActiveRoles Management Shell snap-in from Windows PowerShell
At the Windows PowerShell prompt, enter the following command:

Add-PSSnapin Quest.ActiveRoles.ADManagement

This is the script:

Get-QADGroupMember 'Exchange Retention Exception' | ForEach-Object {set-Mailbox $_.Name -ManagedFolderMailboxPolicy "Managed-Folders-60-Days"}

MS: Report items amount and size of each manage folder in Exchange

This powershell script will show how many items and size of each managed folder of all users in a Exchange 2007/2010 organization.

Get-Mailbox foreach { $mbx = $_.DisplayName; Get-MailboxFolderStatistics $_.identity -FolderScope 'Managed Folders' select @{n="DisplayName";e={$mbx}},FolderPath,ItemsInFolder,@{n="FolderSize(MB)";e={$_.folderSize.toMB()}}} export-csv c:\reports\ManagedFolders_12152010.csv

MS: E-mail Records Management and E-mail Retention

Great posts of Adam Harmetz @ Microsoft Records Management Team Blog about e-mail retention in Exchange 2007:

http://blogs.msdn.com/b/recman/archive/2006/12/19/email-records-management-part-1.aspx

http://blogs.msdn.com/b/recman/archive/2007/01/05/e-mail-records-management-part-2.aspx

http://blogs.msdn.com/b/recman/archive/2007/01/18/e-mail-records-management-part-3-e-mail-retention.aspx

MS: Create a Managed Folder Mailbox Policy on Exchange 2007 or 2010

Create a Managed Folder Mailbox Policy on Exchange 2007 or 2010

Create a Managed Custom Folder

>> Open Exchange Management Console.
>> Expand the Organization Configuration node and then click Mailbox.
>> Click in Managed Custom Folder tab
>> Right-click and choose the New Managed Custom Folder
>> The New Managed Custom Folder wizard appears. Complete required information.

Also we can use the following example cmdlet:

New-ManagedFolder -Name '3 Months Retention' -FolderName '3 Months Retention' StorageQuota 'unlimited'

Create a Managed Folder Mailbox Policy

>> Open Exchange Management Console.
>> Expand the Organization Configuration node and then click Mailbox.
>> Click in Managed Folder Mailbox Policies tab
>> Right-click and choose the New Managed Folder Mailbox Policy
>> The New Managed Folder Mailbox Policy wizard appears. Complete required information.

Also we can use the following example cmdlet:

new-ManagedFolderMailboxPolicy -Name "RetentionPolicy" -ManagedFolderLinks "3 Months Retention"

Assign the policy to a mailbox

>> Open Exchange Management Console.
>> Expand Recipient Configuration.
>> Double click on the desired mailbox.
>> Click on Mailbox Settings tab.
>> Select Message Records Management.
>> Click on Properties button.
>> Select the Managed Folder Mailbox Policy and make sure that Managed folder mailbox policy checkbox is checked.

Also we can use the following example cmdlet to apply to policy to a single mailbox:

Set-Mailbox -Identity GMusumeci -ManagedFolderMailboxPolicy "RetentionPolicy"

The following example cmdlet apply to policy to multiple mailboxes:

Get-Mailbox -database "EXCHSRV01\Storage Group 1\Mailbox Database 1" Set-Mailbox -ManagedFolderMailboxPolicy "RetentionPolicy"

Force the updates

We can force at server level or user level, using following two cmdlets:

Start-ManagedFolderAssistant –Identity EXCHSRV01
Start-ManagedFolderAssistant –Mailbox GMusumeci

MS: Get Exchange Mailbox Info (Exchange 2007 / 2010 or later)

This PowerShell script show the size of the Inbox folder and export the result to CSV file (excel)

Get-Mailbox foreach { $mbx = $_.DisplayName; Get-MailboxFolderStatistics $_.identity -FolderScope 'Inbox' select @{n="DisplayName";e={$mbx}},FolderPath,ItemsInFolder,@{n="FolderSize(MB)";e={$_.folderSize.toMB()}}} export-csv c:\Inbox.csv

This is another script to show the size of the Inbox folder and export the result to CSV file (excel)

Get-Mailbox -ResultSize Unlimited Select-Object Name, @{n='Inbox';e={(Get-MailboxFolderStatistics $_.Identity -FolderScope Inbox).FolderAndSubfolderSize.ToMb() }} Export-Csv c:\Inbox.csv -NoTypeInformation

MS: A reboot from previous installation is pending on Exchange 2007

When you try to install a Exchange 2007 component like Management Tools, you will receive a message: A reboot from previous installation is pending. Please restart the system and rerun setup.

Solution:

1) Remove an orphaned UpdateExeVolatile registry key value

Navigate to HKLM\SOFTWARE\Microsoft\Updates\

In the right navigation pane, double-click the UpdateExeVolatile key and configure the key with a value of 0

2) Delete the orphaned PendingFileRenameOperations registry key

Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\, right-click the PendingFileRenameOperations key and select Delete.

MS: Exchange 2007 Certifications

I worked a lot with Exchange 2007 in the last year. I designed, implemented and trained users.

Exchange 2007 SP1 starts a new wave of migrations. Time to certificate and improve knowledge!

When Exchange 2007 was release last year and I worked for InfoGroup Sistemas in Spain, I studied Exchange 2007 in detail. Below you will found my favorite books.

I teach these Exchange 2007 MOCs:

MOC 5047: Introduction to Installing and Managing Microsoft Exchange Server 2007.
MOC 5049: Managing Messaging Security using Microsoft Exchange Server 2007.
MOC 5050: Recovering Messaging Servers and Databases using Microsoft Exchange Server 2007.
MOC 5051: Monitoring and Troubleshooting Microsoft Exchange Server 2007.

Microsoft Exchange Server 2007: Tony Redmond's Guide to Successful Implementation

Probably the best book about Exchange 2007 around. Amazon

How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile, and Voice Access

Henrik Walther is Microsoft Exchange MVP (Most Valuable Professional) and writes Exchange-related articles for http://www.msexchange.org/, one of the best sites of Exchange Server. Great book, very easy to read and full of examples. Amazon

MCTS Self-Paced Training Kit (Exam 70-236): Configuring Microsoft Exchange Server 2007

This MS Press book is not good like others Training Kit I read before. But will help you to understand the exam. Amazon

MS: How to Install Exchange 2007 SP1 Prerequisites on Windows Server 2008

If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domain(s) by using a computer running Windows Server 2008, you must first install the Active Directory remote management tools on Windows Server 2008 prior to preparing the schema or a domain by using the following command:

ServerManagerCmd -i RSAT-ADDS

For more information about preparing the Active Directory schema and domains, see How to Prepare Active Directory and Domains

To install the Windows Server 2008 operating system prerequisites for Client Access servers

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

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

If the server will support Outlook Anywhere clients, install the RPC over HTTP proxy feature by running the following command:

ServerManagerCmd -i RPC-over-HTTP-proxy

To install the Windows Server 2008 operating system prerequisites for Edge Transport servers

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install Active Directory Lightweight Directory Services (AD LDS), which was previously known as Active Directory Application Mode (ADAM), by running the following command:

ServerManagerCmd -i ADLDS

To install the Windows Server 2008 operating system prerequisites for Hub Transport servers

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

To install the Windows Server 2008 operating system prerequisites for Mailbox servers

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

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

If the Mailbox server will be clustered, you must also install the Failover Clustering feature by running the following command:

ServerManagerCmd -i Failover-Clustering

To install the Windows Server 2008 operating system prerequisites for Unified Messaging servers

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install the Microsoft Windows Media Player audio/video codecs required by the Unified Messaging server by running the following command:

ServerManagerCmd -i Desktop-Experience

To install the Windows Server 2008 operating system prerequisites for a computer that will host the Hub Transport, Client Access, and Mailbox server roles

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

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

If the server will support Outlook Anywhere clients, install the RPC over HTTP proxy feature by running the following command:

ServerManagerCmd -i RPC-over-HTTP-proxy

To install the Windows Server 2008 operating system prerequisites for the Exchange management tools

Open a Command Prompt window.
Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:

ServerManagerCmd -i PowerShell

Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

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

MS: New MSIT Whitepapers on Exchange 2007

Microsoft IT has released 4 new whitepapers that can give you an inside look at how Exchange Server 2007 is run within Microsoft:

• Exchange Server 2007 Design and Architecture at Microsoft
  
• Managing the Calendaring and Collaboration Process By Using Exchange Server 2007 Web Services
  
• Daily Operations with Exchange 2007
  
• Exchange Server 2007 Deployment Checklist

MS: Exchange 2007 Guides

Exchange Server 2007 Design and Architecture at Microsoft

How the Microsoft Information Technology organization designed the corporate Exchange Server 2007 environment Technical White Paper.

Managing the Calendaring and Collaboration Process By Using Exchange Server 2007 Web Services

Microsoft is using Exchange Server 2007 Web Services to support communication and collaboration for two of its own internal applications. This case study provides a technical-level overview of how Microsoft developers are using Exchange Server 2007 Web Services.

Daily Operations with Exchange 2007

Operating a Global Messaging Environment by Using Exchange Server 2007 Technical White Paper

Exchange Server 2007 Deployment Checklist

This technical white paper discusses the deployment checklists that the Exchange Messaging team created based on the Exchange Server 2007 architecture and design specifications for the corporate production environment.

MS: Optimizing Outlook 2007 Cache Mode Performance for a Very Large Mailbox

How to optimize Outlook 2007 Cache Mode Performance for a Very Large Mailbox in a Exchange Server
http://msexchangeteam.com/archive/2007/12/17/447750.aspx

MS: How To Obtain The Latest Update Rollup for Exchange 2007

This article describes how to obtain the latest update rollup for Microsoft Exchange Server 2007. Update rollups are a common way to distribute Exchange 2007 fixes (Hotfix) and Exchange 2007 modifications. You can install the latest update rollup to help keep the product up to date.

http://support.microsoft.com/kb/937052

MS: Windows 2003 SP2 SLP and Exchange Problems

Windows 2003 SP2 Scalable Networking pack and its possible effects on Exchange
http://msexchangeteam.com/archive/2007/07/18/446400.aspx

MS: Exchange 2003 Change Password in OWA

Implementing the Change Password feature with Outlook Web Access
http://support.microsoft.com/kb/297121

VMware: Exchange Server 2003 Performance on VMware ESX Server 3

This paper discusses the performance and scalability of Microsoft Exchange Server 2003 when deployed within virtual machines running under VMware ESX Server 3.01.

http://www.vmware.com/pdf/Virtualizing_Exchange2003.pdf

MS: Exchange 2007 IMAP4 Client Access Configuration

1. Set MSExchangeIMAP4 service to automatic
Set-service msExchangeIMAP4 -startuptype automatic

2.Configure IP Address and Port for IMAP4

a.To set the IP address and port for communicating with Exchange using IMAP4 with SSL, run the following command:
Set-IMAPSettings -SSLBindings: IPaddress:Port

b.To set the IP address and port for communicating with Exchange using IMAP4 with no encryption or Transport Layer Security (TLS) encryption:
Set-IMAPSettings -UnencryptedOrTLSBindings IPaddress:Port

3.Configure IMAP4 Authentication - IMAP4 (143) /IMAP4 SSL (993)

a.If you will not be using TLS encryption and you want to allow Basic authentication on an unsecured port, run the following command:
Set-IMAPSettings -LoginType PlainTextLogin

b.If you will not be using TLS, but you want to restrict Basic authentication to use only secured ports, run the following command:
Set-IMAPSettings -LoginType PlainTextAuthentication

c.If you want to use TLS encryption before authentication, run the following command:
Set-IMAPSettings -LoginType SecureLogin

4.Enable IMAP4 Protocol for the User Mailbox (Enabled by default)
Set-CasMailbox MailboxName -IMAPenabled:$true ($false disables the protocol for the specified user)

5.Configure the SMTP Receive Connector on the Exchange Server to Allow Anonymous in order to send Email using the following command:
Set-ReceiveConnector "Servername\default Servername" -PermissionGroups “ExchangeServers,ExchangeUsers,ExchangeLegacyServers,AnonymousUsers"

6.Restart the Microsoft Exchange IMAP4
ServiceRestart-service MSExchangeIMAP4

7. Check the status of the Microsoft Exchange IMAP4
ServiceGet-Service MSExchangeIMAP4

8.Dump the IMAP4 configuration
Get-IMAPSettings

Note: Remember do not use the Administrator account to test IMAP4, IMAP, SMTP.

MS: Exchange 2007 POP3 Client Access Configuration

1. Set MSExchangePOP3 service to automatic
Set-service msExchangePOP3 -startuptype automatic

2.Configure IP Address and Port for POP3

a.To set the IP address and port for communicating with Exchange using POP3 with SSL, run the following command:
Set-PopSettings -SSLBindings: IPaddress:Port

b.To set the IP address and port for communicating with Exchange using POP3 with no encryption or Transport Layer Security (TLS) encryption:
Set-PopSettings -UnencryptedOrTLSBindings IPaddress:Port

3.Configure POP3 Authentication - POP3 (110) /POP3 SSL (995)

a.If you will not be using TLS encryption and you want to allow Basic authentication on an unsecured port, run the following command:
Set-PopSettings -LoginType PlainTextLogin

b.If you will not be using TLS, but you want to restrict Basic authentication to use only secured ports, run the following command:
Set-PopSettings -LoginType PlainTextAuthentication

c.If you want to use TLS encryption before authentication, run the following command:
Set-PoPSettings -LoginType SecureLogin

4.Enable POP3 Protocol for the User Mailbox (Enabled by default)
Set-CasMailbox MailboxName -Popenabled:$true ($false disables the protocol for the specified user)

5.Configure the SMTP Receive Connector on the Exchange Server to Allow Anonymous in order to send Email using the following command:
Set-ReceiveConnector "Servername\default Servername" -PermissionGroups “ExchangeServers,ExchangeUsers,ExchangeLegacyServers,AnonymousUsers"

6.Restart the Microsoft Exchange POP3 Service
Restart-service MSExchangepop3

7. Check the status of the Microsoft Exchange POP3 Service
Get-Service MSExchangepop3

8.Dump the POP3 configuration
Get-PopSettings

Note: Remember do not use the Administrator account to test POP3, IMAP, SMTP.

MS: Exchange 2003 ports

For Exchange Communication:
Port 80 for HTTP
Port 691 for Link State Algorithm routing protocol

For Active Directory communication:
Port 389 for LDAP (TCP and UDP)
Port 3268 for Global Catalog Server LDAP (TCP)
Port 88 for Kerberos Authentication (TCP and UDP)

For DNS communication:
Port 53 for DNS (TCP and UDP)

For RPC communication:
Port 135 – RPC endpoint mapper (TCP)
Ports 1024 and higher for RPC services

If you are using IPSec between Frontend- and Backend Servers you have to open:
Port 500 for IKE (UDP)
Port 51 for Authentication Header (AH)
Port 50 for Encapsulation Protocol (ESP)

Rules for firewall

DNS
SMTP
CIFS (Both)
FE/BE Link State Routing (691)
LDAP
LDAP (GC)
LDAP (UDP)
NTP
Ping
Kerberos Sec (TCP)
Kerberos Sec (UDP)
Kerberos Adm (UDP)
RPC (All)
HTTP Exchange Link State Routing (TCP691)
RPC over HTTP Information Store (TCP6001)
RPC over HTTP DSReferral (TCP6002)
RPC over HTTP DSProxy (TCP6004)

Client Access protocols:

HTTP
HTTPS
POP3
POP3 Secure
IMAP
IMAP Secure
SMTP
SMTP Secure

MS: Top 7 Tips for Deploying Exchange Server 7

1 ) What are the hardware requirements for Exchange Server 2007?
Microsoft has published the hardware/software requirements for Exchange Server 2007 at http://www.microsoft.com/exchange/evaluation/sysreqs
In short, the server must have:
• X64 processor; either the Intel EM64T or AMB64 platforms
• At least 2GB of RAM (plus 2-5 MB per mailbox for optimum performance)
• Light = 2MB/Mailbox
• Medium = 3.5MB/Mailbox
• Heavy = 5MB/Mailbox
• Other factors including the number of Storage Groups, server role, etc play a huge part. See this link for more detailed information: http://msexchangeteam.com/archive/2006/11/27/431644.aspx
• Windows Server 2003 x64 or Windows Server 2003 R2 x64, either Standard or Enterprise

2) What are the upgrade paths to Exchange Server 2007?
In-place upgrades are out. You will need to install a new Exchange Server 2007 machine into an existing Exchange 2000 or 2003 organization and move the data. Upgrading from Exchange 5.5 will require a little more work as you will need to completely upgrade the organization to Exchange 2000 or 2003 first. More information on the process can be found here: http://technet.microsoft.com/en-us/library/a313c016-0e51-466e-a3de-953e1e0d347d.aspx

3) How should I begin planning for disk space?
The factors that affect your storage plans are much more lenient than before, but they will still require some thought.
• Mailbox Size and Count In other words if your target is 1000 mailboxes at 500MB each then you need to think about 488 GB for the base.
• Dumpster Size You should calculate the additional drive space you will need to hold deleted items until the retention period has expired. This could range from 10-40% and even higher depending on the retention period and expected mail volume.
• Content Indexing If you plan to index mailbox items, then you should add another 5% to the overall volume requirements in order to hold the index.
• Growth You should factor in growth in either mailbox numbers or volume. 20% is a generally acceptable number to use to factor growth.
• Log Files The amount of storage they consume will be based entirely on the frequency of backups and the volume of changes made daily to the database files. Many Exchange administrators use 10% as an initial estimation of log files. As always, plan to have logs stored on a separate set of disks.
• IOPS Mailbox IOPS or Database I/O per mailbox, per second is still an important calculation but we have far more breathing room than we did with previous versions of Exchange. (These numbers are possible if you are using Outlook in cached mode.)
• Light Usage (Receive 20 messages a day) 0.11 expected IOPS per user
• Average Usage (Receive 40 messages a day) 0.18 expected IOPS per user
• Heavy Usage (Receive 80 messages a day) 0.32 expected IOPS per user
• Very Heavy Usage (Receive 120 messages a day) 0.48 expected IOPS per user
• In our mailbox example above; 1000 Average mailboxes would require 180 Disk IOPS for adequate performance. A good 7200 RPM drive can usually get a true 100 IOPS while the more expensive drives can get closer to 150.
• To meet our capacity and IOPS goals, we would need to look at a disk system that could hold at least 860 GB of data and operate at 220 IOPS (for growth) Four disks in a RAID 10 confi guration would probably fit the bill.
Here is a great place to learn more about the variables and to perform a more scientific approach to drive estimation: http://msexchangeteam.com/archive/2007/01/15/432199.aspx

4) What do I need to know about Server Roles?
Well, you can’t install a server without choosing a role so you must first understand the roles (and your design) before you can proceed. There are five server roles in Exchange Server 2007; Mailbox Server, Client Access, Hub Transport, Unified Messaging and Edge Transport. Here are a few key notes on each:
• Mailbox Server The name says it all. These will likely be your largest servers
• Client Access Provides HTTP/HTPPS access to the data; OWA, RPC over HTTP and ActiveSync
• Hub Transport Think of this as your internal Bridgehead server
• Unified Messaging Communicates with your PBX system. These components are usually installed on a separate server.
• Edge Transport Inbound SMTP traffic goes here. These components must reside on a separate server. This is where message hygiene is configured and how mail gets into your environment. In single-server environments, the Inbound SMTP and message hygiene functionality can be forced on your Mailbox/CAS/Hub server.
• For more detailed information and the Server Role Roadmap, follow this link: http://technet.microsoft.com/en-us/library/aa996319.aspx

5) What role does the AD Site have with Exchange Server 2007?
The AD site definitions are important for internal mailbox routing in an Exchange Server 2007 environment. Exchange Server no longer uses routing groups. Instead, it routes based on the routing topology defined within the Active Directory Sites and Services. Here are a couple of important items to note:
• Ensure there are no IP subnets defined in more than one AD site and that there is no overlap
• At least one Hub Transport server should be installed in each Active Directory site
• A Client Access server must be deployed in each site that contains Mailbox servers

6) Does my Active Directory need to be at a certain functional level before I can install Exchange Server 2007?
Yes. First and foremost the Schema Master for your Active Directory Forest must be running Windows Server 2003 R2 or Windows Server 2003 SP1.
Second, you need to make sure the Active Directory domain level functional level must be set for Windows Server 2000 (or higher) native mode for all domains in the forest.

7) Do I have to upgrade my Outlook clients before I install Exchange Server 2007?
Probably not. Outlook 2003, 2003 and Outlook 2007 are all supported. For Outlook Web Access, clients need to have a supported browser such as Internet Explorer versions 7, 6, 5.5, and 5.01, Mac OS X, Linux, Safari, Firefox, Netscape, and Opera.