Professional Documents
Culture Documents
Contents
Directory Services ....................................................................................................... 6
1.
3.
4.
5.
a)
Messaging ............................................................................................................................ 20
2.2
3.2
3.3
3.4
3.5
3.6
2.
All Exchange roles will be combined. This makes the solution simple, completely
modular that can be expanded brick by brick as needed ........................................ 25
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
3.7.2
3.7.3
3.7.4
Locations. ................................................................................................................................. 26
6.2
7.2
7.3
8.2
11
Appendix ......................................................................................................... 38
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
11.1
11.2
Imp notes: - This Document is prepared on the Basis of RFP requirement and solutions, in each
point the Document is divided into three areas, 1. Role or Service, 2. Current Architecture and
Solution.
Directory Services
1. Overview of Directory Services
A directory service provides the ability to store information about networked devices and
services, and the people who use them, in a central location within a distributed environment. A
directory service also implements the services that make this information available to users,
computers, and applications. Therefore, a directory service is both a directory (the store of this
information) and a set of services that provide the means to securely add, modify, delete, and
locate data in the directory store.
By deploying Windows Server 2012 Active Directory Domain Services (AD DS) in MSTD
environment, MSTD can take the advantage of the centralized, delegated administrative model
and single sign-on (SSO) capability that AD DS provides or MSTD can use the AD DS for the
third party SSO.
MSTD can use Active Directory Domain Services (AD DS) in Windows Server 2012 to simplify
user and resource management while creating scalable, secure, and manageable infrastructures.
You can use AD DS to manage your network infrastructure, including branch office, Microsoft
Exchange Server, and multiple forest environments.
Figure 1 illustrates, the benefits of AD DS and how it acts as the focal point of the Windows
Server 2012 R2 network, demonstrating how it can be used to manage identities and broker
relationships between distributed resources.
a. Improving the Security of the MSTD AD Infrastructure The ability to better defend the
AD infrastructure from exploitation and minimize the risk of information compromise as
documented.
b. Global Logon the ability for any authorized MSTD user to logon to any local MSTD
network (Active Directory forest) connected to the intranet or any Internet application which will
authenticating through AD DS of MSTD (Eg:- SSO)
c. Sharing Active Directory Contact Objects across AD Forests The ability for any
authorized MSTD user to look up and find any other MSTD user natively within the desktop
Outlook client, Outlook Web Access, or authorized mobile device (e.g. Microsoft Mobile
Application).
6. AD Setup
h) The AD Services will be setup on the Virtual Instance of windows 2012 Std. Edition, as a
Single forest, single domain model.
PDC
ADC1
DC Site
ADC2
ADC3
DRC Site
8. Domain Name
Active Directory domains can be identified using a DNS name, which can be the same as an
organization's public domain name, a sub-domain or an alternate version (which may end in
.local). While Group Policy can be applied to an entire domain, it is typical to apply policies to
sub-groups of objects known as organizational units (OUs). All object attributes, such as
usernames, must be unique within a single domain and, by extension, an OU.
A) Current Scenario: - Currently MSTD is using the Domain name as Mahavat.gov.in
with XYZ IP Address provided by ISP.
B) Solution Design : MSTD can use the same Domain for the new infrastructure setup this domain
system will also be used to mailing users. But at the time of implementation, the
new public IP nee to edit in the register DNS.
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
10
MSTD should take a specific down time for the changes of IP address from
existing to new IP address.
9. Domain Controller at Site:When you create the first domain controller in your organization, you are also creating the first
domain, the first forest, the first site, and installing Active Directory. Domain controllers running
Windows Server 2003 store directory data and manage user and domain interactions, including
user logon processes, authentication, and directory searches. Domain controllers are created by
using the Active Directory Installation Wizard.
It is often good practice to put at least one domain controller in each site to enhance network
performance. When users log on to the network, a domain controller must be contacted as part of
the logon process. If clients must connect to a domain controller located in a different site, the
logon process can take a long time. The best network performance is available when the domain
controller at a site is also a global catalog. This way, the server can fulfill queries about objects in
the entire forest. However, enabling many domain controllers as global catalogs can increase the
replication traffic on your network
A) Current Scenario: - MSTD does not have any Domain Controller at both the site.
B) Solution Design:MSTD will deploy the total four Domain Controller in both the site (2 at Each Site),
PDC (primary Data Center) will have two 2 Domain Controller out of which one will
be the Primary Domain and Other one will be the ADC (Additional Domain
Controller), Another Site (DRC) will have 2 Domain controller and both the server
will act as an ADC.
Reason for 2 Domain Controller at each Site: - MSTD will deploy the 2
Domain controller at each site for Disaster Recovery Purpose, If one DC fails the
user will not having any Impact for logon. This will required a zero down time.
10.
When you install Active Directory Domain Services (AD DS), a set of basic Active Directory
features is enabled by default. In addition to the basic Active Directory features on individual
domain controllers, there are new domain-wide and forest-wide Active Directory features
available when all domain controllers in a domain or forest are running a later version of
Windows Server.
A) Current Scenario: - MSTD does not have any Domain.
B) Solution Design: - The Functional level of the Domain will be Windows 2008.
11
11.
During installation of Active Directory on a Windows Server 2000/2003/2008/2012 all FSMO roles
will automatically be installed on the first server. But Best Practice dictates to move some of this
Flexible Single Master of Operation (FSMO) roles to separate servers
12.
Active Directory Sites and Services is a Microsoft Management Console (MMC) snap-in that you can
use to administer the replication of directory data among all sites in an Active Directory Domain
Services (AD DS) forest. This snap-in also provides a view of the service-specific objects that are
published in AD DS.
Administrators who are responsible for forest-wide service administration can use Active Directory
Sites and Services to manage the intersite replication topology for the forest. Administrators who
are responsible for application services can be delegated responsibility for the service containers
into which application-specific objects are published
13.
AD Global Catalog.
The global catalog is a distributed data repository that contains a searchable, partial
representation of every object in every domain in a multidomain Active Directory Domain
Services (AD DS) forest. The global catalog is stored on domain controllers that have been
designated as global catalog servers and is distributed through multimaster replication. Searches
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
12
that are directed to the global catalog are faster because they do not involve referrals to different
domain controllers.
The global catalog provides the ability to locate objects from any domain without having to know
the domain name. A global catalog server is a domain controller that, in addition to its full,
writable domain directory partition replica, also stores a partial, read-only replica of all other
domain directory partitions in the forest. The additional domain directory partitions are partial
because only a limited set of attributes is included for each object. By including only the
attributes that are most used for searching, every object in every domain in even the largest forest
can be represented in the database of a single global catalog server.
Benefit for the GC Services.
14.
The replication topology of Active Directory directory service provides the network of connections
between domain controllers in a forest according to their location in Active Directory sites. A site is
an Active Directory object that you create and configure to represent an area of good network
connectivity, typically corresponding to a local area network (LAN). The site object is associated with
a set of one or more subnets, which are objects that identify a range of IP addresses. Each domain
controller has an IP address that maps to a subnet, and that mapping in turn identifies the site of the
domain controller. By recognizing domain controllers according to site locations, the replication
system ensures that each domain controller is updated with directory changes in the most efficient
and timely manner possible, given network conditions and directory service configuration. The
replication topology is generated automatically at regular intervals to accommodate network and
configuration changes, and is designed to ensure that all domain controllers are connected without
redundancy and with minimum cost.
13
A) Current Scenario: - MSTD does not have any site currently so no current replication
tropology is present.
B) Solution Design: - Two Site replication will happen as per the below Map.
15.
AD DNS.
Domain Name System (DNS) is a system for naming computers and network services that is
organized into a hierarchy of domains. DNS naming is used in TCP/IP networks, such as the
Internet, to locate computers and services with user-friendly names. When a user enters a
DNS name in an application, DNS services can resolve the name to other information that is
associated with the name, such as an IP address.
For example, most users prefer a friendly name, such as corp.contoso.com, to locate a
computer, such as a mail server or Web server, on a network. A friendly name can be easier
to learn and remember. However, computers communicate over a network by using numeric
addresses. To make the use of network resources easier, name systems such as DNS provide
a way to map the user-friendly name for a computer or service to its numeric address.
The DNS Server role in Windows Server 2012 combines support for standard DNS protocols
with the benefits of integration with Active Directory Domain Services (AD DS) and other
Windows networking and security features, including such advanced capabilities as secure
dynamic update of DNS resource records
14
16.
AD Schema.
Active Directory Schema is a Microsoft Management Console (MMC) snap-in that you can use to
view and manage the Active Directory Domain Services (AD DS) schema.
Current Scenario: - MSTD does not have any Domain.
Solution Design: - By default Schema will be installed with AD Directory
Services enabled, But due to Exchange 2013 in the MSTD infrastructure going to
deployed, Administration team need upgrade the Schema. This Schema will be
upgraded at the time of First Exchange Instance installation with the below help
command line.
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
17.
Group Policy is an infrastructure that allows you to specify managed configurations for users and
computers through Group Policy settings and Group Policy Preferences. You can manage Group
Policy settings and Group Policy Preferences in an Active Directory Domain Services (AD DS)
environment through the Group Policy Management Console (GPMC). By using Group Policy, you
can significantly reduce our organizations total cost of ownership. Various factors, such as the large
number of policy settings available, the interaction between multiple policies, and inheritance
options, can make Group Policy design complex.
Current Scenario: - MSTD does not have any group policy.
Solution Design: - AD administrator will configure the all the new Group Policys
through (GPMC) tool which will done after the basic installation of AD services.
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
15
MSTD Management needs to discuss and Finalize the changes which is require to do
through GP.
Below is some of the application or services which we can controller through GP.
(lockout policy , screen saver settings , logon scripts publishing , folder shares allotment ,
populate desktop icons ,assign printers , to limit Internet explorer options as a result of
Managed Administrative Templates, USB disabled , Delegation Rights)
18.
AD DHCP.
Dynamic Host Configuration Protocol (DHCP) is a client-server technology that allows DHCP servers
to assign, or lease, IP addresses to computers and other devices that are enabled as DHCP clients.
When DHCP servers are deployed on our network, we can automatically provide client computers
and other TCP/IPv4 and IPv6 based network devices with valid IP addresses.
Current Scenario: - MSTD does not have any DHCP configure in any AD.
Solution Design: - AS per the new Infrastructure of PDC and DRC currently
there is no requirement of DHCP Services, But if Changes required by MSTD
management, AD administrator will enabled the DHCP services on PDC and
create the Scope as per network Subnet.
19.
AD OU Structure.
After domain planning is complete, an OU structure can be designed. In the best practices
OU model, departments within the domain manage their internal operations, while the
domain's IT staff manages the overall infrastructure. In other words, each department
manages its objects in the directory, while the domain IT staff manages the configuration of
the directory service itself.
Best practices for creating an OU design introduces the role of "OU owner." The Active
Directory OU owner is comparable to most Windows 2012 domain administrators. This
means that domain administrators who manage users and resources in a Windows 2012
domain will manage the same resources in an Active Directory domain, but will be owners of
OUs.
Expect to make periodic changes to your OU structure to reflect changes in your
administrative structure and to support policy-based administration. OUs are designed to be
easily changed.
OUs are containers within domains that can contain other OUs, users, groups, computers, and
other objects. These OUs and sub-OUs form a hierarchical structure within a domain, and are
primarily used to group objects for management purposes
Current Scenario: - MSTD does not have any OU structure. Below is the eg :- of
one location of MSTD .
16
17
20.
You use Active Directory Users and Computers to manage recipients. Active Directory Users and
Computers is an MMC snap-in that is a standard part of Microsoft Windows Server operating
systems. However, when you install Exchange 2013, the setup wizard automatically extends the
functionality of Active Directory Users and Computers to include Exchange-specific tasks
You can use Active Directory Users and Computers to create new user accounts or manage existing
user accounts. Below is some of the example for which we can use AD User and Computer Snap-in
i)
j)
k)
l)
m)
n)
o)
p)
q)
r)
21.
Windows Server 2012 Hyper-V also introduces VM-Generation ID (VMGenID). VMGenID provides a
way for the hypervisor to communicate to the guest OS when significant changes have occurred. For
example, the hypervisor can communicate to a virtualized DC that a restore from snapshot has
occurred (Hyper-V snapshot restore technology, not backup restore). AD DS in Windows Server 2012
is aware of VMGenID VM technology and uses it to detect when hypervisor operations are
performed, such as snapshot restore, which allows it to better protect itself.
Hyper-v Failover.
When a Hyper-V replica failover occurs (planned or unplanned), the Windows Server 2012
virtualized DC detects a VMGenID reset, triggering the aforementioned safety features. Active
Directory operations then proceed as normal. The replica VM runs in place of the primary VM.
18
22.
Messaging
1
19
Day to day Management of mail messaging Servers and the related servers, storage, backup and security
systems such as
20
Technical Requirements
Below are the business and functional requirements that the target messaging system
should meet as understood at this stage. These requirements will be mapped to different
solution areas throughout the proposal document.
2.1
Messaging
Below is the Current users count and Mail box Size limit which is provided in RFP. As per MSTD users
count trend will increase every month wise.
Requirement
Exchange Version
Total Number
users (9842)
Details
2013
of
Primary
mailbox
quota in GB
4 GB (1075) and 2 GB
(8767)
Archive size in GB
4 GB (1075) and 2 GB
(8767)
Designation
1
1
1
9
72
401
590
1191
4726
2850
9842
Designation
4 GB
4 GB
4 GB
2 GB
2 GB
2 GB
Designation
4 GB
4 GB
4 GB
2 GB
21
2.2
2 GB
2 GB
50 (Assumption)
75 (Assumption)
Yes
Yes
Physical Load balancer to be deployed for mail flow.
Outlook Web access , POP & IMAP access
Outlook anywhere for internal as well as external users
Outlook (2007 and higher) & Active-Sync
Unified Communication
Instant Messaging: Instant messaging service (real-time interaction) should be provided to all the
Department users to facilitate inter and intra office communication.
Voice and Video Chat: The Voice and Video chat feature should allow the officers of the Department
to communicate with each other using live chat, video conferencing and real-time content sharing
(documents, presentations, images, etc.) This feature will be allowed for Deputy Commissioners and
above. Inter-office video conferencing facility will be enabled only during department mandated
time-slots for optimal utilization of the WAN. Intra-office video conferencing will be permissible
throughout the day over the LAN.
Current Scenario :- MSTD does not having any standard Unified Communication
device
Solution Design: - Infrastructure Team is going to deploy the New Communication Lync
Server through which below specified designation users will get the facility of unified
communication as per RFP.
Designation
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
No
No
No
No
22
3
3.1
Enable
Availability
Continues
Simplify Administration
Collaborate Effectively
E-mail Archiving
23
3.2
Purpose
The Client Access server in Exchange 2013 functions much like a front door,
admitting all client requests and routing them to the correct active Mailbox
database. The Client Access server provides network security functionality
such as Secure Sockets Layer (SSL) and client authentication, and manages
client connections through redirection and proxy functionality. The Client
Access server authenticates client connections and, in most cases, will proxy
a request to the Mailbox server that houses the currently active copy of the
database that contains the user's mailbox. The Client Access server provides
authentication, limited redirection, and proxy services, and offers all the
usual client access protocols: HTTP, POP and IMAP, and SMTP. The Client
Access server, a thin and stateless server, doesnt do any data rendering.
Theres never anything queued or stored on the Client Access server
Mailbox server
The Mailbox server includes all the traditional server components found in
Exchange 2010: the Client Access protocols, the Transport service, the
Mailbox databases, and Unified Messaging (the Client Access server redirects
SIP traffic generated from incoming calls to the Mailbox server). The Mailbox
server handles all activity for the active mailboxes on that server.
24
Current Scenario: - MSTD does not having any In house Mailing system which can
manage by MSTD administrator team.
Solution Design: - Exchange Administrator will install both the roles on 2 Virtual
Exchange 2013 Instance in both the location and addition one Mailbox Role virtual
Instance in one more server in both the location for the High Database Aviability.
Total 6 Virtual Exchange 2013 Enterprise Edition instance will be install (3 at PDC and 3
at DRC). This 6 Virtual Instance will Install in 6 different HOST (HP BL660 gen8
Server).
Exchange 2013 Server Editions
Exchange Server 2013 comes with Standard and Enterprise editions. The Standard Edition is usually
targeted for small deployments or distributed branch servers. The Enterprise Edition, on the other
hand, addresses large and complex requirements of enterprise customers.
The table below compares the features of the two editions:
Edition
Available Features
Design Recommendation :- Keeping the future scalability in mind, Exchange 2013 Enterprise edition
need to be deployed in MSTD with maximum features utilization as per RFP.
3.3
Design Recommendation: - The recommendation is for MSTD to use Windows 2012 Standard
edition for all Exchange 2013 server roles.
3.4
25
The Active Directory driver is the core Microsoft Exchange component that allows Exchange services
to create, modify, delete, and query for Active Directory Domain Services (AD DS) data. In Exchange
2013, all access to Active Directory is done using the Active Directory driver itself. Previously, in
Exchange 2010, DSAccess provided directory lookup services for components such as SMTP,
message transfer agent (MTA), and the Exchange store.
The Active Directory driver also uses Microsoft Exchange Active Directory Topology
(MSExchangeADTopology), which allows the Active Directory driver to use Directory Service Access
(DSAccess) topology data. This data includes the list of available domain controllers and global
catalog servers available to handle Exchange requests
Exchange 2013 relies on Active Directory services for user authentication, permissions management,
and directory information. As a deployment prerequisite, make sure that the functional level of your
forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003
with Service Pack 2 or later. Although 32-bit global catalog servers are supported, 64-bit servers
should be considered for large environments e.g. more than 20,000 Active Directory objects. 64 bit
DCs / GCs also offer a higher consolidation ratio.
Design Recommendation: - Windows Server 2012 R2 Domain Controllers / Global Catalogs are
Recommended at two datacenter.
3.5
3.6
26
3.6.1
The following are the Design Assumptions for the target messaging solution:
3.6.2
The completed mailbox role requirements calculator is attached below. A detailed description of the
Design Outputs follows.
MSTD_ExchangeCalcu
lator.xlsm
3.6.3
The core minimum Bill of Material / Bill of Quotes for the Exchange 2013 solution is summarized
from the previous sections in the table below.
Exchange
2013 Server
Edition
9842
Enterprise
Edition
3.6.4
Number
of
Servers
Configuration
Comments
Windows 2012
R2 STD
8 Core CPU
with 96
GB of RAM
Windows 2012
R2 STD edition
2X8, 16 GB of
RAM
Operating
System Edition
Locations.
27
5. Design Components
The primary messaging solution is to deploy new Exchange 2013 environment that spans MSTD
physical data center locations.
Costs of Ownership
Technological engineering quality
Scalability
Fault Tolerance / Reliability
Industry best practices
Supportability
Ease of administration
Compatibility with existing systems
Reliability
Vendor specifications
28
It is with Remote replication capability that is used to periodically replicate same volume is
protected on two arrays, from the Primary DC Site (PDC Mumbai) to the NDR Site (SDC Mumbai)
synchronously and Primary DC Site (PDC Mumbai) to DR Site (DRC) Asynchronously.
3PAR Remote Copy, based on 3PARs Thin Copy technology, it allows remote storage capacity to be
sized for the written data versus the approach used with traditional architectures, which size remote
storage for allocated (but unwritten) capacity. Implemented natively over IP or Fibre Channel with
only a handful of simple, intuitive commands, 3PAR Remote Copy can be configured, managed, and
tested in a matter of minutes.
29
Web gateway security that protects against web threats, including malicious software,
spyware, botnets, viruses, and malware.
Rapid data and system recovery recovers individual files and folders in seconds or complete
Windows systems in minutes to dissimilar hardware or virtual environments
6.1
Front End Pools are also the primary store for user and conference data. Information about each
user is replicated among three Front End Servers in the pool, and backed up on the Back End Servers.
Additionally, one Front End pool in the deployment also runs the Central Management Server, which
manages and deploys basic configuration data to all servers running Lync Server. The Central
Management Server also provides Lync Server Management Shell and file transfer capabilities.
The Back End Servers are database servers running Microsoft SQL Server that provide the database
services for the Front End pool. The Back End Servers serve as backup stores for the pools user and
RFP Supporting Solution Doc for MSTD, Version 0. 3 Draft
Prepared by Surinder Pal Singh
30
conference data, and are the primary stores for other databases such as the Response Group
database. You can have a single Back End Server, but a solution that uses SQL Server mirroring is
recommended for failover. Back End Servers do not run any Lync Server software.
You may choose to deploy SQL mirroring with or without a witness. We recommend using a witness
because it enables failover of the Back End Server to be automatic. Otherwise, an administrator
must manually invoke failover. Note that even if a witness is deployed, an administrator can
manually invoke Back End Server failover, if necessary.
Design Recommendation: - 2 SQL servers should be used at MSTD with SQL mirroring as HA
6.2
Edge Server
Edge Server enables end 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 Skype, AOL and Google Talk.
Deploying Edge Server also enables mobility services, together with a reverse proxy, which supports
Lync functionality on mobile devices. Users can use supported Apple iOS, Android, Windows Phone,
or Nokia mobile devices to perform activities such as sending and receiving instant messages,
viewing contacts, and viewing presence. In addition, mobile devices support some Enterprise Voice
features, such as click to join a conference, Call via Work, single number reach, voice mail, missed
calls and VOIP calls over WiFi. The mobility feature also supports push notifications for mobile
devices that do not support applications running in the background. A push notification is a
notification that is sent to a mobile device about an event that occurs while a mobile application is
inactive.
Edge Servers also include a fully-integrated Extensible Messaging and Presence Protocol (XMPP)
proxy, with an XMPP gateway included on Front End Servers. You can configure these XMPP
components to enable your Lync Server 2013 users to add contacts from XMPP-based partners (such
as Google Talk) for instant messaging and presence.
Design Recommendation: 2 Edge Server will be implemented at MSTD in HA mode for External
connectivity and for access from Mobile devices
31
TELCO / ISP
INTERNET
Router
Router
Reverse Proxy
Firewalls
Firewalls
Reverse Proxy
Perimeter Network
Perimeter Network
Firewalls
Exchange Edge Servers
Firewalls
SAS
SAS
Front End
Front End
SQL Server
SQL Cluster
(mirroring) with
SQL Witness
SQL Cluster
(mirroring) with
SQL Witness
Front End
Front End
Front End
Front End
Pool 2
Pool 1
Front-End
Front-End
DAG
DAG
Directory Servers
Storage
Directory Servers
Storage
File Share
The Backup Service is a feature in Lync Server 2013, designed to support the disaster recovery
solution. It is installed on a Front End pool when you pair the pool with another Front End pool.
If the pool in one site fails, users can be failed over from that pool to the pool in the other site, which
then provides services to all the users in both pools. For capacity planning purposes, each pool will
be designed to handle the workloads of all users in both pools in the event of a disaster.
32
In addition to providing disaster recovery ability, two paired pools serve as the backup Registrars for
each other. In Lync Server 2013, backup Registrar relationships between Front End pools are always
1:1 and reciprocal. This means that if P1 is the backup for P2, then P2 must be the backup for P1, and
neither can be the backup for any other Front End pool. This is a change from Lync Server 2010, in
which Front End pool backup relationships could be many to one.
Even though backup relationships between two Front End pools must be 1:1 and symmetrical, each
Front End pool can still also be the backup registrar for any number of Survivable Branch Appliances
7.1
7.2
33
whichever comes first. When the user logs back in, they will log in to the backup pool. If they log in
before the failover has completed, they will be in Resiliency mode until failover is complete. Only
then the user is able to establish new sessions or re-establish previous sessions.
During failback
User can sign in to the home pool in Resiliency User can sign in to the original home pool
mode.
in regular mode.
Scheduling or modifying
scheduled
meetings, Not possible while user is in Resiliency mode.
creating ad-hoc conferences
Available
Available
User Experience for a User Homed in an Unaffected Pool during Failback of another Pool
34
User task
During failback
Viewing
presence
affected user
of Shows the last presence state set by the Working. Unaffected users see updates made
affected user.
by affected users.
Ongoing
conferences
All modalities of conference are terminated.
organized by affected user
Ongoing
organized
user
by
conferences Conference continues, and affected user can Conference continues, and affected user can
unaffected stay in the conference and all modalities stay in the conference and all modalities
work.
work.
7.3
Available
35
8
8.1
8.2
36
37
TELCO / ISP
INTERNET
Router
Router
Reverse Proxy
Firewalls
Firewalls
Reverse Proxy
Firewalls
SAS
SAS
Front End
Front End
SQL Server
SQL Cluster
(mirroring) with
SQL Witness
SQL Cluster
(mirroring) with
SQL Witness
Front End
Front End
Front End
Front End
Pool 2
Pool 1
Front-End
Front-End
DAG
DAG
Directory Servers
Storage
Directory Servers
Storage
File Share
Perimeter Network
Perimeter Network
Firewalls
Exchange Edge Servers
38
11 Appendix
11.1 Microsoft Product Mapping
S.No
MS Solution mapping
Messaging
Active Directory
Operating System
Non
Functional Recommended
Solution Specific comment
Characteristic
Technical capability
Scalability
Private Cloud
High availability
Monitoring
SCOM
Disaster recovery
Application Level
Multi Tenancy
NA
NA
Scale Unit