c


 



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.



  



A: Exchange 2007 provides built-in protection to keep the e-mail system up and running and protected from outside
threats and lets employees work more productively from wherever they are by using a variety of clients. These clients
include Microsoft 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 the Exchange 2007 product documentation.



 

   
  !"



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 Auto discover service, you can reduce the complexity of client configuration and reduce administrative
costs that are associated with troubleshooting connectivity issues for users.

#
 $  

 

%  & 

A: You can find Exchange Server 2007 product documentation on theExchange 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 Tech Center. 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.

'
 

! 

% 


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.

(
$  %

)*+
 )*+

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, see Exchange Server 2007 Editions and Client Access Licenses.


   
 



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 Requirements

:
 !!$, -  



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.

.
 (#/, % 



%%,- 



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.

c

 !

  *  0  -&  !!
!,! !, %(#/
, 

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.

cc
 !!$(#/, 

 


  



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.

c
 $ %&-  


 

 &

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 moreinformation
about how to plan and deploy Exchange Server 2007, see theMicrosoft Exchange Server 2007 product documentation.

Active Directory

c
 !$&%&-    %

&- *  0  -



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.

c#
 !$  *  0  -

 



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.

c'
-$
,!! "
  

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 2007servers 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.

c(
-   %

  



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

c
) 


!
,%!-   
&%-
!

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.

c:
-&
$%!- 



)! * 


! 
!! -*  
0  -
  

& !,


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.

c.
 )! * 


!
 !,!&$

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.



  - &

 $ %!-    


  
   , 1
%
 ! 
!!  
&
*  0  -
  $%!- 



2  

 324
!

!!

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.
c
-&
$%!- 



)! * 


! 
!! 
&*  
0  -
  $%!- 



2  

 
! 
!!

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.



* 

 

A: The Auto discover 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 appropriate Exchange
2007 Mailbox server that contains the user's mailbox. The Auto discover service is also used to make configuring
Outlook 2007 clients easier and to provision mobile devices that are used to connect to Exchange 2007. By default, the
Auto discover service is enabled.

Exchange 2007 Management


)$&  

 


 ,-

  

&&
 


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.

#

%%  % ,! !


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 Folders blog.

1!!&, ,  %, !  

  

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 MicrosoftMobile Information Server 2001/2002
products have been added to the core Exchange Server product, like Outlook Mobile Access and server-side ActiveSync,
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"), and DNSBL 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, and Live Meeting and Sharepoint as its
collaboration software of choice. Exchange Server is now to be simply e-mail and calendaring

  






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:

(.## # = Exchange 2003 RTM (including SBS2003)

( ( = Exchange 2003 SP1

(:  = Exchange 2003 SP2

5 
 !,!  

6c

The following new features for high availability and improvements to existing high availability features are available in
Exchange 2007 SP1:

jÊ Standby continuous replication (SCR)

jÊ Support for the following features in Windows Server 2008:
—Ê Multiple subnet failover clusters
—Ê Dynamic Host Configuration Protocol (DHCP) Internet Protocol version 4 (IPv4)
—Ê IPv6
—Ê Exchange and failover cluster network configuration
—Ê New quorum models (disk and file share witness)
jÊ Continuous replication (log shipping and seeding) over a redundant cluster network in a cluster continuous
replication (CCR) environment
jÊ Reporting and monitoring improvements
jÊ Performance improvements
jÊ Transport dumpster improvements
jÊ Exchange Management Console improvements

 



(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 MicrosoftMobile Information Server 2001/2002
products have been added to the core Exchange Server product, like Outlook Mobile Access and server-side ActiveSync,
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"), and DNSBL 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 Meeting and Sharepoint as its collaboration software of
choice. Exchange Server is now to be simply e-mail and calendaring.

Exchange 2003 provides improved functionality in the following areas:

jÊ Routing
jÊ Support for Volume Shadow Copy service
jÊ Support for Outlook 2003 Cached Exchange Mode
jÊ Outlook Web Access for Exchange 2003
jÊ Mobile Device Support for Exchange 2003
jÊ 

) "!
!  7 )  &

The following checklist outlines the physical and logical factors you should take into consideration when assessing your
current environment before deploying Exchange.

6-
!%!

jÊ Data center floor space

jÊ Rack space
jÊ Network sizing
jÊ WAN (may need to provision higher bandwidth connections)
jÊ Degree of separation between physical sites (latency introduced)
jÊ LAN upgrades
jÊ Backbone
jÊ Modem pools or alternate dial-up
jÊ Hardware needs
jÊ Servers
jÊ Memory
jÊ Processor
jÊ Storage
jÊ High bandwidth network interface cards (NICs)
jÊ Routers
jÊ Memory
jÊ Processor
jÊ Switches
jÊ Firewalls
jÊ Power
jÊ Power grid Service Level Agreement (SLA)
jÊ Projected power draw
jÊ Uninterruptible power supply (UPS) or other power-insulating device (generators, etc.)
 jÊ Designated "hot" site

 

jÊ Training on newly introduced technologies and procedures

jÊ Augmentation
jÊ Administrators
jÊ Support staff

V%-

jÊ Time zone issues

jÊ Languages

*8

jÊ Encapsulation upgrade (asynchronous transfer mode [ATM], etc.)

jÊ Optimization (permanent virtual circuit [PVC] for frame relay)
jÊ Overall quality of connections

+*8

jÊ Encapsulation change (token ring to Ethernet)

jÊ Layer 2 device removal or upgrade

8"

jÊ TCP/IP end-to-end
jÊ IP Hop count between endpoints
jÊ Subnetting considerations (Microsoft® Active Directory® directory service site considerations)
jÊ Device configuration
jÊ Routers and open ports
jÊ Switches
jÊ Firewalls and open ports
jÊ Ports and layer 4 protocols enabled on filtering or blocking devices
jÊ All encryption and decryption operations
jÊ All format-change operations (for example, other mail gateways and X.400 connectors)
jÊ remote procedure call (RPC) connectivity
jÊ network basic input/output system (NetBIOS)
jÊ Public key infrastructure (PKI)
jÊ Virtual private network (VPN)
jÊ Shared dependencies between Internet Information Services (IIS), Simple Mail Transfer Protocol (SMTP), and
Network News Transfer Protocol (NNTP)
jÊ DNS
jÊ Windows® Internet Name Service (WINS)

8"% 
-
&

jÊ Shared dependencies between DHCP, NTLM, NTLMv2, and LM

jÊ Windows NT® Server version 4.0 domain structure: Trusts, primary domain controllers, backup domain
controllers
jÊ Windows 2000 Server or Windows ServerΡ 2003 Active Directory
 jÊ Forest structure
jÊ Domain structure
jÊ Migration
jÊ Site structure

  -

jÊ Kerberos
jÊ Migration
jÊ Security principles
jÊ Security identifier (SID) history

0   


jÊ Migration
jÊ Active Directory Connector
jÊ Meta directories

*& 
 

jÊ Migration
jÊ Permissions delegation
jÊ Management

&9" 
  
 
!!  




 


:
!  

 
!! 

Before breaking out the Exchange CDs and actually installing Exchange 2003, you must decide your strategy and tactics.
If you have not done this see (Check Exchange Migration Strategy here)

You may already realise that Exchange 2003 needs to extend the Active Directory schema. This makes sense when you
realize that a mailbox is now an attribute of the user, hence the user object needs extra attributes which translate to
tabs in the user property sheets. Best to install Exchange 2003 in an Windows Server 2003 domain, rather than a
Windows 2000 domain. (Check Exchange Compatibility here)

If you are migrating from Exchange 5.5 to Exchange Server 2003, then remember that the old Exchange 5.5 has its own
directory database (Dir.edb).As a pre-requisite to installing Exchange 2003, this account information must be
transferred to Windows 2003's Active Directory. Incidentally, Exchange 2003 also relies on Windows 2003 for IIS,
account security, Event Viewer and the SMTP service.

 

0% 


Exchange Server 2003 Requires the following Windows 200x services

jÊ .NET Framework
jÊ ASP.NET
jÊ Internet Information Services (IIS)
jÊ World Wide Web Publishing Service
jÊ Simple Mail Transfer Protocol (SMTP) service
jÊ Network News Transfer Protocol (NNTP) service

For security reasons in Windows 2003 IIS is locked down, so not only make sure that you install the services, but also
that the corresponding services are set to Automatic. Finally start the service.
ã/  
 



lust like its predecessors, Exchange 2003 comes in two editions. Always choose the Enterprise edition because it has no
limit on the mail Store database. The standard edition should come with a warning that the 16 GB limit will be
insufficient for all but the smallest organization.

As a consultant, I have had several assignments helping people when they reach the 16 GB limit. Whilst each job gave
me work, I had this feeling that the problem should have been avoided, that Microsoft should place a warning on that
Standard Edition - ' Beware you will be in trouble when you hit the 16 GB store limit '.

The Enterprise edition also supports multiple mailbox stores which means that you can have different backup strategies
for different users. Naturally, you would need the Enterprise version of Exchange and Windows if you wished to create a
cluster of Exchange servers.

Get a test machine to install Exchange 2003, then you can practice with its quirky setup interface.

$
!! 

 



4Ê  %;

%%
,4Ê  %;& %%
4Ê 5 !!-%! 
 %

If you are new to Exchange 200x, a further difficult is that the setup menu is quirky. Exchange has several strange drop
down menus which are not seen in other Microsoft setup programs. However, once you run this setup menu a few
times, you begin to understand how its mind works and configuration becomes easier.

There are two reasons why you may want to install Exchange 2003 in stages, security and the time it takes to run the
first full setup. The adage: 'The more security you have the more work there will be', applies here. To install Exchange
2003 you must be not only an Administrator, but also a member of the Enterprise Admins and Schema Admins.
Incidentally, consider creating a special domain account which will used in installation, and then this account will
become the first Exchange 'Full Administrator'.

What setup /forestprep does is create the Exchange Organisation name in Active Directory. So be very careful with this
Organization name as you cannot change your mind later. In addition /forestprep extends the schema and modifies the
users attributes to include a mailbox. In practical terms, this means that 4 new tabs will appear on the User's property
sheet as viewed in Active Directory Users and Computers.

Make sure that you run /forestprep on the domain controller which is also the schema master and preferably a Global
Catalog server.

Setup /domainprep creates two new security groups: Exchange Domain Servers and Exchange Enterprise Servers. You
can inspect the new groups in the USERS folder of Active Directory Users and Computers. /domainprep also creates the
Exchange System Objects container in Active Directory.

The other benefit of running /forestprep and /domainprep switches early in the deployment is that it will save time
later; allowing ordinary administrator to install the exchange binary files more quickly.

Now would be the time to run Exchange 2003's setup and install the binary files. Once that's completed verify the
installation by checking the services, and if it were me I would be desperately keen to send my first email in my new
Exchange Organization.

2$
!!

If you have lots of servers to install, and you distrust Ghost for such an important job, you could try creating an
unattended 'Answer' file by using setup /createunattend on the first, perfectly installed server. Then, use the
/unattendfile switch when installing the other Exchange 2003 servers. For more details try setup /? at the command
prompt.

s&&,-
)/
 

Keep in mind that your strategy for this phase of the migration is co-existence between Exchange 5.5 and a new
Exchange 2003 server. Temporarily, both generations of Exchange will be in the same site of the same organization.
Eventually, you will decommission the Exchange 5.5 servers but for now both servers will be active and communicating.
Remember that even if you wanted to, it is not possible to make an in-place upgrade of the Exchange 5.5 servers to
Exchange 2003.

When you run setup on the Exchange 2003 server, you will need the name of an existing Exchange 5.5. server as well as
the NT 4.0 service account name and password. A final complication is that you may need to be an administrator in the
NT 4.0domain and this may involve creating trusts and adding the Active Directory installation account to the NT 4.0'
Administrators Local Group.

Read all menus and error messages ʹ extra carefully.

1 ,!
 $
!!  



jÊ Made sure you have enough Disk Space

jÊ Check the Edition of Exchange Server (Enterprise is best)
jÊ Check Active Directory, a user's property sheet is a good place to start.
jÊ Check DNS.
jÊ LDAP port 389 in use, so cannot connect to Exchange 5.5.Solution change and synchronise port numbers.
jÊ If installation fails make sure you delete EXCHSRV \mbdata before trying again.
jÊ Why does no-one ever check the Event Viewer? If there is a problem you will see a red error dot in the logs.
Remember to check the Application log as well as the System log.If the messages are not self explanatory, look
up the error number in TechNet.
jÊ Check that ALL the IIS components are installed including SMTP and NNTP. Make sure that ASP.NET and
jÊ .NET Framework are also installed.
jÊ Run DCDiag or NetDiag for extra clues as to what is wrong with the server. See more on DCDiag

$  $
!!  



All installations reward planning; in the case of Exchange 2007, decide on the underlying operating system and then
decide which Exchange roles to install. What makes setting up Exchange 2007 such a joy is the way the wizard helps you
check the pre-requisites. For example, it prompts you to raise the domain level, and shows you the way to install .Net
Framework 2.0

The trickiest feature of Exchange 2007 is not the installation, but the new method of creating Mailboxes from the
Exchange manager. In Exchange 2007, creating mailboxes (mailbox enabled users) with Active Directory Users and
Computers is fool's gold. Any objects you manage to create have no SMTP address and don't work. You simply must use
the Exchange Management Console to create mailboxes.

c c c)
- 2!- % -
&

Before you install Exchange Server 2007, you need a 64-bit operating system; I choose the Windows Server 2003 R2
rather than the minimum requirement of Windows Server 2003 with SP1.

An even better option would be to install Exchange Server 2007 SP1 on Windows Server 2008, but note those three
letters: SP1. lust to emphasise that for Server 2008 you need the later, slipstreamed SP1 DVD (or image), and not the
original RTMdisk. Furthermore, you need a clean install of Windows Server 2008 on 64-bit hardware, and not an
upgrade from W2K3.
It terms of tactics, Microsoft recommend that you install Exchange 2007 on member server. Exchange on a Domain
Controller is not supported, and should only be used for testing where you only have one machine. If you have already
prepared your domain, then jump to Key preparation steps

c c *  0  -

Creating the Active Directory domain is not strictly a part of installing Exchange, I added here below a brief description
of the most important features for the sake of completeness.

0& 5   !+!

The Domain Function Level must be at least - Windows 2000 Server Native. Fortunately, this is not a great burden as
there is only one lower setting, 2000 Mixed. This is a reminder that Exchange Server 2007 has Severed the umbilical
cord to Exchange 5.5.Thus all those old 5.5 servers must be decommissioned and removed if you are migrating an
existing organization to Exchange Server 2007.

You also need to check the Forest Functional Level, particularly where you want the advanced features of Exchange
2007. Incidentally, Functional Level is my one of my 'Litmus tests' for seeing if people have sufficient Active Directory
knowledge to install Exchange 2007.If someone does not know how to find and configure Function Levels, then they are
likely to need help installing Exchange 2007.

V!,!)!

Every active directory site where you install Exchange Server 2007 needs at least one Global Catalog server. As you may
know, GC is a configurable role of every domain controller.

-
&$ /080& )   

A trivial task, I appended the fully qualified domain name to the hostname. What I did was open the System Icon,
Computer Name (Tab), click on the Change button.

As with Exchange 200x, the mail server relies on Active Directory. Therefore, I installed a Windows Server 2003 (RC2)
member server then ran DCPROMO, from there I followed the wizard's prompting to create a new domain in a new
forest.

08/* &   <s 

When I installed my active directory domain, the plan was to persuade DCPROMO to install DNS using the wizard to
automatically add all the _SRV records. To succeed, at the menu below, I elected the middle (automatic) option, Install
and configure DNS server on this computer.
I was taken aback to get an error message, however, I allowed the DCPROMO to finish, then I went to the Services and
Stopped then restarted the Netlogon Service. What followed was a magic moment, restarting the Netlogon Service
triggered the creation of all the DNS records under _msdcs.

The bottom line is check that DNS has the 'A' Host record for each Exchange 2007 server.

c c =-%% 
%
,-  
!! 



At every stage of installing Exchange 2007, kind friendly wizards guide you through the minefield. Here is a screen shot
of the wizard checking then explaining a problem with mixed mode.

s
0& +!

As indicated by the wizard, I needed to Raise Domain Level 2003 (2000).What I did was launch the ADUC (Active
Directory Users and Computers), right click on your domain and select, Raise Domain Function Level. As I had no old
domain controllers, I chose Windows Server 2003.

V!,!)!
I would like to give a timely reminder of the importance of Global Catalog to Exchange. Insure that at least one Domain
Controller on the subnet where you install Exchange 2007 has Global Catalog enabled.

85&"


Exchange 2007 requires .Net Framework 2.0 (or 3.0). We need to install PowerShell before the main Exchange 2007.This
is an indication of the importance of the new PowerShell / PowerShell cmdlets.

)


One minor surprise, was that when I installed on Windows Server 2003, Exchange 2007 needs MMC v 3.0.

6!!

Once you start using Exchange Server 2007 it wont belong before you meet PowerShell. If follows therefore, that you
have to add it as a 'Feature' of Windows Server 2008, else, on Windows Server 2003 install PowerShell together with
.Net Framework by downloading the files from Microsoft's site.

(#/, 

Production versions of Exchange 2007 require 64-bit hardware. Don't be lulled by 32-bit beta versions of Exchange
2007, they are only for testing, and for a specific preparation context. That context is to prepare Active Directory and
domains for Exchange 2007 from a computer that has a 32-bit processor. Remember that Exchange 2007 will be the first
Microsoft product which runs solely on 64-bit processors.

Other than this processor requirement, just use common sense and provide plenty of RAM. It's also worth spending a
few minutes thought and planning on the disks sizes and partitions, particularly servers hosting the Mailbox Role. For
larger organization, this would be a good time to review your SAN (Storage Area Network) needs.

88816

Finally, avoid 'over-think', you do not, repeat, not need the NNTP service. The good news is that the wizard coupled with
the result pane not only alerts you to the problem, but also suggests a remedy.

c c #Installation Switches to Prepare Active Directory

Prerequisites, you need the Exchange Server 2007 disk or image.(SP1 would be even better)Each command is prefaced
by setup. You could also try setup /? to see the full list of options, for example: /mode or /role.

 % /PrepareADCreates the necessary global Exchange objects and universal security groups in Active Directory.Must
be run by a member of the Enterprise Admins group, run this command in both the root and current domain. You may
find that if you run this command as a Schema Admin (and Enterprise Admin), there is no need to run the other
commands.

/PrepareLegacyExchangePermissions This command is needed if your organization contains Exchange Server 2003 or
2000 computers. It modifies the permissions assigned to the Enterprise Exchange Servers group so that the Recipient
Update Service can run. Remember to logon as a member of the Enterprise Admins group.

/PrepareSchema This prepares the Active Directory schema so that it allows Exchange Server 2007 to install. You must
be amember of both the Schema Admins and Enterprise Admins. You need to run this command in the root domain, or
the domain which holds the Schema Master role.

/PrepareDomain /PrepareDomain domain name This creates a new global group in the Microsoft Exchange System
Objects container called Exchange. You must be a member of both the Enterprise Admins and the Domain Admins
group.

One more point, if you are using a Windows Server 2008 computer, first install the AD DS management tools.


c c '  ! >  %!  ,


  
ï ce e
 c 
e se      s es s s s e e s ye e
  y See eF ee ye 
 se -- Sce  s

 c e c
e  
ee   se seec c s c
e   e e  ee   
 y  s  see e
F e e ye   s  ese c 
  ss  e    
 v y ee 
  
c Se ve 
e s  y  e 
eve   e  e e
 e  es 
 es  y   
e      ev sy
c se ec



ey vee 
ee  see eec ce ves
ee -- Sce  s s

e ev sesess e  v yee 
 
cc
e2007e esy e

c c (
    )
+


jÊ ece s 
!!"c
eSe 
s scecesyse c eve 
s
jÊ  cec
e 
ee  se cecy  e
y sec
ese ve ss  
e
 s ceceï
  #esesesy  e
jÊ  ee-e e se  e c ec s
ï e ccess  ï ce 
y  ee 
jÊ ï cey c ee Se ve seey c  ecevee  e -e ecc 
jÊ F  Sse ve ses ey cec
ï 
jÊ  ecsee
eSe ve se e ee  e ecc 
jÊ ecse vcesseeee  sc sc
eSe vces e 
#eeye
 

c s  c
e
jÊ  y
sees

cecec
ees e e!!"$ 
Fes"c s"c
eSe ve 
jÊ e e es % c es   e eseeeB$ &c
eSe ve  Bes $ cces ye '
e  ec
e2007e esscec(ees
ys cec
e 
ee  se 
e e( e ey 
 ec
eSe ve Bes$ cces yse 

c c  


 !



ï ceceee e  yses

s ey e c
e2007 s   e e
s
ece  e e  es y ec
ese ve  seecey c 
ys e se  e
es

c c:*   ! 
 




  
 !



!,



(sc-e se ve  eesS 

)! * 

3)*4

The CAS server also requires ASP.Net and the WWW service. Remember that this should be the first role to implement
for Exchange Server 2007.See more on CAS

2  

 

Needs specify. No worries, setup will automatically install as needed. This Unified Messaging role provides integration
for email, calendars, voicemail and if you still use it, fax.

ã 

No special requirements

1
%

The Edge Transport Server (Formerly Gateway Server) must be in it's own workgroup. lust will not operate in a Domain
for the obvious reason of security.

The role of Edge Transport server is to accept messages from the internet that come are addressed to your Exchange
2007 organization. After these emails are processed, the Edge server routes them to the Hub Transport servers inside
your organization.

)! s &

Mapi clients need Outlook 2002 or later. Outlook 2007 is by far the best client. Outlook 2007 and Exchange 2007 are
made for one another.OWA (Outlook Web Access) is a great alternative all clients need is a browser.

c c .1 ,!
  

6c$
!! 6,!&


6,!&6 ,! 5!s%! 


Solution: Temporarily disable the OAB, then delete the replicas or move them to another Exchange server. This task is
ideal for PowerShell:

The cmdlets are

get-PublicFolderStatisticsCheck the situation

get-PublicFolder
remove-PublicFolderDangerous if you don't know what you are doing, effective if you do.

Get-PublicFolderStatistics -Server <YourExchangeServer> | fl

Get-PublicFolder -Server <server containing the public folder database> "\" -Recurse -ResultSize:Unlimited | Remove-

PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue

Get-PublicFolder -Server <server containing the public folder database> "\Non_Ipm_Subtree" -Recurse -
ResultSize:Unlimited |

Remove-PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue

6,!&& !*

6! -

Solution: Check the Exchangesetup.log for this message:

[ERROR]The Exchange server Address list failed to respond- error 0x8004010f

Next launch the Event Viewer and check the Application log (not the system log) for Event ID: 8325.If you examine the
details it will tell you precise Filter Rule that is preventing installation.

This problem occurs when you add the Mailbox role to Exchange 2007.The root cause was an incorrect filter was
created in Exchange 2003.

6,!&
 ,9  *  0  -

[ERROR] Active Directory operation failed on DC.YourDom.com The object 'CN=Default Global Address List, CN=All
Global Address List

Solution: Launch ADSI Edit and investigate the Address Lists Container, in particular, edit the purported Search attribute.

6,!&08

Example: Unable to connect to 'Your DC' DC No Exchange Server with identity 'Your Server' was found

Solution: Check with Netdiag and Dcdiag. With luck it could just be a latency, or initial connection problem, which
mysteriously disappears when you try to repeat the Exchange 2007 server install.

6,!& 



0& )!!


Solution: Upgrade to Windows Server 2003.Or install a Windows Server 2003 in that child domain or site.

6,!&*0)3*  0  -) 

4

Remove (uninstall) the ADC on the Windows 2003 servers before continuing with Exchange 2007 server install.

Problem: CAS server setup fails with a Watson Multi Valued Property error

Solution: Launch ADSI Edit check Default Offline Address List. In particular, set the value of the MsExch Version attribute
to 4535486012416

6,!&0
,!$6(

Windows Server 2008.Problem installation failed. Reason, I had foolishly disabled IPv6.Solution, give the NIC and
IPv6address.Extra information, I had checked the install Hub Transport role, whether this was relevant, I have not had
time to research.

c c c
V!5 
 
 

6c

I am guessing, but service pack 1's feature list looks as thought Microsoft has engaged their top project manager to
oversee SP1.It seems as though he has listened to customer feedback from the RTM version, trawled forums, and sat
down with the Exchange 2007 team and asked, 'What could we have done better?'Then the project manager produced
a list of improvements and enhancements to be delivered is SP1.This is procedure is typical of service pack ones, a
welcome but unspectacular list of improvements. It is only later in the development cycle when SP3 or SP4 tend to
introduce brand new features.

To my way of thinking, Exchange Server 2007 SP1 will always be the 'Longhorn service pack'. Other benefits of running
Exchange 2007 on Windows Server 2008 include, support for IPv6, and for high availability, Standby Continuous
Replication (SCR).

c c cc*3 !",* 

4

OWA continues to improve as it matures as a technology. The highlights of SP1's enhancements are:

jÊ Recover deleted items through Outlook Web Access.

jÊ Users can create their own Personal Distribution Lists
 jÊ Users can copy folders and individual items
jÊ Support for Public Folders through the /owa virtual directory
jÊ For secure email there is now S/MIME
jÊ Improved delegation so that others can access some of your folders - watch out for the Delegation Wizard

c c c$&%&
2  

 s!

Again it is the emerging, maturing technologies that require the most tweaking, making clunky components in the RTM
version work smoothly in SP1. Unified Message enhancements include:

jÊ The ability to record high-fidelity voice messages in Exchange Unified Messaging

jÊ Integration of missed call notification e-mail messages with Office Communicator 2007
jÊ Users can now open their Outlook Voice Access from Microsoft Office Communicator 2007 without needing a
PIN
jÊ oS (uality of service) support
jÊ You can configure Unified Messaging to use the Secure Real time Transport Protocol (SRTP)

c c c

1
%

SP1 adds more settings to the Exchange Management Console (Formerly the Exchange System Manager), for example
the ability to set additional message limits on connectors. Speaking of the Exchange Management Console, Microsoft
have added new features in many areas. It's as though they pruned back too far when they reduced Exchange 2003's
seven levels, to three levels in Exchange Server 2007.Now with SP1 features that were not ready or settings that were
overlooked have been introduced.

One welcome new feature is the ability to import and export .pst files. Indeed, Microsoft have revamped the Move
Mailbox tool to make migrations and transitions to Exchange Server 2007 that bit easier.

c c c#6,!&
  

6c

The bad news with every service pack these days is that it inadvertently introduces a few, often obscure problems. The
good news is that there is an Update Rollup 1 to fix such problems for Exchange Server 2007 SP1.Here are some of the
problems that the Rollup 1 fixes:

jÊ The Auto discover service fails in Outlook 2007 after you install Exchange Server 2007 Service Pack 1.
jÊ Sundry garbled OWA messages in 'Subject' field, especially the '?'.
jÊ The Store.exe process hogs the CPU. You may also get: these Event IDs 9659, 8206, 8213, or 8199 in the log.
jÊ The Microsoft Exchange Information Store service hangs.
jÊ Email messages get stuck in the submission queue.
jÊ An external NDR message is sent to all recipients on a distribution list.
jÊ An application cannot run Windows PowerShell commands by impersonating a user account.
jÊ Beware, SP1 resets Connector Receive MaxMessageSize to 10 MB.


 !,

Mailbox Server holds the Mailbox database and Public folder databases for your organization. It only retains the mailbox
and it won͛t transfer your mails. Transferring mails between your mailbox servers are handled by Hub Transport servers.
The mailbox server role will be introduced only after the installation of Hub Transport Server and Client Access Server
Roles. 4 types of high availability options are introduced in Exchange Server 2007, if we are installing Mailbox Server
with the High Availability\Clustering options Like CCR, SCC, or SCR, then no other server roles to be installed with this
server role.

+)s ʹ will provide an option to achieve HA at the database level and not at the server level. LCR specifically designed for
small business organization, Active Mailbox Databases can be replicated to the passive Mailbox Database on the same
server, if the active database goes down, we can activate the passive copy to function as active and if the server goes
down, Mailboxes won͛t be accessible until the server got rebuild and the mailbox got restored.

))sʹ will provide an option to achieve HA at the database level and the server level. CCR will replicate the Active
Mailbox Server from one server to Passive Mailbox Database at another Server, Where in, if the active Server goes
down, automatic failover will occur and the passive server will function as active.

)) ʹ will provide HA at the server level only. if the active server goes down, the passive server will begging to function
as active by referring the active copy which is accessible for all the servers in SCC. We can have centralized location to
place the Mailbox and public folder database and the active server point to the same location. It͛s like Clustering option
available in Exchange Server 2003. If the SAN goes down, mailbox won͛t be accessible.

)s ʹ will provide HA option at the Site level failure. With SCR there is no need to implement windows failover
clustering feature installed to replicate the active database to passive database. Like active and passive mailbox
database copy in other HA option, we have Source Database and Target Database in SCR.

)! * 



The role that handles client requests for OWA, Outlook Anywhere, ActiveSync, OVA and offline address book
distribution. MAPI request from outlook client are directly connected to mailbox database, even though the MAPI
clients are directly connected to Mailbox Database to access the mailboxes, MAPI client still depends on client Access
Server for Auto Discover and Availability Service. CAS is responsible for any connection to Mailbox Server, when you
want the Mailbox Server from outside the Exchange organization CAS is responsible. It͛s also responsible for Non MAPI
Clients connection.

This role must be installed after the hub transport role and before the mailbox server role. You can install the mailbox
server role at the same time as the client access role, but not before.

 ,1
%

The Main Purpose of the Hub Transport Server Role is to transfer the mails throughout your exchange environment, this
server role is responsible for internal mail flow, it replaces the bridge head servers in Exchange server 2003. This can be
used as an edge transport server in Smaller Organization by installing and anti spam agents in Hub Transport Server
itself. This must be the first role installed in Exchange 2007. You can install the client access server role and the mailbox
server role at the same time as the hub transport role, but not before.

We have two connectors to look at in Hub Transport Server.

)  ʹ Responsible to outbound mail flow, by default, there is no Send Connector created (which means mail
flow will not happen externally) to route external mails, we have to create a send connecter based on our requirement.

s  )  ʹ Receive connector is responsible to receive inbound emails. By default the external mails are not
received internally until the anonymous authentication is enabled
2  

 

Functions as the interface point for the VOIP gateway or IP-PBX phone system. Allows user mailbox to be the single
point of storage and access for voice mail and fax messages, in addition to their normal email.

1
%

The Edge Transport Server Role is to transfer mails from inside of your organization to the outside world. It should be
implemented at the edge of the network (perimeter Network). Main purpose is to prevent your exchange server from
all kinds of Attack. Must have ports 25 (SMTP) and 50636 (LDAPS) open from it to the hub transport server on the
internal LAN. Port 25 is to send mail in. Port 50636 is to replicate the Exchange information that it needs, such as
changes to users͛ safe and blocked senders lists.

 -    ʹSince the Edge Transport Server is sitting at the edge of the network and to have to
communication between the Hub Transport Server, we are having edge synchronization. It is the process to update the
ADAM in the Edge Transport Server

*

s   ʹ Its additional feature which is used to rename the email address from internal users. This option
will provide an uniformity in the SMTP address if we are having lot of domains and if company wish to have the external
SMTP

Leave a Comment

February 10, 2011

Cluster Continuous Replication

Filed under: Exchange Server 2010 Ͷ exchange2k10 @ 3:46 pm

CCR is one of the high availability feature introduced in Exchange Server 2007 to provide availability service at the server
level and database level. If we look at LCR, we can achieve high availability at the database level only, if the server goes
down the data won͛t be accessible until the server is built again. Most the exchange server administrator will prefer to
go for CCR because of the following features

1.Ê High Availability at the Database and Server level

2.Ê Automatic failover, if any problem with active server\database

3.Ê Failover occurs with in less than 3 minutes time

4.Ê Reduce the frequency of full backup on regular basis

5.Ê No single point of failure

Here in this post, basic information on the cluster continuous replication is discussed and the following topics͙

jÊ How CCR works

jÊ How to check the storage group copy status

jÊ What is Copy ueue length and Replay ueue length?

jÊ Seeding\Reseeding of the CCR database

jÊ When failover will occurs

))s"
?
Like LCR, CCR uses the same asynchronous log file shipping and replaying technology to update the passive copy same
like active copy. Once the second node is added to the CCR, the current active database will be copied to the passive
database and this process in called seeding. Once seeding got completed the log file created in the active server will be
shipped to the passive one and it will replay to passive node.

By default, a hidden shared folder on the storage group where the active database copy will be created, where in, the
passive node find the shared folder and using SMB the changes in the log file will be copied to the passive node and
replayed to the passive database using the replication service.

Once the log file got committed in the active database, then the log file will be shipped to passive node. Monitoring the
committed logs on the active database will be monitored by inspector component.

The sever level failover and the database level high availability is achieved using windows cluster service and the log file
shipping and replaying process are controlled by MS Exchange Replication service.

  "
 % %-


To view the storage group copy status use the below shell command

Get-StorageGroupCopyStatus ʹServer ͞Cluster Name͟

To view the Mailbox Database status in CCR use the below shell command

Get-MailboxDatabase ʹServer ͞Cluster Name͟ ʹStatus | FT Name, Mounted

To view the replication health

Test-ReplicationHealth ʹIdentity ͞Server name͟


)%-  !s%!-  !

If you run the Get-StorageGroupCopyStatus it will provide the details of storage group health status and the copy queue
length and replay queue length status.

Copy ueue Length: It͛s the log file count, where the transactional logs that are in the queue to be transferred from
active node to passive node
Replay ueue Length: These are the log file that are transferred from active server to passive server and are waiting to
be replayed into the passive database.

 @s
 ))s,


Seeding:

When passive node is added to the cluster, the current database will be copied as a passive copy in the passive node;
this process of duplicating the active database to passive server is seeding. We can perform seeding using

Update-StorageGroupCopy ʹIdentity ͞Server Name\Storage Group Name͟

Reseeding:

If active database got corrupted and its inaccessible to users, we can bring the active copy to live from the passive copy,
the process of duplicating the active database copy same like passive database copy is reseeding, we can perform
reseeding using

Restore-storageGroupCopy ʹIdentity ͞Server Name\Storage Group Name͟

Also, we can use the below commands to suspend and resume the log file replication process.

Suspend-StorageGroupCopy ʹidentity ͞Storage Group Name͟

Resume-StorageGroupCopy ʹidentity ͞Storage Group Name͟

 ! !! 

In CCR, if any problem with a store or server, the failover will occur automatically. If we deeply look into when this
automatic failover occur from passive to active node, following are the ways͙

1.Ê If active node shutdown for any reason

2.Ê NIC card problem and result in connectivity problem between both the nodes

3.Ê If there is failure in achieving the Majority node in the quorum, failover will occur.

Lets us look into the resources in the CCR; we can have once instance of storage group, information store service and
system attendant will be functioning for the entire CCR. Even though who have two servers in CCR functioning as a
active node and passive node, the mailbox database in the active node will active and the system attendant and the
information store service on the active node will be functioning only in active node. If failover occur, the information
store service and the system attendant service in the passive node will continue to function.

Failover: failover is the process of changing the passive node to active node because of some problem in the active
node. In CCR failover is automatic

Switch over: Switch over is the same process of making the active node to passive node but the failover is manual.

If any more information is need in CCR please inform us, we will post you with full detail.

Leave a Comment

February 4, 2011

Local Continuous Replication

Filed under: Exchange Server 2010 Ͷ exchange2k10 @ 10:03 am

Here in this post, I͛m explaining the concept of Local Continuous Replication in detail. LCR is a new high availability
option that is specifically introduced for Small Business Organization to achieve High Availability on the Exchange
Mailboxes using a single Exchange server by maintaining a set of storage groups on a second set of hard disks, where
the Active copy of the database will be replicated to the passive copy using Log Shipping and Log replying process.

Microsoft placed a good diagram in TechNet article to represent the LCR concept

We are going to look at the below topics related to Local Continuous Replication in Exchange server 2007

jÊ How the log file shipping and replying technology works

jÊ How to Enable\Disable Local Continuous Replication

jÊ What is seeding\reseeding and how to perform seeding\reseeding

jÊ How to check the LCR function

jÊ How to troubleshoot the LCR active copy failure

+)s"

In Exchange 2007, LCR uses a concept called Asynchronous Log file shipping and replaying technology to move the logs
from Active copy of the mailbox database to Passive copy of the mailbox database. This process will be taken care by MS
Exchange Replication Services, where in it will monitoring the committed logs on the active copy of the mailbox
database and the same will be moved to the passive copy using log file shipping process and that moved log will be
replayed into the passive copy of the mailbox database using replaying technology.

,!@0
,!+ !)  
s%!  

Since the LCR is a disk level high Availability option, it͛s better to choose a good hard disk. Local continuous replication
can be enabled at the storage group level.

To enable the Local Continuous replication

à Right click the storage group -> select enable Local continuous replication -> provide the log file and secondary passive
copy location -> click finish to enable LCR
Below diagram shows the health status of Local continuous replication for the first storage group

To disable Local Continuous Replication

à Right the LCR enabled storage group and select Disable Local Continuous Replication, you will be prompted by the
below warning click ok to disable LCR



 @
 %&
 @
 

Seeding à It is the process of creating a duplicate copy of the existing mailbox database while enabling the LCR
operation, once we are enabling the LCR, the exact copy of the active database will be copied to the passive database
and after that the log file shipping and replaying process will happen.

How to perform seeding,

In some scenario, you may need to perform seeding from the active copy to make the passive copy healthy as like Active
mailbox database copy, to perform seeding we have to follow these 3 steps
 1.Ê Suspend the current LCR option à Suspend-StorageGroupCopy -Identity ͞Storage group Name͟

2.Ê Update storage group copy à Update-StorageGroupCopy -Identity ͞Storage group Name͟

3.Ê Resume the suspend operation of LCR à Resume-StorageGroupCopy -Identity ͞Storage group Name͟

Suspend will perform a temporary stop for log file shipping

Update will perform the seeding by copying the Active copy of the mailbox database to the passive copy of the Mailbox
database

Resume will perform the log file shipping and replay the logs to the passive copy

Reseeding

Reseeding is the reverse process of seeding, in which for some reason the active mailbox database got corrupted and
we can perform a reseed to bring the active database to the exact copy of the Passive copy.

  "+)s   

To monitor the health of LCR function, we can check the below things

1.Ê Storage Group Copy Status

C:\Documents and Settings\Administrator>Get-StorageGroupCopyStatus |ft storagegroupname, copyqueuelength,

replayqueuelength, summarycopystatus

StorageGroupName CopyueueLength ReplayueueLength SummaryCopyStatus

ͶͶͶͶͶ- ͶͶͶͶͶ ͶͶͶͶͶʹ ͶͶͶͶͶʹ

First Storage Group 0 0 Healthy

 ,!
+)s   %- ! 

If any problem occurred to the active copy of the mailbox database then no need to worry, since we have the passive
copy, which is same like active one. To restore the passive copy to function as active, we have to perform the following
steps.

1.Ê Check the replication status of storage group copy

2.Ê Dismount the database

3.Ê Run the Restore-StorageGroupCopy ʹIdentity ͟ Storage Group Name͟ below diagram shows the details when
you run this command

1.Ê Log file located in passive database copy will be restored to active database copy

2.Ê Database file located in passive database copy will be restored to active database copy
In LCR, if the server goes down

1.Ê We have to rebuilt the server

2.Ê Create the storage groups and databases

3.Ê From the backup we can restore the database

%&, !"&&  


 !"

 * 

 

Outlook 2007 use two methods: Service Connection Point (SCP), DNS (two predefined URL, HTTP redirection and SRV)

 ,!
,
 & 



1. If all stores are unable to mount, please check if the following services is started first:

Microsoft Exchange Information Store

Microsoft Exchange System Attendant

Then check if you run a File-Based Antivirus Software scanning against the program and database files of an Exchange
computer. Please disable the anti-virus software and test the issue again. In order to isolate the issue, you can also
create a new database to see if it can be mounted.

2. If one specific is unable to mount, please first check if you are running Exchange Standard Edition, your mailbox stores
will dismount when you reach the 16-GB size limit, KB 828070 addresses this issue.

Verify that the database was shut down in a clean (consistent) state. Use ESEUTIL /MH. If the database is shutdown in a
dirty (inconsistent) state, you cannot mount it and you must replay at least one transaction log file to bring it to a clean
state.

Verify the integrity of the database. Use ESEUTIL /G, which will check the low-level integrity of the database.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ

! - 0%-*


 , 

&


% 

,- 


When the message is submitted by using SMTP client, the SMTP address is used to submit the message. In addition, the
Sender and Recipient are resolved by searching the proxyAddresses attribute. For example, if the recipient͛s SMTP
domain is configured as authoritative domains but the recipient email address cannot be found in proxyAddresses
attribute of all the users. Then, a NDR message will be generated indicated that the user does not exist. In contrast, if
the message sent to an external recipient, nevertheless, the recipient email address can be found in the proxyaddresses
attribute of the local user, the message will be delivered to the local user instead of the external recipient.

b. When the message is submitted by using MAPI client such as Outlook or OWA, the legacyExchangeDn is used to
submit the message. Therefore, if the submitted recipient͛s legacyExchangeDn cannot be found in AD user object, a NDR
message will be generated indicated that the recipient does not exist.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶʹ
 !-
& ! , 
& !
    

legacyExchangeDn: This attribute is a unique legacy distinguished name which identifies your mailbox. This attribute is
mainly used for backwards compatibility purposes for the Mail Application Programming Interface (MAPI) clients, for
example, /o=org/ou=site/cn=recipients/cn=gyip.

proxyAddresses: A multi-valued attribute that contains all the e-mail addresses for which you can receive mail. The
format of this attribute is PREFIX :proxy, where PREFIX is either SMTP, X400, GWISE, or NOTES, for example,
SMTP:gyip@microsoft.com.

TargetAddress: This attribute is the e-mail address to which you want to redirect the mail. This attribute is formatted
like the proxyAddresses attribute, where there is a prefix that defines the address type, for example,
͞SMTP:gyip@microsoft.com͟. The attribute is only for mail-enabled user or mail-enabled contact.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶʹ
  
 , 
!!    

 
Raise DOmain Level
As indicated by the wizard, I needed to Raise Domain Level 2003 (2000). What I did was launch the ADUC (Active
Directory Users and Computers), right click on your domain and select, Raise Domain Function Level. As I had no old
domain controllers, I chose Windows Server 2003.

Global Catalog
Insure that at least one Domain Controller on the subnet where you install Exchange 2007 has Global Catalog enabled.

.Net Framework 2.0

Exchange 2007 requires .Net Framework 2.0 (or 3.0). We need to install PowerShell before the main Exchange 2007.

MMC V 3.0
when I installed on Windows Server 2003, Exchange 2007 needs MMC v 3.0.

Pwershell ʹ Windows Server 2003 install PowerShell together with .Net Framework

64 Bit Hardware ʹ Production versions of Exchange 2007 require 64-bit hardware.

No NNTP ʹ Finally, avoid ͚over-think͛, not need the NNTP service.

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

$
!!   
6%*  0  -

Setup /PrepareAD Creates the necessary global Exchange objects and universal security groups in Active Directory.
Must be run by a member of the Enterprise Admins group, run this command in both the root and current domain. You
may find that if you run this command as a Schema Admin (and Enterprise Admin), there is no need to run the other
commands.

/PrepareLegacyExchangePermissions This command is needed if your organization contains Exchange Server 2003 or
2000 computers. It modifies the permissions assigned to the Enterprise Exchange Servers group so that the Recipient
Update Service can run. Remember to logon as a member of the Enterprise Admins group.

/PrepareSchema This prepares the Active Directory schema so that it allows Exchange Server 2007 to install. You must
be a member of both the Schema Admins and Enterprise Admins. You need to run this command in the root domain, or
the domain which holds the Schema Master role.

/PrepareDomain /PrepareDomain domainname This creates a new global group in the Microsoft Exchange System
Objects container called Exchange. You must be a member of both the Enterprise Admins and the Domain Admins
group.

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

   "     



 
!!


 !!- 
* Check the installation log at: C: \ExchangeSetupLogs. Also check the system and application event logs.
* Launch the Exchange Management Console and check your newly installed Exchange server. If this is a brand new
installation check that the Organization Name is the same as you planned.
* Create a mail-enabled user and then connect to that mailbox using Outlook Web Access, or an Outlook client if you
prefer.
* Once you create a Hub Server see if you can receive email from another mail-enabled account.
* For CAS servers make sure you check with OWA.
* In the case of the Edge Server send email to an external internet account.
* Check that services to see that the dozen or so Microsoft Exchange Services are running. Note they begin with
Microsoft and not Exchange.
* If anything seems wrong check the Exchange files underneath: C: \Program Files\Microsoft\Exchange Server.
* When there is no quick resolution to the problem, seek the ExBPA (Exchange Server Best Practices Analyzer), then run
the Exchange 2007 Readiness check. The best way is to launch the Exchange Management Console and open the
Toolbox and there you will find the Exchange Server Best Practices Analyser.

    

 s!

 
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-
  
  !
  
  


Eseutil /a (New switch for Exchange 2007) LLR replays logs.
(Eseutil /cc Performs a hard recovery after a database restore. Exchange 2003)
Eseutil /d Performs an offline compaction of a database.
Eseutil /g Verifies the integrity of a database.
Eseutil /k Verifies the checksums of a database.
Eseutil /m Generates formatted output of various database file types. e.g. /mh
Eseutil /p Repairs a corrupted or damaged database.
Eseutil /r Performs soft recovery to bring a single database into a consistent or clean shutdown state.
Eseutil /y Copies a database, or log file.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-
 &-

     

A


  %
 
 
2003 Std 2003 Ent 2007 Std 2007 Ent
Storage groups 1 4 5 50
Stores per group 2 5 5 50
Database Limit 75 GB 16 TB 16 Tb 16 Tb
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

Scenario based Uestion

$ -     %

 s
%    *6$ )!  A   !! -   ,!
 
Exchange Server 2007 sets limits on the number of server objects that MAPI clients can open. If you choke down the
number of objects any one client can open, then you will get lots of Event 9646, indicating that a MAPI client has
opened too many objects on the Exchange 2007 server.
As so often these cases, there is a registry setting where you can change the defaults:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

You need to create a sub-key called: MaxObjsPerMapiSession

Next, right-click the MaxObjsPerMapiSession that you just created, click New, and then click DWORD Value
objtMessage. In the ͚Value͛ data box, type the new maximum number of objects, say 500.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

  &     0,


 & 6
!! 
ANs. By ͞Mount-Database -Identity ExchSrv\MgrDatabase͟
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-
  1 ,!
  8 0 !- s%    

 
1. Toolbox , ExBPA, Logs, powershell

# Exchange Mail Flow Tools

1) Launch the Exchange Management Console
2) Click on the Toolbox
3) Examine the Mail flow Tools

# ExBPA (Exchange Best Practice Analyzer)

It may be a help, or the ExBPA may distract you from troubleshooting NDRs.
# Check the Logs
Good technique is to begin by looking in the Application log for errors. A variation of this tip is to increase the
Diagnostic Logging.
# Check the queue and SMTP logs on the Exchange 2007 server.
# Firewalls and Anti-virus software
You may try turning off temporarily anti-virus software and even the client-side firewall to see if that enables the email
to get through.
# PowerShell for Viewing ueues
It may speed up troubleshooting your Exchange NDR if you use the PowerShell cmdlets, for example:
get-ueue
retry-ueue
get-Message -queue

# Regtrace
You could also gather more clues about your Exchange NDR with Regtrace, which you find on the Exchange 2003 CD in
the support\utils\i386 folder.
# Telnet
Try telnet over port 25. Naturally, you need to substitute a real Exchange 2007 server for ͚YourServer͛. Open a
command prompt, type:
Telnet YourServer 25
ͶͶͶͶͶͶͶͶͶͶʹ
# Send another email to the same recipient but using a different sender.
# If it͛s attachment, then try with no attachment.
# If it͛s just one email address that produces the Non-delivery report, what happens if you type the SMTP address
manually, compared with when you click the user account in the GAL?
# Alternatively, you could send emails to different recipients from the original sender.
# Is the the Exchange NDR random, or can you reproduce it easily?
# Do you have multiple sites? If so are they all affected, or just one?
# If all else fails try sending an email to oneself!
# Bear in mind that Microsoft Outlook has a ͚Test Account Settings͛ button to collect information from the client side.
# Check the logs
ͶͶͶͶͶͶͶͶͶͶͶͶͶʹ
$&



 "   
 ,!


Troubleshooting Edge Server ueues

Problem at the Edge Server
In the ueue Viewer, you see messages displaying the error message:
451 5.7.3 ͚Cannot achieve Exchange Server authentication͛.

!  6,!&     & )

!
* Navigate to Server Configuration ʹ> Hub Transport
* Right-click the Receive connector, and then select Properties.
* Select the Authentication tab.
* Check the Transport Layer Security (TLS) check box.
* Check the Exchange Server authentication check box.
* Click Apply.
2> Synchronize with the Hub Server
To complete the job, force synchronization with one of these PowerShell commands.
Start-EdgeSynchronization [Exchange 2007 RTM]
Start-EdgeSynchronization -server HubServerName [Exchange SP1]

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-
%!  !!  


1. As soon as an Outlook users sends an email, the Microsoft Exchange Mail Submission service takes over.
2. The Submission service then notifies a Hub Transport server in the local Active Directory site.
3. The email is then sent to the for the categorizer͛s submission queue.
4. The store driver uses MAPI to connects to a user͛s ͚Outbox͛ folder, it then retrieves the message from ht e
corresponding Mailbox server.
5. Then the store driver converts the MAPI format into the Summary-Transport Neutral Encapsulation Format (S/TNEF).
This format has no plain text part, and is in eightʹbit binary format.
6. Next, the store driver places the email into the submission queue and moves the message from the user͛s ͚Outbox͛ to
their ͚Sent Items͛ folder.
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

$ 


16  !
 & !$A8  

 
)  $& !

Internet emails are typically routed by the Hub Transport via an Edge server subscription. Alternatively, you could
create a Send connector on the Hub Transport server itself, and configure it to deliver outgoing internet email.

> Launch the Exchange Management Console.

> Expand the Organizational Configuration node.
> Select the Hub Transport node.
> Click on the Send Connectors.
> In the Actions pane, select New Send Connector.
> The Wizard will guide you through the options. In particular look for the Internet option from the drop down box.
> Choose a Smart Host, or DNS MX records to send the email.

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

 !!, & 

 c





& !,


Recommendations for up to 1,000 Mailboxes

> 64-bit hardware. Twin (quad) processor. Check the supplier on the Windows Server Catalog (HCL).
> 4 GB RAM.
> 4 Storage groups.
> 5 GB Disk space. RAID 1/0 Data striped across mirrored sets. (Avoid RAID 0/1)
> Standard edition of Exchange 2007 Server SP1 or later.

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-

 $  ++s    


Single Instance Storage (SIS)

 !$
 3$4 Claimed we get better performance by removing the idea of storing just one instance of a
file that was sent to multiple users. Classic trade off, more disk space better performance. What I had not realized,
(because I had not thought the problem through) was that SIS only worked if all the recipients were in the same
mailstore. Thus with the modern tendency of more storage groups, the saving was not quite as great as imagined.

+
 + s
!   3++s4
The idea behind LLR is to enables you to recover Exchange databases when the most recent transaction log files have
been damaged. LLR is a new feature in Exchange Server 2007 which holds the last few log files in memory until the
database is shut down. The benefit is to prevent scenarios where part of log file 3 has been written to the database, but
part of log file 2 hasn͛t. This explains the main reason why the log files have been reduced from 5MB in Exchange 2003
to 1MB in Exchange 2007. Thus if you lose the last log it only costs 1MB of data instead of 5MB.
ͶͶͶͶͶͶͶͶͶͶͶͶͶʹ
s*$0 0
" )       

  !, 

Speed DiskFailure I/O

RAID 1 Good Poor Best
RAID 1/0 Best Poor Best
RAID 5 Good Best Poor

ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ-
1   

   
 B   %

Exchange Server 2007 is available in two editions, Standard and Enterprise. The Enterprise Edition supports 50 storage
groups (50 databases), whereas the Standard Edition supports only 5 storage groups (5 databases).
ͶͶͶͶͶͶͶͶͶͶͶͶͶͶͶ

 ))s    

    

 ))s 3)!
 )  
 s%!  4
Microsoft͛s CCR concept involves combining the failover features provided by the Cluster Service

Exchange CCR uses the database recovery ability of Exchange 2007 server. The cluster technology works by
continuously updating a passive copy of the mailbox database. However, it is continuous in the sense that after an
active node finishes (closes) a log, that log is immediately copied across to the passive node.

Once you have built the cluster, then failover only occurs when the passive server misses 10 heartbeats. This
corresponds to about 12 second of broken connection.
ͶͶͶͶͶͶͶͶͶͶͶͶͶ
  "))s
6
!!

test-ReplicationHealth
get-StorageGroupCopyStatus
get-ClusteredMailboxServerStatus

 %%  s2    



Exchange 2003 s RUS (Recipient Update Service) has been replaced in Exchange 2007 by two PowerShell cmdlets,
update-AddressList and update-EmailAddressPolicy.
ͶͶͶͶͶͶͶͶͶͶ

)  *5&
/,
*     



By default, forms-based authentication is enabled in Exchange 2007. This is how to check the configuration:

* Launch the Exchange Management Console.

* Open the properties of owa (Default Web Site) on the Outlook Web Access tab.
* Set the type of logon prompt. The emphasis on ͚Prompt͛, users can ignore your suggestion if they know any of the
other methods. Here are the choices of prompts for forms-based authentication: FullDomain (cp\guy) , PrincipalName
(guy@cp.com), or plain UserName (guy).
* Reset IIS as recommended in the warning message.
* If necessary, you can adjust the format by configuring the Active Directory directory service and Internet Information
Services (IIS). If you do use Active Directory and IIS to set which user name formats users can enter, this is independent
of the above OWA forms-based authentication prompt.