Part 1 TE MA ED HT IG PY R ◆ ◆ ◆ ◆ ◆ ◆ ◆ Chapter 1: Introducing Exchange Server 2010 Chapter 2: Introduction to Email Administration Chapter 3: Standards and Protocols Chapter 4: Understanding Availability, Recovery, and Compliance Chapter 5: Message Security and Hygiene Chapter 6: Introduction to PowerShell and the Exchange Management Shell Chapter 7: Exchange Autodiscover Chapter 8: Virtualizing Exchange Server 2010 Chapter 9: Exchange Server, Email, and SharePoint 2007 CO ◆ ◆ RI AL Exchange F
Chapter 1 Introducing Exchange Server 2010 Email clients used to be fairly simple and text based. Email servers had few connectivity options, no high-availability features, and no integrated directory. Then, beginning in the mid-1990s we saw a big push toward providing email service to most of our user communities. We also saw email go from an occasionally used convenience to a business-critical tool.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 2003 or Exchange 2007 pretty well, but there will be new details to learn with Exchange 2010. Sometimes these implementation or management details are things that we have to learn the hard way — thus the trepidation associated with any new version of Exchange. However, this next milestone in the evolution of Exchange Server is a good one. We can’t help but be excited about learning about this new version and sharing what we have learned.
EXCHANGE SERVER ARCHITECTURE ◆ Document. ◆ Don’t believe everything you read from a vendor; their job is to sell you things. ◆ Don’t put off maintenance that might affect your up-time. ◆ If you get in trouble, call for help sooner rather than later. A few hundred dollars for a phone call to your vendor or Microsoft Product Support Services is better than a few days of downtime. ◆ Share your knowledge and configuration information with coworkers.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Certainly this is true for hardware that has been in production for more than three or four years. Add to this the fact that there is no ‘‘in-place’’ upgrade from Exchange 2000, 2003, or 2007 to Exchange Server 2010. The good news is that most server-class hardware that has been purchased since the end of 2005 or later probably already includes the x64 processor extensions that Windows 2008 x64 requires.
EXCHANGE SERVER ARCHITECTURE Notice in the Instructions line of CPU-Z that this particular chip supports x86-64. This means this chip will support the x64 instruction sets. Intel chips will report that they support the EM64T instruction set. Windows Server 2008 x64 Because of some of the underlying requirements of Exchange Server 2010, you must run Windows Server 2008 x64 Service Pack 2 or Windows Server 2008 R2.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Applying Special Hotfixes If you get a rollup fix such as Exchange 2010 rollup fix 4 and then later you require an individual hotfix from Microsoft to address a specific issue, you may need to uninstall the post–rollup 4 hotfix prior to installing rollup fix 5. If you ever get a hotfix for Exchange 2010 to address a specific issue, always ask the Microsoft product support person if you will have to uninstall it prior to applying the next rollup.
EXCHANGE SERVER ARCHITECTURE and makes creating dedicated server roles much easier. In a small organization with only one Exchange server, the same server may be assigned the Mailbox, Hub Transport, and Client Access server roles. High-Availability Decisions High-availability decisions do not need to be made at installation time. Unlike previous versions of Exchange Server, high availability for Exchange Server 2010 databases can be added incrementally after the initial deployment of the Mailbox server.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Is the Edge Transport Server Role Required? A common misconception about Exchange 2010 is that the Edge Transport role is required for Exchange 2010. This is not the case. Inbound email can be sent directly to the Hub Transport role, or you can continue to use your existing third-party antispam/message hygiene system to act as an inbound message relay for Exchange Server. Microsoft’s solution to this dilemma is the Edge Transport server.
EXCHANGE SERVER ARCHITECTURE ◆ Integrated Microsoft content filter is included for spam detection. Spam can be rejected, deleted, quarantined, or delivered to the user’s Junk E-mail folder. ◆ Multiple message quarantines allow messages that are highly likely to be spam to be quarantined and sent to a quarantine mailbox on your Exchange server. A separate quarantine exists in the form of the user’s Junk E-mail folder for messages that are still tagged as spam but with a lower Spam Confidence Level (SCL).
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Figure 1.4 Viewing a voicemail message sent via Unified Messaging Not all voice systems are going to support this feature ‘‘right out of the box.’’ More and more vendors (such as Cisco and Mitel) are tweaking their Voice over Internet Protocol (VoIP) systems to talk directly to Exchange Server 2010 Unified Messaging, but you may still require a VoIP gateway of some type.
EXCHANGE SERVER ARCHITECTURE Customers are often reluctant to deploy unified messaging solutions due to the complexity, administrative overhead, schema changes, client-side deployment requirements, and cost. Microsoft is determined to make their unified messaging implementation less expensive than competing products and much better integrated with Active Directory.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Continuous Replication Basics If we had to pick a single technology that is the most compelling in Exchange Server 2010, it would be the continuous replication technology. This new technology supports the ability to replicate a database to one or more additional Exchange Mailbox servers within your organization.
EXCHANGE SERVER ARCHITECTURE checked to ensure that they are in the correct sequence. Once this is verified, the replication service copies the log file (E0000000001.LOG) to the target log file directory. The Information Store service then replays the transactions found in the E0000000001.LOG file and the transactions are committed to the passive copy of the database. At any given time, the most out-of-sync passive copy of the database will be approximately 15 minutes.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 XYZZY requires a high-availability solution that not only provides email access in the event of an Exchange server failure in the local office, but also provides a contingency in case their headquarters office has to be shut down. Email should be hosted in the Colorado office in the event the Florida office has to be closed. The solution that switches active email services over to Colorado must be smooth and simple.
EXCHANGE SERVER ARCHITECTURE Figure 1.7 Domain controller/ global catalog server Traditional MAPI to Exchange connectivity Outlook MAPI/RPC client System Attendant Exchange 2003 Server Information Store Second, the client connects to the RPC interface provided by the Information Store service (store.exe). This means that the Outlook RPC client is connected directly to the information store on the Exchange server on which their mailbox database resides.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Mailbox server on which a public folder replica is located. The RPC Client Access Service does not handle connectivity for public folders. Figure 1.
EXCHANGE SERVER ARCHITECTURE Maximum Number of Databases and Database Availability Groups Exchange Server 2010 Standard Edition permits a maximum of five mailbox databases on each Mailbox server. Exchange Server 2010 Enterprise Edition permits a maximum of 100 mailbox databases per Mailbox server. The maximum number of mailbox databases includes both the active and the passive copies. You must take this into consideration when planning database availability groups.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 all from the same company), the truth of the matter is that these tasks were not that simple to perform via script. That has all changed with Exchange Server 2010 (and also with Exchange Server 2007).
IMPROVED MESSAGE AND CONTENT CONTROL tasks can be performed from the EMS (command-line interface); a subset of these tasks can be performed from the EMC graphical user interface. Anything that can be performed from the EMC can be performed via the EMS; there are advanced administrative tasks that can be performed only from the EMS. The EMC (shown in Figure 1.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Once a user has been assigned to a managed folder mailbox policy, any additional custom folders that must be created in that user’s mailbox will show up in the Managed Folders folder in the root of the user’s mailbox, such as those shown in Figure 1.10. You can now configure message journaling based on a specific type of content or folder. Figure 1.
IMPROVED MESSAGE AND CONTENT CONTROL ◆ Assign the managed folder mailbox policy to one or more users. A user does not need a managed folder mailbox policy. Only a single managed folder mailbox policy can be assigned to a user at one time. ◆ Create managed content settings for default folders (Inbox, Sent Items, etc.) to control the length of time that messages should remain in these folders and types of content that are allowed. This step is optional.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 More information on the archive and retention policy features can be found in Chapter 22, ‘‘Getting Started with Email Archiving.’’ Message Transport Rules Message transport rules are quite similar to Outlook rules and are even created using a wizard similar to one used to create Outlook rules. However, these rules are quite a bit more powerful and are executed on the Hub Transport servers.
IMPROVED MESSAGE AND CONTENT CONTROL Figure 1.11 Examining a transport rule Per-User Journaling Journaling a message is the process of keeping a message from one or more senders based on long-term storage, legal, regulatory, or human resources requirements. Exchange 2000/2003 essentially had one option for message journaling: create an additional mailbox store and move any mailboxes that must be kept to that mailbox store.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 ◆ Messages can also be retained using transport rules by keeping only internal or only external messages. ◆ Messages can be sent to an SMTP address that is external to the Exchange organization, such as a Microsoft Office SharePoint Server 2007 server or a third-party service provider. Figure 1.12 shows an example of a transport rule that applies to the Executives group.
IMPROVED MESSAGE AND CONTENT CONTROL message transport rules can assign a classification based on sender, recipient, message content, importance, and so on. Figure 1.13 shows an example of a message that is being composed in Outlook Web App and has had the built-in Attorney/Client Privilege classification assigned to it; the classification text is shown just above the address list. The server administrator can create additional classifications and customize the text strings. Figure 1.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Exchange Management Management of Exchange-related components and recipient objects is now performed with the new management API. All operations that can be performed have been defined as tasks. The management API provides access to all management functions via the EMS tasks, also known as cmdlets (pronounced ‘‘command-lets’’). The EMS is a set of extensions for the Windows PowerShell.
CLIENT-SIDE FEATURES Figure 1.14 Scheduling out-of-office messages for internal and external recipients When setting up an out-of-office message for external recipients, the user can specify that the response go only to senders whose address is in their Contacts folder or to any sender. Improved Calendaring and Resource Management Calendaring, resources, and out-of-office features were not as complete as most of today’s sophisticated email users require.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 relating to meeting requests, such as a Tentative response followed soon after by a Decline or Accept response. The user sees only the most recent message. Figure 1.15 Resource type is designated when the mailbox is created. The Scheduling Assistant makes the process of scheduling a meeting using either Outlook or Outlook Web App much simpler and recommends best meeting times based on requested attendees.
CLIENT-SIDE FEATURES New and Improved Outlook Web App Those of us who gushed when we saw the Outlook Web Access interface in Exchange 2003 thought a web interface could not get much better. For Outlook Web App in Exchange 2010, the Exchange team started over from scratch to build a much more functional interface than ever before.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Of course, you have to have the corresponding version of Windows Mobile that will take advantage of all the newest features. Windows Mobile 5 with the Microsoft Security and Feature Pack (MSFP) uses EAS v2.5, Windows Mobile 6 uses EAS v12, and Windows Mobile 6.1 uses EAS v12.1. Table 1.3 shows a comparison of some features of various versions of EAS and the versions of Exchange Server. Table 1.
CLIENT-SIDE FEATURES Table 1.3: Exchange ActiveSync Features (CONTINUED) Setting/Restriction E2K3 SP2 EAS v2.5 E2K10 EAS 12 E2K10 E2K10 Standard CAL Enterprise CAL EAS v12.1 EAS v12.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 Note that some of the advanced device configuration features require the use of an Exchange Server 2010 Enterprise Client Access License (CAL) for the device. This does not mean that the Exchange 2010 server requires the Enterprise Edition of Exchange Server, though. Now, Where Did That Go? As new and better functions and APIs have been introduced, naturally some functions are no longer emphasized or supported.
NOW, WHERE DID THAT GO? Exchange Server 2003 Features Removed from Exchange Server 2010 Since the release of Exchange Server 2003, a number of Exchange Server 2003 (and Exchange 2000) features have been removed. Although most of these features will not affect the majority of the Exchange deployments out there, you should keep them in mind and thoroughly evaluate your existing messaging environment to make sure you are not dependent on a feature that has no equivalent in Exchange Server 2010.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 ◆ The Exchange installable file system (ExIFS), which was also known as the M:\ drive, is no longer available. ◆ The GroupWise, cc:Mail, and Microsoft Mail connectors are no longer available. Exchange Server 2007 Features Removed from Exchange 2010 Although Exchange Server 2007 did not enjoy wide deployment, there will be organizations that will be transitioning from Exchange Server 2007 to Exchange Server 2010.
THE BOTTOM LINE scripting for Exchange 2010 has been greatly improved through the use of the EMS. Many tasks are simplified or more powerful through the EMS, but it is not necessary to learn scripting in order to start working with Exchange 2010. We strongly encourage you to get to know many of the powerful features of the EMS as you get comfortable with Exchange 2010. A number of advanced administration tasks do not have a graphical user interface option.
CHAPTER 1 INTRODUCING EXCHANGE SERVER 2010 organization. This task consists of setting the Outlook Web App policy to a new policy name. What is the quickest way to assign all of your users the new policy? Recognize Exchange architecture changes. Significant changes were made to the Exchange Server 2010 architecture to improve the scalability, security, and stability. This includes providing only an x64 edition of Exchange Server 2010.
