Microsoft Lync Ignite

Setup and Deployment# 2011-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.Lync Server 2013 Set-up FlowLync Server 2013 Hardware and Software RequirementsLync Server 2013 Manageability ToolsQ & AAgenda2Slide Objective:

Notes:Goals: Present the on-premises deployment Setup and Deployment changes introduced in Lync 2013Transfer knowledge about the homogenous setup flow to include new roles and featuresDescribe new hardware and software requirements along with the new capacity modelExplain new/updated tools for the setup and administration

# 2011-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.Lync Server 2013Setup Flow# 2011-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.Setup FlowDefining the topologyPreparing the infrastructure and systemsFinalizing and implementing the topology designHardware and software infrastructureFile storage Distributed File System (DFS) and permissionsRequest certificatesInternet Information Services (IIS) and SQL configurationSimple URLs and DNS records

Using Topology BuilderAdministrator rights and permissionsAdministration toolsDefine and configure poolsEdit and configure simple URLsSelect the Central Management Store (CMS)Publish the topologyDelegate setupSetting up and installing Front-End Servers/poolsInstall and configure the CMSConfigure certificates for FEsSetting up Kerberos authenticationAdding server roles4Slide Objective:

Notes:Planning & PreparationAny product/technology requires a lot of planning and preparation beforehand and Lync is no exception.Hardware procurement and preparationPlanning for virtualization and file storageCertificatesdepending on the cert authority, it would take timeIIS componentsnew components like dynamic compression for MobilityDNS, AD (forest and domain functional levels)Simple URLsMore things to plan and prepare than there was for Lync 2010HA/DRadditional servers/pools and SQL ServersVoice gateways and trunks to support M:N routingPlan with both IT and business groups about the requirements, especially on the voice routing and HA/DRDFS is primary file storage in 2013 nowThis was a frequent ask from Lync 2010 customersDoesn't mean that you shouldn't still do backups per the backup/recovery guidance

Define the topologyDefine the new topology or merge the legacy one and update as necessaryPlan for the permissions on other systems like AD and DNS (generally different groups at the IT department so plan for their schedules)Topology is now laid out differently than it was in 2010 (shared components)If you are migrating from 2010 its just like adding in a new pool to your existing topologySQL mirroring and SQL witnesses are defined in the topology

Topology Publish & ImplementationPermissions are criticalPublish the topologyObtain the File share and SQL permissions before publishing the topology, or install the databases manuallyIf required, delegate setup permissions for Lync poolsDo the actual setup, assign the certificates and add additional server rolesConfigure Kerberos authentication if it is requiredKeberos setupWe do this to ensure that Lync Servers will use Kerberos authentication of web traffic as this is faster and more scalable than NTLMManual database installAllows for better control of the database placementServer to Server Auth certificate is created in the first FE and then published via CMS to all Fes (this is different behavior in the cert wizard)Mirror and witness configuration will be done for you via topology

# 2011-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.Setup FlowInstall Topology BuilderAD setupADDomain-Joined SystemLync Server SystemsAuthor desired topologySQL Back EndPublish topologyRetrievetopologyInstall componentsCertificatesStart servicesCertificate maintenanceSQL database setup performed through Topology Builder or manually

SQL instanceCentral management topology and configuration database

If first pool is SE: SQL instance is SQL Express

Add/removeOffice Web AppsSetup Web AppsCreate farmand hostCertificateLocal setupInstalls core and SQL instances RTCLOCAL and LYNCLOCALOther SystemsExchangeUM/OWA/ArchivingReverse Proxy, SCOMSQL Reporting ServicesValidate deployment

5Slide Objective: Discuss deployment steps

Notes:In any domain joined system, extend the AD schema and perform Forest and Domain PrepInstall the Topology Builder and define the topology (use the Lync Planning Tool before everything else to plan your environment)Publish the topologySQL databases will be created on the SQL Server instance defined in the Topology BuilderIf the first pool in the environment is a SE box, install SQL Express and create a CMS database by selecting Prepare first SE Server in the deployment wizardCMS databases will be installed by Topology Builder or manually by either selecting Prepare first SE Server option or running install-CsDatabase cmdletStart deploying Lync ServersRun the Deployment wizard on each Lync Server to setup RTCLOCAL and LYNCLOCAL SQL Express instances and install core files (LYNCLOCAL is a second SQL instance installed by the bootstrapper to host Lyss databases)Retrieve the topology directly from the CMS, or manually with the Export-CsConfiguration cmdlet for Edge ServersInstall the Lync Server roles and components defined in the topologyRequest (or import if requested prior to the deployment) and assign the certificatesNew certificate requirementOAuth used for Server to Server authenticationBootstrapper invokes ReplicateCMSCertificate as wellFinally, start the servicesPerform ongoing certificate maintenanceRenew when requiredIf you change topology to add/remove any roles to the existing servers, run local setup on the relevant Lync Servers and configure certificates if requiredIf your deployment includes Web Conferencing, set up Office Web Appsserver or poolManually create the WebAppHost and host on Office Web Apps ServerAfter the Lync specific roles are deployed, either deploy or integrate with the other essential systems like Exchange, Reverse Proxy, SQL Reporting Services, SCOM, etc.Finally, continuously validate deployment against any configuration issuesYou can also run the schema updates manually directly using the LDF filesAuthor only the topology that you will actually be deploying (reference the Quorum slide from earlier)Make sure that the AD computer accounts have already been created# 2011-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.Custom database setup with Install-CsDatabase cmdletFour different ways for placing the databases files:with no parameter for DB file locations-DatabasePath-UseDefaultSqlPaths-DatabasePathMap

Changes in Setup and Deployment

6Slide Objective:

Notes:

Install-CSDatabase cmdlet has three options for placing the databaseNo parameter: Built in algorithm determines the Database and Log Files-DatabasePath: You can specify the log and database paths (comma separated path list)-UseDefaultSQLPaths: Stores the DB and log files specified in the SQL Server Instance (stores all logs in the same path, all DB files in the same path)-DatabasePathMap: Works similar to UseDefaultSQLPathsyou specify a Log and DB path for all the databases.

# 2011-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.New prerequisite check in Deployment WizardWindows Identity Foundation (WIF)Windows PowerShell v3.NET Framework 4.5Bootstrapper changes to support new rolesPersistent ChatXMPP Translating Gateway ServiceCertificate changesOAuthTokenIssuer certificate for Server-Server authenticationXMPP consideration in Edge Server certificatesNew parameter for Request-CSCertificate: AllSipDomainNew certificate management cmdletsChanges in Setup and Deployment7Slide Objective:

Notes:New prerequisite checksWIFsimplify user access for developers by externalizing user access from applications via claims and reducing development effort with prebuilt security logic and integrated .NET tools.PowerShell v3

Setup Bootstrapper now supports Persistent Chat. Install Persistent Chat role and any prerequisites if enabled in the Topology. More details will be covered in Module 07: Persistent Chat Experience and Infrastructure

CertificatesOAuthTokenIssuer certificate required for Server-Server authentication, particularly for Exchange 2013 integration for archiving and HD photoIf the customer have too many SIP domains, -AllSipDomain parameter can be used instead of typing too many SANs. Once used, all SIP domain FQDNs will be added to the Certificate Signing Request (CSR).

Other certificate changesServer-Server certificate improvementsIn Lync 2013, Lync Server to server authentication and MRAS propose a new requirement that the previous assigned certificate should be valid for a certain period of time. We generalize it to store the previous assigned certificate information for any type of the certificate. Server-Server and MRAS wants the old assigned certificate to be valid for some time after the new certificate is assigned. The minor difference is that Server-Server requires the new assigned certificate to be valid after its assignment, while MRAS requires the new assigned certificate to be valid after its assignment (by default), or to be valid only after certain time if EffectiveTime is specified. No service restart is required for these new certificates to take effect.

Since XMPP components are running on the Edge Server, Certificates should be planned accordingly.

New certificate management cmdlets: Set-CsCertificate, Roll-CsCertificate, and Remove-CsCertificate -Previous

WIF is required to support server to server authenticationBootstrapper really means Lync Server Deployment WizardXMPP covered by Architecture moduleServer to server auth token issuer certificate is similar to the Edge Server MRAS certificate

# 2011-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.Synthetic Transactions for deployment validationTest-CsComputerChecks and validates the local configurationLocal groupsWindows Firewall exceptionsFile store ACLsIIS virtual directoriesLocal applicationsLync Server 2013 services (status, auto start modes, etc.)

Test-CsDatabaseChecks and verifies connectivity to the SQL Server and returns database version infoCould be run against local or remote SQL ServerDeployment Validation8Slide Objective:

Notes:Addition to setup and deployment logs, two cmdlets can be used to validate successful deploymentTest-CsComputer: Checks and validates the local configurationLocal groupsWindows Firewall exceptionsFile store ACLsIIS virtual directoriesLocal applicationsLync Server 2013 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 ServerMake sure to familiarize yourself with the following cmdletsTest-CsComputerTest-CsDatabaseThese are probably more useful after the fact to check to see if something has become broken

# 2011-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.Separate set-up bitsIndependent install experienceInstall and then configureTopology builder configures only discovery URLsConfiguration done by its own PowerShell moduleImport-Module OfficeWebAppsUse Certificate Friendly Name in New-OfficeWebAppsFarmOffice Web Apps Installation

9Slide Objective:

Notes:Office Web Apps is the only role that is not fully integrated with Lync 2013 bootstrapper (Office Web Apps requires manual installation) Has a separate setup package by the Office teamPart of an Office Web Apps suiteTopology Builder:Office Web Apps discovery URL is configured in the topologyLync Pools associated with the Office Web Apps Server/poolsMultiple Pools/sites can share the same Office Web Apps Server/pool

Installation and configuration done manually by import-module OfficeWebAppsCertificate is specified with its Friendly Name. This must be taken into consideration if the Certificate friendly name is different from the Subject NameUsed to be called the WAC Server so don't be surprised if you see that name hanging around somewherePoint out the check box regarding the external name of your Office Web Apps ServerOffice Web Apps can be a farm of servers behind an HLBWe will cover this role more later this week# 2011-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.Lync Server 2013 Hardware and Software Requirements# 2011-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.Topology and function changes that affect hardware sizingCollocated Audio/Video (A/V) MCUCollocated XMPP gatewayNew CPU-intensive features (Multiview, HD conferencing, etc.)

Hardware and Software RequirementsFront-End Server11Slide Objective:

Notes:There are a lot of changes to the Front-End boxes with Lync 2013There is no option for dedicated A/V Pools anymore with Lync 2013. A/V MCU always collocated

New performance overheadsXMPP translating gateway service is collocated with Front-End ServersEstimations For the XMPP component estimations that we see, if we have to support all 12.5K users for XMPP interoperability, @ 20 contacts per user (very realistic in the Large Enterprise scenario), we would end up at around 12.5K users * 20 * 15KB/contact ~ 4-5 GB of memory required for the XMPP gateway process (collocated with the Front End Server)

Although its not on the slide, you might mention:The number of Front-End Servers that can be in a single EE pool will likely change. The final numbers will be determined at RTMWith the registration and presence data (business logic) on Front-End Servers, the SQL back end can support more FEsThe number of users that each EE Front-End supports will likely change. The final numbers will be determined at RTM

# 2011-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.Hardware requirementsFinal numbers will be available at product release Hardware and Software RequirementsEdge Servers, Stand-alone Mediation Servers, and DirectorsHardware Component Recommended CPU64-bit dual processor, hex-core, 2.26 gigahertz (GHz) or higherIntel Itanium processors are not supported for Lync Server server rolesMemory32 gigabytes (GB)DiskEight or more 10,000-RPM hard disk drives with at least 72 GB free disk space.

Two of the disks should use RAID 1, and six should use RAID 10

- OR -

Solid state drives (SSDs), which provide performance similar to eight 10,000-RPM mechanical disk drivesNetworkOne dual-port network adapter, 1 gigabit per second (Gbps) or higher (two recommended, which requires teaming with a single MAC address and single IP address)12Slide Objective:

Notes:New features like Mobility, multiview, and HD conferencing requires more processing power and new enterprise-grade CPUsSingle 1 GB NIC is supported, but teamed 1 GB network interface cards (NICs) or 10 GBE is recommended given that multiview w and HD conferencing requires more bandwidthSupported minimum memory is 16 GB, but 32 GB is recommended (when 12.5 K users are enabled and using all workloads, the memory footprint is about 24 GB)Consider disk space requirements for Front-End ServersAdditional SQL InstanceLyncLocalInitial DB size of 4 GB for all databases# 2011-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.NIC RecommendationsMinimum supported NIC: Dual-port network adapter 1Gbps (Ethernet)Recommended: 2 Dual Ethernet 1Gbps (Teamed Ethernet)Operating SystemWindows Server 2008 R2 SP1 or above for Lync Server rolesMicrosoft Windows Server 2012Microsoft SQL ServerSQL Server 2008 R2 SP1 and aboveSQL Server 2012Lync Server 2013 automatically installs SQL Server 2012 Express (Denali) on each Front EndSupported Back-End High Availability is SQL MirroringNo support for Always On or SQL ClusteringHardware and Software RequirementsNetwork, Operating System, SQL13Slide Objective:

Notes:Network100 Mbps NIC is not supportedIf the A/V conferencing being utilized a lot, consider 4x1 Gbps NIC Teaming

OS SupportWindows 2008 R2 SP1 and aboveWindows Server 2012 will be supported as well when the product shipped

SQL SupportSQL Server 2008 R2 SP1 and aboveSQL Server 2012 is supportedNew high-availability features like Always on or legacy single copy SQL clustering are not supportedSQL back end High Availability is supported with SQL Mirroringmore details can be found on Module 18: High Availability and Disaster RecoverySQL Clustering is only supported in migration scenarios and should be switched to SQL mirroring as soon as migration completes.The product planning teams chose to do mirroring, since it works in both versions of SQL. If you read the release notes for SQL 2012, they indicate that you should not build applications based on SQL mirroring, as it will eventually be end of life. However, due to timing, we need to choose a common HA option between SQL 2008 and SQL 2012. This meant that SQL always on could not be selected. We did not want to force all customers to have to use SQL 2012.# 2011-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.Software PrerequisitesWIFServer support for server-to-server authentication scenariosDownload: http://support.microsoft.com/kb/974405 PowerShell v3Part of Windows Management Framework 3.0Download: http://www.microsoft.com/en-us/download/details.aspx?id=29939Lync 2010 November Cumulative Update on Lync 2010 ServersDownload: http://support.microsoft.com/kb/2493736Microsoft .NET Framework 4.5included in the Lync Server Setup MediadotNetFx45_Full_x86_x64.exe.NET FW 4.5 RC QFE: NDP45-KB2713435-x64.exeWindows Desktop ExperienceAll Front-End ServersRequired for supporting the media stack on A/V Conferencing and applications like Call Park, Response Group, and Conferencing AnnouncementHardware and Software RequirementsSoftware Prerequisites14Slide Objective:

Notes:New required components:PowerShell v3Windows Identity FoundationNovember Cumulative Update for Lync 2010 Servers to interoperability with Lync 2013.NET Framework 4.5 is required

Same requirements as Lync Server 2010Windows Desktop ExperienceWindows Media Format Runtime all Front-End Servers to support the media stack (to run the Windows Media Audio (.wma) files that the Call Park, Announcement, and Response Group applications play for announcements and music)

MSMQ# 2011-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.Admin Tools and Core ComponentsWindows 7 (x64 only), Windows Server 2008 R2, Windows Server 2012Microsoft Windows PowerShell v3 requiredActive Directory (AD) Forest/Domain Functional Level Windows Server 2003 (Native mode only)Windows Server 2008 Windows Server 2008 R2Windows Server 2012InfrastructureHardware Load Balancer (HLB) for Web ServicesEven with DNS load balancing deployed, HWLB is still required for HTTP/HTTPS trafficHardware Load Balancer Partners for Lync Serverhttp://technet.microsoft.com/en-us/lync/gg269419Hardware and Software RequirementsAdmin Tools, Active Directory, Infrastructure15Slide Objective:

Notes:For admin toolsWindows 7 and higherWindows 8 will be supported

AD functional level requirementsSame as Lync 2010but Windows Server 2012 will be supported as well when the product ships

Hardware Load Balancer still required for web traffic even for DNS Load Balanced poolsARRApplication Request Routing is NOT supportedUC OIP site: http://technet.microsoft.com/en-us/lync/gg269419# 2011-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.Server VirtualizationSupport for all Lync Server 2013 workloadsSupported on Standard Edition and Enterprise Edition and all other rolesSupported HypervisorsMicrosoft Windows Server 2008 R2 SP1 Microsoft Hyper-V minimum (guest and host)VMWare ESX 5Take advantage of Windows Server 2012 Hyper-V (3.0)New large vCPU with NUMA architecture and large memory support

Unsupported virtualization featuresQuick/Live migrationDynamic memory (being tested)VM replicaVirtualization support in Lync 2013 Planning ToolFinal numbers will be available at product release16Slide Objective:

Notes:There are a lot of improvements on client side virtualization, and those will be covered in the Module 17: Virtual Desktop Infrastructure

SupportedVirtualization is fully supported on all server roles for all workloadsHyper-V 2.0 shipped with the Windows Server 2008 R2 and VMWare ESX 5 is supportedHyper-V 3.0 on Server 2012 will also be supported with the new vCPU and memory support

Not SupportedQuick and Live Migration Servers need to be rebooted after migrated to a new host (same for vMotion on VMWare)VM Replica feature on Hyper-V 3.0 is not supported as a Lync Disaster Recovery Scenario

Lync 2013 Planning Tool support planning for virtualization# 2011-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.Lync Server 2013 Manageability Tools# 2011-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.Planning ToolA step-by-step tool to plan and design all the Lync infrastructure including hardware sizing with the user modelsNew Supported Features High Availability and Disaster RecoveryIPv6MobilityExchange Unified Messaging (UM)Exchange 2013 archiving integrationPersistent ChatXMPP federationMedia bypassMulti-view and HD conferencingVoice applications (Call park, Response Groups)Planning Tool

18Slide Objective:

Notes:New planning tool with Lync Server 2013 includes many features that need capacity planning as listed on the slide# 2011-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.Support for Lync 2013 topologySupport for the new featuresPersistent ChatOffice Web Apps High Availability and Disaster RecoveryPaired poolsSQL mirroringMerge and manage Lync 2010 topologyM:N RoutingTrunksIPv6XMPPLegacy Topology Builder should be retiredTopology Builder

19Slide Objective:

Notes:New topology builder supports all the configuration items retained from the Lync 2010 Server, and many new fancy features are introduced in Lync 2013 to support a homogenous deployment experienceLync 2010 Topology builder should not be used after the Legacy Topology Merge operation, and the legacy topology builder should be retired# 2011-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.Demo: Manageability Tools in Lync Server 2013 Slide Objective:

Notes:Optional Demo:Go through the following tools and depending on the time:Lync Server 2013 Planning ToolUse planning tool to configure two sites, and show the audience the output including HW requirements, Ports, certificates and DNS records

Topology BuilderFocus on the new features like Office Web Apps, Persistent Chat, XMPP, and High Availability features# 2011-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.Q & A# 2011-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. 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.11/18/201322# 2011-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.