Exchange

Overview of the Hub Transport Server Role
miércoles, 13 de febrero de 2019 21:09
The Hub Transport server role handles all mail flow inside the organization, applies transport rules,
applies journaling policies, and delivers messages to a recipient's mailbox.
Messages that are sent to the Internet are relayed by the Hub Transport server to the Edge Transport
server role that's deployed in the perimeter network.
Messages that are received from the Internet are processed by the Edge Transport server before they're
relayed to the Hub Transport server.
If you don't have an Edge Transport server, you can configure the Hub Transport server to relay Internet
messages directly or utilize a third-party smart host.
You can also install and configure the Edge Transport server agents on the Hub Transport server to
provide anti-spam and antivirus protection inside the organization, although this isn't recommended.
You must deploy a Hub Transport server role in each Active Directory site that contains a Mailbox server
role.
HUB TRANSPORT Page 1

Internal Mail Flow
The Hub Transport server role processes all messages that are sent inside the Microsoft Exchange Server
2010 organization before the messages are delivered to a recipient's Inbox or are routed to users
outside the organization.
There are no exceptions to this behavior; messages are always passed through a server that runs the
Hub Transport server role.
Messages are submitted to the Hub Transport server in three ways:
• Through a Receive connector (SMTP submission)

• From the Pickup directory or the Replay directory
• By direct placement in the Submission queue by the store driver
(When a user inside the organization sends a message)
The store driver is a software component of the Hub Transport server that delivers inbound messages to
Exchange stores.
When messages are submitted to the Hub Transport server, they're processed by the categorizer.
The categorizer is a component of Exchange transport that processes all inbound messages and
determines what to do with the messages based on information about the intended recipients.
In Exchange 2010, the Hub Transport server uses the categorizer to expand distribution lists and to
identify alternative recipients and forwarding addresses.
After the categorizer retrieves full information about the recipients, it uses that information to apply
policies, route the messages, and perform content conversion.
Messages are then delivered locally by the store driver to a recipient's mailbox, or they're delivered
remotely by using SMTP to send messages to another transport server.
Messages that are sent by users in your organization are picked up from the sender's Outbox by the
store driver and are put in the Submission queue on a server that runs the Hub Transport server role.

Messaging Policy and Compliance Features
With a collection of transport agents, you can configure rules and settings that are applied as messages
enter and leave the mail flow components.
You can create messaging policy and rule settings that are designed to meet different regulations and
that can easily be changed to adapt to your organization's requirements (A rule that has a message
warning or a disclaimer in all emails that are delivered internally).
The transport-based messaging policy and compliance features include server-based rules that you
configure to enforce your organization's compliance scenarios and the Journaling agent that acts to
enforce message retention.

Anti-Spam and Antivirus Protection
Exchange 2010 provides anti-spam and antivirus protection for messages.
Although these features are designed for use in the perimeter network on the Edge Transport server
role, the Edge Transport agents can also be configured on the Hub Transport server.
In Exchange 2010 the anti-spam and antivirus features provide services to block viruses and spam or
unsolicited commercial email, at the network perimeter.

Overview of the Edge Transport Server Role
In Microsoft Exchange Server 2010, the Edge Transport server role is deployed in your organization's
perimeter network.
Designed to minimize the attack surface, the Edge Transport server handles all Internet-facing mail flow,
which provides SMTP relay and smart host services for the Exchange organization.
The computer that has the Edge Transport server role installed doesn't have access to Active Directory.
To perform recipient lookup tasks, the Edge Transport server requires data that resides in Active
Directory. This data is synchronized to the Edge Transport server using EdgeSync.
EdgeSync is a collection of processes that are run on a computer that has the Hub Transport server role
installed to establish one-way replication of recipient and configuration information from Active
Directory to the AD LDS instance on an Edge Transport server.

Internet Mail Flow
Servers that run the Edge Transport server role accept messages that come into the Exchange 2010
organization from the Internet.
After the messages are processed by the Edge Transport server, they are routed to Hub Transport
servers inside the organization.
All messages that are sent to the Internet from the organization are routed to Edge Transport servers
after the messages are processed by the Hub Transport server.

Anti-Spam and Antivirus Protection
Spammers use a variety of techniques to send spam into your organization. Servers that run the Edge
Transport server role help prevent users in your organization from receiving spam by providing a
collection of agents that work together to provide different layers of spam filtering and protection.

Edge Transport Rules
Edge Transport rules are used to control the flow of messages that are sent to or received from the
Internet.
The Edge Transport rules help protect corporate network resources and data by applying an action to
messages that meet specified conditions.
Edge Transport rule conditions are based on data, such as specific words or text patterns in the message
subject, body, header, or From address, the spam confidence level (SCL), or attachment type.
Possible actions include quarantine of a message, dropping or rejecting a message, appending additional
recipients, or logging an event. Optional exceptions exempt particular messages from having an action
applied.

Address Rewriting
You use address rewriting to present a consistent appearance to external recipients of messages from
your Exchange 2010 organization.
You configure the Address Rewriting agent on the Edge Transport server role to enable the modification
of the SMTP addresses on inbound and outbound messages.
Address rewriting is especially useful when a newly merged organization that has several domains wants
to present a consistent appearance of e-mail addresses to external recipients.

Transport Pipeline
In Microsoft Exchange Server 2010, the transport pipeline is a collection of Exchange 2010 server roles,
connections, components, and queues that work together to route all messages to the categorizer on a
Hub Transport server inside the organization.
Messages from outside the organization enter the transport pipeline through a Receive connector on an
Edge Transport server and are then routed to a Hub Transport server inside the organization.
Messages inside the organization enter the transport pipeline on a Hub Transport server in one of the
following ways:
• Through a Receive connector (SMTP submission)

• From the Pickup directory or the Replay directory
• By direct placement in the Submission queue by the store driver
(When a user inside the organization sends a message)
The Exchange 2010 transport pipeline consists of the following components and processes:
SMTP Receive
When messages are received at the Edge Transport server, anti-spam and antivirus agents filter
connections and message contents, and help identify the sender and the recipient of a message while
the message is being accepted into the organization. When messages are received at a Hub Transport
server, transport rules are applied and, if anti-spam and antivirus agents are configured, these agents
provide an additional layer of anti-spam and antivirus protection.
The SMTP session has a series of events that work together in a specific order to validate the contents of
a message before it's accepted into the organization. After a message has passed completely through
SMTP Receive and isn't rejected by receive events or by an anti-spam and antivirus agent, it's put in the
Submission queue.
Submission
Submission is the process of putting messages into the Submission queue. The categorizer picks up one
message at a time for categorization. There are four types of submission:
○ SMTP submission through a Receive connector.
○ Submission through the Pickup directory or the Replay directory. These directories exist on the
Hub Transport server or Edge Transport server. Correctly formatted message files that are copied
into the Pickup directory or the Replay directory are put directly into the Submission queue.
○ Submission by the store driver, which picks up messages from a sender’s Outbox as they're sent.
○ Submission by an agent.
On the Edge Transport server, submission is generally only through the Receive connector. On the Hub
Transport server, submission can occur through a Receive connector, Pickup directory, Replay directory,
or store driver.
Categorizer
The categorizer picks up one message at a time from the Submission queue. On the Edge Transport

The categorizer picks up one message at a time from the Submission queue. On the Edge Transport
server, categorization is a short process in which the message is put directly in the delivery queue. From
the delivery queue, the message is routed to a computer that's running a Hub Transport server role in
the organization.
On the Hub Transport server, the categorizer completes the following steps:
○ Recipient resolution, which includes top-level addressing, expansion, and bifurcation
○ Routing resolution
○ Content conversion
Additionally, mail flow rules that are defined by the organization are applied. After messages have been
categorized, they're put into a delivery queue. A mailbox delivery queue delivers the message to a local
mailbox by using the store driver. A remote delivery queue delivers the message to a remote recipient
through a Send connector.
Local Delivery
Only messages that are sent to a recipient with a mailbox in the same Active Directory site as the Hub
Transport server on which categorization occurred are delivered locally. In this case, local delivery
means delivery in the same Active Directory site. All messages delivered locally are picked up from a
delivery queue by the store driver and put in the recipient’s inbox on a Mailbox server.
SMTP Send
Messages that are sent to recipients in Active Directory sites that differ from the computer that's
running a Hub Transport server role on which categorization occurred are delivered remotely or outside
the organization. All messages that are sent to a different Active Directory site, to a mailbox that resides
on a computer that's running an earlier version of Exchange, or to a mailbox that resides in a different
Active Directory forest must be routed through a Send connector to a Hub Transport server that can
deliver the message to the intended recipient. All messages that require delivery through the Internet
must be routed through a Send connector to an Edge Transport server that can send messages to the
Internet for delivery outside the organization.

What is Exchange ActiveSync?
jueves, 14 de febrero de 2019 22:32
It is a Microsoft Exchange synchronization protocol that's optimized to work together with high-latency
and low-bandwidth networks.
The protocol lets mobile phones access an organization's information on a server that's running
Microsoft Exchange.
Exchange ActiveSync enables mobile phone users to access their e-mail, calendar, contacts, and tasks
Users can continue accessing their information while they're working offline.
By default, when you install the Client Access server role on a computer that's running Exchange Server,
you enable Exchange ActiveSync.
Exchange ActiveSync lets you synchronize a mobile phone with your Exchange 2010 mailbox.
EXCHANGE ACTIVESYNC Page 13

What can you manage in Exchange Active Sync?
By default, Exchange ActiveSync is enabled. All users who have an Exchange mailbox can synchronize
their mobile phone with the Microsoft Exchange server.
You can perform the following Exchange ActiveSync tasks:
○ Enable and disable Exchange ActiveSync for users

○ Set policies such as minimum password length, device locking, and maximum failed password
attempts.
○ Initiate a remote wipe to clear all data from a lost or stolen mobile phone.
○ Run a variety of reports for viewing or exporting into a reporting solution.

Security Features in ActiveSync
You can configure ActiveSync to use (SSL) encryption for communications between the Exchange server
and the mobile phone client.
Certificate-based authentication works with a self-signed certificate, a certificate from an existing public
key infrastructure, or a third-party commercial certificate.
Besides enabling the ability to configure security options for communications between Exchange and
your mobile phones, Exchange ActiveSync offers the following features to enhance the security of
mobile phones:
Remote wipe
If a mobile phone is lost or stolen you can issue a remote wipe command from the Exchange Server
computer or from any Web browser by using Outlook Web App. This command erases all data from the
mobile phone.
Device password policies

Exchange ActiveSync lets you configure several options for device passwords. These options include the
following:
○ Minimum password length (characters)

This option specifies the length of the password for the mobile phone. The default length is 4
characters, but as many as 18 can be included.
○ Minimum number of character sets

Use this text box to specify the complexity of the alphanumeric password and force users to use a
number of different sets of characters from among the following: lowercase letters, uppercase
letters, symbols and numbers.
○ Require alphanumeric password

This option determines password strength. You can enforce the usage of a character or symbol in
the password in addition to numbers.
○ Inactivity time (seconds)

This option determines how long the mobile phone must be inactive before the user is prompted
for a password to unlock the mobile phone.

○ Enforce password history
Select this check box to force the mobile phone to prevent the user from reusing their previous
passwords. The number that you set determines the number of past passwords that the user
won't be allowed to reuse.
○ Enable password recovery

Select this check box to enable password recovery for the mobile phone. Users can use Outlook
Web App to look up their recovery password and unlock their mobile phone. Administrators can
use the EMC to look up a user's recovery password.
○ Wipe device after failed (attempts)

This option lets you specify whether you want the phone's memory to be wiped after multiple
failed password attempts.
○ Device Encryption Policies

There are a number of mobile phone or device encryption policies that you can enforce for a
group of users. These policies include the following:
○ Require encryption on device

Select this check box to require encryption on the mobile phone. This increases security by
encrypting all information on the mobile phone.
○ Require encryption on storage cards

Select this check box to require encryption on the mobile phone’s removable storage card. This
increases security by encrypting all information on the storage cards for the mobile phone.

What is Direct Push?
It is a feature that's built into Microsoft Exchange Server 2010.
Direct Push keeps a mobile phone current over a cellular network connection.
It provides notification to the mobile phone when new content is ready to be synchronized to the
mobile phone.
For Direct Push to work, the mobile phone or other mobile device must be Direct Push capable.
Mobile phones that support Direct Push issue a long-lived HTTPS request to the server running
Microsoft Exchange.
The Exchange server monitors activity on the user's mailbox and sends a response to the device if there
are any changes.
If changes occur within the lifespan of the HTTPS request, the Exchange server issues a response to the
device that states that changes have occurred and the device should initiate synchronization with the
Exchange server.
The device then issues this request to the server. When synchronization is complete, a new long-lived
HTTPS request is generated to start the process again.
This guarantees that e-mail, calendar, contact, and task items are delivered quickly to the mobile phone,
and the device is always synchronized with the Exchange server.
Direct Push operates in the following way:
A mobile phone that's configured to synchronize with an Exchange 2010 server issues an HTTPS request

A mobile phone that's configured to synchronize with an Exchange 2010 server issues an HTTPS request
to the server. This request is known as a PING. The request tells the server to notify the device if any
items change in any folder that's configured to synchronize in the next 15 minutes. Otherwise, the
server should return an HTTP 200 OK message. The mobile phone then stands by. The 15-minute time
span is known as a heartbeat interval.
If no items change in 15 minutes, the server returns a response of HTTP 200 OK. The mobile phone
receives this response, resumes activity (known as waking up), and issues its request again. This restarts
the process.
If any items change or new items are received within the 15-minute heartbeat interval, the server sends
a response that informs the mobile phone that there's a new or changed item and provides the name of
the folder in which the new or changed item resides. After the mobile phone receives this response, it
issues a synchronization request for the folder that has the new or changed items. When
synchronization is complete, the mobile phone issues a new PING request and the whole process starts
over.
Direct Push depends on network conditions that support a long-standing HTTPS request. If the carrier
network for the mobile phone or the firewall doesn't support long-standing HTTPS requests, the HTTPS
request is stopped. The following steps describe how Direct Push operates when a mobile phone's
carrier network has a time-out value of 13 minutes:
A mobile phone issues an HTTPS request to the server. The request tells the server to notify the device if
any items change in any folder that is configured to synchronize in the next 15 minutes. Otherwise, the
server should return an HTTP 200 OK message. The mobile phone then stands by.
If the server does not respond after 15 minutes, the mobile phone wakes up and concludes that the
connection to the server was timed out by the network. The device reissues the HTTPS request, but this
time it uses a heartbeat interval of 8 minutes.
After 8 minutes, the server sends an HTTP 200 OK message. The device then tries to gain a longer
connection by issuing a new HTTPS request to the server that has a heartbeat interval of 12 minutes.
After 4 minutes, a new e-mail message is received and the server responds by sending an HTTPS request
that tells the device to synchronize. The device synchronizes and reissues the HTTPS request that has a
heartbeat of 12 minutes.
After 12 minutes, if there are no new or changed items, the server responds by sending an HTTP 200 OK
message. The device wakes up and concludes that network conditions support a heartbeat interval of 12
minutes. The device then tries to gain a longer connection by reissuing an HTTPS request that has a
heartbeat interval of 16 minutes.
After 16 minutes, no response is received from the server. The device wakes up and concludes that
network conditions cannot support a heartbeat interval of 16 minutes. Because this failure occurred
directly after the device tried to increase the heartbeat interval, it concludes that the heartbeat interval
has reached its maximum limit. The device then issues an HTTPS request that has a heartbeat interval of
12 minutes because this was the last successful heartbeat interval.
The mobile phone tries to use the longest heartbeat interval the network supports. This extends battery
life on the device and reduces how much data is transferred over the network. Mobile carriers can
specify a maximum, minimum, and initial heartbeat value in the registry settings for the mobile phone.
d

OUTLOOK ANYWHERE
the Outlook Anywhere feature, formerly known as RPC over HTTP, lets clients who use Microsoft
Outlook 2013, Outlook 2010, or Outlook 2007 connect to their Exchange servers from outside the
corporate network or over the Internet using the RPC over HTTP Windows networking component.
The Windows RPC over HTTP Proxy component, which Outlook Anywhere clients use to connect, wraps
remote procedure calls (RPCs) with an HTTP layer.
OUTLOOK ANYWHERE Page 19

Benefits of using Outlook Anywhere
Users have remote access to Exchange servers from the Internet.
You can use the same URL and namespace that you use for Outlook Web App and Microsoft Exchange
ActiveSync.
You can use the same Secure Sockets Layer (SSL) server certificate that you use for both Outlook Web
App and Exchange ActiveSync.
Unauthenticated requests from Outlook can't access Exchange servers.
You don't have to use a virtual private network (VPN) to access Exchange servers across the Internet.
If you already use Outlook Web App with SSL or Exchange ActiveSync with SSL, you don't have to open
any additional ports from the Internet.
You can test end-to-end client connectivity for Outlook Anywhere and TCP-based connections by using
the Test-OutlookConnectivity cmdlet.
To enable Outlook Anywhere, follow these steps in order:
Install a valid Secure Sockets Layer (SSL) certificate from a trusted certification authority (CA) that the
client trusts.
Install the Windows RPC over HTTP Proxy component.
Enable Outlook Anywhere on a computer that has the Exchange Server 2007 Client Access server role
installed.
OUTLOOK ANYWHERE Page 20

The CAS Role
The Client Access server role is one of five distinct server roles for Microsoft Exchange Server 2010.
It supports the following client applications:
○ Outlook Web App (OWA)

○ Exchange ActiveSync (EAS)
○ Post Office Protocol version 3 (POP3)
○ Internet Message Access Protocol version 4 (IMAP4)
○ Outlook
The Client Access server role also provides access to free/busy data by using the Availability service.
It also enables certain clients to download automatic configuration settings from the Autodiscover
service.
As we can see, the Client Access server role accepts connections to your Exchange 2010 server from
different clients.
You must install the Client Access server role in every Exchange organization and every Active Directory
site that has the Mailbox server role installed.
THE CLIENT ACCESS SERVER ROLE Page 21

Client Access Server Network Architecture
In addition to needing a Client Access server in every Active Directory site that contains a Mailbox
server, it’s important to avoid restricting traffic among Exchange servers.
Otherwise, Exchange functionality can be negatively affected.
Make sure that all defined ports used by Exchange are open in both directions between all source and
destination servers.
Installing a firewall between Exchange servers or between an Exchange Server 2010 Mailbox server or
Exchange Server 2010 Client Access server and Active Directory is not supported.
As mentioned before there is a list of ports that have to be available for Microsoft Exchange to work.
Here are the ports that must be open in order for a CAS server to work correctly.

OWA
By default, when you install the Client Access server role on a computer that's running
Microsoft Exchange Server 2010, you enable Outlook Web App.
Microsoft Office Outlook Web App lets you access your Exchange mailbox from almost any Web
browser.
Outlook Web App was called Outlook Web Access in previous versions of Microsoft Exchange.
Features in Outlook Web App

Outlook Web App mailbox policies: In Exchange 2010, you can use Outlook Web App mailbox policies to
control users' access to features in Outlook Web App.
More Web browsers supported: In Exchange 2010, users have access to the standard version of Outlook
Web
App through Safari and Firefox, in addition to Internet Explorer.
Conversation view: Conversation view lets users see all messages in a thread, including messages not in
the current folder.
Chat: Outlook Web App can be configured to work with Microsoft Office Communications Server 2007
or with Microsoft Lync Server 2010 to allow users to chat without having to install Office Communicator
2007 or Lync 2010.
Filters: Users have access to a set of predefined filters to quickly search the contents of folders.
Attach messages to messages: Users can attach a message from their mailbox to a new message. In
previous versions of Outlook Web App, users could attach files to messages, but couldn't attach a
message to a message.
When you install the Client Access server role, a default virtual directory named OWA is created in IIS.
OUTLOOK WEB APP Page 25

Tools for managing OWA
Exchange Management Console: The Exchange console graphical interface.
Exchange Management Shell: Command-line interface.
Internet Information Service (IIS): IIS Manager is used to manage user access to the Outlook Web App
virtual directories.
Web.config: Some Outlook Web App settings, such as the ConnectionCacheSize and MaxRequestLength
values, must be configured by modifying Web.config, this should be modified only by using tools such as
Notepad. If you modify Web.config by using IIS, the file will become corrupted.
Registry Editor: editing the registry.
OWA Mailbox Policies

You can use the Microsoft Office OWA mailbox policies to create organization-level policies to manage
access to features in Outlook Web App.
In Exchange 2010, you can create multiple Outlook Web App mailbox policies and apply them to
individual mailboxes.
A default Outlook Web App mailbox policy is created automatically when the Client Access server role is
installed.
By default, all options are enabled on the default Outlook Web App mailbox policy.
The default Outlook Web App mailbox policy is not automatically applied to any mailboxes.
OUTLOOK WEB APP Page 26

Autodiscover services
viernes, 15 de febrero de 2019 00:03
The Autodiscover service minimizes user configuration and deployment steps by providing clients access
to Exchange features.
For Exchange Web Services (EWS) clients, Autodiscover is typically used to find the EWS endpoint URL.
Exchange stores in Active Directory the configuration of Exchange servers in the organization as well as
information about your users' mailboxes.
Exchange automatically creates at installation the virtual directory autodiscover in IIS
The SCP object is also created in Active Directory at the same time as the Autodiscover service virtual
directory.
The SCP stores and provides authoritative URLs of the Autodiscover service for domain-joined
computers.
Set-ClientAccessService -Identity "MBX-01" -AutoDiscoverServiceInternalUri

"https://mbx01.contoso.com/autodiscover/autodiscover.xml" -AutoDiscoverSiteScope "Mail"
Autodiscover is simple to set up for your domain because it only requires that you create a CNAME
resource record in your external (public) DNS.
A CNAME or canonical name record is the DNS equivalent to a Windows shortcut or an Apple Mac alias.
A CNAME record is an alias for an Address (A) record that maps an IP address to the target server.
The externally accessible FQDN of the Mailbox server (for example, mail.contoso.com)
AUTODISCOVER Page 27
Autodiscover services in Outlook
With only the user credentials, the Outlook client can authenticate to Active Directory and search for the
Autodiscover SCP objects.
○ Outlook on the web

○ Offline address book generation (OAB)
○ Exchange Web Services
○ Exchange ActiveSync
○ Autodiscover
○ POP
○ IMAP
○ Outlook Anywhere
The client then collects the profile information in the form of XML data that's needed to connect to the
user's mailbox and available Exchange features.
You need to set up a special DNS record for your domain name that points to the server providing
Autodiscover services so that Exchange accounts function correctly in Outlook.
For external access, or using DNS, the client locates the Autodiscover service on the Internet by using
the primary SMTP domain address from the user's email address.
Service Connection Points (SCPs) are objects in Active Directory that hold information about services.
It is used when the client connects internally
The SCP object contains two pieces of information, the serviceBindingInformation attribute and the
keywords attribute.
The serviceBindingInformation attribute has the Fully Qualified Domain Name (FQDN) of the Client
Access server in the form of https://cas01.contoso.com/autodiscover/autodiscover.xml
The keywords attribute specifies the Active Directory sites to which this SCP record is associated.
The Autodiscover service queries Active Directory to obtain the connection settings and URLs for the
Exchange services that have been configured.
The Autodiscover service returns an HTTPS response with an XML file that includes the connection
settings and URLs for the available Exchange services.
Outlook uses the appropriate configuration information and connection settings to connect to your
Exchange messaging environment.
When Outlook 2007 is started on a client that is not domain-connected, it first tries to locate the
Autodiscover service by looking up the SCP object in Active Directory. Because the client is unable to
contact Active Directory, it tries to locate the Autodiscover service by using Domain Name System (DNS).
The Availability service makes free/busy information available to Outlook and Outlook on the web.
The Availability service improves information workers' calendaring and meeting scheduling experience
by providing secure, consistent, and up-to-date free/busy information.
Free/busy time
Free/busy, subject, location
AVAILAVILITY SERVICES Page 30

Exchange

Încărcat de

Informații document

Drepturi de autor

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Exchange

Încărcat de

Drepturi de autor:

Overview of the Hub Transport Server Role

miércoles, 13 de febrero de 2019 21:09

HUB TRANSPORT Page 1

Messages are submitted to the Hub Transport server in three ways:

• Through a Receive connector (SMTP submission)

HUB TRANSPORT Page 2

HUB TRANSPORT Page 4

Exchange 2010 provides anti-spam and antivirus protection for messages.

HUB TRANSPORT Page 5

HUB TRANSPORT Page 6

HUB TRANSPORT Page 7

HUB TRANSPORT Page 8

HUB TRANSPORT Page 9

HUB TRANSPORT Page 10

• Through a Receive connector (SMTP submission)

○ SMTP submission through a Receive connector.

HUB TRANSPORT Page 11

○ Recipient resolution, which includes top-level addressing, expansion, and bifurcation

HUB TRANSPORT Page 12

EXCHANGE ACTIVESYNC Page 13

You can perform the following Exchange ActiveSync tasks:

○ Enable and disable Exchange ActiveSync for users

EXCHANGE ACTIVESYNC Page 14

Device password policies

○ Minimum password length (characters)

○ Minimum number of character sets

○ Require alphanumeric password

○ Inactivity time (seconds)

EXCHANGE ACTIVESYNC Page 15

○ Enable password recovery

○ Wipe device after failed (attempts)

○ Device Encryption Policies

○ Require encryption on device

○ Require encryption on storage cards

EXCHANGE ACTIVESYNC Page 16

It is a feature that's built into Microsoft Exchange Server 2010.

Direct Push operates in the following way:

EXCHANGE ACTIVESYNC Page 17

EXCHANGE ACTIVESYNC Page 18

OUTLOOK ANYWHERE Page 19

Users have remote access to Exchange servers from the Internet.

Unauthenticated requests from Outlook can't access Exchange servers.

To enable Outlook Anywhere, follow these steps in order:

Install the Windows RPC over HTTP Proxy component.

OUTLOOK ANYWHERE Page 20

○ Outlook Web App (OWA)

THE CLIENT ACCESS SERVER ROLE Page 21

Otherwise, Exchange functionality can be negatively affected.

THE CLIENT ACCESS SERVER ROLE Page 22

Features in Outlook Web App

OUTLOOK WEB APP Page 25

Exchange Management Shell: Command-line interface.

Registry Editor: editing the registry.

OWA Mailbox Policies

OUTLOOK WEB APP Page 26

Exchange automatically creates at installation the virtual directory autodiscover in IIS

Set-ClientAccessService -Identity "MBX-01" -AutoDiscoverServiceInternalUri

○ Outlook on the web

It is used when the client connects internally

AVAILAVILITY SERVICES Page 30

S-ar putea să vă placă și