Microsoft Lync 2010: Setup, Deployment, Upgrade and Coexistence Scenarios

Peter SchmatzProgram ManagerMicrosoft

EXL319

Robert FlamingProgram ManagerMicrosoft

Session Objectives Lync Server 2010 Deployment and Coexistence

Session ObjectivesPrerequisites: Software and Hardware requirementsChanges in Setup and Deployment in this releaseOverview of End-to-End Setup and Deployment processPurpose of Central Management Server and StoreIntroduction to Deploy Wizard and Topology BuilderOverview of Upgrade and Coexistence

AgendaLync Server 2010 Deployment and Coexistence

Hardware and Software requirements, and Virtualization supportChanges in Setup and DeploymentCentral Management Store and data in Active DirectorySetup Components and Setup FlowDeployment Wizard - Prepare Active DirectoryDemo: Create a simple deployment using Topology BuilderUpgrade and CoexistenceDatabase setupOther setup tasks

Hardware Recommendations

Frontend” (FE) Spec*CPU 8 cores (Dual Quad-Core) 2.00 GHz+16 gigabytes (GB)Attached storage (hard disk drive 10K rpm+, 72GB+)Applicable to other roles (Edge, Monitoring/Archiving)2 network cards (NICs) 1 Gbps+

“Backend” (BE) Spec*CPU 8 cores (Dual Quad-Core) 2.00 GHz+32 GBAttached storage (10Krpm+, 72GB+), multiple spindles2 NICs 1 Gbps+

*Baseline for 80,000 user pool with 8 FEs and 1 BE

Lync Server 2010 Capacity Calculator released

Lync Server Virtualization

Virtualization support now for Audio/Video/AppSharing rolesSupport for all workloadsSupported on Standard Edition and Enterprise EditionHyper-V Windows server 2008 R2 (guest and host) requiredSupport for other Hypervisor implementation through SVVPSurvivable Branch Appliance not virtualizedVM Live Migration not supportedUpdated Lync Server Virtualization Whitepaper

Detailed VM host configuration recommendationsGuidance on VM guest configurationGuidance on mixed physical/virtual deployments Lync

Client Virtualization Whitepaper

Software requirements

Lync Server 2010 rolesWindows Server 2008 SP2 x64 - Windows Server 2008 R2 x64 PowerShell V2

SQL Server® BackendSQL 2005 (SP3/SP4) x64 - SQL 2008 (SP1/SP2) x64 – SQL 2008 R2 x64

Admin Tools, and Core ComponentWindows 7 (x64 only) - Windows Vista SP2 (x64 only) PowerShell V2

Active Directory Forest/Domain level Windows Server 2003Windows Server 2008 Windows Server 2008 R2

Support Added April 2011

Changes in Setup and DeploymentFrom Microsoft Office Communications Server 2007 and 2007 R2

With previous releases configuration data in AD, SQL, Windows Management Instrumentation (WMI)

Now centralized with Lync Server

Changes to Office Communications Server 2007 and 2007 R2 configuration required changes to the AD schema

Required schema changes delayed or blocked deploymentLittle or no schema changes moving forward

Edge server with local configurationLync Server edge configuration won’t get out of sync

Service User Accounts and password expirationLync Server Windows services run as Network Service

Configuration Data Moved to custom storeLync Server 2010 Central Management Store

Central Management StoreXML documents stored in SQL databaseContain all data: Topology, Policies, ConfigurationSingle master database (DB) per deployment

Central Management ServerRuns on one Pool per deploymentCollocated with the 1st Pool of a deploymentPushes (replicates) configuration changes to each serverReplication via HTTPS to Edge servers in Perimeter Network

ReplicaEach Lync server has replica copy of master DBServers continue to operate without access to master DB

Data in Active Directory

Active Directory User extensions

Back Compatibility Schema Office Communications Server 2007 and 2007 R2 schema extensionsEnables interoperability and migration from previous versionsLync Server 2010 will create back compatibility entries for previous versions Third party application compatibilityWill be discontinued in future releases

Central Management StoreImpact on Setup and Deployment

Topology document containsPools, server, fully qualified domain name (FQDN), IP addresses, and PortsServer roles/components and dependencies

Local Setup uses Topology document to install and activate Topology document needs to be authored before any server role can be installed

SQL Server Database is required for initial deploymentEnterprise Edition Pool requires full SQL Server deployedStandard Edition uses a SQL Server Express Installation for SQL Express is a separate option in Deployment Wizard

Lync Server Components for Deployment

Lync Server 2010 Core (OCSCore.msi)x64 onlyCore component and DLLsPowerShell Provider (PowerShell V2 is required)

Deployment WizardLaunched after setup.exe installs Lync Server CoreSplash screen to wrap Deployment tasks

Topology Builderx64 only Requires Lync Server Core

Planning Toolx86 – Web downloadDoes not require Lync Server Core

Setup Flow

Install Topology Builder

AD Setup

AD

Domain Joined System Lync Server Systems

Author desired Topology

SQL Backend

Publish Topology

Local SetupInstalls Core

SQLSQLSQL

RetrieveTopology

Install Components

Activate

Certificates

Certificate Maintenance

SQL DBs setup performed through Topology Builder – or via Install-CsDatabase cmdlet

SQL InstanceCentral Management topology and configuration database

If 1st pool is SE: SQL instance is SQL Express

Add/Remove

PlanningTool

Deployment Wizard Main Screen

Prepare Active Directory Wizard

Prepare Active Directory Powershell cmdlets

Schema Prep Install-CSAdServerSchema –ldf <PathtoLDFfiles> Current state: Get-CsAdServerSchema

Forest PrepEnable-CSAdForest Current state: Get-CSAdForest

Domain PrepEnable-CSAdDomainCurrent state: Get-CSAdDomain

demo

Lync Server 2010Topology Builder

Lync Server 2010 Upgrade and CoexistenceRobert FlamingProgram ManagerMicrosoft

Upgrade and Coexistence Priorities

Service ContinuityMinimize end-user impactMinimize service outage

Topology DiversityScales up and scales downFlexible to many topologies

Minimize cost of upgrade itselfMinimize hardware costsUpgrade leverages new manageability architecture

Upgrade and Coexistence Approach

Traverse topology by poolIterate pool-by-pool, site-by-site, globalSingle iteration for SE, many iterations for world wide EE

Deploy side by sideEnsures service continuity and the lowest end user impactEnables user rollback and service resiliency to logistical issues

Pilot Trial ProductionMinimizes the initial hardware requirementsTrial builds both admin and end user confidenceCosts reduced with each iteration

Servers first, clients last

Upgrade and Coexistence Constraints

Lync Server 2010 works with 2007, 2007 R2, 2010 clientsLync 2010 client works only with Lync Server 2010

Lync Server 2010 upgrade and coexistence works with either Office Communications Server 2007 or OCS 2007 R2 serversLatest updates required for both client and server

Third party applications and gateways require vendor guidance, no direct solution from LyncCustom migration stories for Communicator Web Access, Group Chat, and XMPP Gateway

Upgrade Workflow

Iterate pool-by-pool, site-by-site, using the same method on each pool: Pilot Trial Production

PilotDeploy Lync Server 2010 pool side-by-sideMove a few trial users, deploy new clients and devices

TrialSanity check the workloads, both 2010 only and interoperationValidating admin implementation and end-user experiences

ProductionScale hardware, IT service level agreement, and user supportMove remaining users to the 2010 pool

Upgrade Tools

Three stepsMerge topology to enable server-to-server trustImport configuration to seed settingsMove user to home user on Lync Server 2010, assigns policies

Three toolsMerge with Topology BuilderImport with PowerShell cmdlet Import-CsLegacyConfigurationMove with Lync Server Control Panel

See migration guides for integrated end-to-end processOffice Communications Server 2007 R2 to Lync Server 2010Office Communications Server 2007 to Lync Server 2010

demo

Lync Server 2010Upgrade Tools

Merge Topology Step

Integrate Trusted Server Entries for servers, apps, edgesRun from Topology Builder

PowerShell cmdlets Merge-CsLegacyTopology and Import-CsLegacyConferenceDirectory

Import Configuration Step

Copies configuration from 2007 or 2007 R2Global settings: Location profile to dial planEntitlements: Voice, conferencing, presence policiesCustomizations: Presence ACLs, contact lists, call fwding settings

PowerShell cmdlet Import-CsConfiguration

Move User Step

Homes user on Lync Server, assigns policiesLync Server Control Panel for a few users at a time

PowerShell cmdlet Move-CsLegacyUser for bulk moves

Coexistence before Client Deployment

OCS 2007 and OCS 2007 R2 clients continue to workCan still use Live Meeting. Client Web Access (CWA), and Office Communicator (OC) for meetings

Parity in Workloads for existing featuresInstant Messaging and PresenceBasic Voice and VideoAudio ConferencingWeb, OC and Live Meetings

Join launcher offers Lync Attendee, Lync Web Access (LWA), or legacy client

Coexistence after Client Deployment

All new meetings are the new Lync 2010 meetings

Live Meeting and OC meetings Unedited existing meetings continue to workEdit converts existing meetings to Lync MeetingsNo new Live Meeting meetings (new means Lync Meetings)

Join launcher offers new client, LWA, or Lync Attendee client

Lync Server 2010 Setup and DeploymentOther tasks

Peter SchmatzProgram ManagerMicrosoft

Database Setup

Cmdlet Install-CsDatabaseReads Topology document and configures SQL Stores based on assigned roles (remotely)Access SQL instance and check for connectivity and permissionsCreates databases and tableCreates DB roles and store procedures Requires user to have SQL admin rights to create databases

Run by Topology BuilderDefault auto-allocate drives/foldersOption to use SQL Instance defaults

Run as standalone cmdletSQL administrator may be separate from Lync Server 2010 administratorMore flexibility Special usages: Custom path, SQL cluster, SAN storage

Other Setup tasks

Kerberos Authentication option IIS as Network Service, service principal name (SPN) for Pool

Solution via using a Computer Account in Active Directory

Computer Account password does not fall under password expiration policies

PS Cmdlet available to create, assign, and manage account name and password

Optional configuration

If not configured, NTLM authentication is used

Takeaways

Lync Server 2010Platforms and perquisitesPurpose of new configuration storeIntroduction to deployment toolsSetup and deployment overview Upgrade and coexistence Overview

Related Content

EXL321 Microsoft Lync Server 2010: Administering Lync Server DeploymentEXL323 Setting Up and Deploying Microsoft Lync Server 2010 Edge ServersEXL315 Microsoft Lync 2010: Core Voice Planning and Deployment EXL318 Monitoring Microsoft Lync 2010 Deployments

EXL372-INT What do you want to know about Management and Administration of Lync Server 2010?

EXL371-HOL Deploying a Microsoft Lync 2010 Architecture EXL372-HOL Managing Migration and Co-Existence between Microsoft Lync Server 2010 and Microsoft Office Communications Server 2007 R2EXL377-HOL Managing Microsoft Lync Server 2010 Using Windows PowerShell and the Lync Server Control Panel

C4E254 Exam Cram on Microsoft Lync Server 2010 IT Professional Series: Exam 70-665

Find Me Later At… Exchange and Lync Booth

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

http://northamerica.msteched.com

Connect. Share. Discuss.

Complete an evaluation on CommNet and enter to win!

Scan the Tag to evaluate this session now on myTech•Ed Mobile

© 2011 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.