microsoft lync server

Change page: < 1 2 3 4 > | Displaying page 1 of 4, items 1 to 30 of 93.

Microsoft Lync Server 2013 : SQL Server Dependencies - Creating SQL Server Maintenance Plans

Maintaining the Lync Server Back End databases is important to the overall health and performance of a Lync deployment. Yet this is an aspect that frequently gets overlooked, primarily because Lync administrators are kept busy caring for other aspects of the Lync environment.

Microsoft Lync Server 2013 : SQL Server Dependencies - Maintaining the Lync SQL Databases

An important aspect of the health of any Lync deployment is maintaining the Lync SQL databases. To keep Lync Server operating smoothly and with optimal performance, regular maintenance should be performed on each SQL Server database.

Microsoft Lync Server 2013 : SQL Server Dependencies - SQL Backup Procedures - Backing Up SQL Using SQL Server Management Studio

Another way to back up SQL is by using the native backup function of SQL to create a flat file backup, which can then become the target for a separate backup application if necessary.

Microsoft Lync Server 2013 : SQL Server Dependencies - SQL Backup Procedures - Backing Up SQL Using Windows Server Native Backup

Windows Server 2008 R2 and Windows Server 2012 contain a native backup application called Windows Server Backup.

Microsoft Lync Server 2013 : SQL Server Dependencies - Lync Database Requirements, Installing SQL Server for Lync

For an Enterprise Edition pool, SQL Server 2008 R2 and SQL Server 2012 are the supported Back End database platforms. Since it is the most recent database release, this section provides step-by-step procedures for installing SQL 2012 in preparation for hosting the Lync Server 2013 Back End databases.

Microsoft Lync Server 2013 : Dependent Services and SQL - Server Certificates - Installing Lync Certificates

Lync Server 2013 provides a wizard for requesting, installing, and assigning certificates. For example, the following procedure is used to create an offline SSL certificate request to be sent to a third-party CA for a Front End Server

Microsoft Lync Server 2013 : Dependent Services and SQL - Domain Name System - DNS Load Balancing , Automatic Client Sign-in

Although the sample DNS configurations just shown can be used to meet the minimum requirements for Lync, many organizations rely on the Lync client’s capability to automatically find the Lync pool and sign in the user, an optional but very useful feature.

Microsoft Lync Server 2013 : Dependent Services and SQL - Active Directory (part 2) - Forest Prep, Domain Prep, Lync Server 2013 Security Groups

After the schema has been updated, the Deployment Wizard enables the remaining AD preparation steps. The next step is to prepare the forest for the Lync Server installation, which creates global configuration settings and universal security groups required for the Lync deployment.

Microsoft Lync Server 2013 : Dependent Services and SQL - Active Directory (part 1) - Schema Extensions

To provide the necessary attributes used by Lync Server, it is necessary to extend the AD schema. This process is typically easiest to run on a system that is planned as a Lync Front End Server, and must be run by a user that is currently a member of the Schema Admins group.

Microsoft Lync Server 2013 : Installing the Director Role (part 3) - Install Server

After you’ve browsed to the setup folder using Windows Explorer, the install window might appear behind the current Explorer window. It can be easy to miss this fact, so check the taskbar for the Lync install icon if some time has passed without any screen activity.

Microsoft Lync Server 2013 : Installing the Director Role (part 2) - Creating a Director Pool - Edit Topology, Publish Topology

After the server has been fully prepared for installation, the topology must be edited and published to reflect the new Director pool. This involves both editing the existing topology and then republishing the updated topology so that the Director role can be installed.

Microsoft Lync Server 2013 : Installing the Director Role (part 1) - Prerequisites

Installing the Director role is similar to deploying any other role in Lync Server 2013. Much of the installation process is actually spent completing the prerequisite work, and installing the actual server can be done fairly quickly.

Microsoft Lync Server 2013 : Director Overview (part 3) - Optional Role

Perhaps the biggest change for the Director in Lync Server 2013 is that Microsoft has declared it an optional role in the Lync topology. In prior years the documentation treated it as recommended, especially when deploying external services.

Microsoft Lync Server 2013 : Director Overview (part 2) - Centralized Sign-In , Optimized External Access Path, Simple URL Entry Point

Historically, the Director role played a much bigger part in the sign-in process every single day, and careful planning was required to ensure that there was enough processing capacity available to handle the bulk of sign-in and authentication traffic occurring during the morning hours in each region

Microsoft Lync Server 2013 : Director Overview (part 1) - Benefits of a Director - Internal Endpoint Sign-In Process

There is no logic in an endpoint to indicate that it is initially connecting to a Director pool and not a Front End server, meaning that the same DNS records, authentication methods, and signaling are used from the endpoint’s perspective.

Microsoft Lync Server 2013 : Mediation Server Troubleshooting (part 2) - Synthetic Transactions, Telnet

A feature carried over from Lync Server 2010 is synthetic transactions, which are a set of PowerShell cmdlets used to simulate actions taken by servers or users in the environment.

Microsoft Lync Server 2013 : Mediation Server Troubleshooting (part 1)

Given the Mediation Server’s role of providing PSTN connectivity through a next-hop gateway, ensuring that connectivity to those next-hop services is healthy is important in all troubleshooting scenarios.

Microsoft Lync Server 2013 : Mediation Server Administration

Administration of the Mediation Server role in Lync Server 2013 can be performed through a combination of the Lync Server Control Panel and the Lync Server Management Shell. This section discusses management of Mediation Server services.

Microsoft Lync Server 2013 : Mediation Server Configuration

After a Mediation Server Pool has been installed, there generally is not much configuration left to do. This section discusses some of the configuration options available to a Mediation Server and addresses items that administrators should be aware of when configuring a Mediation Server.

Microsoft Lync Server 2010 : Installing Mediation Server (part 4) - Create Certificates

Like all other roles in Lync Server, the Mediation Server communicates with other servers in the organization using Mutual Transport Layer Security (MTLS). To leverage MTLS, the Mediation Servers will need at least one certificate installed that meets a few requirements.

Microsoft Lync Server 2010 : Installing Mediation Server (part 3) - Install Lync Mediation Server Components

Microsoft Lync Server 2010 : Installing Mediation Server (part 2) - Create a Mediation Server Pool

After the server has been fully prepared for installation, the topology must be edited and published to reflect the new Mediation Server Pool. This involves both editing the existing topology and then republishing the updated topology so that the Mediation Server role can be installed on all servers in the pool.

Microsoft Lync Server 2010 : Installing Mediation Server (part 1) - Hardware Recommendations

Lync Server 2013 is only a 64-bit application and requires a 64-bit-capable processor. This is generally not an issue with any modern hardware, but be sure to verify that any legacy hardware supports a 64-bit operating system before attempting to use it for a Mediation Server.

Microsoft Lync Server 2010 : Mediation Server Overview

The Mediation Server in Microsoft Lync Server 2013 is a service that connects your Lync users and Lync Servers to the PSTN. This server role is required for any connections to the PSTN or a legacy PBX infrastructure.

Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 2) - Using Cmdlets for Configuration Tasks

Notice the last argument set in this command: ArchiveDuplicateMessages. This is a good example of where there are options available through the cmdlets that aren’t exposed to the GUI tools.

Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 1) - Creating Site and User Policies

It is worth highlighting the Archiving Configuration option Block Instant Messaging (IM) or Web Conferencing Sessions If Archiving Fails. This is what Microsoft refers to as “critical mode.”

Microsoft Lync Server 2013 Monitoring and Archiving : Monitoring Components Installation (part 2) - Monitoring Administration

This section reviews common administration tasks for the Lync Server 2013 Monitoring role. In general, there isn’t much day-to-day administration of the Lync Server 2013 Monitoring components. Instead, this section focuses on the reports generated by the Monitoring Server.

Microsoft Lync Server 2013 Monitoring and Archiving : Monitoring Components Installation (part 1) - Monitoring Configuration

Although both configuration and administration can be done from the Silverlight web GUI or the Lync Server Management Shell, the configuration section focuses on the former and the administration section focuses on the latter, to avoid duplication of concepts.

Microsoft Lync Server 2013 Edge Server : Edge Server Troubleshooting (part 3) - Lync Centralized Logging, Lync Server Management Shell, Telnet, Troubleshooting Lync Services

Lync Server 2013 introduced Centralized Logging. Each Lync Server runs a service that can receive commands from any other Lync Server to enable logging for troubleshooting scenarios.

Microsoft Lync Server 2013 Edge Server : Edge Server Troubleshooting (part 2) - DNS Records

When troubleshooting any Edge Server issue, it is important to check that all necessary DNS records exist and are resolving to the correct IP addresses.