LYNCSERVER2013 Deployment _ System Requirements (normalization test is Project)

LYNCSERVER2013 Deployment System Requirements--lyncserver have to understand some basic knowledge

system Requirements fall into the following categories:

1. System requirements for running the LyncServer2013 server

2. Install and manage required Administrator privileges

3. System requirements for SQL Server

4. System Requirements for management tools

5. DNS requirements (a record and SRV record)

===lyncserver Deployment Overview

Lyncserver is divided into standard and Enterprise editions, the only difference is that the standard is not supported by the enterprise high availability. Enterprise High-availability implementations require multiple front-end servers to be deployed to a single pool, and the backend uses SQL mirroring to make the database highly available, with up to 12 front-end servers in the pool. Standard version for small companies or branch offices, the database uses the SQLExpress version, if the branch office does not want to deploy Lyncserver can also, AudioCodes has a solution for Microsoft Lyncserver SBA Branch self-survival. This is a small knowledge of science!

= = = System requirements for running the LyncServer2013 server

First of all, the Lyncserver Standard Edition and Enterprise Edition hardware and software requirements are the same, Lync Standard Edition Server two can support up to 5000 users, Enterprise Edition each pool is about 80000 users
LYNCSERVER2013 only supports 64-bit hardware and 64-bit windowsserver operating system
Operating System Requirements:

Windows Server R2 sp1& the latest Server Pack (Server08 cannot use Powershell3.0 by default, you need to install. Net Framework4.5 First)

Windows Server 2012

Windows Server2012 R2

= = = Administrator privileges required for installation and management

Setup.exe – The executable file that is used to start the Lync Server 2013 Administration Tool installation

Deploy.exe –deploy.exe is called by Setup.exe and is responsible for deploying software components for server roles

Bootstrapper.exe –bootstrapper.exe is called by Setup.exe and is responsible for deploying and configuring server Roles

Topologybuilder – Responsible for providing a wizard-style user interface for creating, viewing, and validating Lync Server 2013 topologies

All of these require local administrator permissions on the operating server, and project implementation will first join the service account to the server local Administrators group

It's safe to do so, before you've had a problem, not a good deal.

Adminuihost – responsible for providing a WEB-based graphical user interface for managing Lync Server 2013

load PowerShell.exe for Lync Server 2013 Modules – responsible for providing command-line administration tools with Lync Server 2013 management-specific cmdlets

The above two need to Csadmin group permissions, also need to add our account to Enterprise Group, DomainAdmins, Schema Admins, install Lync Central Management store also need to add service account to Csadmin Group

System Requirements for ===sqlserver

Very simple, only need to open the inbound TCP port 1433 to SQL Server, outbound UDP1434, in order to facilitate the direct firewall can be shut down

= = = System requirements for management tools

Server2012 and R2 only need to paste a bunch of commands to install the required roles and programs.

SERVER08R2 need to install the Microsoft.NET Framework 4.5 before you can enable Powershell3.0, if PowerShell is installed, use the command to see if the version is 3.0 or above, Microsoft Silverlight is also necessary.

Get-host | Select-object Vers

===dns Requirements

The server name that Lync Topology Builder uses is the FQDN, such as LyncFe01.contoso.com instead of LYNCFE01, all the computers must be joined to the domain, and the SQL Server has to be joined to the domain to ensure that all lyncserver can access SQL properly

A record

We need to point the Pool.contoso.com a record to the IP address of three front-end servers, respectively.

Make sure each server has a DNS a record, and our front-end server has three records as follows

Fe01.contoso.com, Fe02.contoso.com, Fe03.contoso.com

Other records will be described at deployment time

SRV record

_sipinternaltls._tcp.contoso.com applies to Pool.contoso.com port 5061---The automatic configuration of the Lync 2013 client is required when working internally. Because the Pool.contoso.com corresponds to multiple servers ' IP addresses, you can use DNS polling to implement the payload OH

Finally remind novice friends, above is just some basic overview of Lync, of course, these knowledge simple and practical to remember OH.

After the implementation of the project, the deployed operating system will need to install the latest patches, Lyncserver is the same, so as to avoid some bugs, patches exist to fill the loopholes! Do not download the latest server patches to see my blog post, there are detailed steps to download the update http://1163739403.blog.51cto.com/11663406/1827684

Next chapter ramble on some deployment requirements after you start the deployment process ...

This article from "Sameold" blog, declined reprint!

LYNCSERVER2013 Deployment _ System Requirements (normalization test is Project)