Installation and Co- existence

This part of Exchange Server 2007 includes the interview Questions and Answers on Exchange Server 2007 Installation and Co existence
options introduced in Exchange Server 2007.
If you want know more on Exchange Server 2007 Interview question and Answers, please follow the Questions and Answers posted by me..
please, Leave your comments on this.
1. What are the pre requisites to install Exchange Server 2007?
1. Microsoft .Net Framework 2.0
2. Microsoft ASP .Net
3. World Wide Web Service
4. MMC 3.0
5. Windows power shell
6. SMTP & NNTP service should not be installed
2. Whats the order to install Exchange Server 2007 Roles in a exchange Server 2003 organization?
1. Client Access Server Role
2. Hub Transport Server Role
3. Mailbox Server Role
4. Unified Messaging Server role
3. What are the versions available in Exchange Server 2007?
There are two types of Exchange Server 2007 version release
64 bit for production environment
32 bit only for non-production environment
4. What are the Operating system requirements to install Exchange Server 2007?
Exchange Server 2007 can be installed on
Windows Server 2003 SP2 64-bit,
Windows Server 2003 R2 SP2 64-bit or
Windows Server 2008 64-bit
5. What are the Active directory requirements to install Exchange Server 2007?
1. Domain functional level at least windows server 2000 native or higher
2. Schema Master must be run on windows 2003 server with sp1
3. At least one Domain Controller, in each domain with windows server 2003 sp1
4. At least one global catalog server in Active Directory Site which hosts exchange Server 2007
5. 4:1 ratio of Exchange processor to global catalog server processors
6. What are the hardware requirements to install Exchange Server 2007?
Processor 64 bit processor
RAM 2 GB + 5 MB per Mailbox
Disk Space At least 1.2 GB on the drive on which you install Exchange
- 200 MB of available disk space on the system drive
File Format NTFS
7. What are the Software requirements to install Exchange Server 2007?
Following are the software prerequisites to install Exchange Server 2007
1. Microsoft .Net Framework 2.0
2. IIS
3. WWW
4. MMC 3.0
5. Microsoft Windows Power Shell
8. What is Transition in Exchange Server 2007?
Transition is the scenario in which you upgrade an existing Exchange organization to Microsoft Exchange Server 2007. To perform the
transition, you must move data from the existing Exchange servers to new Exchange 2007 servers. For example, when upgrading from an
Exchange Server 2003 or Exchange 2000 Server organization to an Exchange 2007 organization, you perform a transition
When transitioning to Exchange 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 data to the new Exchange 2007 server.
9. What is Migration in Exchange Server 2007?
Migration is the scenario in which you upgrade to Exchange 2007 by migrating data from a non-Exchange messaging system to Exchange
2007 or from an existing Exchange organization to a completely new Exchange organization, without retaining any of the Exchange
configuration data in the first organization. For example, when merging with another company, you can perform a migration. In this scenario,
you move mailboxes and data to the other companys Exchange organization, without retaining any of the configuration data from your
existing Exchange organization. Another example is when upgrading from Lotus Notes to Exchange 2007, you perform a migration. In this
scenario, you must move mailboxes and data to the new Exchange 2007 organization, without retaining any of the data from the Lotus Notes
organization.
The migration process includes installing a completely new Exchange 2007 organization, and then migrating mailboxes from the old
messaging system to the new Exchange 2007 messaging system, using various tools for migration.
10. Is it possible to do in place upgrade from Exchange Server 2003 to Exchange Server 2007?
No in-place upgrade on existing Exchange server organization. Install new Exchange Server 2007 server into existing organization, and move
data to new server.
11. What are the transition options available in Exchange Server 2007
We can make transition in following options
Single forest to single forest you have an existing single forest Exchange 2003 or Exchange 2000 topology, you can transition to a single
forest Exchange 2007 organization
Single forest to cross forest If you have an existing single forest Exchange 2003 or Exchange 2000 topology, you can transition to a
cross-forest Exchange 2007 topology
Cross forest to cross forest If you have an existing cross-forest Exchange 2003 or Exchange 2000 topology with Exchange servers and
mailboxes in each forest, you can transition to an Exchange 2007 cross-forest topology.
Resource forest to resource forest -
Single forest to resource forest -
12. What are the considerations for Exchange Server 2007 to co exists with Exchange server 2000 and Exchange Server 2003?
Exchange Organization in Exchange Native Mode Exchange Server 2007 routing group (DWBGZMFD01QNBJR) is created
only for coexisting with earlier versions of Exchange.
Routing Group Connector is required between Exchange Server 2003 and Exchange Server 2007 (created during setup).
Exchange Server 2003 computers cannot interoperate with the Unified Messaging server role. Exchange 2003 mailboxes
cannot be Unified Messagingenabled.
Exchange 2003 Front-ends cannot talk to Exchange Server 2007 Mailbox Server Roles.
No in-place upgrade on existing Exchange server. Install new Exchange Server 2007 server into existing organization, and
move data to new server
13. Will Front End server talk to Exchange Server 2007 Mailbox server in an Exchange organization having both exchange 2003
and exchange Server 2007?
Exchange Server 2003 Front-end server cannot talk to Exchange Server 2007 Mailbox Server Roles
14. What is the status of routing group connector in co existed of Exchange Server 2003 and 2007?
Exchange Organization in Exchange Native Mode Exchange Server 2007 routing group (DWBGZMFD01QNBJR) is created only for coexisting
with earlier versions of Exchange.
Routing Group Connector is required between Exchange Server 2003 and Exchange Server 2007 (created during setup).
15. Which service should not be installed in Exchange Server 2007 installation?
SMTP and NNTP service should not be installed
16. What are the Exchange Server editions available?
There are two types of Exchange Server 2007 editions available
1. Standard Edition
2. Enterprise Edition
17. What is the difference between standard and Enterprise Edition?
Exchange 2007 functions Standard Edition Enterprise Edition
Number of Data Stores Supported 5 includes Mailbox/Public Folder 50 combination of both
Clustering support No Yes
OS Support Windows 2003 64 bit Windows 2003 64 bit
18. What to do if exchange Server 5.5 in your organization in order to upgrade to Exchange Server 2007?
You cannot upgrade an existing Microsoft Exchange Server version 5.5 organization to Exchange Server 2007. You must first migrate from the
Exchange Server 5.5 organization to an Exchange Server 2003 or an Exchange 2000 Server organization. Then you can transition the
Exchange 2003 or Exchange 2000 organization to Exchange 2007.
19. What are the Planning considerations for Client Access Server Role?
The Client Access server role supports the Outlook Web Access, Outlook Anywhere, and Exchange ActiveSync client applications, in addition to
the POP3 and IMAP4 protocols. The Client Access server role also hosts several key services, such as the Auto discover service and Exchange
Web Services.
In order to have better client access functionality we have to perform a Planning consideration on Exchange Active Sync. Outlook web Access,
outlook anywhere, POP3 and IMAP4 protocols and also securing client access
20. What are the Planning Considerations of Hub Transport Server Role?
Hub Transport server role is a required role in a Microsoft Exchange Server 2007 organization that provides routing within a single
organizational network by using the Active Directory directory service site. Hub Transport server role installed handles all mail flow inside the
organization, apply transport rules, apply journal rules, and deliver messages to recipients mailboxes
We have to perform a Planning Consideration on
Topology for mail flow inside and outside the Exchange organization
Server capacity determine how to perform performance monitor
Security includes delegation of administrative roles and verification that IP connections are only enabled from authorized
servers
Transport Features determine the transport features that you will enable at the Hub Transport server and how they will be
configured
21. What are the Planning Considerations of Mailbox Server Role?
The Microsoft Exchange Server 2007 Mailbox server role hosts mailbox databases and provides e-mail storage and advanced scheduling
services for Microsoft Office Outlook users The Mailbox server role can also host a public folder database, which provides a foundation for
workflow, document sharing, and other forms of collaboration
We have to perform a planning consideration on
Sizing the database,
Planning for public folder,
Co hosting with other server roles and
Planning for clustered Mailbox server
22. What are the Planning Considerations for Edge Transport Server Role?
Exchange Server 2007 Edge Transport server role is designed to provide improved antivirus and anti-spam protection for the Exchange
organization. Computers that have the Edge Transport server role also apply policies to messages in transport between organizations. The
Edge Transport server role is deployed in an organizations perimeter network.
Edge Transport Should not be included in Active Directory
Should be installed in a Standalone Server
Edge Transport Should not be Part of the domain
ADAM Should be Installed
Pre requisites .Net framework , Windows Management Shell, MMC 3.0


Shadow redundancy components
The following table describes the components of shadow redundancy. These terms are used throughout the topic.

Term Description
Transport server An Exchange server that has message queues and is responsible for routing messages.
In Exchange 2013, a transport server is a Mailbox server (the Transport service on the
Mailbox server).
Transport
database
The message queue database on an Exchange 2013 transport server. Shadow queues
and Safety Net are also stored in the transport database.
Transport high
availability
boundary
A database availability group (DAG) in DAG environments, or an Active Directory
site in non-DAG environments. When a message arrives on a transport server in the
transport high availability boundary, Exchange tries to maintain 2 redundant copies of
the message on transport servers within the boundary. When a message leaves the
transport high availability boundary, Exchange stops maintaining redundant copies of
the message.
Primary message The message submitted into the transport pipeline for delivery.
Shadow message The redundant copy of the message that the shadow server retains until it confirms the
primary message was successfully processed by the primary server.
Primary server The transport server that's currently processing the primary message.
Shadow server The transport server that holds the shadow message for the primary server. A transport
server may be the primary server for some messages and the shadow server for other
messages simultaneously.
Shadow queue The delivery queue where the shadow server stores shadow messages. For messages
with multiple recipients, each next hop for the primary message requires separate
shadow queues.
Discard status The information a transport server maintains for shadow messages that indicate the
primary message has been successfully processed.
Discard
notification
The response a shadow server receives from a primary server indicating a shadow
message is ready to be discarded.
Safety Net The Exchange 2013 improved version of the transport dumpster. Messages that are
successfully processed or delivered to a mailbox recipient by the Transport service on a
Mailbox server are moved into Safety Net. For more information, see Safety Net.
Shadow
Redundancy
Manager
The transport component that manages shadow redundancy.
Heartbeat The process that allows primary servers and shadow servers to verify the availability of
each other.


1. DS proxy service.
Directory Service Proxy (DSProxy) is the Exchange Server 2003 component that provides an address book service to Microsoft Office
Outlook clients. DSProxy is implemented in DSProxy.dll and has two functions:
To emulate a MAPI address book service and proxy requests to an Active Directory server
To provide a referral mechanism so that Outlook clients can directly contact Active Directory servers.
What is a smart host?
7 out of 14 rated this helpful - Rate this topic
Applies To: Windows SBS 2008
A smart host (also known as a relay host) is a dedicated server through which Exchange Server routes all outgoing messages. The
smart host then forwards the message to the remote domain. When you designate a smart host, your Exchange Server needs to
transmit only to the smart host instead of repeatedly contacting the remote domain until a connection is made. This improves the
performance of your server and the reliability of your e-mail delivery.
Contact your Internet Service Provider (ISP) for smart host configuration information.



circular logging

Circular logging is a method of conserving hard disk space in the Microsoft Exchangetransactional logging process. It
works by overwriting individual log files to keep the transactional log (the set of all log files) from expanding without limit
on the hard disk.
When circular logging is disabled, every single log file goes into the transactional logdatabase, and no limit exists as to
how large that database can get. When circular logging is enabled, however, the transactional log can only grow to
one megabyte (1 MB) in size. After that limit has been reached, the first log file is overwritten automatically to keep the
transactional log database from growing any larger. The term "circular" arises from the fact that the set of log files starts
to "rotate" once the disk space limit is reached, something like a LIFO (last-in, first-out) queue.
Circular logging is commonly used with Exchange native data protection, because in that mode, backups are not made so
a detailed transactional log is not necessary. Circular logging is disabled by default in Exchange 2010. That's because, if
circular logging has been enabled and the database becomes corrupted or otherwise compromised, it cannot be
completely recovered if data has been added more recently than the time that the last full backup was created.
Circular logging is an artifact from old versions of Exchange that were released when hard disks were much smaller than
they are today. Contemporary hard disks have more than enough space to run Echoing with circular logging disabled.
The only reason to enable it would be when a hard disk is nearly full.



How can you prevent PF referral across slow WAN links?

On each individual Exchange connector, you can prevent public folder referrals. To do this, right-click the connector,
clickProperties, and then click to select the Do not allow public folder referrals check box. By default, this check box is
not selected.