Exchange Mod 1
When combining server roles, reduce the maximum number of mailboxes by 20%
When combining server roles, reduce the maximum number of mailboxes by 20%
You can combine all server roles, except the Edge Transport server role, on one server
You can combine all server roles, except the Edge Transport server role, on one server
You can combine server roles with Mailbox servers that are DAG members
You can combine server roles with Mailbox servers that are DAG members
You can deploy Exchange Server 2010 only on 64-bit versions of Windows Server 2008
You can deploy Exchange Server 2010 only on 64-bit versions of Windows Server 2008
Domains:
a collection of computers that a Microsoft Windows network administrator defines.
Forests
a set of one or more domains that share common configuration and schema information. They Exchange organization and Active Directory forest have a one-to-one relationship
The benefits of deploying Exchange Servers as virtual machines include:
a. Increases hardware utilization and decreases the number of physical servers.
Sites
are defined as one or more IP subnets. Typically, all of the IP subnets in a given physical location are part of the same site. Sites do not typically encompass more than one physical location.
Memory
• Recommended: 8 GB plus 2-10 MB per mailbox • Maximum: 64 GB
Reviewing DNS requirements for Ex server 2010 (next card)
Reviewing DNS requirements for Ex server 2010 (next card)
Disk
(1) 1.2 GB disk space for Exchange Server files and 200 MB of free disk space on the system drive.
. Memory
(1) A minimum of 2 GB of system memory, plus 2 to 6 MB per mailbox. This (a) Recommendation is based on the number of mailbox databases and the user-usage profile.
DNS Requirements
(1) Before you install Exchange Server 2010, you must configure DNS correctly in your Active Directory forest. (2) All servers that run Exchange Server 2010 must be able to locate Active Directory domain controllers, global catalog servers, and other Exchange servers.
File system
(1) Drives formatted with NTFS file system
Exchange Online Services: When you subscribe you can take advantage of the following features:
(1) Email and calendar functions. Exchange Online delivers email services, including spam filtering, antivirus protection, and mobile-device synchronization. (2) Email coexistence and migration tools. The Office 365 Suite includes email coexistence and migration tools. (3) If you have AD DS and Microsoft Exchange Server, the Microsoft Online Services Directory Synchronization tool synchronizes your user accounts, contacts, and groups from your local environment to Microsoft Online Services.
Role of DNS
(1) Exchange Server services use DNS to locate a valid domain controller or global catalog. (2) By default, each time a domain controller starts the Netlogon service; it updates DNS with service (SRV) records that describe it as a domain controller and global catalog server, if applicable. (3) To ensure that the domain controller updates DNS records properly, it is essential that all domain controllers use an internal DNS server that supports dynamic updates. (4) After DNS records are registered, computers that are running Exchange Server can use DNS to find domain controllers and global catalog servers.
For all server roles, you must install:
(1) Microsoft .NET Framework 3.5, or later (2) Windows Remote Management (WinRM) 2.0 (3) Windows PowerShell version 2.
/PrepareLegacy ExchangePermissions
(1) Necessary if the organization contains Exchange Server 2003 servers (2) Modifies the permissions assigned to the Enterprise Exchange Servers group to allow the Recipient Update Service to run (3) Must be run by a member of the Enterprise Admins group
/PrepareDomain domainname
(1) Prepares the domain for Exchange Server 2010 by creating a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers
/PrepareAD /OrganizationName: organizationname
(1) Prepares the global Exchange Server objects in Active Directory, creates the Exchange Universal Security Groups in the root domain, and prepares the current domain (2) Must be run by a member of the Enterprise Admins group
/PrepareSchema
(1) Prepares the schema for the Exchange Server 2010 installation (2) Must be run by a member of the Enterprise Admins and Schema Admins groups
Use the following steps to secure computers that are running Exchange Server 2010:
(1) Restrict physical access. Like all servers, physical access to a computer that is running Exchange Server should be restricted. (2) Restrict communication. You can use firewalls to restrict the communication between servers, and between servers and clients. (3) Reduce the attack surface. To limit software flaws that hackers can use, eliminate unnecessary software and services from your Exchange servers. (4) Restrict permissions. Evaluate who has permissions
Exchange Server 2010 Editions
(1) Standard Edition: should meet the messaging needs of small and medium corporations, but also may be suitable for specific server roles or branch offices (2) Enterprise Edition: Edition is for large enterprise corporations, and enables you to create additional databases apart from including other advanced features.
SRV Resource Records are DNS records.
(1) These records identify servers that provide specific services on the network.
/OrganizationName
(1) Use the parameter to specify the name to give the new Exchange organization. (2) This parameter is required if you are installing the first server in an organization and you have not run /PrepareAD.
/roles, /r
(1) Use this parameter to specify which roles you want to install. (a) If you specify multiple roles, separate them with commas.
/mode, /m
(1) used for Install and upgrade (2) Use this parameter to control what the setup program does.
Processor
(1) x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). (2) AMD processor that supports the AMD64 platform. (3) Intel Itanium IA64 processors not supported.
Domain controller
: database, which includes user and computer accounts.
MX records
A Mail Exchanger (MX) record is a resource record that allows servers to locate other servers to deliver Internet email by using the Simple Mail Transfer Protocol (SMTP). (1) An MX record identifies the SMTP server that will accept inbound messages for a specific DNS domain. Each MX record contains a host name and a preference value. (2) When you deploy multiple SMTP servers that are accessible from the Internet, you can assign equal preference values to each MX record to enable load balancing between the SMTP servers.
Global Catalog
A global catalog server is a domain controller that holds a subset of limited information from other domains in the forest.
AD DS consists of several components: (next card)
AD DS consists of several components: (next card)
Considerations for Deploying Exchange Server 2010 As a Virtual Machine (next card)
Considerations for Deploying Exchange Server 2010 As a Virtual Machine (next card)
Deployment options for Ex sever 2010 (next card)
Deployment options for Ex sever 2010 (next card)
configuration:
Exchange configuration
Global Catalog:
Exchange object attributes for mail-enabled and mailbox-enabled objects
Schema
Exchange object classes and attributes
Domain:
Exchange recipients
Hardware Recommendations for combining server roles (next card)
Hardware Recommendations for combining server roles (next card)
SchemaHow Exchange Server 2010 Uses AD DS (next card)
How Exchange Server 2010 Uses AD DS (next card)
Hybrid Deployment with Office 365:
In Exchange Server 2010 Service Pack 2 (SP2), it is possible to create a hybrid deployment between on-premises Exchange Server and Exchange Online from Office 365.
Reviewing Active Directory Partitions: (next card)
Reviewing Active Directory Partitions: (next card)
Large or complex organization needs to deploy dedicated servers for each server role, and may have to deploy multiple servers for each role.
Large or complex organization needs to deploy dedicated servers for each server role, and may have to deploy multiple servers for each role.
Options for Integrating Exchange Server 2010 and Exchange Online Services in Office 365 (next card)
Options for Integrating Exchange Server 2010 and Exchange Online Services in Office 365 (next card)
Preparing ADDS for Ex server 2010 (next card)
Preparing ADDS for Ex server 2010 (next card)
Process for installing ex server 2010 (next card)
Process for installing ex server 2010 (next card)
Server Roles in Ex sever 2010 (next card)
Server Roles in Ex sever 2010 (next card)
Sever requirements for sever ex 2010 (next card)
Sever requirements for sever ex 2010 (next card)
Domain Partition:
contains all objects in the domain's directory.
Configuration partition:
contains configuration Information for AD DS and applications, including Active Directory site and site link information.
Schema Partition:
contains definition information for all object types and their attributes that you can create in AD DS. This data is common to all domains in the forest, and AD DS replicates it to all domain controllers in the forest. However, only one domain controller maintains a writable copy of the schema.
Client Access server role
enables connections from all available client protocols to the Exchange Server mailboxes. (a) You must assign at least one Client Access server in each Active Directory site that contains a Mailbox server.
Trusts
enables users from a trusted domain to authenticate in another trusting domain.
Application Partitions:
hold specific application data that the application requires. The main benefit of application partitions is replication flexibility.
Hub Transport server role
is responsible for message routing. (a) Performs message categorization and routing, and handles all messages that pass through an organization. (b) You must configure at least one Hub Transport server in each Active Directory site that contains a Mailbox server or a Unified Messaging server. (c)server running the Hub Transport server role must be a member of an Active Directory domain.
Edge Transport server role
is the Simple Mail Transport Protocol (SMTP) gateway server between your organization and the Internet. (a) To ensure security, you should deploy the computer that runs the Edge Transport server role in a perimeter network, and it should not be a member of your internal Active Directory forest. (b)Because the Edge Transport server is not part of an Active Directory domain, it cannot use AD DS to store configuration information.
Host Records:
provide a host name to IP address mapping. (1) Host records are required for each domain controller and other hosts that need to be accessible to Exchange Servers or client computers. (2) Host records can use IPv4 (A records) or IPv6 (AAAA records).
Unified Messaging server role
provides the foundation of services that integrate voice and fax messages into your organization's messaging infrastructure. (a) This role requires the presence of three server roles: -- Hub Transport -- Client Access -- Mailbox (b) The Unified Messaging server provides access to voice messages and faxes.
Replication
replicates information between domain controllers.
Mailbox server role
responsible for managing mailbox and public folder databases. (a) Mailboxes and public folders reside on the Mailbox servers. Mailbox servers contain mailbox and public folder databases. (b) You can enable high availability by adding mailbox servers to a Database Availability Group (DAG). (c) Because Mailbox servers require Active Directory access, you must install this role on a member server in an Active Directory domain.
Processor cores:
•Minimum: 2 •Recommended: 8 •Maximum: 24 •Plan on using half the processor cores for the mailbox server role