PROJECT HOMEWORK 3

1.

What are differences between Exchange 2007/2010/2013

2007
2010
2013
5 SERVER roles
5 server roles
Cut down roles
Exchange Management Shell, EMC Console & Public Folder Management Console
2007
High Availability for Mailbox(LCR, SCR, CCR and SCC) and Hub server 2007
In 2010, there was DAG, RBAC, CAS Array, EMC, Archive mailbox, Mail tips,
Moderated delivery,
In 2013, EAC, OWA Offline Access and App, DAG-Auto reseed and Managed Store,
Data Loss Policy and Policy tips, Load Balancing CAS, No CAS Array, All clients
connect through RPC-over-Https, Exchange Workload Management, Anti-Malware
scanning

2. What are CCR, LCR, and SCR?

LCR is a single-server solution that uses built-in asynchronous log shipping

technology to create and maintain a copy of a storage group on a second set of disks
that are connected to the same server as the production storage group. LCR provides
log shipping, log replay, and a quick manual switch to a secondary copy of the data.
CCR, which is a non-shared storage failover cluster solution, is one of two types of
clustered mailbox server (CMS) deployments available in Exchange 2007. CCR is a
clustered solution (referred to as a CCR environment) that uses built-in asynchronous
log shipping technology to create and maintain a copy of each storage group on a
second server in a failover cluster. CCR is designed to be either a one or two data
center solution, providing both high availability and site resilience.
SCR is a new feature introduced in Exchange 2007 SP1. As its name implies, SCR is
designed for scenarios that use or enable the use of standby recovery servers. SCR
extends the existing continuous replication features and enables new data availability
scenarios for Exchange 2007 Mailbox servers. SCR uses the same log shipping and
replay technology used by LCR and CCR to provide added deployment options and
configurations by providing the administrator with the ability to create additional
storage group copies.

3. What is DAG?
A database availability group (DAG) is the base component of the Mailbox
server high availability and site resilience framework built into Microsoft
Exchange Server 2013. A DAG is a group of up to 16 Mailbox servers that
hosts a set of databases and provides automatic database-level recovery
from failures that affect individual servers or databases.
A DAG is a boundary for mailbox database replication, database and server
switchovers and failovers, and an internal component called Active Manager.
Active Manager, which runs on every Mailbox server, manages switchovers
and failovers within DAGs.
Any server in a DAG can host a copy of a mailbox database from any other
server in the DAG. When a server is added to a DAG, it works with the other
servers in the DAG to provide automatic recovery from failures that affect
mailbox databases, such as a disk, server, or network failure.
Scenario: I have two sites with active users in both sites, one site with a cas array and 2
mailbox servers, another site with a cas array and 4 mailbox servers (site 1 and 2). How does
cross site failover work if site 2 goes down and how do you recover?

4. What is a CAS Array?

A Client Access array is, as the name implies, an array of CAS servers. More
specifically, it is an array consisting of all the CAS servers in the Active
Directory site where the array is created. So instead of connecting to a FQDN
of a CAS server, an Outlook client can connect to the FQDN of the CAS array
(such as outlook.domain.com). This makes sure Outlook clients connecting
via MAPI are connected all the time even during mailbox database fail and
switch-overs
5. How would you set one up?
6. What is log shipping?
You can use log shipping to send transaction logs from one database (the primary
database) to another (the secondary database) on a constant basis. Continually
backing up the transaction logs from a primary database and then copying and
restoring them to a secondary database keeps the secondary database nearly
synchronized with the primary database.

7. What are transaction logs?

The transaction log is a serial record of all modifications that have occurred in the
database as well as the transaction that performed each modification. The
transaction log records the start of each transaction. It records the changes to the
data and enough information to undo the modifications (if necessary later) made
during each transaction

8. How do you initiate a switchover with DAG?

9. What is the transport dumpster?
Transport dumpster is a feature built into Exchange Server 2010 HUB transport role
and designed to minimize data loss during mail delivery to a DAG in a lossy failover
scenario.

10.
What is shadow redundancy?
A transport server feature that provides redundancy for messages for the
entire time they're in transit.
11.
What is the safety net?
Formerly known as transport dumpster, this is a feature of the transport
service that stores a copy of all messages for X days. The default setting is 2
days.
12.
What is quorum?
Quorum represents a shared view of members and resources, and the term quorum is
also used to describe the physical data that represents the configuration within the
cluster that's shared between all cluster members. As a result, all DAGs require their
underlying failover cluster to have quorum. If the cluster loses quorum, all DAG
operations terminate and all mounted databases hosted in the DAG dismount. In this
event, administrator intervention is required to correct the quorum problem and
restore DAG operations.

13.
What is the importance of a file share witness?
A FSW is simply a file share that you may create on a completely separate server
from the cluster to act like a disk for tie-breaker scenarios when quorum needs to be
established. The share could reside on a file server, domain controller, or even a
completely different cluster. A witness share needs to be available for a single
connection, and available for all nodes of the cluster to be able to connect to if you
are using the FSW option for quorum. The purpose of the FSW is to have something
else that can count as a vote in situations where the number of configured nodes

isnt quite enough for determining quorum. A FSW is more likely to be used in multisite clusters or where there is no common storage. A FSW does not store cluster
configuration data like a disk. It does, however, contain information about which
version of the cluster configuration database is most recent. Other than that, the FSW
is just a share. Resources cannot fail to it, nor can the share act as a communications
hub or alternate brain to make decisions in the event cluster nodes cannot
communicate.

14.

What are PAM and SAM?

Primary Active Manager and Standby Active Manager

On servers that are members of a DAG, there are two Active Manager
Roles: Primary Active Manager (PAM) and Standby Active Manager (SAM)
PAM is the Active Manager role in a DAG that decides which copies will be
active and passive. PAM is responsible for getting topology change
notifications and reacting to server failures.
The SAM detects failures of local databases and the local Information Store. It
reacts to failures by asking the PAM to initiate a failover (if the database is
replicated).
15.
What is managed availability?
With managed availability, internal monitoring and recovery-oriented features
are tightly integrated to help prevent failures, proactively restore services,
and initiate server failovers automatically or alert administrators to take
action. The focus is on monitoring and managing the end-user experience
rather than just server and component uptime to help keep the service
continuously available.
16.
How does Exchange 2013 provide increased database failure prevention as opposed to

exchange 2010 that used the information store service?

Data Loss Prevention; this is a system designed to detect a potential data breach/leakage incident in a
timely manner and prevent it. When this happens, sensitive data such as personal/company information,
credit card details, social security numbers, etc., is disclosed to unauthorized users either with malicious
intent or by mistake.

17.
What are the server roles in Lync 2010?
Front End, Back End, A/V Conferencing, Mediation, Monitoring, Archiving,
Director, Edge
18.
What are these roles responsible for?

Front End User authentication and registration

Presence information and contact card exchange

Address book services and distribution list expansion

IM functionality, including multiparty IM conferences

Web conferencing and application sharing (if deployed)

Application hosting services, for both applications included with Lync Server (for
example, Conferencing Attendant and Response Group application) and third-party
applications

Back End; Host SQL databases for Front End

Central Management Store (CMS)

Pool Configuration Store

Application Store

A/V Conferencing Provides A/V conferencing functionality to your deployment.

It can be collocated with Front End Server, or deployed separately as a single server
or A/V Conferencing Server pool

Mediation; A necessary component for implementing Enterprise Voice and dial-in

conferencing.

Mediation Server translates signaling and, in some configurations, media between

your internal Lync Server infrastructure and a public switched telephone network
(PSTN) gateway, IP-PBX, or a Session Initiation Protocol (SIP) trunk.

Monitoring; collects data about the quality of your network media, in both
Enterprise Voice calls and A/V conferences.

This information can help you provide the best possible media experience for your
users.

It also collects call error records (CERs), which you can use to troubleshoot failed
calls. Additionally, it collects usage information in the form of call detail records
(CDRs) about various Lync Server features so that you can calculate return on
investment of your deployment, and plan the future growth of your deployment.

Archiving; enables you to archive IM communications and meeting content for

compliance reasons.

If you do not have legal compliance concerns, you do not need to deploy Archiving
Server

Director; Can authenticate Lync Server user requests, but do not home user
accounts, or provide presence or conferencing services.

Directors are most useful in deployments that enable external user access, where the
Director can authenticate requests before sending them on to internal servers.

Directors can also improve performance in organizations with multiple Front End
pools

Edge; Enables your users to communicate and collaborate with users outside the
organizations firewalls.

These external users can include the organizations own users who are currently
working offsite, users from federated partner organizations, and outside users who
have been invited to join conferences hosted on your Lync Server deployment.

Edge Server also enables connectivity to public IM connectivity services, including

Windows Live, AOL, and Yahoo!.

19.

What are the HA features in Lync 2010?

Lync Server 2013 supports mirroring of your Back End Servers for high
availability. You can use Topology Builder to set up mirroring, including
setting up a witness.

Server redundancy through multiple servers in a pool

Support for mirroring to improve Back End Server high availability

Topology Builder supports SQL Server Mirroring

Pool Pairing in geographically-dispersed sites for disaster recovery

POOL PAIRING

For disaster recovery, designate pairs of Front End pools across

geographically dispersed sites. Each site contains a Front End pool which is
paired with a corresponding Front End pool in another site. Both pools in a
pair are active, and the new Lync Server Backup Service replicates data to
keep the pools synchronized

There is no restriction on the distance between two data centers that have
paired pools. Recommendation is to use two data centers with high-speed
links between them

Each pool in a pair should have the capacity to serve all users from both
pools in the event of a disaster

The solution also supports the Central Management Store. If one pool in a
pair contains the Central Management Store, a backup Central Management
store database is created in the backup pool, and Central Management
store services are installed in both pools. At any point in time, one of the
two Central Management store databases is the active master, and the
other is a standby. The content is replicated from the active master to the
standby by the Backup Service

20.

What about the server roles in Lync 2013?

Server Role Consolidation

AV Conferencing, Monitoring and Archiving roles collocated on

Front End

Mediation can be collocated on Front End

Director optional

XMPP functionality built-in to Front End and Edge

Integrated Persistent Chat

In Lync Server 2013, A/V Conferencing service, Mediation service, Monitoring, and
Archiving are collocated on the Front End Server, but additional configuration is
required to enable them. If you do not want to collocate the Mediation Server with
the Front End Server, you can deploy it as a stand-alone Mediation Server on a
separate computer. You can collocate a trusted application server with the Front
End Server.
The following server roles must each be deployed on a separate computer:

Director(optional)

Edge Server

Mediation Server (if not collocated with the Front End Server)

Office Web Apps Server

Extensible Messaging and Presence Protocol (XMPP)

Lync Server 2013 introduces a fully integrated XMPP proxy (deployed on the Edge
Servers) and an XMPP gateway deployed on your Front End Servers. You can
deploy XMPP federation as an optional component. Adding and configuring the
XMPP proxy and XMPP gateway will allow your Microsoft Lync 2013 users to add
contacts from XMPP-based partners for instant messaging (IM) and presence.

21.

What are the differences in Lync 2013 and 2010?

The architecture of front end pools has been changed compared to

Lync 2010

The back end database in Lync 2013 is no longer the real-time data
store in the Lync pool

To avert the single point of failure of the Back-end, most Lync data
now are stored on the Front End Server to enhance the performance
and scalability of the Lync architecture

Front end server in Lync 2013 handles more resources and

information like contacts, presence and conferencing details, etc.
while back end server provides the overall persistent storage of this
data

A/V conferencing is now handled by the front end server

There are no longer separate monitoring server or archiving server

roles in Lync 2013, as of now it is handled by Front End Server

It requires additional computational resources on the front end

server when running video conferencing

22.
How does a client connect in Lync 2013?
By default, Lync client applications can use any port between ports 1024 and 65535
when involved in a communication session; this is because specific port ranges are
not automatically enabled for clients. In order to use Quality of Service, however, you
will need to reassign the various traffic types (audio, video, media, application
sharing, and file transfer) to a series of unique port ranges. This can be done by using
the Set-CsConferencingConfiguration cmdlet.

23.
What port is used for client connections?
TCP 53 Lync DNS query
TCP 5061 Lync clients inside a corporate network
TCP 5063 - Used for incoming SIP requests for Audio/Video conferencing.
TCP 443 Used by Lync clients outside a corporate network or all Lync Online clients
UDP 3478 This port is used for STUN (Session Traversal Utilities for NAT) messages. Lync
clients initiate STUN connectivity check prior to media transmission. Once STUN connectivity
check is succeeded, media transmission happens.
UDP 50000 65000 typical port range used for RTP can be set to a specific port range
on the Lync server
24.
What is the high port range designated for?

CLIENT TRAFFIC TYPE

AUDIO
VIDEO
APPLICATION SHARING
FILE TRANSER

PORT START
50020
58000
42000
42020

In the above table, client port ranges represent a subset of the port ranges configured for
your servers. For example, on the servers, application sharing was configured to use ports

40803 through 49151; on the client computers, application sharing is configured to use ports
42000 through 42019. This, too is done primarily to make administration of QoS easier:
client ports do not have to represent a subset of the ports used on the server

25.

What components are needed for enterprise voice in Lync?

ENTERPRISE VOICE; With Enterprise Voice, Lync Server delivers a stand-alone Voice
over Internet Protocol (VoIP) offering to enhance or replace traditional private branch
exchange (PBX) systems. Enterprise Voice users can call colleagues on your
organizations VoIP network or PBX, and they can call traditional phone numbers
outside your organization. The Enterprise Voice solution includes common calling
features such as answer, forward, transfer, hold, divert, release and park, and
Enhanced 9-1-1

CALL POLICIES; Lync Server 2013 provides mobility policies that determine who can
use mobility features, Call via Work, voice over IP (VoIP) or video, and whether WiFi
will be required for either VoIP or video. The Call via Work feature enables a mobile
user to make and receive calls on a mobile phone by using a work phone number
instead of the mobile phone number. This feature prevents the called party from
seeing the caller's mobile phone number and enables a user to avoid outbound
calling charges. Configuring VoIP and video makes it possible for users to receive and
make VoIP calls and video.

CALL ROUTING; Outbound call routing applies to calls that are destined for a public
switched telephone network (PSTN) gateway, trunk, or private branch exchange
(PBX). When a user places a call, the server normalizes the phone number to E.164
format, if necessary, and attempts to match it to a SIP URI. If the server cannot make
the match, it applies outbound call routing logic based on the supplied dial string.

NORMALIZATION; Normalization rules define how phone numbers expressed in

various formats are to be routed for each specified location, user, or contact object.
The same dial string may be interpreted and translated differently, depending on the
location from which it is dialed and the person or contact object that makes the call.
A set of normalization rules associated with a particular location constitutes a dial
plan

26.

What is windows Fabric

a. Windows Fabric is responsible for distributing the Primary and

Secondary roles for each RoutingGroupId among FEs
b. Windows Fabric provides the messaging infrastructure to replicate
data from primary to secondaries
c. Windows Fabric provides high availability by monitoring the health of
the Front Ends and moving role allocation to healthy FEs in case of a
node failure
d. Windows Fabric guarantees a maximum of one owner for the data

27.
What is STUN/TURN/ICE
STUN, TURN, and ICE are a set of IETF standard protocols for negotiating traversing
NATs when establishing peer-to-peer communication sessions. WebRTC and other
VoIP stacks implement support for ICE to improve the reliability of IP
communications.