Datasheet

34 CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010

Note that some of the advanced device conﬁguration features require the use of an Exchange

Server 2010 Enterprise Client Access License (CAL) for the device. This does not mean that the

Exchange 2010 server requires the Enterprise Edition of Exchange Server, though.

Now, Where Did That Go?

As new and better functions and APIs have been introduced, naturally some functions are no

longer emphasized or supported. There has been a lot of confusion surrounding what will con-

tinue to be supported in Exchange 2010 and w hat will no longer work. The phrase ‘‘no longer

supported’’ itself tends to also generate a lot of confusion because a function may actually con-

tinue to work because it has not truly been removed. These functions and APIs fall into two

unique categories: functions that have been deemphasized and functions that are no longer

available.

Deemphasized Functions

When Microsoft says that in Exchange 2010 certain functions or APIs are no longer empha-

sized, this means that the company will not continue to enhance these features. The features

will continue to be supported, and if there are bugs with these features, the bugs will be ﬁxed.

However, if something is being deemphasized, the writing is on the wall; you should consider

replacing your use of this technology with something else.

The following is a list of some of the APIs and functions that are being deemphasized:

◆ Public folders are still supported in Exchange 2010, but their use is b eing deemphasized

as newer collaborative technologies have been introduced, such as SharePoint and other

portal technologies.

◆ Collaborative Data Objects technologies such as CDOSYS, CDO 1.2.1, and CDOEXM have

been removed completely. Applications using these APIs should be rewritten using the

Transport Agents API or Exchange Web Services API.

◆ Functions provided by Exchange WebDAV extensions are now provided by the Web

Services API. If you have applications that require WebDAV, you will have to either

update them or keep an Exchange 2003/2007 server running.

◆ The Exchange Object Linking and Embedding Database ( ExOLEDB) API functionality is

now provided via the Web Services API.

◆ Store events were removed from Exchange Server 2010 and should be replaced with

functions written using the Web Services API.

Features No Longer Included

As Exchange Server has evolved into its current form, the code has experienced signiﬁcant

changes. This includes many of the new features we have discussed in this chapter, but there

have also been features and programming interfaces that have been removed because it just no

longer makes sense to support outdated technologies.

Some features and APIs have been completely removed from the Exchange 2010 product.

If you require any of these features or APIs, you may need to keep an Exchange 2003 server

in operation. If you still require features provided by the Exchange 2000 Server platform, you

are not even going to be able to transition to Exchange Server 2010 until you can replace that

particular feature requirement with newer software.