Feature Changes from Exchange 2003 and 2007 in Visual C#

Printer PDF 417 in Visual C# Feature Changes from Exchange 2003 and 2007

As with every new version of software, features and functionality of previous versions will be retired. As technology continuously advances and changes, the Microsoft product group has to balance adding new functionality, maintaining existing functionality, and removing outdated functionality for Exchange 2010. Of course, you can retain Exchange 2003 or 2007 functionality by keeping a legacy Exchange server to use only for that functionality, but it s always an in-between step. Therefore, if you re currently running Exchange 2003 or 2007 it is important to clearly understand your current messaging environment in terms of used features and what protocols your applications use. This will prevent you from unpleasant surprises such as an application that stops working because you moved the mailbox to Exchange 2010.

Table 1-2 lists all Exchange 2003 features that are no longer available and explains their replacement functionality available in Exchange 2010.

Administrative groups Routing groups Link state routing Recovery storage group Routing objects Event service Intelligent Message Filter Microsoft Exchange Connector for Novell GroupWise and migration tools Microsoft Exchange Connector for Lotus Notes Network News Transfer Protocol (NNTP) X.400 message transfer agent (MTA) Exchange Installable File System (ExIFS) Exchange extensions in Active Directory Users and Computers (ADUC) Exchange Server Mailbox Merge wizard (ExMerge.exe) Clean Mailbox tool Exchange Profile Redirector tool (ExProfRe) Recipient Update Service Monitoring and status node Message Tracking Center Mailbox Recovery Center Mailbox Management Service Migration Wizard

RBAC permission model. Active Directory site-based routing model. Recovery database. No replacement. Anti-spam agents available in Edge or Hub Transport. No replacement use a third-party migration tool for migration.

Recipient management is exclusive to EMC or Windows PowerShell. Use the Export-Mailbox cmdlet in Exchange 2010 RTM or the NewMailboxExportRequest cmdlet in SP1. No replacement. No separate service available; use EMS for the same functionality. Exchange 2010 Management Pack for SCOM. Use Message Tracking or Tracking Log Explorer tools. Use the Restore-Mailbox cmdlet. Retention Policies or Messaging records management (MRM). Use the Local Move Request and Remove Move Request wizards.

Non-MAPI top-level hierarchies in a public folder store NNTP access to Public folders IMAP4 access to Public folders CDO 1.2.1 MAPI32 CDOEX (CDO 3.0) Exchange WebDAV ExOLEDB Store events

Even though Exchange 2007 looks very similar to Exchange 2010, there have been quite a few changes, as listed in Table 1-3.

Cluster continuous replication (CCR) Standby continuous replication (SCR) Single copy cluster (SCC) Local continuous replication (LCR) Storage groups Extensible Storage Engine (ESE) streaming backup APIs DSProxy Exchange WebDAV Move-Mailbox cmdlet Setup /recoverCMS OWA Document access OWA Web Parts Microsoft Transporter Suite for Lotus Domino or IMAP/POP3 migration Exchange UM Test Phone

Database availability groups (DAGs).

No replacement. Every database has its own set of transaction logs. VSS plug-in for Windows Server Backup. RPC Client Access and Address Book service. Protocols no longer available; use EWS or EWS Managed API. Use Local Move Request and Remove Move Request wizards. Setup /m:RecoverServer. No replacement. Not implemented in Exchange 2010 RTM, again available with Exchange 2010 SP1. No replacement use third-party migration tool for migration. Can still be used with Exchange 2010 RTM, but must be replaced in SP1 with the UM Troubleshooting Tool.

of legacy Exchange versions, you should plan to keep an Exchange server of the required version in operation to ensure continued access to the functionality. however, you should not underestimate the additional effort this creates, such as the need to migrate in a two-step approach from Lotus Domino to Exchange 2007 and then to Exchange 2010.

A traditional Exchange installation requires hardware that is placed in your datacenters, the purchase of software licenses so that the product is allowed to run, and administrators that manage the servers. For some time there has been a push for on-demand service provisioning, where users only pay for the service they use, not for the complete cost basis to establish and deliver the service. In early 2006, Microsoft introduced the idea of Software as a Service (SaaS) to provide application services on-demand and called their in-the-cloud messaging service Exchange Online. To distinguish between Exchange Online and the installation you run in your own company, Exchange 2010 uses the term Exchange On-Premise (or on-prem) because the servers run on your premises. Today s version of Exchange Online is based on Exchange 2010. The two service options available for Exchange differ in the following ways:

Exchange On-Premises This version is generally dedicated to the customer,

Exchange servers are placed in a datacenter for the customer (on the customer s premises), and licensing is a fixed price including both hardware and software licensing.

Exchange Online This service is provided as multi-tenant or hosting service,

generalized and highly standardized for many customers. Licensing is on-demand, meaning that you pay only for the mailboxes you use. The Exchange servers are placed in a common datacenter and you connect to it over the Internet using a secure connection.

Microsoft provides Exchange Online service as part of the Business Productivity Online Services (BPOS) line. Exchange Server 2010 is the first version of Exchange that provides a real hybrid approach to Exchange Online services. It was fully designed to allow you to host your sensitive users on-premises and move the rest to the cloud, or in this case, to Exchange Online. Coexistence between the users is achieved by Exchange 2010 s new feature, Federation Service, which allows sharing mailbox information such as free/busy times with another company, as shown in Figure 1-9. All Exchange 2010 Management Consoles such as EMC are capable of managing both an on-premises and an online setup. Thus, running an Exchange organization that operates as a hybrid service can be a real option for your company to reduce the costs of mailboxes. Features include moving mailboxes from on-premises to Exchange Online while the user of the mailbox is logged in and on a scheduled basis, as well as the ECP, which supports self-service control for users. Of course, Microsoft is not the only company that delivers hosted Exchange 2010. Some companies have hosted Exchange for 10 years or more and have much experience