Lync2013 introduction and infrastructure preparation roles

Lync2013 deployment series Part1: lync2013 introduction and infrastructure preparation

Preface:
Lync 2013 has been released for a long time. I have been conducting relevant learning and testing. with limited resources, I have installed and deployed the simulated roles, since my work is still very busy, I have not organized the previous deployment into documents until recently for your reference and learning. This series does not involve enterprise speech configuration, I hope you can point out errors and provide suggestions.


The infrastructure preparations are divided into five parts:
1. Introduction to lync2013
2. experiment environment topology Introduction
3. DNS record preparation
4. Configuration File Sharing
5. extended ad Architecture

1. Introduction to lync2013
The following describes the topology change and new functions of lync2013. For details, refer to the official technet documentation.

1. lync version and role Introduction
The main difference between lync server 2013 Enterprise Edition and lync server 2013 Standard Edition is that Standard Edition does not support the high availability feature of Enterprise Edition. To achieve high availability, You need to deploy multiple front-end servers in one pool, and then you can mirror the server that runs SQL Server. With Enterprise Edition, you can select to collocate or define an independent intermediary server. The monitoring server and archiving server can use an independent SQL Server server. Alternatively, you can use the SQL server instance running on the database server for the front-end server and the pool.
The server running lync server 2013 Standard Edition is designed to be used by small organizations and remote locations. The Organization's primary deployment deletes these small organizations and remote locations geographically. The Standard Edition server is designed for the user count of approximately 5000 resident users. You cannot store Standard Edition servers in the pool just like front-end servers in Enterprise Edition. In addition, the SQL Server database used by Standard Edition is a parallel server that runs SQL Server express to handle Standard Edition server workloads. This does not mean that all roles must reside on the Standard Edition server. You can have independent intermediary servers and edge servers. Due to lync server 2013, the SQL Server database stored in the central management must reside on the Standard Edition server, which is the same as the server running SQL Server. The monitoring server and archive server use an independent server that contains the SQL Server database.

2. Standard Edition server roles and collocated
In lync server 2013, A/V conferencing services, mediation services, monitoring and archiving are stored on the Standard Edition server, but additional configuration is required to enable them.
Allows you to combine trusted application servers with Standard Edition servers.
The following server roles must be deployed on a separate computer:
• Controller
• Edge servers
• Intermediary server (if not associated with Standard Edition server)
• Office Web apps Server
• Persistent Chat Server
By default, the SQL Server express backend database is deployed on the Standard Edition server. You cannot move it to a separate computer. You cannot merge other databases on the Standard Edition server.
You can also set each of the following databases on a separate database server:
• Monitoring Database
• Archive database
• Persistent chat Database
• Persistent chat compliance database
• Back-end database of the Enterprise Edition front-end pool
You can combine any or all of the above databases in a single SQL instance, or use a separate SQL instance for each database, but there are the following restrictions:
Each SQL instance can only contain one backend database (used in the Enterprise Edition front-end pool), one monitoring database, one Archiving database, one persistent chat database, and one persistent chat compliance database.

Whether these databases use the same SQL server instance or a separate SQL server instance, the Database Server only supports one Enterprise Edition front-end pool, one Archiving server, one monitoring server, one persistent chat database, and one persistent chat compliance database, but not multiple of them.

3. Enterprise Edition server roles and collocated
In lync server 2013, A/V conferencing services, mediation services, monitoring and archiving are stored on the front-end servers, but additional configuration is required to enable them. If you do not want to deploy the intermediary server and the front-end server together, you can deploy it as an independent intermediary server on a separate computer.
Allows you to combine trusted application servers with front-end servers.
The following server roles must be deployed on different computers:
• Controller
• Edge servers
• Intermediary server (if not associated with the front-end server)
• Office Web apps Server
• Lync server 2013 and persistent Chat Server
You can merge each of the following databases to the same database server:
• Backend database
• Monitoring Database
• Archive database
• Persistent chat Database
• Persistent chat compliance database
Any or all of these databases can be stored in a single SQL server instance, or different SQL Server instances can be used for each database, but the following restrictions apply:
Each SQL server instance can only contain one backend database, one monitoring database, one archived database, one persistent chat database, and one persistent chat compliance database.

Whether these databases use the same SQL server instance or a separate SQL server instance, the database server only supports one front-end pool, one archive deployment, and one monitoring deployment.

5. High Availability
One front-end supports 6660 users, and each pool supports up to 80,000 users, including 12 front-end servers.
The maximum meeting size is 250 users.
Best Practice for pairing a front-end pool: There is no distance between two data centers in the front-end pool to be paired with each other. We recommend that you use two data centers in the same world region because there is a high-speed link between them. It is best to have enough distance between the two data centers to avoid a disaster and simultaneously attack the two data centers.
We recommend that you use the following best matching method in practice:
• The Enterprise Edition pool can only be paired with other Enterprise Edition pools. Similarly, the Standard Edition pool can only be paired with other Standard Edition pools.
• The physical pool can only be paired with other physical pools. Similarly, the virtual pool can only be paired with other virtual pools.
User Experience during pool failure
• If failover is performed on the pool, all users in the affected pool will be forced to log out and log on to the backup pool. The user logging on to the backup pool may be in recovery mode in a short time. In recovery mode, you cannot execute tasks that will cause permanent changes on the lync server (such as adding contacts ). After the Failover is completed, all users can obtain all services from the backup pool.
• When the pool fails, any sessions owned by the user will be interrupted. the user must re-establish these sessions after the Failover to continue.
• Users cannot be reconnected during failover or failover. Users located in the failed pool will be temporarily provided by the backup pool. After the primary pool is restored, the administrator can restore these users to provide services for their original primary pool.
• Note that in lync 2013, the location information server database is not copied to the backup pool. As a best practice, administrators should regularly back up the LIS database and use the latest backup copy to restore the LIS database in the backup pool after failover.
User experience during backend server failure
• If you have configured a witness server, the backend server will automatically and quickly fail over when the subject fails. Active users should not be aware of the interruption of ongoing sessions.
• If the witness server is not configured, it takes some time for the Administrator to manually call the Failover. During this period, the active users may be affected. They will continue normal sessions for about 30 minutes. If the master server is not recovered, or the administrator fails over to the backup server, the user switches to the recovery mode, which means, they cannot execute tasks that require permanent changes to the lync server (such as adding contacts ).
Lync server 2013 does not support SQL cluster Topology
Important:DNS load balancing is not supported for one interface, but Hardware load balancing for another interface. Both interfaces must use hardware load balancing, or both interfaces must use DNS load balancing.
Note: If you use a hardware Load balancer, the server Load balancer deployed in the internal network connection must be configured to only balance the traffic sent to servers that access the edge service and A/V edge service. It cannot balance the load of traffic sent to the internal web conferencing edge service or the internal XMPP proxy service.
Note:Lync server 2013 does not support direct server return (DSR) Nat
Access Edge Services, web conferencing Edge Services, A/V Edge Services, and XMPP proxy services are deployed on the same Edge server. The following servers provide the functions required for external user access and must be deployed as dedicated servers:
• Edge servers
• Controller (optional)
• Reverse Proxy
Important:Reverse Proxy does not need to be dedicated to providing services for lync server 2013 only. For example, you can provide services to publish the lync Server web service and provide published websites for another website that is completely unrelated to the lync server. If there is a reverse proxy server in the peripheral network to support other services, you can use it for lync server 2013.


Ii. experiment environment topology Introduction

The entire topology of this series is as follows:

Two physical servers are used in this test. The Windows Server 2012 operating system is installed and hyper-V is enabled. A total of nine virtual machines are installed, except for the Windows Server 2008 R2 SP1 operating system used by TMG, all others use Windows Server 2012 datacenter.
The deployment process of AD, Ca, and DNS is not introduced in this series. If you have any questions, please refer to other articles. The ad in this test environment is a single-Forest single-domain, enterprise Root CA.

Iii. DNS record preparation
First, create four a Records and one SRV record in DNS to prepare for subsequent deployment:


Iv. Configuration File Sharing
1. We chose to use the front-end server to undertake the file sharing service and configure the permissions.





V. extended ad Architecture
1. Open the lync2013 installation media and click yes to install visual c ++

2. Click the default installation location and click Install.

3. Accept the license

4. Click prepare acitve directory

5. Click Run.

6. Next Step

7. Architecture expansion completed

8. continue to expand the forest

9. Next Step

10. Select the contoso.com domain

11. forest expansion completed

12. continue to expand the domain

13. Next Step

14. Domain expansion completed