What’s new in Exchange 2010 Service Pack 3

The Exchange Team is pleased to announce that in the first half of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.


Enabling DHCP Support for Multiple Subnets

Enabling DHCP Support for Multiple Subnets

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

If you have multiple subnets in your network, and do not have a DHCP server on every subnet, determine whether your current routers relay DHCP/BOOTP messages.

If your routers cannot be used for DHCP/BOOTP relay, set up a DHCP/BOOTP relay agent on at least one computer running Windows Server 2003 on each subnet. The DHCP/BOOTP relay agent relays DHCP and BOOTP message traffic between the DHCP-enabled clients on the local network and a remote DHCP server located on another physical network by using the IP address of the remote DHCP server.

Figure 2.3 shows a simple, routed network in which the router acts as a DHCP relay agent.

Subnets Configured to Use a DHCP Relay Agent

If your routers cannot be used for DHCP/BOOTP relay and you choose not to configure DHCP/BOOTP relay agents, you must configure your network so that a DHCP server has a network adapter on each subnet it serves. You can accomplish this by either placing a DHCP server on each subnet, or by multihoming DHCP servers. This distributed configuration does not provide fault tolerance. If a DHCP server becomes unavailable, DHCP clients on the subnet cannot receive IP addresses and options.


  • The DHCP Relay Agent service is available only on computers running Windows Server 2003, Microsoft® Windows® 2000, or Windows NT 4.0. To use the DHCP Relay Agent routing protocol, the Routing and Remote Access service must be installed and enabled.

For more information about installing and configuring DHCP relay agents, see “Configure the DHCP Relay Agent” in Help and Support Center for Windows Server 2003. For more information about the DHCP Relay Agent service, see the Networking Collection of the Windows Server 2003 Technical Reference (or see the Networking Collection on the Web at http://www.microsoft.com/reskit) or see Help and Support Center for Windows Server 2003.

Belal HOZIEN | IT Pro

About Microsoft UM & Virtualization

The WordPress.com Blog

The latest news on WordPress.com and the WordPress community.