Exchange 2007 – A brief walkthrough

1. Exchange 2007 – A brief walkthrough Ismail Mohammed Sr. System Administrator| Unisys - India www.exchangeserverinfo.com

2. AGENDA • New Features in Exchange 2007: • Exchange Management View • Exchange Concepts and Definitions • Unified Messaging Functionality • New Client Functionality • Messaging Policy and Compliance Features • Improvement in Antispam and Antivirus • New Transport and Routing Functionality • New Performance and Scalability Functionality • New High Availability and Cluster Functionality • New Exchange Database Functionality • New Deployment Functionality • Transition in a single Forest

3. New Features in Exchange 2007 • Exchange Management Console : • The Exchange Management Console takes the advantage of the Microsoft Management Console 3.0. A New look & new interface. • Exchange Management Shell • Integrated with Windows Powershell Command. • It provides robust & flexible scripting which reduce the complexity of Vbscript. • It is very useful when you want to perform multiple task or bulk • Pipeline : It essentially takes the output from one command and use it input for another command. Example - Get-mailbox | fl • What if/Confirm : The nice thing about this powershell is if you are not sure about the command you can add whatif/confirmin the syntax. Example : Get-process | stop-process -whatif

4. Exchange 2007 Server Roles Instead of having one generic installation of exchange server now we have exchange to be installed based on sever roles like client, hub, mailboxes, unified and edge server • Hub Transport   : • Mailflow within the exchange organization. • Message routing happens by using Active Directory Sites and Site Topology. • Client Access : • It enables mailbox access through OWA, POP3, IMAP4, Outlook Anywhere and activesync. • Edge Transport  : • Recommended to place this transport server in the DMZ aka Perimeter Network. • It provides antivirus and anti-spam protection in a perimeter network for the Exchange organization . • It is also responsible for all mail entering or leaving the Exchange organization. • ADAM and a component called EdgeSync are used to perform scheduled one-way synchronization of the configuration and recipient information from Active Directory. • Mailbox: •    The Mailbox server role is responsible for hosting mailbox and public folder databases. • Unified Messaging : • It is used for voice messaging, fax, and e-mail messaging into a single messaging infrastructure that can be accessed from a telephone and a computer.

5. Unified Messaging Functionality • With Exchange 2007 Unified Messaging servers, users can access their messages from • Telephone • Can receive Message in terms of WMV format in their mailbox • Can respond to their schedule meeting • Ability to receive incoming Fax • Can redirect their call to his backup resource in his absence. • Can check the user details from the gal if he is not sure on his dial number.

6. New Client Functionality • Improvement in OWA – New look interface, more options available etc. • Exchange Activesync and Mobility: • It also includes improved security and better mobile device management.Exchange, like • HTML Message Support : In earlier version whole e-mail message will be converted into a plain text. • Follow-Up Flag Support – we can flag an e-mail message and also it will appear in the outlook 2007 To-Do bar. • Fast Message Retreival • Windows Sharepoint Services and Windows File Share Access. • Enhanced Device Security by Using Password Polcies • Out-of-Office Support. • Exchange cache mode: • Exchange 2007 provides a new notification mechanism for Outlook 2007 clients that enable the clients that are running in Cached Exchange Mode to start downloading new messages more quickly than with earlier versions of Microsoft Exchange. • Messaging Records Management : • The main principle behind MRM is that it helps an organization with its legal compliance requirements, something that previous versions of Exchange aren’t particularly good at

7. Messaging Policy and Compliance Features • Address rewriting • Transport rule • Disclaimers  • Journaling

8. Antispam Functionality • Connection filtering : Ip allow list, Ip block lists, IP Block List providers and Ip Allow List Providers • Content Filtering : based on the content of the messages.= • Spam Quarantine: Spam quarantine provides a temporary storage location for messages that are identified as spam and that should not be delivered to a user mailbox inside the organization. Spam quarantine functionality is available during the content filtering process. • Recipient Filtering: This enables the Recipient Filter agent to perform recipient lookups for inbound messages so that you can block messages that are sent to nonexistent users or internal-only distribution lists. • Sender ID: Sender ID verifies that each e-mail message originates from the Internet domain from which the message claims to come by examining the sender's IP address and comparing the IP address to the Sender ID record in the sender's public Domain Name System (DNS) server. • Sender Reputation: Sender reputation uses patented Microsoft technology to calculate the trustworthiness of unknown senders. Sender reputation gathers analytical data from Simple Mail Transfer Protocol (SMTP) sessions, message content, Sender ID verification, and general sender behavior and creates a history of sender characteristics.

9. Improvement in Antivirus • Exchange 2007 also provides antivirus stamping, which helps reduce the volume of antivirus scanning across an organization by stamping messages that were scanned for viruses with the version of the antivirus software that performed the scan and the result of the scan. This antivirus stamp travels with the message as the message is routed through the organization. The stamp is used to determine whether additional antivirus scanning must be performed on the message. • Another Exchange 2007 antivirus improvement is the implementation of attachment filtering by a transport agent.

10. New Transport and Routing Functionality • New SMTP Transport Stack : It eliminates the dependency on IIS and reduces the work that is required to help secure a server for perimeter network deployment. • Active Directory Site-Based Routing Topology: • Exchange 2007 takes advantage of the existing Active Directory site topology to eliminate the need to define a separate Exchange routing topology. • No More link state: • Queue at point of failure

11. New Performance and Scalability Functionality • 64 bit architecture: • The 64-bit version of Exchange Server provides new opportunities for performance and scalability. Because of the incremental memory that is available with 64-bit, Exchange 2007 has tremendously different performance characteristics than Exchange Server 2003. 64-bit code also means a substantial reduction in the I/O required for Exchange 2007. • Capability of creating upto 50 storage group • Optimized Database Engine and Cache: • The database page size has been increased from 4 kilobytes (KB) to 8 KB. An 8 KB page size means a greater probability that the contents of an entire message will be read during a single I/O operation, and that the messages contents can now be stored on a single page in the database.

12. New High Availability and Clustering Functionality Mailbox Server Role • Continuous Replication: • Continuous replication is present in two Exchange 2007 features that use built-in asynchronous replication technology to create a copy of a storage group and maintain the copy's currency through log shipping and replay. • The two features that contain this technology are local continuous replication (LCR) and cluster continuous replication (CCR). • Standby Continuous replication • Single copy cluster Client Access Server Role: • Network Load Balance (NLB) Edge Transport Server Role: • You can deploy multiple Edge Transport servers and use multiple DNS Mail Exchanger (MX) records to load balance activity across those servers. Hub Transport Server Role: • It will automatically load balances between available servers. Unified Messaging Server: • Unified Messaging deployments can be made more resilient by deploying multiple Unified Messaging servers where two or more are in a single dial plan. VoIP will take the advantage of round-robin method.

13. New Exchange Database Functionality • Public Folders No Longer Used for System Data • The Exchange database architecture has changed in four significant respects: • The streaming database (.stm) file has been removed from Exchange 2007. • Longer log file names are used, thereby enabling each storage group to generate as many as 2 billion log files before log file generation must be reset. • Transaction log file size has been reduced from 5 MB to 1 MB to support the new continuous replication features in Exchange 2007. • The database page size has increased from 4 KB to 8 KB.

14. New Deployment Functionality • Exchange Server 2007 Setup Wizard : The Exchange Server 2007 Setup wizard includes prerequisite checks, Active Directory service preparation, and a user interface that is easy to use. • Active Directory Preparation

15. Terminology Changes in E2K7

16. Transistion – Quick Ride • Transition is a scenario where we will upgrade our existing Exchange Organization to Exchange 2007 Organization in which we will move our data from existing legacy exchange server to exchange 2007 server.

17. Transition in a single forest • Install Exchange 2007 in the existing environment: Installation of Exchange 2007 need some pre-requisites based on system wide requirement (AD Requirement) and Server Specific Requirement • System-wide Requirement: • Domain Functional Level need to be set @ Windows 2000 native mode or later. • Schema Master Server & GC Server should be having windows 2003 OS with SP1 or later. • Exchange 2003\2000 Organization should be set to native mode. • Server-Specific Requirement: • Hardware Requirement: • Any Intel Xeon or Pentium 4 64-bit processor • Any AMD Opteron or Athalon 64-bit processor • 1 GB of Ram plus 5mb per mailbox for RTM and 2 GB of Ram for SP1 • Disk space 1.2 GB atleast free space. • DVD Rom • Software Requirement: • Microsoft .NET Framework Version 2.0 • Microsoft Windows PowerShell • Run Exbpa • Run setup.com /PrepareLegacyExchangePermissions • Run setup.com /PrepareSchema • Run setup.com /PrepareAD • Finally install Exchange 2007

18. Transition in a single forest 2) Replicate the public folder & System Folders Public Folder: • Exchange 2007 public folder does not store the system folder. Instead of storing it in public folder database it will store in individual user mailbox and request is processed through Availability Service. Just you need to replicate the existing public folder. Once it has been done then delete the public folder store of legacy Exchange 2000\2003. Mailbox movement: • Move the mailbox to new server through the mode of GUI or powershell • Move mailbox session will be four mailboxes per session. • For moving the bulk mailbox, need to run a script. You can download the script from this link : http://technet.microsoft.com/en-us/library/aa997961.aspx OAB : • Rehome the OAB from GUI (EMC console) or through powershell Move-OfflineAddressBook -Identity "OAB" –Server Servername

19. Transition in a single forest 3) Remove the last legacy Exchange 2000\2003 • Confirm your new smtp connector is configured properly and able to send and receive email. • Check the number of routing group, send connector and receive connector we have i.e get-routinggroupconnector and as on. • If required create a new send connector or receive connector. • Check the mailflow how it is flowing to exchange 2007 by mode of message tracking. If it is taking the exchange 2007 as least cost then go ahead and delete all the connectors which are responding to exchange 2003 • Move the RUS to new Exchange 2007 Server • Insert the Exchange 2003 cd in exchange 2003 box and remove the exchange 2003 application. However in ADSIEDIT you will see “First Administrative Group still existing. Don’t delete “First Administrative Group” till the time you confirm that all the clients have outlook 2007 because outlook 2003 and older version use the LegacyExchangeDN property to get free/busy information. • Once your are done, clear up the application log and system log. Shutdown your Exchange 2007 server and take a reboot of all GC’s & DC’s and then restart your exchange 2007 computer.

20. References • Getting Started • http://technet.microsoft.com/en-us/library/bb124265.aspx • www.exchangeserverinfo.com • Upgrading to Exchange 2007 • http://technet.microsoft.com/en-us/library/bb124008.aspx • Transitioning from Exchange 2000/2003 to Exchange Server 2007 (Part 1) • http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html • http://exchangeserverinfo.com/2007/12/04/transition-from-exchange-2003-to-exchange-2007.aspx

21. Feedback / QnA • Your Feedback is Important! Please take a few moments to fill out our online feedback form • Use the Question Manager on LiveMeeting to ask your questions now!

22. Contact • Blog Address www.exchangeserverinfo.com Forums: www.msexchange.org/forums www.exchangeserverinfo.net