Service Pack 1 for Microsoft Exchange Server 2007 is due for release on 30 November 2007! Microsoft has prepared a major update for its flagship mail server which has now received many new features and improvements and can be downloaded from site.

Support for new platform

Microsoft Exchange Server is now fully compatible with Microsoft Windows Server 2008 and can be deployed to a computer running Windows Server 2008 RC0 Escrow build. The full list of supported operating systems can be found here.
Exchange Server 2007 SP1 has a mixed IPv6 128-bit addressing by default when running on a Windows Server 2008 platform. That is it only runs IPv6 when the obsolescent protocol IPv4 is enabled. Otherwise Exchange server will fail running on IP. If you are running a deployment for multiple machines you can create a rule to deploy only for the defined IPv6 range thus avoiding unsupported setup conditions with IPv6-enabled management tools or based on general information about support of IPv6 in Microsoft operating systems. Another way is to call a function that can resolve to an IPv6-address, that is something like IsResolvableEx used to resolve a hostname when performing a Web-Proxy autodiscovery or just issue a ping command on IPv6-address like say

ping6 -n 2 ::1

That is we ping 2 times on a loopback address 0:0:0:0:0:0:0:1 using a short notation (two-colon notation) for writing IPv6 addresses.

New features were added to a remote access for a remote client

Exchange Active Sync a has received a remote wipe confirmation feature and is now enabled with Enhanced Exchange ActiveSync mailbox policy settings which include ability to
Disable Removable Storage
Disable Camera
Disable Wi-Fi
Disable POP/IMAP e-mail
Block Internet Sharing

It both provides for a data protection and ensures a security for sensitive data on mobile devices should they be stolen or accidentally lost by user. This all can be done centrally from within Exchange Management Console or Exchange Management Shell and works in a best traditions of what is meant under a centralized management.

Mobile work becomes faster

The new Service Pack improves and speeds-up long-standing connections between a server and a mobile device mobile devices.

Dramatic improvements in remote work though Outlook Web Access

Microsoft has completely rewritten the Outlook Web Access in Exchange Server 2007 and SP1 brought many of those that were not enabled in the RTM so that OWA now comes with lightning new features too.
First off, running in a Light mode OWA does not time out any longer and no longer drops the session out if user is composing a long message or just working with its calendar for a long time. OWA now prevents you from losing your typed messages by automatically saving the them in as Draft folder as-you-type.
In Premium mode for Outlook Web Access it is now possible for a user to create and edit Personal Distribution Lists and server side rules.
What about support for Microsoft Office System 2007? WebReady Document Viewing has finally been added with support for decoding and viewing in HTML of Word/Excel and PowerPoint X-Documents in OpenXML format.
It is now possible to copy or move folders using a dedicated context menu command.

Public Folders functionality now offers following features:
It is now possible to get full access to public folders from OWA and you don’t have to use the Public virtual directory. And you can get full access to public folders on Exchange 2007 Mailbox servers is now available for users without the need for you to provide Public Folder access from Outlook Web Access on Exchange 2003 Mailbox server. Microsoft has also added search features for Public Folders.

Increased manageability within Exchange Management Console

Exchange Management Console has been enhanced with a brand new interface for administering POP3 and IMAP4 protocols.

Hub Transport Server role has been added with functionality to set message size limits on Active Directory site links.

New features in Mailbox Server role

It is now possible to import and export mailbox by using .pst files. I believe this will provide greater flexibility administrator especially combined with such functionally available in standalone applications as automatic configuration of .pst files for the end user profile.

Those companies that use IP telephony are now able to create SIP URI and E.164 dial plans and add a SIP or E.164 address for a user by using the Enable Unified Messaging Wizard.

Security changes

Exchange Web Services were added with a more granular permission configuration that now supports configuring folder level permissions so that both users and user applications are now able to list and configure permissions on folders. It is also possible to delegate management with services.

Official Document describing what’s new in Exchange Server 2007 SP1
Automatic configuration of mailboxes and Outlook profiles for the client side on the post-deployment stage
Additional information on what you have to do to deploy Exchange Server 2007 SP1 on Windows Server 2008 and Windows Server 2003 family
More information about what’s new about client access features in Exchange Server 2007 SP1

We have several divisions where people mostly roam from one location to another be it a business trip or just a remote work. But as that’s all about doing their jobs they need the information they basically can access only right from the office. One of such types of information is surely their personal corporate mail. That’s how we work today. If we have no access to any collaboration services our work gets stuck. And the mail is the main thing there. So the core task for every system administrator today is how to provide the user with access to their corporate mail remotely from any place no matter where the user will decide to access it from.

How to do that?

One way is to create a Virtual Private Network (VPN). But what if by some reasons you can’t or simply don’t want to setup VPN to avoid making the things for users even more complex? What can you do here? What should you start with? The core term here is “RPC over HTTP“, where RPC is the Remote Procedure Call, a protocol that allows interprocess communications between client and server sides so that a component to be accessed remotely in such a way that we don’t even need to know any low-level information. This is the technology that allows Outlook users to connect to their Exchange mailbox from a remote place. And there’s no need to have a VPN connection. It allows accessing Exchange servers right through your default corporate LAN’s firewall using the basic ports used by browsers to access unsecure and secure contents on the internet. The ports that should be opened to allow access are the TCP port 80 used for basic unsecure connections and the SSL port 443 used for secure connections that are established using the Secure Sockets Layer protocol which is used as basis protocol for the Transport Layer Security (TLS) protocol which version 1.1. is defined in the RFC4346 document.

What should we do to enable all that for our users?

The process contains least two parts we should do to implement the functionality. As we are talking about client-server communications we need to prepare the configurations on both the server as the client. We will consider the Microsoft Exchange Server 2003 installed on the Windows Server 2003 Service Pack 1 and above to be the server side and Microsoft Office Outlook 2003 installed on the Windows XP Professional Service Pack 2 to be the client side.
Configuring Server Side
Let’s start configuring the setup from the server side. First of all we need to configure Exchange Server 2003 back-end server as an RPC proxy server. The process here starts with installing the additional component RPC over HTTP Proxy from the Windows Server Setup Disk. To do that:
1. Click Start and select Control Panel|Add or Remove Programs to start the Add or Remove Programs applet
2. In the Add or Remove Programs windows click Add/Remove Windows Components button
3. The Windows Components screen of the Windows Components Wizard will appear
4. Select Networking Sevices and click the Details button to open the Networking Sevices dialog
4. In the dialog box, check the RPC over HTTP Proxy checkbox and click OK

The RPC component will be installed on the system and the RPC virtual directory will be created on the IIS. Now we need to configure authentication and the encryption.

Configuring client authentication

Basic authentication will be used to authenticate users. This type of authentication has one very annoying property: it sends creadentials in the pure form as the plain text. That’s why we will need to configure SSL and implement the encryption to be used for passing the credentials.
To configure that
1. Click Start and select Programs|Administrative Tools|Internet Information Services (IIS) Manager to start the IIS manager
2. In the manager window navigate to Web Sites and select Default Web Site
3. Expand Default Web Site, right-click the RPC virtual directory, and select Properties command from the shortcut menu
4. In the RPC Virtual Directory Properties page switch to the Directory Security tab
5. Under Anonymous Access and Authentication Control pane click Edit button.
6. The Authentication Methods dialog box will appear
7. Uncheck the Enable Anonymous Access checkbox

That’s needed because by default RPC over HTTP doesn’t allow anonymous access

8. Under Authenticated access section, select the check box Basic authentication (password is sent in clear text)
9. You can also allow the NTLM Windows authentication and leave the Integrated Windows authentication checkbox checked

Microsoft has a note on this type of authentication:
It is recommended that you use Basic authentication over NTLM because of two reasons. First, RPC over HTTP currently supports only NTLM – it doesn’t support Kerberos. Second, if there is an HTTP Proxy or a firewall between the RPC over HTTP client and the RPC Proxy, which inserts via the pragma in the HTTP header, NTLM authentication will not work

10. End with the warning message and ensure that you have correct SSL certificate installed on your server

Now we need to enabled SSL to be used for the RPC Virtual Directory. To do that

1. On the same Directory Security tab mentioned above click Edit button under Secure communications
2. Check both the Require secure channel (SSL) and the Require 128-bit encryption check boxes
3. Click OK to save settings and close the window

See How to Configure the RPC Virtual Directory in IIS article for the detailed info

The next step is to configure the RPC proxy server on Exchange Server 2003 to use specified port range for RPC over HTTP. To do that:
1. Open registry editor by typing regedit in the Run dialog box
2. In the Regsitry Editor navigate to the path


Create the ValidPorts string REG_SZ parameter and set it to the value the is built in the following manner


to open the port range 6001-6002 and one single port 6004

Now we need to configure our Exchange 2003 back-end servers (the GC, Global Catalog servers) and set the NT Directory Services (NTDS) port on them. So we again should to specify registry parameter to do that. This time we need to open the


create a REG_MULTI_SZ ‘NSPI interface protocol sequences’ parameter and set it to value NCACN_HTTP:6004

We ended with the specific preliminary tasks on the server and can start with configuring client application (that is the Outlook 2003) profile to work with RPC over HTTPS. But that’s the story to be covered in the next part when we will talk about client side configuration.

Further info:
RPC over HTTP Interactions on the RPC Proxy Server
How RPC Works
Automatic Configuration of The Client Side
RPC over HTTP Authentication and Security

Technorati tag: