Q: What is Exchange Server 2007?

A: Microsoft Exchange Server 2007 is the next version of Microsoft Exchange. Microsoft

Exchange is the industry’s leading e-mail, calendaring, and unified messaging server. The

release of Exchange Server 2007 is closely aligned with the 2007 Microsoft Office release.

Together, these products deliver a best-in-class enterprise messaging and collaboration solution.

2.0
Q: What’s new in Exchange Server 2007?

A: Exchange 2007 provides built-in protection to keep the e-mail system up and running and

protected from outside threatsand lets employees work more productively from wherever they are

by using a variety of clients. These clients includeMicrosoft Office Outlook 2007, Microsoft Office

Outlook Web Access, and mobile devices. Exchange Server 2007 makes it easier for IT

departments to deliver these new capabilities to their organizations by making the messaging

environment easier to manage and more cost-efficient. For more information about Exchange

Server 2007, see What's New in theExchange 2007 product documentation.

3.0
Q: How does Exchange Server 2007 integrate with Microsoft Office Outlook 2007?

A: Outlook 2007 provides the most complete e-mail, calendaring, contacts, and tasks functionality

available in an e-mail client that is compatible with Exchange. When Outlook 2007 is used with

Exchange Server 2007, users benefit from the new Scheduling Assistant that automates time-

consuming meeting and resource scheduling, the ability to plan and customize out-of-office

communications, and managed e-mail folders that facilitate compliance with internal and

regulatory policies.Outlook 2007 and Exchange Server 2007 also combine to enhance security by

offering features that are easy to use and let users confidently send and receive sensitive

business communications through e-mail. By enabling the Autodiscover service,you can reduce

the complexity of client configuration and reduce administrative costs that are associated with

troubleshooting connectivity issues for users.

4.0
Q: Where can I find Microsoft Exchange Server 2007 product documentation?

A: You can find Exchange Server 2007 product documentation on the Exchange Server 2007

Technical Library Web site, on the Start menu, or by clicking F1 within the product after it has

been installed. You can also access product documentation from the Microsoft Exchange Server
TechCenter. You can visit the Exchange Server Community Web site or the Exchange Team

Blog Web site for additional product information, common issues, and troubleshooting assistance.

5.0
Q: What are the Exchange Server 2007 licensing options?

A: Customers can purchase the Exchange Enterprise Client Access License (CAL) or the

Exchange Standard CAL. The Exchange Enterprise CAL is sold as an add-on to the Exchange

Standard CAL. Two server editions will continue to be offered:Exchange Server Enterprise

Edition and Exchange Server Standard Edition. You can run either CAL together with either

server edition. For more information about Exchange Server 2007 editions and Client Access

Licenses, see Exchange Server 2007 Editions and Client Access Licenses.

6.0
Q: What do I get with the Exchange Enterprise CAL vs. the Exchange Standard CAL?

A: In addition to the improvements and new capabilities that are available with the Exchange

Standard CAL, the Exchange Enterprise CAL includes Unified Messaging, advanced compliance

capabilities, and on-premises and hosted antivirus and anti-spam protection. For more

information about Exchange Server 2007 editions and Client Access Licenses, seeExchange
Server 2007 Editions and Client Access Licenses.

7.0
Q: What are the different editions of Exchange Server 2007?

A: Exchange Server 2007 is offered in two server editions: Standard Edition and Enterprise

Edition. Exchange Server 2007 Standard Edition is designed to meet the messaging and

collaboration needs of small and medium organizations. It may also be appropriate for specific

server roles or branch offices. Exchange Server 2007 Enterprise Edition, designed for large

enterprise organizations, enables the creation of multiple storage groups and databases. For

more information about Exchange Server 2007 editions and Client Access Licenses, see

Exchange Server 2007 Editions and Client Access Licenses.Hardware and Software equirements

8.0
Q: Will I have to buy new hardware to run Exchange Server 2007?
A: If you are running 64-bit hardware in your current messaging environment, you may not have
to buy additional hardware. However, Exchange 2007 does require hardware and an operating
system that are 64-bit. 64-bit hardware provides the system architecture that is required to
support the increased memory, storage, and enhanced security requirements in a more cost-
effective manner. For more information about how to select the hardware for Exchange 2007, see
How to choose server hardware for Exchange Server 2003 that can be effectively re-used for
Exchange 2007.
9.0
Q: Which 64-bit processors are supported by Exchange Server 2007?

A: Exchange Server 2007 supports servers that have "x64" processors. Most new servers include

processors from Intel and AMD that provide this x64 support. The Intel processors are called Intel

Extended Memory 64 Technology (EM64T), and the AMD processors are called AMD64.

Exchange Server 2007 does not support Itanium (IA-64) processors.

10.0
Q: Should servers that are running Active Directory domain controllers and the global catalog be
upgraded to 64-bit?

A: For the best performance, when an Active Directory organization contains more than 20,000

objects, you should upgrade to 64-bit. Upgrading servers that run Active Directory domain

controllers and the global catalog to 64-bit improves the overall performance and scalability of

your Exchange Server 2007 environment. However, 32-bit domain controllers are still supported.

Lookup and response times between the Exchange 2007 categorizer and the Active Directory

directory service will improve with the use of 64-bit. The size of the Extensible Storage Engine

(ESE) database that holds Active Directory can frequently be larger than 3.0 gigabytes (GB). This

prevents caching of the contents of the whole database, and therefore increases lookup and

response times. By using 64-bit, the available RAM for caching can be increased beyond 4.0 GB.

This is large enough to cache the whole ESE database, even for large Active Directory

organizations, and will improve Exchange 2007 lookup and response times.

11.0
Q: Will I need the 64-bit version of Windows Server 2003 to run Exchange Server 2007?

A: You will need the 64-bit version of Windows Server 2003 or Windows Server 2003 R2 to

deploy Exchange 2007. Volume licensing customers can exchange their 32-bit version of

Windows Server 2003 for the 64-bit version any time by using their media kits.

12.0
Q: How can I upgrade my current Exchange 2000 Server or Exchange Server 2003 environment?

A: When you upgrade to Exchange Server 2007, you cannot perform an in-place server upgrade

on an existing Exchange server. Instead, you must install a new Exchange 2007 server into the

existing organization, and then move the required data to the new Exchange server. Exchange

Server 2007 supports mixed environments that include Exchange 2000 Server, Exchange Server

2003, or both. This allows for an easier and more gradual transition. For more information about
how to plan and deploy Exchange Server 2007, see the Microsoft Exchange Server 2007 product

documentation.
Active Directory

13.0
Q: Should I map my current routing groups to my current Active Directory sites?

A: Yes. Exchange 2007 is based on Active Directory sites. If your current Microsoft Exchange

environment maps as closely as possible to Active Directory sites, your interoperability and

migration story will be easier. Additionally, the recommended upgrade path is to upgrade all the

Exchange 2000 Server or Exchange Server 2003 servers in a single routing group before

you upgrade the next routing group. This lets you fully decommission a routing group as you

upgrade and reduces the complexity of your current routing topology. Mapping the Exchange

2000 Server or Exchange Server 2003 routing groups to the Exchange 2007 physical topology

also makes it easier to plan for an upgrade to Exchange 2007 because the two environments

are similarly organized and generally correlate to Active Directory sites.

14.0
Q: Should I create a dedicated Active Directory site for Exchange Server 2007?

A: You can deploy Exchange Server 2007 directly into your organization’s existing Active

Directory topology. For many organizations, deploying directly into the existing Active Directory

topology greatly simplifies the overall management of the Exchange 2007 deployment. However,

given the extensive access to domain controllers and global catalog servers that is required by

Exchange 2007, you may decide to create dedicated sites for your organization. You might want

a dedicated site if other applications in your organization must access Active Directory domain

controllers and the global catalog server.

15.0
Q: Why do I have to disable link state routing?
A: Link state routing must be disabled whenever two or more routing groups are configured to
send or receive mail from an Exchange 2007 computer that has the Hub Transport server role
installed. (The Hub Transport server was formerly known as a bridgehead server). This is
because Exchange 2007 uses Active Directory to determine routing topology. The Exchange
2007 servers do not propagate link state updates. If link state routing is enabled and there is
more than one routing group configured to send mail to or from an Exchange 2007 Hub Transport
server, routing loops might occur.

16.0
Q: Why are routing groups not used in Exchange Server 2007?
A: Exchange 2007 uses Active Directory sites to replace routing groups. Using Active Directory is

more efficient because it allows for site awareness and eliminates the requirement to create and

maintain a routing topology that is separate from an organization’s physical topology.

Exchange 2007 Server Roles

17.0
Q: Can the Exchange 2007 server roles be deployed and configured on the same physical
hardware?

A: Because Exchange 2007 is role-based, you can deploy all Exchange Server 2007 server roles,

except the Edge Transport server role on a single physical server. If you are clustering, you

cannot deploy the Mailbox server role on the same server as the Client Access, Unified

Messaging, Hub Transport, or Edge Transport server roles. When the server roles are installed

on the same or shared hardware, they function as separate entities.

18.0
Q: Why must I deploy an Exchange 2007 server that has the Client Access server role installed in
every Active Directory site that contains user mailboxes?

A: Installing the Client Access server role in every Active Directory site that contains user

mailboxes reduces the use of corporate bandwidth by redirecting the connection to the Client

Access server that is in the same Active Directory site in which the user's mailbox is contained.

19.0
Q: What if the Client Access server role is not available from the Internet?
A: You can disable redirection for the Client Access server. The Internet-accessible Client Access
server will act as an HTTP proxy to the Client Access server that is located in the same site as
the user’s mailbox.

20.0
Q: Why must I deploy an Exchange 2007 server that has the Hub Transport server role installed
in the same Active Directory site in which I deployed an Exchange 2007 server that has the
Unified Messaging (UM) server role installed?
A: Unified Messaging servers submit voice mail and fax messages to a Hub Transport server by
using SMTP. This can occur only if they are deployed in the same Active Directory site.

21.0
Q: Why must I deploy an Exchange 2007 server that has the Client Access server role installed in
the same Active Directory site in which I deployed an Exchange 2007 server that has the Unified
Messaging server role installed?

A: Unified Messaging Web services that run on the Client Access server enable full client

functionality for UM-enabled users. Additionally, installing and configuring a Client Access server

in the same site as the Unified Messaging servers reduces the bandwidth that is required if they

are deployed in separate Active Directory sites.

22.0
Q: What is the Autodiscover service?

A: The Autodiscover service gathers the required configuration information in Active Directory to

enable Outlook 2007,Office Outlook Web Access, and mobile e-mail clients to efficiently locate

and connect to the appropriateExchange 2007 Mailbox server that contains the user's mailbox.

The Autodiscover service is also used to make configuringOutlook 2007 clients easier and to

provision mobile devices that are used to connect to Exchange 2007. By default, the

Autodiscover service is enabled.

Exchange 2007 Management

23.0
Q: Can I manage Exchange Server 2003 or Exchange 2000 Server by using Exchange Server
2007 management interfaces?

A: No. All administration of Exchange Server 2007 must be done by using the Exchange

Management Console or the Exchange Management Shell. All administration of Exchange 2000

Server or Exchange Server 2003 must be done by using their respective administrative

interfaces. The one exception to this rule is that you can use Exchange System Manager found

in Exchange Server 2003 to perform most Exchange Server 2007 public folder administrative

tasks.

24.0
Q: What is happening with public folders?
A: Public folders are similar to mailbox stores, but the information within a public folder store is
contained within a dedicated database. Exchange 2007 de-emphasizes public folders. Public
folders may not be included in future releases, but support for public folders will be maintained
through at least 2016. Current Microsoft Exchange customers should plan to migrate to
Outlook 2007 and Exchange 2007. We recommend that you investigate integrating
Microsoft Windows SharePoint Services with Exchange Server 2007 if you must have an
application that supports sharing documents, calendar items, contacts, and tasks and archiving
distribution lists. For other customized applications that are being developed, you should use
Microsoft .NET. For more information about public folders, see the Exchange 2007 and Public
Foldersblog.

Tell me a bit about the capabilities of Exchange Server.

1) Outlook Anywhere (OWA)

2) Mailbox Can sync with Blackberry Device.

3) Calender Shairing.

4) MAPI & POP3 Client support.

Exchange Server 2003 (v6.5) debuted on September 28,2003. Exchange Server 2003 (currently
at Service Pack 2) can be run on Windows 2000 Server (only if Service Pack 4 is first installed)
and 32-bit Windows Server 2003, although some new features only work with the latter. Like
Windows Server 2003, Exchange Server 2003 has many compatibility modes to allow users to
slowly migrate to the new system. This is useful in large companies with distributed Exchange
Server environments who cannot afford the downtime and expense that comes with a complete
migration.

One of the new features in Exchange Server 2003 is enhanced disaster recovery which allows
administrators to bring the server online quicker. This is done by allowing the server to send and
receive mail while the message stores are being recovered from backup. Some features
previously available in the Microsoft Mobile Information Server 2001/2002 products
have been added to the core Exchange Server product, like Outlook Mobile Access and server-
sideActiveS ync, while the Mobile Information Server product itself has been dropped. Better anti-
virus and anti-spam protection have also been added,both by providing built-in APIs that facilitate
filtering software and built-in support for the basic methods of originating IP address,SPF
("Sender ID"), andDNSBL filtering which were standard on other open source and*nix-based mail
servers. Also new is the ability to drop inbound e-mail before being fully processed, thus
preventing delays in the message routing system.There are also improved message and mailbox
management tools, which allow administrators to execute common chores
more quickly. Others, such as Instant Messaging and Exchange Conferencing Server have been
extracted completely in order to form separate products. Microsoft now appears to be positioning
a combination of Microsoft Office, Microsoft Office Live Communications Server, Live Meetingand
Sharepoint as its collaboration software of choice. Exchange Server is now to be simply e-mail
and calendaring.

What are the different Exchange 2003 versions?

Go to your server in Exchange System Manager, right-click your server, choose Properties, and
on the General tab make
a note of the version number.
Each version of Exchange Server includes a build number so that you can easily identify which
version of the product you
are running:

6944.4 = Exchange 2003 RTM (including SBS2003)

7226.6 = Exchange 2003 SP1

7638.2 = Exchange 2003 SP2

Features of 2007
Management tool is Exchange Management console
• Compatible on 64 bit OS
• RE-written OWA with browsable GAL
• Restore database to any server
• Message routing based on AD Site
• Storage capacity in STD-5stores Each is 75GB +
ENT-50stores unlimited database
• Unified messaging
• Transport rules
• No in place upgradation
Auto Discover feature inbuild in Exchange 2007 but its
work only with office 2007

Version Features
Standard Edition
The Standard Edition has:
• Up to 5 storage groups
• Up to 5 databases
• 16 TB per database
The Standard Edition supports
Local Continuous Replication.
Enterprise Edition
The Enterprise Edition has:
• Up to 50 storage groups
• Up to 50 databases
• 16 TB per database
The Enterprise Edition supports:
• Local Continuous Replication
• Single Copy Clusters
• Cluster Continuous Replication
# 8 1.Edge Transport server role
2.Anti-spam Connection Filtering
3.Anti-spam: Sender and Recipient Filtering
4.Anti-spam: Safe Sender List Aggregation
5.Anti-spam: Sender ID
6.Calendar Attendant

DSACESS
Starting with Exchange Server 2000 Microsoft began using
the AD - Active Directory as the repository for Exchange
related data. So microsoft had to create certain rules to
make sure that the Exchange Server communiated with the AD
in such a way that it did not create excessive network
traffic or overwhelm domain controllers with too many LDAP
requests. ( For beginners i would like to explain this in a
little more detail - whenever Exchange would need any data
from the Active Directory it will use an LDAP query for
geting the data. Now all the data is present in the AD and
AD is present on DCs - that is Domain Controlers, hence
Exchange would be sending LDAP queries to DCs for the data.)
So for controlling the communication between
Exchange and AD; microsoft created a component called the
DS Access. DS Access would act as an intermediary between
the AD and Exchange Server.
Thus, DS is used by all the Exchange components
to query the AD and acquire the configuration and recipient
information. Example of the Exchange components that use DS
Access are Exchange System Attendant, Message Transfer
Agent and the Exchange information store.
DS Access is a generic name assigned to a group
of DLLs - DSAccess.dll, Dscmgs.dll and Dscperf.dll. These
are collectively called the DS Access or the DS access
cache. The DS Access cache is actually made up of two
seperate caches:

The Configuration Cache - The configuration cache is used

to store information pertaining to the configuration data,
including store and routing objects. It is set to 5 MB by
default.
When the system boots, DS Access initiates a
discovery process designed to identify the AD topology
(primarily related to the site structure), the domain
controllers, and which domain controllers act as global
catalog servers.
DS Access repeats the discovery process every 15
minutes to check for configuration changes and verify that
the known domain controllers are still available. Whenever
Exchange server needs to access a domain controller or a
global catalog server, it consults the DS Access cache to
determine which server is best fit for the job.

The User Object Cache - By default the Exchange Server sets

aside 140 MB for the user object cache, which stores user
object data. Objects within this cache are flushed when the
cache fills up or when the object's TTL expires. The
default TTL for the user object is 5 mins.
This user object cache is designed for preventing
excessive LDAP queries. When the Exchange server needs to
know something about a user, it checks the DS Access cache
first to see if the information is already stored there. If
the information is cached, then Exchange uses the cached
copy instead of issuing an LDAP query. If the required
information is not cached, Exchange has to retrieve the
necessary information from the DC via an LDAP query and it
stores the results in the DS Access cache.

-> Its very simple answer is that when exchenge clients send
request to access his/her mailbox,tthat time exchange sent
cliets request for authentication to dc and for this it
maintains a dsaccess profile in which it maintains the name
of DC and GC server and according to this profile it sends
authentication request to clients nearest dc means dsaccess
is a process which works as bridge between exchnage server
and dc to pass AD releated query from exchange server to
Domain controller.

-> There are many components within Exchange that require

access to Active Directory services, such as the
information store and the message categorizer. The DSAccess
component optimizes the communication between these
components and Active Directory.

The Exchange components that need to interact with Active

Directory use DSAccess to retrieve Active Directory
information rather than communicating directly with domain
controllers and global catalog servers. As a result,
DSAccess is therefore a very important part of Exchange.
DSAccess is good for system performance, since it maintains
a cache that effectively reduces the number of LDAP queries
that these Exchange server components make to Active
Directory. This is good for query speed as well as load
reduction on both domain controllers and global catalog
servers. Note, though, that Global Address List (GAL)
lookups from Outlook clients do not use this cache.

It’s the System Attendant service that initializes

DSAccess, which comes in the form of a Dynamic Link Library
(DLL) file DSACCESS.DLL. In addition to DSACCESS.DLL there
are two other associated DLLs, DSCMGS.DLL and DSCPERF.DLL.
DSCMGS.DLL contains the information DSAccess uses to write
event log entries, whilst DSCPERF.DLL contains performance
object information.

To see which processes are using DSACCESS.DLL, you can use

TASKLIST.EXE (Windows 2003 and Windows XP) or TLIST.EXE
(older versions of Windows) for from a command line by
running the following command on your Exchange server:

tasklist –m dsaccess.dll

You should see output similar to that shown in Figure 1,

where you can see that processes such as the Information
Store (store.exe) and the System Attendant (mad.exe) are
using DSACCESS.DLL.