lync 2013 deployment ewan mackellar / andrew ehrensing microsoft corporation exl321

41
Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Upload: seth-conquest

Post on 14-Dec-2015

215 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013 Deployment

Ewan MacKellar / Andrew EhrensingMicrosoft Corporation

EXL321

Page 2: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

About this Presentation

Capabilities are subject to change

Packaging and licensing have not yet been determined

Any screen captures or concepts shown are pre-release and for illustration purposes only

DisclaimerThis presentation contains preliminary information that may be changed substantially prior to final commercial release of the software described herein. The information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of the presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of the presentation. This presentation is for informational purposes only.

MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this presentation. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this information does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

All performance statistics are pre-release and subject to change

Page 3: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Session Objectives

Session Objective(s): The Setup & Deployment changes introduced in Lync Server 2013Migration from legacy versions to Lync 2013

Key Takeaways:Setup and Deployment prerequisitesNew hardware and software requirements along with the new capacity modelNew/Updated tools for the setup & administration

Page 4: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Topology Changes

Page 5: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync Server 2013 On-Premise Topology

Publicclouds

Federatedbusinesses

Remoteusers

SQL

Front end servers

Back end SQL server

Web access and mobile

PSTN

ADActive

directory

SQL

Monitoring

Exchange UM and archiving

System Center

WAC

Lync endpoints

FPO

Edge server

DMZ

Optional persistent chat pool

XMPP Gw

Central Mgt

Voice routing

Conferencing

Lync Web App

Mobile

SIP registrar

Page 6: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Setup Flow

Page 7: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Setup Flow

• Hardware and software infrastructure

• File storage (DFS) and permissions

• Request certificates• Internet Information

Services (IIS) and SQL configuration

• Simple URLs & DNS records

Preparing the infrastructure and

systems

• Using Topology Builder• Administrator rights

and permissions• Administration tools• Define and configure

pools• Edit and configure

simple URLs• Select the CMS

Defining the topology

• Publish the topology• Delegate setup• Setting up and installing FE

servers/pools• Install and configure the

CMS• Configure certificates for

FEs• Setting up Kerberos

authentication• Adding server roles

Finalizing and implementing the topology design

Page 8: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Changes in Setup and Deployment

Changes to path for RTCLOCAL and LYNCLOCALSupport of separate operating system and application drive

Custom database setup with Install-CsDatabase cmdletFour different ways for placing the databases files:

with no parameter for DB file locations-DatabasePath-UseDefaultSqlPaths-DatabasePathMap

Sysprep supportSupport creating an image using Sysprep that can easily

be specialized by providing a script to assist users in creating a SysPrep'able image.

Page 9: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Changes in Setup and Deployment

New prerequisite check in Deployment WizardWindows Identity Foundation (WIF)Powershell v 3.NET Framework 4.5

Bootstrapper changes to support new rolesPersistent ChatXMPP Translating Gateway Service

Certificate ChangesOAuthTokenIssuer certificate for Server-Server authenticationXMPP consideration in Edge Server certificatesNew parameter for Request-CSCertificate: –AllSipDomainNew certificate management cmdlets: Set-CSCertificate -Roll

Page 10: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Changes in Setup and DeploymentOpen Authorization (OAUTH) protocol

Provides authentication and authorizationUsed for server – server communications

Lync 2013 <-> Exchange 2013Lync 2013 <-> SharePoint 2013Lync 2013 <-> Office 365

ComponentsRealms / Authorization Server

Realm – a security containerPartner application realm

No username/passwords exchanged between realmsRequired when integrating Exchange, SharePoint 2013

Page 11: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Deployment ValidationSynthetic Transactions for deployment validation

Test-CsComputer – Checks and validates the local configuration

Local groupsWindows Firewall exceptionsFile store ACL’sIIS virtual directoriesLocal applicationsLync server services (status, auto start modes etc)

Test-CsDatabase – Checks and verifies connectivity to the SQL server and returns Database version info.

Could be run against local or remote SQL server

Page 12: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Office Web Apps Installation

Separate setup bits

Independent install experience

Install and then configureTopology builder configures only discovery URL’s

Configuration done by its own Powershell moduleImport-Module OfficeWebAppsUse Certificate Friendly Name in New-OfficeWebAppsFarm

Page 13: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Hardware and Software Requirements

Page 14: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsFront End Server

Topology and function changes that effect hardware sizing

Collocated A/V MCUCollocated XMPP gatewayNew CPU intensive features (Multiview, HD Conferencing etc.)

Beta 2 current scalability capabilities12-20 Servers per Pool12.5K users per Front End *Subject to change at RTM!!

* Depending on the user model

Page 15: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsFront End Server

Hardware requirements (As of Beta 2 – Not finalized yet)

RTCLOCAL and LYNCLOCAL database size changes (as of Beta 2)Initial size: 4GB per DB – Should be planned beforehand (especially for Virtual Machines)

Component Spec (Minimum)

Server Enterprise-grade server with a minimum of 2 CPU sockets (8-24 CPU core total)

CPU Intel Xeon 5500 series or AMD Opteron 6100 series (2 GHz+)

NIC Dual 1 GbE or 10 GbE

Storage Enterprise Edition FE: 8 or more SATA or SAS HDD 10K RPM or higher (DAS), or equivalent storage, RAID 1

Standard Edition FE with collocated SQL DB server 4 disks, RAID 1Memory 16-GB PC2-6400 DDR2, or PC3-8500 DDR3 memory (or faster)

Page 16: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsDirector and SQL Back End

Director, Monitoring, and Archiving Servers (As of Beta 2 – Not finalized yet)

Component Spec (minimum)

Server Enterprise-grade server with a minimum of 2 CPU sockets (8-24 CPU core total)

CPU Intel Xeon 5500 series or AMD Opteron 6100 series (2 GHz+)

NIC Dual 1 GbE or 10 GbE

Storage 2 or more SATA or SAS HDD 10K RPM or higher (DAS), or equivalent storage, RAID 1

Memory 8-GB PC2-6400 DDR2, or PC3-8500 DDR3 memory (or faster)

SQL Back-End Server (As of Beta 2 – Not finalized yet)

Component Spec (minimum)

Server Enterprise-grade server with a minimum of 2 CPU sockets (8-24 CPU core total)

CPU Intel Xeon 5500 series or AMD Opteron 6100 series (2 GHz+)

NIC Dual 1 GbE or 10 GbE

Storage 8 or more SATA or SAS HDD 10K RPM or higher (DAS), or equivalent storage, RAID 1 or 10 (4 spindles: OS, Log, Log, DB). SAN with 4 dedicated LUNs

Memory 32-GB PC2-6400 DDR2, or PC3-8500 DDR3 Memory (or faster)

Page 17: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsNetwork, Operating System, SQL

NIC Recommendations:Minimum supported NIC: Single 1 Gbps (Ethernet)Recommended: Dual Ethernet 1 Gbps (Teamed Ethernet)Media Server minimum NIC: Teamed 4 x 1 Gbps (NIC Teaming) (Edge and Front Ends for Audio/Video)

Operating System:Windows Server 2008 R2 SP1 or above for Lync server rolesWindows Server 2008 is only supported on SQL Server, File Server, Domain Controller, etc.New: Microsoft Windows Server 2012

SQL Server:SQL Server 2008 R2 SP1 and above for database servers (back end, Archive/Monitoring databases)Lync Server 2013 automatically installs SQL Server 2012 Express (Denali) on each Front EndSupported Back-End High Availability is SQL Mirroring

No support for “Always On” or “SQL Clustering”

Page 18: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsSoftware Prerequisites

Software Prerequisites:Windows Identity Foundation (WIF)

Server support for server-to-server authentication scenariosDownload: http://support.microsoft.com/kb/974405

PowerShell 3Part of Windows Management Framework 3.0Download: http://www.microsoft.com/en-us/download/details.aspx?id=29939

Lync 2010 Cumulative Update 6 on Lync 2010 serversDownload: http://support.microsoft.com/kb/2493736

Microsoft .NET Framework 4.5 – included in the Lync Server Setup MediadotNetFx45_Full_x86_x64.exe.NET FW 4.5 RC QFE: NDP45-KB2713435-x64.exe

Windows Desktop Experience – All Front End serversRequired for supporting the media stack on A/V Conferencing and applications like Call Park, Response Group and Conferencing Announcement

Message Queuing – (MSMQ) and Directory Service Integration on Front End and Archiving servers

Page 19: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Hardware and Software RequirementsAdmin Tools, Active Directory, Infrastructure

Admin Tools and Core ComponentsWindows 7 (x64 only) and Windows Server 2008 R2 - Windows 8 on the wayMicrosoft Windows PowerShell™ V3 required

Active Directory Forest/Domain Functional Level Windows Server 2003 (Native mode only)Windows Server 2008 Windows Server 2008 R2Windows Server 2012

InfrastructureHardware Load Balancer (HLB) for Web ServicesEven with DNS load balancing deployed, HWLB is still required for HTTP/HTTPS trafficHardware Load Balancer Partners for Lync Server

http://technet.microsoft.com/en-us/lync/gg269419

Page 20: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Server VirtualizationSupport for all Lync Server workloads

Supported on Standard Edition and Enterprise Edition and all other roles

Supported HypervisorsMicrosoft Windows Server 2008 R2 SP1 Hyper-V® minimum (guest and host)VMWare ESX 5

Use current Lync Server 2010 hardware recommendations for virtualization Will take advantage of Windows Server 2012 Hyper-V (3.0)

New large vCPU with NUMA architecture and large memory support

Unsupported Virtualization FeaturesQuick/Live MigrationDynamic MemoryVM Replica

Virtualization support in Lync 2013 Planning Tool

Page 21: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Client Deployment

Page 22: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013 Client DeploymentNo standalone Lync 2013 Client MSI

Lync client part of Office 2013

Two Lync 2013 Client Deployment Options

Traditional MSI install as part of Office 2013 PreviewClick to Run installInstallation customization and process included in the Office 2013 Preview Resource Kit Documentation

Online Meeting Outlook add-in automatically installed with the Lync 2013 Preview client

Office 2013 Preview installs side by side with Office 2010 / Lync 2010 client.

Page 23: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Customizing Client Deployment

Office Customization ToolSetup Used to specify default installation location on the client and default organization name, additional network installation sources, the product key, end-user license agreement, display level, earlier versions of Office to remove, custom programs to run during installation, security settings, and Setup properties.

Features Used to configure user settings and to customize how Office features are installed. Administrators can use the OCT to specify initial default values of Office application settings for users. Users can modify most of the settings after the installation.

Additional content Used to add or remove files, add or remove registry entries, and configure shortcuts.

Outlook Used to customize a user's default Outlook profile, specify Exchange settings, add accounts, remove accounts and export settings, and specify Send\Receive groups.

Use the Office Customization Tool (OCT)Use CONFIG.XML to Perform Installation TasksUse Setup Command-Line Options to specify the Config.xml and configuring Client Bootstrapping Policies

CONFIG.XML

Specify the path of the network installation point.

Select the products to install.

Configure logging and the location of the Setup customization file and software updates.

Specify installation options, such as user name.

Copy the local installation source (LIS) to the user's computer without installing Office.

Add or remove languages from the installation.

Page 24: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Customizing Client Media Ports

Set-CsConferencingConfiguration

Setting Description Lync Server Management Shell cmdlet

Cmdlet parameters

Portrange\Enabled

Specifies whether the port ranges sent by the server should be used by the client for media and signaling. Used in conjunction with the subvalues MinMediaPort and MaxMediaPort.

CsConferencingConfiguration ClientMediaPortRangeEnabled

Portrange\MinMediaPort

Specifies the starting port number to use for media. Combines with MaxMediaPort to specify the range of ports. The recommended minimum range is 40 ports.

CsConferencingConfiguration

ClientMediaPort (represents the starting port number to use for client media)

Portrange\MaxMediaPort

Specifies the highest port number to use for media. Combines with MinMediaPort to specify the range of ports. The recommended minimum range is 40 ports.

CsConferencingConfiguration

ClientMediaPortRange (indicates the total number of ports available for client media; default is 40)

Page 25: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Client Enhanced Privacy Mode

Enable Enhanced Privacy ModeRestricts presence visibility only to people in your contact listEnabling allows users to select which option they prefer (all people see presence vs only contact list sees presence)Get-CsPrivacyConfiguration | Set-CsPrivacyConfiguration -EnablePrivacyMode $True

Only works for Lync 2010 and Lync 2013 Preview clients

OCS 2007 R1 and OCS 2007 R2 clients do not honor the enhanced privacy mode setting

Page 26: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Manageability Tools

Page 27: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Planning Tool

Planning toolA step-by-step tool to plan and design all the Lync infrastructure including hardware sizing with the user models

New Supported Features (as of Beta 2)

High Availability & Disaster RecoveryIPv6MobilityExchange Unified MessagingExchange 2013 Archiving IntegrationPersistent ChatXMPP federationMedia BypassMulti-view & HD ConferencingVoice applications (Call park, Response Groups)

Page 28: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Topology Builder

Support for Lync 2013 topology

Support for the new featuresPersistent ChatOffice Web Apps High Availability and Disaster Recovery

Paired PoolsSQL Mirroring

Merge and manage Lync 2010 topologyM:N Routing – TrunksIPv6XMPP

Legacy Topology Builder should be retired

Page 29: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Ewan MacKellarMicrosoft Corporation

Planning Tool and Topology Builder for Lync 2013

Page 30: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Lync 2013

Migration

Page 31: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Legacy Versions

Lync Server 2010

Uses CMS (Central Management Store)Lync 2010 client, No Live Meeting clientEasy migration pathTopology Builder

OCS 2007 R2

No CMS (Central Management Store)Configuration stored in Active DirectoryLive Meeting and Office Communicator clientMigration to Lync Server 2013 Preview similar to Lync 2010 migration

Page 32: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Migration ApproachLync Server 2013 Preview infrastructure deployed side-by-side with existing infrastructureSimilar to previous migrationsIn place upgrade not supported

Migrate Side-by-side, Site-by-siteEnsures service continuity, low end user impactEnables rollback, resiliency to logistical issues

Build Pilot ProductionMinimize initial hardware requirementsTrial builds administrator and end user confidence and minimizes risk

33

Page 33: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Support Boundaries Server supports migration from N-1 or N-2

N (15): Lync 2013 PreviewN-1 (14): Lync 2010*N-2 (13): Office Communications Server (OCS) 2007 R2*

Client support depends on workloadN-1 client (Lync 2010) against Lync Server 2013 PreviewN-2 client (Communicator 2007 R2) against Lync Server 2013 PreviewN client (Lync 2013 Preview) against Lync 2010 Server

Voice CoexistenceSupport Legacy Mediation Servers (N-1, N-2)Lync 2013 Preview SBA cannot use the Lync 2010 Pool

* With Latest Updates

Page 34: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Support Boundaries (Cont’d)

Persistent Chat supports migration fromN-1 (14): Lync 2010* Group ChatN-2 (13): Office Communications Server (OCS) 2007 R2* Group Chat

Persistent Chat Client supportN-1 chat client (Lync 2010) against Lync 2013 Persistent Chat ServerN-2 chat client (Communicator 2007 R2) against Lync 2013 Persistent Chat Server

Lync 2013 Preview cannot connect to Legacy Group Chat Servers

* With Latest Updates

Page 35: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Voice Routing Coexistence

Home Server Mediation

Server

Lync Server 2013 Preview 2013 2013 Supported

Lync Server 2013 Preview - Lync Server 2010

2013 2010 Supported

2010 2013 Supported

Lync Server 2013 Preview - OCS 2007 R2

2013 2007 R2 Supported

2007 R2 2013 Not Supported

Mediation Server Next Hop Server Home Server

Lync Server 2013 Preview 2013 2013 2013 Supported

Lync Server 2013 Preview - Lync Server 2010

2013 2013 2010 Supported

2010 2010 2013 Supported

Lync Server 2013 Preview - OCS 2007 R2

2013 2013 2007 R2 Supported

2007 R2 2007 R2 2013 Supported

Outbound Calls

Inbound Calls

** Assumed certified Gateways for the release of MS shown in the tables above

Lync 2010 PoolLync 2013

Preview Pool

Lync 2010 SBA

Supported Supported *

Lync 2013 Preview SBA

Not Supported Supported

* Contents from 2010 SBA will write monitoring and archiving contents to Lync 2010 store

Survivable Branch Appliance (SBA)

36

Page 36: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Migrating from Lync Server 2010Topology

Download existing topology in Lync Server 2013 Preview Topology BuilderDefine new Lync 2013 Preview Pool and publish the new topologyUse Lync Server 2013 Topology Builder, Lync 2010 topology builder cannot be used

ConfigurationData exists in Lync 2010 Central Management Store (CMS)Lync Server 2013 Preview uses Lync 2010 CMS instance

Users (Performed on Lync 2013 Preview System)Via Lync Server Control PanelFrom Management Shell: Move-CsLegacyUser

Roll back from Management Shell: Move-CsUser

37

Page 37: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Migrating from OCS2007 R2

TopologyMerge topology using the Topology builder

Imports Legacy topology and conference directoriesRerun when Legacy topology changes

Publish the new topology

ConfigurationMerge other configuration from Lync Management Shell:

Import-CsLegacyConfiguration

Rerun when legacy configuration has changed with -ReplaceExisting

UsersVia Lync Server Control PanelFrom Management Shell: Move-CsLegacyUserRoll back from Management Shell: Move-CsUser

Other Move-Cs cmdletsApplications: Move-CsApplicationEndpoint

Response Group: Move-CsRgsConfigurationExchange UM contacts: Move-CsExUmContactConferencing dirs: Move-CsConferenceDirectory

38

Page 38: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

In Review: Session Objectives And Takeaways

Session Objective(s): •The on-premises deployment Setup & Deployment changes introduced in Lync Server 2013

•Migration and Coexistence with legacy versions

Key Takeaways:•Transfer knowledge about the homogenous setup flow to include new roles and features

•New hardware and software requirements along with the new capacity model

•New/Updated tools for the setup & administration

Page 39: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Related ContentEXL314 – Lync 2013 Architecture Wed 13:45-15:00

Lync Demos – Microsoft Booth

EXL316 – Lync 2013 Meeting Improvements Wed 17:00-18:15EXL321 – Lync 2013 Deployment Thur 8:15-9:30

EXL325 – Lync 2013 Voice Improvements Thur 15:30-16:45

EXL334 – Lync 2013 Enterprise Networking Fri13:45-15:00

EXL231 – Demystifying Integration of Lync to PBX Fri8:15-9:30

EXL224 – Lync 2013 Customer Panel Q&A Thur 13:45-15:00

Page 40: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

Track Resources

Download and evaluate Exchange 2013 Preview

Download and evaluate Lync 2013 Preview

Get a Lync Business Value Assessment

Get an Exchange and Lync Technical Briefing

See and test drive Exchange and Lync in our Customer Immersion Experience Centers

Page 41: Lync 2013 Deployment Ewan MacKellar / Andrew Ehrensing Microsoft Corporation EXL321

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the

part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.