The Experts below are selected from a list of 18 Experts worldwide ranked by ideXlab platform
Michel De Rooij - One of the best experts on this subject based on the ideXlab platform.
-
Exchange 2013 Mailbox Server
Pro Exchange 2013 SP1 PowerShell Administration, 2014Co-Authors: Jaap Wesselius, Michel De RooijAbstract:The primary Role of the Mailbox Server is to host Mailbox databases where the recipient Mailboxes are hosted. But in Exchange Server 2013, there’s more done besides hosting those Mailboxes. The Hub Transport service is also running on the Mailbox Server, and this service is responsible for all SMTP message routing in the Exchange organization. The Unified Messaging (UM)service is also part of the Mailbox Server Role, and there's a Client Access service (CAS) running on the Mailbox Server as well. As explained in the previous chapter, the Client Access Server is a stateless protocol proxy, proxying user requests to the Mailbox Server; this is the Server where all processing takes place. But in Exchange 2013, the business logic was moved from the Client Access Server to the Mailbox Server. This is the reason you’ll find the Autodiscover section in this chapter instead of in Chapter 3.
Jaap Wesselius - One of the best experts on this subject based on the ideXlab platform.
-
Exchange 2013 Mailbox Server
Pro Exchange 2013 SP1 PowerShell Administration, 2014Co-Authors: Jaap Wesselius, Michel De RooijAbstract:The primary Role of the Mailbox Server is to host Mailbox databases where the recipient Mailboxes are hosted. But in Exchange Server 2013, there’s more done besides hosting those Mailboxes. The Hub Transport service is also running on the Mailbox Server, and this service is responsible for all SMTP message routing in the Exchange organization. The Unified Messaging (UM)service is also part of the Mailbox Server Role, and there's a Client Access service (CAS) running on the Mailbox Server as well. As explained in the previous chapter, the Client Access Server is a stateless protocol proxy, proxying user requests to the Mailbox Server; this is the Server where all processing takes place. But in Exchange 2013, the business logic was moved from the Client Access Server to the Mailbox Server. This is the reason you’ll find the Autodiscover section in this chapter instead of in Chapter 3.
Juergen Hasslauer - One of the best experts on this subject based on the ideXlab platform.
-
Chapter 6 – Exchange Server 2007 Failover Clustering
Designing Storage for Exchange 2007 SP1, 2008Co-Authors: Pierre Bijaoui, Juergen HasslauerAbstract:Publisher Summary This chapter provides an introduction to Windows Failover Clustering (WFC) in Windows Server 2003 and Windows Server 2008, followed by a discussion of Exchange Server 2007 Clustered Mailbox Servers. Clusters are multiple computers that appear to users as a single highly available system. The objective of clustering concept is a “no single point of failure” configuration. If one component fails, another component takes over the responsibility, and the service offered by the cluster should not be affected from an end-user point of view. Typically, a clustered deployment is considered if one wants to increase the availability of messaging service, or if business continuity requirements demand a geographically dispersed deployment with relatively short recovery time objectives. Exchange administrators should have at least a basic knowledge of the WFC concept to understand the various cluster architectures used by the two implementation alternatives for a Clustered Mailbox Server (CMS) in Exchange Server 2007, Cluster Continuous Replication (CCR), and Single Copy Cluster (SCC). The Mailbox Server Role is the only Role in Exchange Server 2007 that can be deployed on a cluster. In Exchange Server 2007, Outlook Web Access or transport services are provided by the Client Access Server (CAS) and Hub Transport (HT) Server Role. Both Roles cannot be installed on a WFC. A Server with the HT and another with the CAS Role must be online in the same AD site; otherwise, users cannot send and receive emails or connect to their Mailbox using Internet protocols. The minimal configuration is four Exchange Servers: two clustered nodes for the Mailbox Server and two multiRole Servers with both the HT and CAS Role installed. Additionally, two Active Directory (AD) global catalog Servers are needed.
Tony Redmond - One of the best experts on this subject based on the ideXlab platform.
-
Microsoft Exchange Server 2007 with SP1: Tony Redmond's Guide to Successful Implementation
1998Co-Authors: Tony RedmondAbstract:Exchange 2007 represents the biggest advance in the history of Microsoft Exchange Server technology. Given Exchange's leap to x64 architecture and its wide array of new features, it isn't surprising that the SP1 release of 2007 would be particularly robust in terms of hotfixes, security enhancements and additional functionality. Tony Redmond's upgraded edition of his popular Microsoft Exchange Server 2007 bible features extensive coverage of the significant changes and additions offered with SP1. Every chapter has been updated, with particular focus on the most pivotal aspects of SP1, including:*install enabling on Windows Server 2008 *IVp6 support*Unified Messaging inclusion*EMC enhancements*Client Access Improvements for Outlook Web Access and Activesync*New user interfaces for POP3 and IMAP4*System resource monitoring and message routing improvements*New features for the Mailbox Server Role*.pst file data managment improvements*new high-availability features*optimization for mobile access*and much mor e!*Complete coverage of all the updates in SP1 ensure admins skip the initial 2007 release's bugs and upgrade with ease*Written by HP Services CTO Tony Redmond, the world's most trusted author of Exchange books for over a decade*250+ pages of updates throughout, including totally new sections on Windows 2008 compatibility, Microsoft Yona, Windows Mobile 6 and 6.1 devices, Apple iPhone, and more!
Pierre Bijaoui - One of the best experts on this subject based on the ideXlab platform.
-
Chapter 6 – Exchange Server 2007 Failover Clustering
Designing Storage for Exchange 2007 SP1, 2008Co-Authors: Pierre Bijaoui, Juergen HasslauerAbstract:Publisher Summary This chapter provides an introduction to Windows Failover Clustering (WFC) in Windows Server 2003 and Windows Server 2008, followed by a discussion of Exchange Server 2007 Clustered Mailbox Servers. Clusters are multiple computers that appear to users as a single highly available system. The objective of clustering concept is a “no single point of failure” configuration. If one component fails, another component takes over the responsibility, and the service offered by the cluster should not be affected from an end-user point of view. Typically, a clustered deployment is considered if one wants to increase the availability of messaging service, or if business continuity requirements demand a geographically dispersed deployment with relatively short recovery time objectives. Exchange administrators should have at least a basic knowledge of the WFC concept to understand the various cluster architectures used by the two implementation alternatives for a Clustered Mailbox Server (CMS) in Exchange Server 2007, Cluster Continuous Replication (CCR), and Single Copy Cluster (SCC). The Mailbox Server Role is the only Role in Exchange Server 2007 that can be deployed on a cluster. In Exchange Server 2007, Outlook Web Access or transport services are provided by the Client Access Server (CAS) and Hub Transport (HT) Server Role. Both Roles cannot be installed on a WFC. A Server with the HT and another with the CAS Role must be online in the same AD site; otherwise, users cannot send and receive emails or connect to their Mailbox using Internet protocols. The minimal configuration is four Exchange Servers: two clustered nodes for the Mailbox Server and two multiRole Servers with both the HT and CAS Role installed. Additionally, two Active Directory (AD) global catalog Servers are needed.