Microsoft Lync Server 2013Multitenant Hosting PackDeployment GuideMicrosoft Lync Server 2013 Multitenant Hosting PackPubli...
This document is provided “as-is”. Information and views expressed in this document, includingURL and other Internet Web s...
Contents1 Overview of the Microsoft Lync Server 2013 Multitenant Hosting Pack ................................. 11.1 Under...
4.2 Flexible Systems Scaling.................................................................................................
8.3 Update Active Directory for Hosted Management Services............................................ 388.4 Global Client...
10.2.4 Configure Federation Between Lync Server On-Premises and Lync ServerMultitenant Hosting Pack..........................
13.3.3 Join Conference by Using Conferencing Dial-out.................................................. 6413.3.4 Audio Bri...
11 Overview of the Microsoft Lync Server 2013Multitenant Hosting PackMicrosoft® Lync® Server 2013 Multitenant Hosting Pack...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide21.2 How to get the Lync Server 2013 Multitenant Hosti...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide3Feature Comparison: Lync Server 2010 Multitenant Host...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide4Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide5Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide6Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide7Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide8Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide9Feature Lync Server2010Hosting PackLync Server 2013Ho...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide10Feature Lync Server2010Hosting PackLync Server 2013H...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide11Feature Lync Server2010Hosting PackLync Server 2013H...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide12Feature Lync Server2010Hosting PackLync Server 2013H...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide13each server, and related software requirements, such...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide1480,000 user pool with eight Front End Servers and on...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide15You can also deploy the Lync Server Multitenant Host...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide162.5 Active Directory Domain Services RequirementsDep...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide173 Understanding the Lync Server 2013 MultitenantHost...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide183.3 Lync Server 2013 Control PanelSome enhancements ...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide19Server allocation provides basic redundancy for each...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide20Windows Server 2008 R2 with SP1 Enterprise (required...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide21The following table lists the load balancing technol...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide224. Run the Microsoft Lync Server 2010 Best Practices...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide23o Install or Update Lync Server System - complete st...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide24Migrate-TenantOrgV2.ps1 –TenantOrg <Tenant OU Name> ...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide25##.Parameter MappingFile##.Parameter MoveConferenceD...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide26write-richlog -strLogText " Param - Move conference ...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide27write-richlog -strLogText "Adding $($user.RegistrarP...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide28{write-richlog -strLogText "Starting move of$($User....
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide29write-richlog -strLogText "Force moving of$($User.Si...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide30write-richlog -strLogText " Numberof user found :$($...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide316.1 Deploying the TopologyThis section provides inst...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide326.2 Change the Name and Domain of the Server Running...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide336.4 Install the Lync Server 2013 Multitenant Hosting...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide34Completed Topichttp://technet.microsoft.com/en-us/li...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide35the following sections of this document after you de...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide36The “Bootstrap local machine” process assumes that a...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide37“Deploying External User Access” in the TechNet Libr...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide388.2 Modify Lync Server Management ShellThe Lync Serv...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide39following cmdlet demonstrates how to configure the A...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide40If the IP PBX is not qualified for Lync Server you c...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide418.8 Configuring MobilityMobility support for your Ly...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide42Alternatively, to open the Active Directory Module f...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide43we stored previously in the $OU variable). Notice th...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide44Get-CsTenant | Format-Table -AutoSize Id,DomainsId D...
Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide45TenantExtensionDigits The number of digits to be use...
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide
Upcoming SlideShare
Loading in …5
×

Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide

3,524 views

Published on

Guía de despliegue de Lync 2013 Multitenant

Published in: Technology
  • Be the first to comment

Microsoft lync server_2013_multitenant_pack_for_partner_hosting_deployment_guide

  1. 1. Microsoft Lync Server 2013Multitenant Hosting PackDeployment GuideMicrosoft Lync Server 2013 Multitenant Hosting PackPublished:June2013Document Version:1.2, 06/14/13Changes in this version:Updated section 7.5 to remove the following:“In addition, create one external DNS record for the FQDN of the Front End pool foreach external IP address of the Front End Servers.”Abstract:The Microsoft Lync® Server 2013 Multitenant HostingPackfeatures include integrationwith Microsoft Exchange Server, Microsoft Outlook, and other communication technologies. TheLync Server2013 Multitenant Hosting Pack enables customers to manage geographicallydispersed offices and mobile users in a way that reduces travel expenses, while maintaininghighly collaborative team environments. This document describes the Lync Server 2013Multitenant Hosting Pack, and includes information about how to deploy and configure it.
  2. 2. This document is provided “as-is”. Information and views expressed in this document, includingURL and other Internet Web site references, may change without notice.Some examples depicted herein are provided for illustration only and are fictitious. No realassociation or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in anyMicrosoft product. You may copy and use this document for your internal, reference purposes.Copyright © 2012 Microsoft Corporation. All rights reserved.
  3. 3. Contents1 Overview of the Microsoft Lync Server 2013 Multitenant Hosting Pack ................................. 11.1 Understanding the Lync Server 2013 Multitenant Hosting Pack....................................... 11.2 How to get the Lync Server 2013 Multitenant Hosting Pack Software ............................. 21.3 What’s Available in the Lync Server 2013 Multitenant Hosting Pack................................ 21.3.1 Comparing versions of the Lync Server Multitenant Hosting Pack............................. 21.4 Known Issues ................................................................................................................... 122 Determining Your Infrastructure Requirements .................................................................... 122.1 Hardware Requirements.................................................................................................. 132.1.1 Hardware Requirements for Servers Running Lync Server 2013 .............................. 132.1.2 Hardware Requirements for Back End Servers and Other Database Servers ........... 132.2 Integration with Exchange Server.................................................................................... 142.3 Network Infrastructure Requirements ............................................................................ 152.4 Domain Name System (DNS) Requirements.................................................................... 152.5 Active Directory Domain Services Requirements............................................................ 162.6 Load Balancing Requirements ......................................................................................... 162.7 Port and Protocol Requirements ..................................................................................... 162.8 Certificate Requirements................................................................................................. 162.9 Software Requirements................................................................................................... 162.10 Reverse Proxy Configuration........................................................................................ 163 Understanding the Lync Server 2013 Multitenant Hosting Pack ........................................... 173.1 About Lync Server Multitenant Hosting Pack User Types ............................................... 173.2 Lync Server Multitenant Hosting Pack Server Roles........................................................ 173.3 Lync Server 2013 Control Panel....................................................................................... 184 Planning for the Lync Server Multitenant Hosting Pack......................................................... 184.1 Example Topology............................................................................................................ 184.1.1 About the Example Topology .................................................................................... 18
  4. 4. 4.2 Flexible Systems Scaling................................................................................................... 204.3 Role-specific Load Balancing and Fault Tolerance........................................................... 205 Migrating from the Lync Server 2010 Multitenant Hosting Pack........................................... 215.1 Migration Prerequisites ................................................................................................... 215.2 Performing the Migration................................................................................................ 225.3 Migrating Tenants............................................................................................................ 235.3.1 Known Limitations..................................................................................................... 245.3.2 Prerequisities............................................................................................................. 245.3.2.1 PoolMapping.csv ............................................................................................... 245.3.2.2 Migrate-TenantOrgV2.ps1................................................................................. 246 Deploying a New Lync Server 2013 Multitenant Hosting Pack Deployment.......................... 306.1 Deploying the Topology................................................................................................... 316.2 Change the Name and Domain of the Server Running Lync Server ................................ 326.3 Installation Media............................................................................................................ 326.4 Install the Lync Server 2013 Multitenant Hosting Pack................................................... 337 Define the Topology ............................................................................................................... 347.1 Create a Front End Pool................................................................................................... 357.2 Configure Front End Servers............................................................................................ 357.3 Update the SQL Server Databases................................................................................... 367.4 Add Server Roles.............................................................................................................. 367.5 Deploy Edge Servers ........................................................................................................ 367.6 Define the Edge Topology................................................................................................ 377.7 Monitoring....................................................................................................................... 378 Post-Installation Configuration............................................................................................... 378.1 Install Additional Components ........................................................................................ 378.2 Modify Lync Server Management Shell........................................................................... 38
  5. 5. 8.3 Update Active Directory for Hosted Management Services............................................ 388.4 Global Client Policies for Address Book Web Query........................................................ 388.5 Lync Server Dial Plans ...................................................................................................... 398.6 Integration with on-premises PBX or Call Center............................................................ 398.7 Changing the Root OU ..................................................................................................... 408.8 Configuring Mobility ........................................................................................................ 419 Provisioning Tenant Organizations......................................................................................... 419.1 Create and Secure the Organizational Units.................................................................... 419.2 Set TenantId and ObjectId ............................................................................................... 419.2.1 Set the DomainUrlMap Attribute.............................................................................. 439.3 Add UPN Suffix to Tenant OU .......................................................................................... 439.4 Create Tenant SIP Domain............................................................................................... 439.5 Configure Exchange Email................................................................................................ 449.6 Configure Exchange Unified Messaging........................................................................... 449.6.1 Create Tenant Exchange Dial Plan and Exchange UM Mailbox Policy ...................... 449.6.2 Assign Tenant Dial Plan to All Available Exchange UM Servers ................................ 459.6.3 Update Exchange UM/Lync Server Integration Configuration.................................. 459.6.4 Create Lync Server Contacts for Exchange UM Subscriber Access ........................... 4610 Configuring Federation........................................................................................................ 4810.1.1 Enabling a Tenant for Federation.......................................................................... 4810.1.2 Getting Tenant Federation Settings ...................................................................... 4810.2 Configure Tenant Federation Settings.......................................................................... 4910.2.1 Configuring federation with an on-premises deployment in another organization4910.2.2 Configuring federation with other Hosting Pack deployments............................. 5010.2.3 Configuring federation with a Lync Online tenant ................................................ 51
  6. 6. 10.2.4 Configure Federation Between Lync Server On-Premises and Lync ServerMultitenant Hosting Pack.................................................................................................... 5110.2.5 Adding Domains to the Tenant Block List.............................................................. 5110.2.6 Clearing the Tenant Block List ............................................................................... 5210.2.7 Clearing the Tenant Allow List............................................................................... 5210.2.8 Resetting Tenant to Allow All Domains Except Those Listed on the Block List..... 5211 Create Tenant DNS Records ................................................................................................ 5211.1 Create Tenant Meeting Simple URLs............................................................................ 5311.1.1 Import the Required Modules for Windows PowerShell ...................................... 5311.1.2 Configure the Simple URL to Use the Back-end Database .................................... 5411.1.3 Get Tenant Organization ID................................................................................... 5411.1.4 Create the Simple URLs for a Tenant Organization............................................... 5511.1.5 Set the Simple URL DNS Name.............................................................................. 5512 Provisioning Tenant Users................................................................................................... 5612.1 Enable Tenant Users for Exchange UM........................................................................ 5612.2 Set User TenantID, GroupingID, and ObjectId.............................................................. 5712.2.1 Known Issue........................................................................................................... 5712.3 Configure the user Base Simple URL with the Tenant Organization’s Base URL.......... 5912.4 Enable Tenants for Lync Server.................................................................................... 6012.5 Set Address Book Policy for Tenant User ..................................................................... 6012.6 Providing the Lync Server 2013 Interface for online meeting...................................... 6013 Overview of the Audio Conferencing Provider ................................................................... 6113.1 Integrating with Audio Conferencing Provider............................................................. 6113.2 Provisioning with Audio Conferencing Provider........................................................... 6213.3 Integration Workflows with Audio Conferencing Provider.......................................... 6313.3.1 Create and Schedule a Web Conference............................................................... 6313.3.2 Activate a Conference ........................................................................................... 63
  7. 7. 13.3.3 Join Conference by Using Conferencing Dial-out.................................................. 6413.3.4 Audio Bridging Sequence....................................................................................... 6513.3.5 Use Audio Controls from Lync Server.................................................................... 6513.4 Known Issues................................................................................................................ 6614 Code Samples...................................................................................................................... 6714.1 Prerequisites................................................................................................................. 6714.2 Dependencies............................................................................................................... 6714.3 Provision a Tenant Organization .................................................................................. 6814.3.1 Create and Secure Organizational Unit................................................................. 6814.3.2 Enable the Tenant Organization............................................................................ 6814.3.3 Add an Additional SIP Domain to the Tenant Organization.................................. 7014.3.4 Adding Domains to the Tenant Allow List for Federation..................................... 7214.3.5 Adding Domains to the Tenant Block List for Federation ..................................... 7414.3.6 Removing Domains from the Tenant Allow List for Federation............................ 7514.3.7 Removing Domains from the Tenant Block List for Federation ............................ 7614.3.8 Allowing all Domains for Tenant Federation......................................................... 7714.3.9 Enabling a Tenant for Federation.......................................................................... 7814.3.10 Enabling Federation between two Hosted Tenants.............................................. 7914.4 Provision Tenant Users................................................................................................. 81
  8. 8. 11 Overview of the Microsoft Lync Server 2013Multitenant Hosting PackMicrosoft® Lync® Server 2013 Multitenant Hosting Pack is a unified communications (UC) solution fortelecom and hosting providers. Unified communications is a way for telecom and hosting providers toexpand their service offering to their current customers.The Lync Server 2013 Multitenant Hosting Pack features include integration with Microsoft ExchangeServer, Microsoft Outlook®, and other communication technologies. The Lync ServerMultitenant HostingPack enables customers to manage geographically dispersed offices and mobile users in a way thatreduces travel expenses, while maintaining highly collaborative team environments. This increasedintegration of communication channels translates to improved organizational flexibility that is oftendifficult to find in larger enterprise organizations.For more information and additional resources about Lync hosting, see “Partner Hosted Lync”athttp://go.microsoft.com/fwlink/p/?LinkId=308942 and “Microsoft Lync Server Multitenant Pack forPartner Hosting Resources”http://go.microsoft.com/fwlink/p/?LinkId=306561.1.1 Understanding the Lync Server 2013 Multitenant Hosting PackThis section describes how the Hosting Pack integrates with the core system infrastructure. To betterunderstand the overall system it helps to define unified communications, Lync Server, and the LyncServer Multitenant Hosting Pack.Unified communications (UC) is a system that integrates platforms for communicationsincluding email, voice mail, telephony, instant messaging (IM), and voice and videoconferencing. UC solutions are installed on the client’s core systems, adding a UC layer to theoverall infrastructure. This UC layer adds integration and interconnects the communicationssystems with the organization’s core system services.Microsoft Lync Server2013 is a family of servers functioning as UC servers thatintegrate with allthe Microsoft line-of-business software. Lync Server adds these new communication possibilitieswithin the organization. A Lync Serverand Exchange Server layer provide system integrationbetween Exchange and other communication systems like IM, presence, voice and video calls,desktop sharing, file transfer, and ad hoc conferences.Microsoft Lync Server 2013 Multitenant Hosting Packis a special deployment configurationscoped for hosting or telecom services providers. The solution enables service providers to hostmultitenant Lync Serverinstances shared across multiple customer environments. In addition,the Lync ServerMultitenant Hosting Pack solution includes an add-on layer that allows ourpartners to build communication packages that use the Lync Server Multitenant Hosting Pack tointegrate with the core layer.
  9. 9. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide21.2 How to get the Lync Server 2013 Multitenant Hosting PackSoftwareA license is required to use the software. To download and install the Lync Server 2013 MultitenantHosting Packsoftware, you need to log on to the Microsoft Volume Licensing Service Center athttp://go.microsoft.com/fwlink/?LinkId=238381.1.3 What’s Available in the Lync Server 2013 Multitenant HostingPackThe features that integrate with other components and applications include the following:Presence A collection of attributes that provides an indication of a persons status, activity,location, willingness to communicate, and contact information.Instant messaging (IM) A form of real-time text-based communication.Data and desktop sharing A feature that allows users to share files, use whiteboard, anddisplay their desktop to a meeting or to conversation participants.Conferencing Two-way video and audio transmissions between users in multiple locations.Unified Messaging This feature is available only in combination with Microsoft ExchangeServer. An application that consolidates a users voice mail, fax, and email into one mailbox, sothat the user only needs to check a single location for messages, regardless of type. The emailserver is the platform for all types of messages, making it unnecessary to maintain separatevoice mail and email infrastructures.Private branch exchange (PBX) replacement UC integration with Voice over Internet Protocol(VoIP) systems can replace traditional phone exchange systems.Lync ServerMultitenant Hosting Pack partner feature set includes:Appliances Hand and head set I/O devices.Conferencing server gateway video Real-time IP video, voice, and data services.Audio conferencingprovider Integration with hosted conferencing systems.Short Message Service (SMS) Text messaging systems used by phones and mobilecommunication systems.1.3.1 Comparing versions of the Lync ServerMultitenant Hosting PackThe following table compares the features available in the Lync Server Multitenant Hosting Pack2010and 2013.
  10. 10. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide3Feature Comparison: Lync Server 2010 Multitenant Hosting Pack and Lync Server 2013 Multitenant Hosting PackFeature Lync Server2010Hosting PackLync Server 2013Hosting PackPresence1 to 1 and multi-party IM/Presence Yes YesContacts list Yes YesAddress Book Service Web Query service Yes YesDistribution List Expansion protocol (DLX) Yes YesInstant Messaging (IM)Point-to-point IM Yes YesMultiparty/Group IM Yes YesPersistent Chat No NoPC to PC audio/video dial out calling Yes YesFile transfer Yes YesMobile VoIP to PC audio No YesClick to communicate from Office apps Yes YesInteractive contact card in Office 2010 and Office 2013 Yes YesLync skill search in SharePoint Server (on-premises) Yes YesLync skill search in SharePoint Online No No
  11. 11. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide4Feature Lync Server2010Hosting PackLync Server 2013Hosting PackPrivacy mode No NoClient SupportLync Client 2010 and Lync Client 2013 Yes YesWeb app for joining scheduled meetings Yes YesRich attendee client (joining meetings) Yes YesMac attendee client Yes YesCWA (2007 R2) No NoOC 2007 R2 No NoLync phone edition (Lync-based IP phones) No NoSupport expected in afuture releaseLync Attendant client (receptionist rich client) No YesLync Server 2010versionCommunicator Mobile (Windows Phone 6.x) No NoLync Mobile No YesLync desktop client Yes YesMac Messenger Yes YesAttendee (meeting only) Yes YesLync Mobile clients(for Android, Windows Phone, iPhone)Yes(If provisioned)Yes(If provisioned)
  12. 12. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide5Feature Lync Server2010Hosting PackLync Server 2013Hosting PackConferencing and Online MeetingsMeeting attendee capacity 250 250Point-to-point audio/video Yes YesVideo conferencing over IP Yes YesAudio conferencing over IP only Yes YesMeeting recording Yes YesRegistration No NoPublic Events page No NoCustomer branding No NoCustomer invitations No NoManaged Q&A No NoVirtual breakout rooms No NoEasy Assist No NoDesktop sharing Yes YesApplication sharing Yes YesWhite boarding and annotation Yes YesOffice document upload No No
  13. 13. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide6Feature Lync Server2010Hosting PackLync Server 2013Hosting PackPowerPoint upload Yes YesPolling Yes YesUnauthenticated in Web App (reach) Yes YesUnauthenticated attendee (rich client) Yes YesScheduled conferences using Outlook plugin Yes YesRound table support Yes YesLobby Yes YesIntegration with select partners for PSTN audio conferencing(ACP)Yes YesProvisioning for approved ACP partners for Office 365customersNo NoScheduling an online meeting in OWA No YesClient side recording and playback Yes YesCloud side recording and playback No NoAuthenticated experience in Web app (reach) No NoGenerate a link to a scheduled meeting via web page Yes YesPSTN audio conferencing in MCUs Yesvia audio conferencingproviderYesvia audio conferencingprovider1:1 Chat Yes Yes
  14. 14. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide7Feature Lync Server2010Hosting PackLync Server 2013Hosting PackBackstage/Content Preview for Presenters Yes YesMute / Unmute all attendees No YesMute / Unmute individual attendees Yes YesIn-meeting Attendee Permission Controls Yes YesInteroperability with on-premises video conferencing systems No Yesvia 3rdpartyMultimedia, JPEG, Text Page, Web Page,Screen snapshot (Desktop Annotation)No YesPSTN dial-out from scheduled meetings Yesvia audio conferencingproviderYesvia audio conferencingproviderAd-hoc audio dial-out conferencing YesVoIP via SIP TrunkYesVoIP via SIP Trunk“Meet now” audio dial-out conferencing Yesvia audio conferencingproviderYesvia audio conferencingproviderScheduled audio dial-out conferencing Yesvia audio conferencingproviderYesvia audio conferencingproviderSharingPoint-to-point/multiparty data conference (white boarding) Yes YesPoint-to-point/multiparty file share Yes YesPoint-to-point/multiparty desktop and application sharing Yes Yes
  15. 15. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide8Feature Lync Server2010Hosting PackLync Server 2013Hosting PackPoint-to-point/multiparty Microsoft PowerPoint® slide sharing Yes YesPolling Yes YesIntegrationMicrosoft Outlook integration for IM, presence, calendar(with users on the same hosting partner)Yes YesMicrosoft SharePoint® integration for IM, presence(with users on the same hosting partner)Yes YesPublic IM Connectivity and FederationInter-tenant federation Yes YesFederation with Extensible Messaging and Presence Protocol(XMPP)No NoIM/P/A/V Federation with Office Communications Server,Lync Server, Lync OnlineYes YesIM/P/A/V with Windows Live Messenger / Skype No YesIM/P and voice with Skype No YesPublic IM connectivity and presenceAOL®, Yahoo!®, Windows LiveNo NoIBM Sametime federation No NoCalling featuresPublic switched telephone network (PSTN) calling via Lyncincoming and outgoingYes Yes
  16. 16. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide9Feature Lync Server2010Hosting PackLync Server 2013Hosting PackAd-hoc PSTN dial-out for meetings No NoCall controlshold, transfer, forward, simultaneous ringYes YesVoice policies Yes YesAccess to Exchange Online voice mail No NoTeam call No YesDelegation (boss-admin) for Voice No NoCall park No NoOutgoing DID manipulation No NoE-911 No NoDial plans & Policies No NoIP desk phone support No YesResilient Branch Office Appliance No NoCall Admissions Control (CAC) No NoSupport for Analog devices (e.g. FAX) No NoResponse groups No Yesvia 3rdpartyPrivate Line (secondary DID for execs) No NoDirect connectivity with PBX via gateways Yes Yes
  17. 17. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide10Feature Lync Server2010Hosting PackLync Server 2013Hosting PackDirect SIP for audio with on-premises IP-PBXs No YesDirect SIP for signaling (presence updates) with on-premises IP-PBXNo YesRCC (click-to-call) with on-premises PBX No NoMalicious call trace No NoUnassigned Number No NoNetwork QoS – DSCP No NoMedia path optimization No NoPhone number management No NoCDR & billing reporting Yes YesIntegration with call center solutions (Aspect) No YesTeam call No YESDelegation No YesPrivate line (secondary Direct Inward Dialing (DID)) No NoCall park No NoOutgoing DID manipulation No NoVoice featuresPrivate dial plans No No
  18. 18. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide11Feature Lync Server2010Hosting PackLync Server 2013Hosting PackHosted Exchange Unified Messaging (UM) for voice mail Yes YesACP Integration with select carriers Yes YesVoice integration with select carriers Yes YesSecurity and ArchivingIM & media encryption Yes YesIM filtering Yes YesAnti-malware scanning for meeting content and file transfers Yes YesIM archiving (server side) No YesSharePoint and Exchange Co-existencePresence Integration with Exchange/SP on-premises Yes YesPresence integration with Exchange/SP online Yes YesOn-premise UM integration with Exchange Online No NoUM integration with Exchange on-premises Yes YesHybrid with Lync OnlineServer/cloud co-existence (split domain) on user basis (someusers on-premises, some users online)No NoSplitting workloads (eg. Voice on-premises, IM&P in the cloud) No NoAdministration and Manageability
  19. 19. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide12Feature Lync Server2010Hosting PackLync Server 2013Hosting PackWindows PowerShell support Yes YesLync Server Control Panel UI No NoFeature Configurability Per User Yes YesAttendee/User Reporting No NoReporting (CDR, QoE) Yes YesSupport for 3rdparty applicationsClient automation APIs (client side) Yes YesServer side APIs Yes YesSupportTenant User support No NoIT Support Yes Yes1.4 Known IssuesThe Lync Update Installer requires write permissions to the folder in which it is run. If you startthe installation from a read-only folder, the installer will present a blank list of updates to apply,and the installation will not complete successfully.You should copy the installation files to a location that is not read-only, and run Setup from thatlocation.2 Determining Your Infrastructure RequirementsAll servers running Lync Server 2013 must meet certain minimum system requirements. Systemrequirements for Lync Server 2013 include the server hardware, the operating system to be installed on
  20. 20. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide13each server, and related software requirements, such as Windows® updates and other software thatmust be installed on the servers.2.1 Hardware RequirementsLync Server 2013 server roles and computers running Lync Server administrative tools require 64-bithardware.The specific hardware used for a Lync Server 2013 deployment can vary depending on size and usagerequirements. This section describes the recommended hardware. Although these arerecommendations, not requirements, using hardware that does not meet these recommendations canresult in a significant impact on performance as well as other problems.2.1.1 Hardware Requirements for Servers Running Lync Server 2013The following table describes the recommended hardware for all servers where you plan to install LyncServer 2013. These recommendations are based on a user pool of 80,000 users with eight Front EndServers and one Back End Server.Hardware Recommendations for Servers Running Lync Server 2013Hardware component RecommendedCPU One of the following:64-bit dual processor, quad-core, 2.0 GHz or higher64-bit 4-way processor, dual-core, 2.0 GHz or higherIntel Itanium processors are not supported for Lync Server 2013 server roles.Memory 16 GBDisk Local storage with at least 72 GB free disk space on a 10,000 RPM disk driveNetwork 1 network adapter required (2 recommended), each 1 Gbps or higherThese recommendations are based on a maximum of 39,000 external users per Front End pool (whichfollows the user model of 80,000 users per Front End pool, with 30% of users connecting externally and1.5 multiple points of presence (MPOP).2.1.2 Hardware Requirements for Back End Servers and Other DatabaseServersThe requirements for the Back End Server and other database servers are similar to those of serversrunning Lync Server 2013, except that Back End Servers require additional memory. The following tabledescribes the recommended hardware for a Back End Server or other database servers, based on an
  21. 21. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide1480,000 user pool with eight Front End Servers and one Back End Server containing all databases requiredfor your Lync Server deployment.Hardware Recommendations for Back End Servers and Other Database ServersHardware component RecommendedCPU One of the following:64-bit dual processor, quad-core, 2.0 GHz or higher64-bit 4-way processor, dual-core, 2.0 GHz or higherIntel Itanium processors are not supported for Lync Server 2013 server roles.Memory 32 GB recommended for Back End Server (with or without collocated Archivingand Monitoring databases), 16 GB recommended for Archiving and Monitoringdatabase (not collocated with the Back End Server).Disk Local storage with at least 72 GB free disk space on a 10,000 RPM disk driveNetwork 1 network adapter required (2 recommended), each 1 Gbps or higher2.2 Integration with Exchange ServerThe Lync Server 2013 Multitenant Hosting Packsupports integration with Exchange Server 2010 SP3 orlatest Service Pack and Exchange 2013. You can configure integration with both hosted Exchange andExchange Server on-premises. This includes support for Exchange Unified Messaging (UM) for: presence,IM, workload, conferencing, and VoIP servers and services.To configure integration with hosted within the same hosting pack deployment cloud, follow the sameprocess for a Lync Server 2013 on-premises deployment. For more information, see “IntegratingMicrosoft Lync Server 2013 and Microsoft Exchange Server 2013” at http://technet.microsoft.com/en-us/library/jj688098.aspx.For more information about configuring integration with Exchange Unified Messaging, see the followingtopics:“Deploying On-Premises Exchange UM to Provide Lync Server 2013 Voice Mail” athttp://technet.microsoft.com/en-us/library/gg398768(v=ocs.15).aspx.“Providing Lync Server 2013 Users Voice Mail on Hosted Exchange UM” athttp://technet.microsoft.com/en-us/library/gg425807(v=ocs.15).aspx.To integrate the hosting pack with Exchange on-premises, you need to establish a MPLS or VPNconnection to the on-premises network, and then establish an Active Directory trust relationshipbetween the on-premises Active Directory and you’re the Active Directory of the hosting provider wherethe hosting pack is deployed.
  22. 22. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide15You can also deploy the Lync Server Multitenant Hosting Pack into a multi-tenant Exchange Server 2010forest as long as the Exchange Server 2010 deployment is in a supported state following the guidancedescribed here: http://technet.microsoft.com/en-us/exchange/hh563895.aspx.2.3 Network Infrastructure RequirementsThe requirements for your network infrastructure will vary greatly depending on your deployment, thenumber of tenant users you need to support, and the features used by those tenants. For generalinformation about network infrastructure requirements for Lync Server 2013, see “NetworkInfrastructure Requirements” athttp://go.microsoft.com/fwlink/?linkid=204603.Specific requirements for deploying the Lync Server Multitenant Hosting Pack, or requirements thatdiffer from those for Lync Server 2013 Enterprise Edition, are noted in the sections for the associateddeployment task.It is important to understand the bandwidth implications for hosting providers and customers whenenabling a new tenant for your service. Bandwidth requirements vary greatly depending on the numberof users and which services are used by tenant users. As a hosting provider, you will need to plan thenetwork requirements with tenant customers by utilizing the same principles used in any other LyncServer deployment.In Lync Server Multitenant Hosting Pack, tenants are treated like branches where users are hosted at theCentral Site. The Lync bandwidth calculator should be used to get an idea of what the bandwidthrequirements required for tenants as branches that connect to the Central Site for Lync services.The following Lync traffic will need to be supported on the hosting provider and tenant:SignalingAudio/Video ConferencingPSTN callsTenant peer-to-peer calls will occur within the tenant network. Any conferencing traffic will be via thehoster and tenant networks.It’s still recommended that tenants configure port based Quality of Service (QoS) on the internalnetwork if multiple locations will be on the hosted platform. Although some traffic will be traversingthrough the internet, the peer to peer client communication can be maintained in higher QoS policies onthe tenant’s internal network by configuring static ports for different modalities for client connections.For more information, see Network Bandwidth Requirements for Media Traffic athttp://technet.microsoft.com/en-us/library/jj688118(v=ocs.15).aspx.2.4 Domain Name System (DNS) RequirementsTo support client automatic configuration for all hosted domains, you must work with your hostedcustomers to ensure that the required DNS records are created for each hosted domain. To facilitateinitial testing, this documentation assumes that hosting providers will follow the standard guidance toconfigure a single supported SIP domain during initial deployment. That SIP domain is both publiclyregistered and used as the Active Directory® Domain Services domain for all servers running Lync Server2013. It will be used for initial testing. The “Provisioning Tenant Organizations” section later in thisdocument covers adding DNS records, updating certificates, and other related steps.
  23. 23. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide162.5 Active Directory Domain Services RequirementsDeploy a pair of redundant Active Directory servers according to Exchange Server 2013 guidance. Fordetails, see “Planning Active Directory” in the TechNet Library athttp://go.microsoft.com/fwlink/?LinkId=230823.The Lync Server 2013 Multitenant Hosting Pack supports a Single forest Active Directory environmentwith User or Resource forests. For details about Active Directory and Lync Server 2013, see “ActiveDirectory Domain Services Requirements, Support, and Topologies” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398760.aspx.2.6 Load Balancing RequirementsWe recommend that you use hardware load balancing for all supported roles. For details abouthardware load balancing in Lync Server, see “Load Balancing Requirements” in the TechNet Libraryathttp://go.microsoft.com/fwlink/?LinkId=235820, and “Components Required for External User Access”in the TechNet Library athttp://go.microsoft.com/fwlink/?LinkId=235821.2.7 Port and Protocol RequirementsFor details about port and protocol requirements for communications between Lync Server, see “Portsand Protocols for Internal Servers” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398833.aspx. Specific information about port and protocol requirements that differ fromLync Server 2013 Enterprise are called out in the associated section of this document.2.8 Certificate RequirementsFor Lync Server 2013 certificate requirements, see “Certificate Infrastructure Requirements” in theTechNet Library athttp://technet.microsoft.com/en-us/library/gg398094.aspx.Additional or specific certificate requirements are called out in the associated sections of this document.2.9 Software RequirementsFor web conferencing, the Lync Server 2013 Multitenant Hosting Pack also requires Office Web Apps andthe Office Web Apps Server (formerly known as WAC Server) to handle PowerPoint presentations. Fordetails, see Configuring Integration with Office Web Apps Server and Lync Server 2013 athttp://technet.microsoft.com/en-us/library/jj204792(OCS.15).aspx.2.10Reverse Proxy ConfigurationFor information about using Reverse Proxies with the Lync Server 2013 Multitenant Hosting Pack, seethe following articles:Configuring Reverse Proxy Access to Microsoft Lync Using F5 BIG-IP Local Traffic Manager athttp://blogs.technet.com/b/nexthop/archive/2013/02/22/configuring-reverse-proxy-access-to-microsoft-lync-using-f5-big-ip-local-traffic-manager.aspx.Using IIS ARR as a Reverse Proxy for Lync Server 2013 athttp://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx.
  24. 24. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide173 Understanding the Lync Server 2013 MultitenantHosting PackThe Lync Server Multitenant Hosting Pack solution is an infrastructure layer that enables connectionbetween various technology solutions. Dependencies for the solution include Microsoft ExchangeServer, Exchange UM and Active Directory. Additionally the Lync Server Multitenant Hosting Pack canalso communicate with VoIP devices.The logical infrastructure for Lync Server Multitenant Hosting Pack includes zones for edge systems,proxy systems, data center systems, and VoIP. The server roles are focused within the edge systemroles, proxy roles for Exchange, data center roles for Active Directory, Lync Server Multitenant HostingPack, and Exchange.3.1 About Lync Server Multitenant Hosting Pack User TypesIt is important to understand the different types of users to understand why server roles used in a LyncServer Multitenant Hosting Pack deployment differ from those used in an enterprise deployment of LyncServer 2013.In a typical enterprise deployment of Lync Server 2013, there are the following types of users:Internal users These users access Lync Server services from inside the corporate network.External users These users have Lync Server user accounts and access Lync Server from outsidethe corporate network.Federated users These users have accounts with federated partners and access Lync Serverfrom outside the corporate network.In a Lync Server Multitenant Hosting Pack deployment, there are the following types of users:External users Also known as tenant users in this guide, these users have Lync Server useraccounts associated with a specific tenant, and access Lync Server from outside the host’snetwork.Federated users These users have accounts with federated partners and access Lync Serverfrom outside the host’s network.3.2 Lync Server Multitenant Hosting Pack Server RolesEdge Servers act as the first point of contact for requests coming from clients, federated traffic, andmedia in a hosted deployment.In a Lync Server Multitenant Hosting Pack deployment, incoming requests from tenant users go througha proxy on the Edge Serversand are redirected to the appropriate Front End pool.For the reference architectures included in this guide, all other server roles are the same as the roles forLync Server 2013. For details, see “Server Roles” in the TechNet Library athttp://go.microsoft.com/fwlink/?LinkId=230824.
  25. 25. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide183.3 Lync Server 2013 Control PanelSome enhancements included in the Lync Server Multitenant Hosting Pack are not compatible with theLync Server Control Panel. For example, enabled users are not displayed in the User section of the LyncServer Control Panel.You should use the Lync Server Control Panel only in read-only mode. You should make all changes tothe topology, server configuration, or user configuration by using cmdletsin the Lync ServerManagement Shell. For details, see “Lync Server Management Shell” in the TechNet Libraryathttp://go.microsoft.com/fwlink/?LinkId=213040.Important There are no restrictions on the use of the Topology Builder tool. You can use Topology Builder as youwould normally with a Lync Server 2013Enterprise Edition deployment.4 Planning for the Lync Server Multitenant HostingPackThis section provides information to assist you in planning and preparing for deploying the Lync ServerMultitenant Hosting Pack.4.1 Example TopologyThe topology described in this section illustratesthe basic architectures necessary to support 20,000tenant users with heavy business uses with approximately 75% concurrency and PSTN access. It is notmeant to describe an actual deployment, but rather as a starting point for planning a deployment. Itprovidesa high-level understanding of the architecture and scalability of the productYou should use the topology provided as a starting point in the planning process. Keep in mind thatyou’ll need to customize the topology to meet the needs of your organization’s expected usage profiles,service level agreements, and cost control requirements.Scaling estimates are based on testing done by Microsoft using Lync Server 2013 Enterprise Edition. Fordetails, see the following:“Running Lync Server on Virtual Servers” in the TechNet Libraryathttp://technet.microsoft.com/en-us/library/gg399035(v=ocs.15).aspx.“Capacity Planning Using the User Models” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg615015(v=ocs.15).aspx.“Estimating Voice Usage and Traffic” in the TechNet Library at http://technet.microsoft.com/en-us/library/gg398439(v=ocs.15).aspx.4.1.1 About the Example TopologyThe example topologyis designed to support up to 20,000 tenant users that have PSTN access andA/V/PSTN, and that primarily use MAPI (that is, Outlook Anywhere) at approximately 75% concurrency.
  26. 26. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide19Server allocation provides basic redundancy for each server role with the exception of Monitoring andArchiving, which do not support fault-tolerance.Other assumptions about this architecture include the following:Concurrency of use for the Exchange UM service will be <0.5%.On average, only one in ten users is expected to be in a call at any given time. For details aboutestimating voice usage and traffic, see “Estimating Voice Usage and Traffic” in the TechNetLibrary at http://technet.microsoft.com/en-us/library/gg398439(v=ocs.15).aspx. Depending onthe percentage of calls using media bypass (including PC-to-PC calls), you may need fewer oradditional Mediation Servers in your environment.The following figure illustrates the example topology.TopologyarchitectureThe following table provides details about the number and types of servers in the Topology, includingthe processor and memory requirements for each. Operating System support includes the 64-bitversions of the following:Windows Server 2008 R2 with Service Pack 1 (SP1) Standard (required) or latest service pack(recommended)
  27. 27. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide20Windows Server 2008 R2 with SP1 Enterprise (required) or latest service pack (recommended)Windows Server 2008 R2 with SP1 Datacenter (required) or latest service pack (recommended)Windows Server 2012 StandardWindows Server 2012 DatacenterServers in theTopologyServer role # of servers CPU cores RAMEdge Server pool 2 4 16 GBFront End pool 8 4 16 GBMediation Server 8 4 16 GBBack End Server 2 4 32 GBMonitoring/Archiving database 2 4 32 GB4.2 Flexible Systems ScalingIt is possible to configure multiple Lync Server Multitenant Hosting Packserver roles on a single physicalor virtual server, but it is not recommended for any roles other than Monitoring and Archiving serverroles. For best performance and scalability, you should use one role per server. For example, as demandfor web conferencing services increases, you can increase the number of Front EndServers withoutaffecting other areas in the collaboration environment.4.3 Role-specific Load Balancing and Fault ToleranceDifferent server roles support different techniques and architectures for load balancing and faulttolerance. Most Lync Server roles are designed to use DNS load balancing, a new feature in Lync Server2013 implemented at the application level in both clients and servers. When used in a Lync ServerMultitenant Hosting Pack deployment, the requesting application retrieves a list of the IP addresses ofall available Front End Servers in a given pool and tries to connect with one after another until aconnection succeeds. In contrast, most SIP trunk providers need to be told in advance the IP addressesof all Mediation Servers and will distribute incoming calls to those servers in a round-robin fashion. Tolearn more about DNS load balancing for Lync Server 2013, see “DNS Load Balancing” in the TechNetLibrary at http://technet.microsoft.com/en-us/library/gg398634(v=ocs.15).aspx.Note: The hosting pack supports distributed load balancing, but for optimal performance in large scaledeployments, hardware load balancing is recommended.
  28. 28. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide21The following table lists the load balancing technology per server role that service providers can use as aguideline for deployment in a production environment to implement high availability and faulttolerance.Load Balancing Per Server RoleServer role Load balancing technologyEdge Server Hardware load balancersFront End Server Hardware load balancersExternal Web Services Integrated reverse proxy and load balancer or hardware load balancersMediation Server outbound to PSTN Hardware load balancersMediation Server inbound from PSTN SIP Trunk Configuration5 Migrating from the Lync Server 2010 MultitenantHosting PackIf you are migrating from the Lync Server 2010 Multitenant Hosting Pack, follow the instruction in thissection. If you are not migrating, skip this section and proceed to the next.The process for migrating includes deploying a Lync Server 2013 Multitenant Hosting Pack Front Endpool, and then configuring co-existence to add that pool to your Lync Server 2010 Multitenant HostingPack topology.5.1 Migration PrerequisitesYou will need to perform the following tasks before starting the migration process:1. Deploy a new SQL instance.2. Deploy an Office Web Apps server.See “Configuring Lync Server 2013 to Work with Office Web Apps Server” athttp://technet.microsoft.com/en-us/library/jj204944(v=ocs.15).3. Create a new File share.See Configure File Storage athttp://technet.microsoft.com/en-us/library/jj205150(v=ocs.15).
  29. 29. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide224. Run the Microsoft Lync Server 2010 Best Practices Analyzer and confirm that there are nocritical issues for the Lync Server 2010 Multitenant Hosting Pack.Caution Use onlythe LyncServerUpdateInstaller.exe provided with the Lync Server 2013 Multitenant HostingPack. Do not use Microsoft Update to install the any Lync Server 2013updates.5.2 Performing the Migration Prepare Active Directory for coexistence1. On the server that will be the Front End server, run Setup.exe for the Lync Server 2013Multitenant Hosting Pack.2. Select Install Administrative Tools.3. Install CsServices.msi from the ..Setupamd64setup folder on the installation media. The file isalso copied to the following location when you install the Hosting Pack:c:programdatamicrosoftLync serverdeploymentcache5.0.8308setup folder4. Open the Lync Server Management Shell, and run the following two cmdlets. You may need torun "import-module LyncOnline" before running the cmdlets.o Install-CsAdServerSchemao Install-CsAdServiceSchema5. In the Deployment Wizard, select "Prepare Active Directory"(this should now be showing as partially complete)6. Complete Step (3) Prepare Current Forest.7. Complete Step (5) Prepare Current Domain. Define the topology1. On the Lync Server 2013 Multitenant Hosting Pack Front End server, open Topology Builder andselect Download Topology from existing deployment,and then choose a location to save thetopology.2. In Topology Builder expand Lync Server 2013, then right-click Enterprise Edition Front Endpools, select New Front End Pool, and then complete the wizard.3. Publish the topology. Update the Lync Server 2013 Multitenant Hosting Pack Front End server1. On the Lync Server 2013 Multitenant Hosting Pack Front End server, run setup.exe and completethe following:
  30. 30. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide23o Install or Update Lync Server System - complete steps 1-4o Check that all Lync services start in Administrative Tools > Services.2. Install the Lync Server 2013 backward compatibility tools from ..amd64setupOCSWMIBC.msion the installation media.3. Create the DNS A record for the Lync Server 2013 Front End pool on a DNS server.4. Enable Remote User Access on the Lync Server 2010 Multitenant Hosting Pack Edge Pool.Note Users homed on the new Lync Server 2013 Multitenant Hosting Pack Front End Pool will not be able tologin via the Lync Server 2010 Multitenant Hosting Pack Director/Front End pool.5. Publish the Lync Server 2013 Multitenant Hosting Pack Front End pool external web services URLon the reverse proxy. Validate co-existence1. Provision a new tenant and user on the Lync Server 2013 Multitenant Hosting Pack Front Endpool.2. Configure a Lync client to use the Lync Server 2010 Multitenant Hosting Pack Access Edgeaddress on port 443 and verify sign-in.3. Add a federated contact that is homed on the Lync Server 2010 Multitenant Hosting Pack pool,and verify IM and Presence works in both directions.4. Perform a "Meet Now" with the Lync Server 2013 Multitenant Hosting Pack user, and then addthe Lync Server 2010 Multitenant Hosting Pack federated contact, an external federatedcontact, and a web participant. Test all modalities (AV, Whiteboard, PPT upload, etc.)5.3 Migrating TenantsThe script included in this section will migrateone tenant at a time, including the tenant users that arespread across multiple Lync Server 2010 Multitenant Hosting Pack pools. To use the migration script1. Configure Tenant OU base location in Migrate-TenantOrgV2.ps1 (line 46)$TenantOrgBaseLocationStr ="OU=LHP Tenants,DC=uc-world,DC=co,DC=uk"2. Configure PoolMapping.csv with source and destination pools3. Run the script with the following syntax:
  31. 31. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide24Migrate-TenantOrgV2.ps1 –TenantOrg <Tenant OU Name> -MappingFile<PoolMapping.csv> –MoveConferenceData <$True | $False> -ForceMove<$True | $False>Note When you run the script, you may receive a warning “Failed to find content folder for user sip:<user SIPaddress>.” This message is generated when attempting to move a user with the Move-CsUsercmdlet and the userhas no stored meeting content. If no meeting content folder is found for the user, this message is displayed. If youknow that the user has no meeting content to move, you can safely ignore this warning.5.3.1 Known LimitationsThe following are known limitations of the script provided:On the Tenant OU, the msRTCIP-DomainUrlMap requires populating to meet Lync Server 2013Multitenant Hosting Pack requirementsOn the Tenant users, the msRTCSIP-ObjectId needs populating to meet Lync Server 2013Multitenant Hosting Pack requirements5.3.2 PrerequisitiesThe script requires the following:PoolMapping.csv – the PoolMapping.csv file should include the Lync Server 2010 MultitenantHosting Pack Front End pools and the corresponding target Lync Server 2013 MultitenantHosting Pack pool that the users will be migrated to.JDB-HelperCmds.dll – this file is required for the script to run.The method of supplying this file or code to compile is TBDMigrate-TenantOrgV2.ps1 – a script that migrates tenants5.3.2.1 PoolMapping.csvCreate a .csv file in the following format, replacing the pool names with the pool names for yourdeployment.SrcPool,DstPoolV1FEPOOL.contoso.com,V2FEPool.fabrikam.com5.3.2.2 Migrate-TenantOrgV2.ps1#<##.Synopsis##.Description##.Parameter TenantOrg
  32. 32. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide25##.Parameter MappingFile##.Parameter MoveConferenceData##.Parameter ForceMove##.Example##.Version###>param ( [parameter(Mandatory=$true)] [string] $TenantOrg,[parameter(Mandatory=$true)] [string] $MappingFile,[parameter(Mandatory=$true)] [Bool] $MoveConferenceData,[parameter(Mandatory=$true)] [Bool] $ForceMove)# Import-moduleimport-module ActiveDirectoryimport-module Lyncimport-module LyncOnlineImport-Module .JDB-HelperCmds.dll#variables$FailedMoves = 0$SuccesfulMoves = 0$FailedMoveUserList = New-Object System.Collections.ArrayList$Today = get-date -uformat "%y-%m-%d-%H-%M-%S"$LogFileName= "c:lyncprojectMigrate-TenantOrg-"+$Today+".log"$starttime = get-datewrite-richlog -strLogText "### Starting Migrate-TenantOrg ###" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText "Parameters: " -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevelInformationalwrite-richlog -strLogText " Param - Mapping file : $($MappingFile)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational
  33. 33. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide26write-richlog -strLogText " Param - Move conference data :$($MoveConferenceData) " -strFileName $LogFileName -strSubSystem"Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText " Param - Force Move : $($ForceMove) " -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational$TenantOrgBaseLocationStr ="OU=LHP Tenants,DC=uc-world,DC=co,DC=uk"$TenantOrgOUStr = "OU=$($TenantOrg),$($TenantOrgBaseLocationStr)"#Get list of user in Tenant Org$TenantOrgUserList = Get-CsUser -OU $TenantOrgOUStrwrite-richlog -strLogText "A total of $($TenantOrgUserList.count)users were found." -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText "User list:" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevelInformationalforeach($user in $TenantOrgUserList){write-richlog -strLogText " $($user.SipAddress)" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 2 -logMode File -logLevel Informational}#build list of pools$PoolList = New-Object System.Collections.ArrayListwrite-richlog -strLogText "Building Pool list" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalforeach($User in $TenantOrgUserList){if($PoolList.Contains($user.RegistrarPool)){#list already includes pool}else{#pool is not in the list, adding
  34. 34. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide27write-richlog -strLogText "Adding $($user.RegistrarPool) topool list." -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational$rtn = $PoolList.add($user.RegistrarPool)}}#build pool mapping hash tablewrite-richlog -strLogText "Importing pool mapping list" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational$PoolMappingList = ((get-content -Path $MappingFile) -replace ",","=")-join "`n" | ConvertFrom-StringDatawrite-richlog -strLogText "Pool mapping imported, the followingmapping will be used:" -strFileName $LogFileName -strSubSystem "Main"-intIdentLevel 1 -logMode File -logLevel Informationalforeach($pool in $PoolList){write-richlog -strLogText " $($Pool) is mapped to$($poolMappingList.get_item($pool.Friendlyname))" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 2 -logMode File -logLevel Informational}#foreach to move user to new poolforeach($user in $TenantOrgUserList){try{if($MoveConferenceData){write-richlog -strLogText "Starting move of$($User.SipAddress) including conference data from$($user.RegistrarPool) to$($PoolMappingList.get_Item($user.RegistrarPool.Friendlyname))" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel InformationalMove-CsUser -id $user.sipaddress -Target$PoolMappingList.get_Item($user.RegistrarPool.Friendlyname) -MoveConferenceData -Confirm:$False}else
  35. 35. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide28{write-richlog -strLogText "Starting move of$($User.SipAddress) excluding conference data from$($user.RegistrarPool) to$($PoolMappingList.get_Item($user.RegistrarPool.Friendlyname))" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel InformationalMove-CsUser -id $user.sipaddress -Target$PoolMappingList.get_Item($user.RegistrarPool.Friendlyname) -Confirm:$False}write-richlog -strLogText "Move for $($User.SipAddress)complete" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational$SuccesfulMoves++}catch{write-richlog -strLogText "Move for $($User.SipAddress)failed" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel1 -logMode File -logLevel Errorif($ForceMove){try{write-richlog -strLogText "Attempting force move for$($User.SipAddress)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalif($MoveConferenceData){write-richlog -strLogText "Force moving of$($User.SipAddress) including conference data from$($user.RegistrarPool) to$($PoolMappingList.get_Item($user.RegistrarPool.Friendlyname))" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel InformationalMove-CsUser -id $user.sipaddress -Target$PoolMappingList.get_Item($user.RegistrarPool.Friendlyname) -MoveConferenceData -force -Confirm:$False}else{
  36. 36. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide29write-richlog -strLogText "Force moving of$($User.SipAddress) excluding conference data from$($user.RegistrarPool) to$($PoolMappingList.get_Item($user.RegistrarPool.Friendlyname))" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel InformationalMove-CsUser -id $user.sipaddress -Target$PoolMappingList.get_Item($user.RegistrarPool.Friendlyname) -Force -Confirm:$False}}catch{write-richlog -strLogText "Force move failed for$($User.SipAddress)." -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Error$FailedMoves++$FailedMoveUserList.add($User.SipAddress)}}else{write-richlog -strLogText "Force move will not beattempted for $($User.SipAddress)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevelInformational$FailedMoves++$FailedMoveUserList.add($User.SipAddress)}}}#report on move processwrite-richlog -strLogText "#############POST RUN REPORT#############"-strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText " Tenant Org : $($TenantOrg)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational
  37. 37. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide30write-richlog -strLogText " Numberof user found :$($TenantOrgUserList.count)" -strFileName $LogFileName -strSubSystem"Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText " Numberof successful moves :$($SuccesfulMoves)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText " Numberof failed moves :$($FailedMoves)" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalif($FailedMoves -gt 0){write-richlog -strLogText " Failed move list:" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalforeach($user in $FailedMoveUserList){write-richlog -strLogText " $($user)" -strFileName$LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational}}write-richlog -strLogText "#########################################"-strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informationalwrite-richlog -strLogText "### Ending Migrate-TenantOrg ###" -strFileName $LogFileName -strSubSystem "Main" -intIdentLevel 1 -logMode File -logLevel Informational6 Deploying a New Lync Server 2013 MultitenantHosting Pack DeploymentThe deployment of Lync Server 2013 Multitenant Hosting Pack is very similar to the deployment of LyncServer 2013, Enterprise Edition. This document provides guidance only on which steps to complete, skip,or modify to deploy the Lync Server Multitenant Hosting Pack successfully.This section details where service providers must perform tasks other than the standard Lync Server2013 tasks defined in “Deploying Lync Server 2013” in the TechNet Library athttp://technet.microsoft.com/library/gg412892(v=ocs.15).aspx. Unless otherwise directed, follow all thesteps in that guide. Any steps to be added, skipped, or modified are noted as appropriate in theremainder of this guide, and include a link to the applicable procedure.
  38. 38. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide316.1 Deploying the TopologyThis section provides instructions on how to deploy Lync Server Multitenant Hosting Pack using theexample topology. This sample deployment is designed to support approximately 20,000 tenant users. Itincludes guidance on how to integrate Lync Server with an existing Active Directory infrastructure, butdoes not provide instructions on the initial deployment of that infrastructure. Note that the existinginfrastructure must not include any previous deployments of Lync Server 2013. It also includes asummary of the process for creating private tenant organizations within Active Directory Instructionsabout how to configure Exchange UM features to provide voicemail and other features for Lync Serverusers are also included.This documentation provides a staged approach to deploying a consolidated Lync Server MultitenantHosting Pack lab, starting with the minimum configuration required to get you up and running. Theinitial Hosting Pack topology deployment described in this section includes the following environmentand components:A single forest, single domain Active Directory structureTwo domain controllers with DNS and an Enterprise Root certification authority (CA)An Edge pool consisting of two Edge ServersAn Enterprise Edition Front End pool consisting of two Front End ServersA Mediation Server pool consisting of two Mediation ServersA SQL Server-based Back End Server that also contains the Central Management storeA SQL Server-based Monitoring and Archiving back-end server databaseA DFS file server hosting the Lync Server file storeA Lync Server Multitenant Hosting Pack deployment is different from a Lync Server 2013 EnterpriseEdition deployment in the following ways:A different set of installation media is used. Hosting Pack installation media has been optimizedfor hosts and is the only media supported for hosted, multitenant deployments.No provision is made for “internal” users. All users are expected to connect over the Internet.Procedures are provided to permit per-tenant Exchange Server dial plans without requiringper-tenant Lync Server dial plans.Other than the few procedural modifications required to accommodate the preceding, deploymentprocedures are based on the following standard deployment process for Lync Server 2013 EnterpriseEdition:Lync Server 2013: “Deployment” in the TechNet Library at http://technet.microsoft.com/en-us/library/gg398664(v=ocs.15).aspx lists the standard procedures for deploying Lync Server2013.
  39. 39. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide326.2 Change the Name and Domain of the Server Running Lync ServerIt can be difficult to change server names after you deploy the Lync Server Multitenant Hosting Pack.You should make sure the server names for the following roles are the name you want to use before youstart your deployment:Edge ServerFront EndMediation Server To change the computer name and domain of a server1. To open Server Manager, click Start, click Administrative Tools, clickServer Manager.2. In Server Manager, click Change System Properties.3. In the System Properties, click Change.4. In Computer Name/Domain Changes, click More.5. On the DNS Suffix and NetBIOS Computer Name dialog box, do the following:a. In the Primary DNS suffix of this computer field, enter the name of the external domain tobe used by Lync Server (for example, <externaldomain>.com).b. Clear the Change primary DNS suffix when domain membership changes checkbox.6. Click OKon each dialog box until you close the System Properties dialog box.7. Verify that both the public domain name and the private Active Directory name are in the DNSsuffix search order for the IP address.8. Restart the server to apply the changes.6.3 Installation MediaTo download and install the Lync Server 2013 Multitenant Hosting Pack software, you need to log on tothe Microsoft Volume Licensing Service Center at http://go.microsoft.com/fwlink/?LinkId=238381.After the Setup Wizard starts, the installation proceeds as described in the standard Lync Server 2013Enterprise Edition Deployment documentation in the TechNet Library documentation, with anyexceptions to those steps noted in this document.
  40. 40. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide336.4 Install the Lync Server 2013 Multitenant Hosting PackUse the Lync Server Multitenant Hosting Pack installation media for this procedure. To start theinstallation, open Setup.exe in the amd64 folder on the Front End server.The installation media also includes a tool for applying patches to the Lync Server software,amd64LyncServerUpdateInstaller.exe.To begin your deployment, follow the procedures in the topics listed in the following table. Include eachof the child topics within the sections listed.Checklist for Installing the Lync Server 2013 Multitenant Hosting PackCompleted TopicDeploying Lync Server 2013 Enterprise Editionhttp://technet.microsoft.com/library/gg412892(v=ocs.15)Preparing the Infrastructure and Systemshttp://technet.microsoft.com/en-us/library/gg398205(v=ocs.15).aspxSet Up Hardware and the System Infrastructurehttp://technet.microsoft.com/en-us/library/gg425852(v=ocs.15).aspxSystem Requirements for Enterprise Edition Servershttp://technet.microsoft.com/en-us/library/gg398588(v=ocs.15).aspxInstall Operating Systems and Prerequisite Software on Servershttp://technet.microsoft.com/en-us/library/gg398588(v=ocs.15).aspxRequest Certificates in Advance (Optional)http://technet.microsoft.com/en-us/library/gg412733(v=ocs.15).aspxConfigure IIS
  41. 41. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide34Completed Topichttp://technet.microsoft.com/en-us/library/gg412918(v=ocs.15).aspxConfigure SQL Server for Lync Server 2013http://technet.microsoft.com/en-us/library/gg425848(v=ocs.15).aspxConfigure DNS Records for a Front End Poolhttp://technet.microsoft.com/en-us/library/gg398079(v=ocs.15).aspxDefining and Configuring the Topologyhttp://technet.microsoft.com/en-us/library/gg398339(v=ocs.15).aspxInstall Lync Server Administrative Toolshttp://technet.microsoft.com/en-us/library/gg398665(v=ocs.15).aspx7 Define the TopologyWhen you perform the procedures for defining the topology, there are changes to two of theprocedures that you need to be aware of for a Lync Server Multitenant Hosting Pack deployment.Note The Lync Server 2013Planning Tool is not supported for the Lync Server Multitenant Hosting Pack.These changes apply to the procedures in “Defining and Configuring the Topology” in the TechNetLibrary at http://technet.microsoft.com/en-us/library/gg398339(v=ocs.15).aspx:When performing the steps in “Define and Configure a Topology in Topology Builder” athttp://technet.microsoft.com/en-us/library/gg398788(v=ocs.15).aspx, you will be prompted toprovide a location and file name for saving the topology. Choose New Topology and follow theinstructions.You do not need to specify additional supported domains at this time. Adding tenant SIPdomains is covered later in the “Create Tenant SIP Domain”and in the “Provisioning TenantOrganizations” sections in this document.The Topology Builder does not allow you to configure a topology in which the Edge Servers arebypassed. Because of this, you must make some configuration changes to your topology to enablecommunications between servers running Lync Server 2013. You should perform the steps described in
  42. 42. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide35the following sections of this document after you deploy Lync Serve 2013 and the Lync Server 2013Multitenant Hosting Pack:Error! Reference source not found. Describes how to set Front End Servers to capture neededinformation about NAT traversal. (In enterprise deployments, this information is captured by theEdge Servers.)Create Tenant DNS Records Lists the service records that you need to create and includes notesabout port usage.7.1 Create a Front End PoolWhen performing the steps in “Define and Configure a Front End Pool” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398538(v=ocs.15).aspx, create a new Enterprise EditionFront End pool. Continue to follow the steps provided, applying the modifications as described in thefollowing list:1. When defining the computers in this pool, use the fully qualified domain names (FQDNs) of thecomputers that will be in the Front End pool. These servers are FE0101 and FE0102 in thearchitecture, where the first two digits represent the pool number (in this case there is just one),and the second two digits represent the server within the pool (in this case “01” and “02”).2. On the Select features page, select all features.3. On the Select collocated server roles page, leave all options unselected.4. On the Associate server roles with this Front End pool page, leave all options unselected. Youwill update the topology when these server roles are deployed in later steps.5. On the Define the SQL store page, define a new SQL database, specifying the FQDN and(optionally) named instance you created earlier according to Configure SQL Server for LyncServer 2013.6. Complete all remaining steps in “Define and Configure a Front End Pool” in the TechNet Libraryat http://technet.microsoft.com/en-us/library/gg398538(v=ocs.15).aspx.7. After you define and configure your topology, proceed with all steps listed in“Finalizing andImplementing the Topology Design” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398178(v=ocs.15).aspx.7.2 Configure Front End ServersYou can complete most of procedures involved in “Setting Up Front End Servers and Front End Pools” inthe TechNet Library at http://technet.microsoft.com/en-us/library/gg398827(v=ocs.15).aspxwith thefollowing exceptions:
  43. 43. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide36The “Bootstrap local machine” process assumes that a great number of language packs areinstalled and will raise errors for any not installed. It is safe to ignore these errors for anylanguages that you don’t intend to use.7.3 Update the SQL Server DatabasesAfter you configure your Front End servers, you will need to update the SQL Server databases so thatthey are compatible with the updates applied with the Lync Server Update tool. To update the SQL Server databases1. On all Front End servers, open the Lync Server ManagementShell and run the following cmdletto stop Lync Server services:Stop-csWindowsService2. On one of the Front End servers, run the following cmdlet to update the databases:Install-CsDatabase -Update -ConfiguredDatabases –SqlServerFqdn<SQL ServerFQDN>3. On all Front End servers, run the following cmdlet to restart Lync Server services:Start-csWindowsService7.4 Add Server RolesExcept where noted in this section, you can follow the standard procedures for “Adding Server Roles” inthe TechNet Library at http://technet.microsoft.com/en-us/library/gg412794(v=ocs.15).aspx. You needto deploy the following additional server roles:Edge Servers Instructions for service providers are provided in the “Deploy Edge Servers”section later in this document.Enterprise Voice (Mediation Servers)Dial-in Conferencing For an overview, see the “Overview of the Audio Conferencing Provider”later in this document.MonitoringArchivingResponse GroupNote Do not add the Call Park application because it is not supported in the Lync Server Multitenant Hosting Pack.7.5 Deploy Edge ServersThe guidance in this section and in the “Provisioning Tenant Organizations and Tenants” section later inthis document describes how to implement these configurations. Follow the standard guidance in
  44. 44. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide37“Deploying External User Access” in the TechNet Library at http://technet.microsoft.com/en-us/library/gg398918(v=ocs.15).aspxunless otherwise directed as follows:When you follow the steps in “Configure DNS for Edge Support” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398756(v=ocs.15).aspx, you must configure theDNS records for the initial test SIP domain. Configure the SRV record to point to the Edge Serverpool.When you perform the steps in “Configure the DNS Suffix for Edge Servers” in the TechNetLibrary at http://technet.microsoft.com/en-us/library/gg398756(v=ocs.15).aspx, set the DNSsuffix to the value to the name of the external domain used by the Lync Server deployment.7.6 Define the Edge TopologyTo be consistent with instructions provided in “Defining Your Edge Topology” in the TechNet Library athttp://technet.microsoft.com/en-us/library/gg398591(v=ocs.15).aspx, this document assumes thatyou’re using DNS load balancing. If you choose to use hardware load balancing for the Edge Server pool,see the task for for doing so later in the same topic.Also, this deployment guide assumes that the external Edge interfaces are not configured to use NAT. Ifyou choose to use NAT for this purpose, you will need to develop your own procedures for doing so.Complete the steps to “Define the Topology for a DNS Load Balanced Edge Pool” in the TechNet Libraryat http://technet.microsoft.com/en-us/library/gg398591(v=ocs.15).aspx.7.7 MonitoringFor details about Monitoring, see “Deploying Monitoring” in the TechNet Libraryathttp://technet.microsoft.com/en-us/library/gg398199(v=ocs.15).aspx.8 Post-Installation ConfigurationYou must complete the tasks in this section after you complete the installation.8.1 Install Additional ComponentsYou need to install a few more components on all Front End Servers, Edge Servers, Mediation Servers,Monitoring Server, and Archiving Servers before you can complete the post-installation configurationprocess.Run the following Windows Installer scripts from an elevated command prompt on every instance ofthese servers before proceeding:SetupCSServices.msi
  45. 45. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide388.2 Modify Lync Server Management ShellThe Lync Server Multitenant Hosting Pack includes an additional Windows PowerShell® module(included in the CSServices.msi file) that provides cmdlets used in the management of tenants and otheraspects of the hosted solution. Modification of the Lync Server Management Shell is done automaticallyduring setup of the hosting pack.After you run setup, run the following cmdleteach time you open the Lync Server Management Shell:Import-Module LyncOnlineNote This step is not necessary if you are running Windows Server 2012.8.3 Update Active Directory for Hosted Management ServicesThe Lync Server 2013 Hosting Pack includes tools to update the Active Directory schema and create aroot organizational unit for Lync resellers and tenants. To use them, open the Lync Server ManagementShell with elevated permissions (open as administrator) on a server that has Active Directory toolsinstalled, and run the following cmdlets:Install-CsAdServiceSchemaEnable-CsAdForestEnable-CsAdDomain(Get-CsTopology -AsXml).ToString() > C:Topology.xmlPublish-CsTopology -FileName "C:Topology.xml"Enable-CsTopologyEnable-CsServiceTopologyThe first command extends the Active Directory schema to include information required by the LyncServer 2013 Hosting Pack. The second command prepares the Active Directory forests for operation ofthe Lync Server 2013 Hosting Pack. The third command prepares the Active Directory domain for theLync Server 2013 Hosting Pack. The remaining commands re-publish and enable the topology.Part of the Active Directory domain preparation is the creation of the root tenant OU, “OCS Tenants”.Tenants can be created either directly in this directory, or in one or more levels of nested reseller OUs.8.4 Global Client Policies for Address Book Web QueryThe Lync Server 2013 Hosting Pack is designed to allow clients to use only the Address Book Web Queryservice, and not the Address Book Service that can be used in Lync Server 2013 Enterprise Edition. The
  46. 46. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide39following cmdlet demonstrates how to configure the Address Book server for all users by setting theglobal client policy to allow only the Address Book Web Query service:Set-CsClientPolicy –Identity global -AddressBookAvailabilityWebSearchOnlyThis command sets the AddressBookAvailability parameter to WebSearchOnly. Keep in mind that ifclient policies are set at the site or user level, these policies must also have the AddressBookAvailabilityparameter set to WebSearchOnly. For example, if there is a client policy for users on the Redmond site,you must set the AddressBookAvailability property of that policy:Set-CsClientPolicy –Identity site:Redmond –AddressBookAvailabilityWebSearchOnly8.5 Lync Server Dial PlansDial plans in Lync Server are distinct from dial plans in Exchange UM. Dial plans, which were calledlocation profiles in Microsoft Office Communications Server 2007, do not route calls to Exchange bymatching the name of the Lync Server dial plan to the name of the Exchange dial plan. Instead, calls arerouted in part by matching the Lync Server user’s SIP address with their SIP unified messaging extension.As a result, Lync Server administrators can create one or more Lync Server dial plans based ongeography, tolling or other considerations and employ them without regard to the tenant to which auser belongs.To create a new Lync Server dial plan, run a command similar to the following from the Lync ServerManagement Shell:New-CsDialPlan –Identity Site:Seattle –SimpleName SeattleDialPlanWhen you create a dial plan, a default normalization rule is associated with that dial plan. You shouldmodify that normalization rule to apply to the dial plan. Here is an example of modifying a normalizationrule for the SeattleDialPlanwe just created:New-CsVoiceNormalizationRule – Identity „Site:Seattle/SeattlePrefix‟ –Pattern „^9(d*){1,5}$‟ –Translation „+1206$1‟The preceding dial plan was created at the user scope, which means it must be assigned directly to theuser or users to whom it will apply. To assign a dial plan to a user, use the Grant-CsDialPlancmdlet:Grant-CsDialPlan –Identity john@contoso.com –PolicyName"SeattleDialPlan"8.6 Integration with on-premises PBX or Call CenterFor more information about integrating the hosting pack with an on-premises PBX, see “Direct SIPDeployment Options” at http://technet.microsoft.com/en-us/library/gg398672(v=ocs.15).aspx.
  47. 47. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide40If the IP PBX is not qualified for Lync Server you can use a Sessions Border Controller (SBC). For moreinformation, see Components and Topologies for SIP Trunking at http://technet.microsoft.com/en-us/library/gg398720(v=ocs.15).aspx.8.7 Changing the Root OUYou can change the root organizational unit (OU) when installing the Lync Server 2013 MultitenantHosting Pack in an Active Directory environment that already has an organizational unit for tenants, orwhen you want to change the root tenant OU for any reason. This procedure describes how to useldp.exe to change the otherWellKnownObjects attribute to point to the root tenant OU. To change the root OU for a tenant1. Run ldp.exe.2. In the Connection menu, click Connect.3. In the Connection menu, click Bind.4. In the View menu, click Tree and select the configuration partition from drop-down menu, thenclick OK.Note: The configuration partition option is the one that begins with “CN=Configuration”.5. Right-click the root node, select Modify, and then do the following:a. In the Edit Entry box, enter “otherWellKnownObjects” for Attribute and“B:32:DE8197E3283B2C439A62F871E529F7DD:<DN of root tenant OU here>” forValues.b. In the Operation box, select Replace and then click Enter.c. Click Run.6. On the Connection menu, click Exit to close ldp.exe.
  48. 48. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide418.8 Configuring MobilityMobility support for your Lync Server 2013 Multitenant Hosting Pack deployment is configured the sameas for a Lync Server 2013 on-premises deployment.In order to enable mobility for your deployment, you must request and be provisioned for an FQDNaccess proxy, which enables Push notification. Push notifications are required for Windows mobiledevices, and work on Android and iPhone devices.To request provisioning, you will need to send a request, including the FQDN of your Access Proxy, tohostlync@microsoft.com.For more information about configuring mobility, see the following topics in the TechNet library:Planning for Mobility at http://technet.microsoft.com/en-us/library/hh689981(v=ocs.15).aspxDeploying Mobility at http://technet.microsoft.com/en-us/library/hh690055(v=ocs.15).aspxAutodiscover Service Requirements at http://technet.microsoft.com/en-us/library/hh690012(v=ocs.15).aspx9 Provisioning Tenant OrganizationsAfter you deploy the Lync Server 2013 Hosting Pack, including the Edge Server, Front End Server, BackEnd Server, and Mediation Server, you can provision tenant organizations. Before you can provisionindividual users, you must create tenant organizations in Active Directory, Lync Server, and ExchangeServer by following the steps in this section.9.1 Create and Secure the Organizational UnitsBy default, the Lync Server 2013 Hosting Pack is configured so that tenant OUs are created under theroot organizational unit called “OCS Tenants”. Many hosting providers will want to represent resellerorganizations as subordinate OUs (sub-OUs), each with sub-OUs representing tenants. You should useActive Directory permissions or other suitable mechanisms to ensure that management tools haveadequate access to the tenant OU, and that other tenants do not have inappropriate access.9.2 Set TenantId and ObjectIdLync Server 2013 Hosting Pack uses the Active Directory attributesmsRTCSIP-TenantIdand msRTCSIP-ObjectIdto associate tenant OUs with individual users, so you must copy the tenant OUs to thoseattributes. You can use Windows PowerShell commands from the Active Directory module to create thisassociation. To use the Active Directory cmdlets you must either import the Active Directory moduleinto your Windows PowerShell or Lync Server Management Shell window, or you must run thecommands from the Active Directory Module for Windows PowerShell window. The Active Directorymodule is installed by default on your domain controller. To import the Active Directory module, run thefollowing command at the Windows PowerShell prompt:Import-Module ActiveDirectory
  49. 49. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide42Alternatively, to open the Active Directory Module for Windows PowerShell window, on the Start menu,clickAdministrative Tools, and then click Active Directory Module for Windows PowerShell.The following commands will copy the tenant OU, based on the globally-unique identifier (GUID) of theOU, into the msRTCSIP-TenantIdand msRTCSIP-ObjectIdattributes.$OU = "OU=fabrikam,OU=OCS Tenants,DC=litwareinc,DC=com"$OUObject = Get-ADOrganizationalUnit -Identity $OU$GUID = $OUObject.ObjectGUIDThe first line in the preceding commands sets a variable to the full LDAP path of the OU we want to set.The second line calls the Get-ADOrganizationalUnitcmdlet to retrieve that OU, storing it the variable$OUObject. The third line retrieves the GUID, stored in the ObjectGUID property, of the OU and stores itin another variable ($GUID). Next we need to set the msRTCSIP-TenantId and msRTCSIP-ObjectIdproperties.$OUObject |Set-ADOrganizationalUnit -Replace @{msRTCSIP-TenantId=$GUID}$OUObject |Set-ADOrganizationalUnit -Replace @{msRTCSIP-ObjectId=$GUID}In these two lines we pipe the OU object that is stored in our $OUObject variable to the Set-ADOrganizationalUnitcmdlet. Set-CsADOrganizationalUnit has a number of parameters that allow youto directly set Active Directory properties, such as Server, City, and PostalCode. For the less-commonlyused properties, such as msRTCSIP-TenantId, we use the Replace parameter, passing it the name of theproperty we want to set and the value we want to set it to. Using the Replace parameter will replace anyvalue or values currently stored in that property with the value you specify.Finally, we retrieve all the users in the specified OU and set the msRTCSIP-GroupingId and msRTCSIP-TenantId properties to the GUID of the OU:Get-ADUser -LDAPFilter "(ObjectClass=user)" -SearchBase $OU -Properties msRTCSIP-GroupingID,msRTCSIP-PrimaryUserAddress,comment|Set-ADUser -Replace @{msRTCSIP-GroupingID=$GUID}Get-ADUser -LDAPFilter "(ObjectClass=user)" -SearchBase $OU -Properties msRTCSIP-GroupingID,msRTCSip-TenantID,msRTCSIP-PrimaryUserAddress,comment |Set-ADUser -Replace @{msRTCSip-TenantID=$GUID}The first thing we do in each of these commands is to retrieve all the users in the OU. We do that bycalling the Get-ADUsercmdlet and passing values for the LDAPFilter and SearchBase parameters. TheLDAPFilter value specifies that we want to retrieve all users who actually are users, meaning theirObjectClass property has a value of user. The SearchBase property is set to the FQDN of the OU (which
  50. 50. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide43we stored previously in the $OU variable). Notice that we also supply values for the Propertiesparameter. This isn’t necessary, but it will speed up your query by limiting the amount of data abouteach user that is returned. This is especially useful if you’re running these commands over a remotesession.After we’ve retrieved all the users in the specified OU, we pipe that information to the Set-ADUsercmdlet, which will modify the settings for each of those users. We again use the Replaceparameter, this time replacing the value in the msRTCSIP-GroupingId property with the GUID of the OU.Finally, we do the exact same thing, but this time replacing the value of the msRTCSIP-TenantId propertywith the GUID.9.2.1 Set the DomainUrlMap AttributeYou will also need to configure the msRTCSIP-DomainUrlMap attribute in the following format:<TenantSipDomain#<HosterBaseMeetingUrl>/<TenantSipDomain>. You can set the value by usingADSIEdit or other tool.9.3 Add UPN Suffix to Tenant OUTo enable users in the tenant OU to have user principal names (UPNs) that match their email and SIPaddresses, the domain must be added as a permitted UPN suffix to the tenant OU. Use ADSIEdit or othertool to add the domain to the OU’s uPNSuffixes property.9.4 Create Tenant SIP DomainTo provide customized behaviors for a tenant-specific SIP domain (referred to in this document astenantSIP domain), Lync Server needs to be aware of the domain.If a domain is added to your deployment, it will be added to the list of supported domains in TopologyBuilder. However, meeting URLs are not automatically added, which will result in an error in TopologyBuilder. After a domain is added to your deployment, you will need to manually edit the topology file toallow users to be configured with any supported SIP domain. To manually edit the topology file for your deployment1. Run the following cmdlet to retrieve your topology file, replacing the path with the correct pathfor your environment.(Get-CsTopology -AsXml).ToString() > C:Topology.xml2. Edit the topology.xml file using Notepad, and find the InternalDomainsAllowAllDomains="false"section. Change the value for the section from "false"to "true".The value is case-sensitive.3. Run the following cmdlet to publish the updated topology.Publish-CsTopology -FileName "C:Topology.xml"Next, use ADSIEdit or other tool to add the domain to the msRTCSIP-Domains attribute of the tenantOU. Afterward, you should see the domain listed when querying the properties of the tenant:
  51. 51. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide44Get-CsTenant | Format-Table -AutoSize Id,DomainsId Domains-- -------OU=fabrikam.com,OU=OCS Tenants,DC=fabrikam,DC=com {fabrikam.com}OU=fabrikam.net,OU=OCS Tenants,DC=fabrikam,DC=net {fabrikam.net}9.5 Configure Exchange EmailUse tools and procedures of your choice to configure the tenant OU with email, including one or moreSMTP domains and private address lists.9.6 Configure Exchange Unified MessagingTo configure Exchange UM, you need to perform steps on servers running Exchange and Lync Server.For more information about configuring Exchange UM, see the following topics:Planning for Exchange Unified Messaging Integration at http://technet.microsoft.com/en-us/library/gg399031(v=ocs.15).aspxDeployment Process for Integrating On-Premises Unified Messaging and Lync Server 2013 athttp://technet.microsoft.com/en-us/library/gg425737(v=ocs.15).aspx.Deploying On-Premises Exchange UM to Provide Lync Server 2013 Voice Mail athttp://technet.microsoft.com/en-us/library/gg398768(v=ocs.15).aspxProviding Lync Server 2013 Users Voice Mail on Hosted Exchange UM athttp://technet.microsoft.com/en-us/library/gg425807(v=ocs.15).aspx9.6.1 Create Tenant Exchange Dial Plan and Exchange UM Mailbox PolicyTo enable users for Exchange UM, they must be assigned a dial plan and Exchange UM mailbox policy. Inorder for each tenant organization to have its own dial-by-name directory and other forms of privacy,each tenant must be assigned to a different dial plan. A tenant dial plan and associated Exchange UMmailbox policy can be created using the following Exchange 2013 Management Shell command:New-UMDialplan -Name "<TenantDialPlanName>" -UriType SipName -NumberofDigitsInExtension <TenantExtensionDigits> -VoIPSecuritySecured -CountryorRegionCode 1 -GenerateUMMailboxPolicy$true -AccessTelephoneNumbers <TenantAccessTelephoneNumber>This example uses variables as placeholders that you should replace with real values when provisioninga tenant:TenantDialPlanName A unique name for the dial plan. It is advantageous for troubleshootingpurposes to have the TenantDialPlanName reflect the name of the tenant and reseller.
  52. 52. Microsoft Lync Server 2013 Multitenant Hosting Pack Deployment Guide45TenantExtensionDigits The number of digits to be used in Exchange UM extensions. Note thatto simplify management, full 10-digit phone numbers were used when developing thisdocumentation.TenantAccessTelephoneNumber This is the E.164 telephone number or numbers that userswill call to retrieve their voicemail and otherwise interact with Outlook Voice Access.Here’s an example of what this command might look like:New-UMDialplan -Name "FabrikamDP" -UriType SipName -NumberofDigitsInExtension 10 -VoIPSecurity Secured -CountryorRegionCode 1 -GenerateUMMailboxPolicy $true -AccessTelephoneNumbers "+12065551234"The UriType specifies the URI type that will be sent and received with SIP messages. Possible values areSipName, E164, and TelExtn. The VoIPSecurity parameter can have a value of Secured, SIPSecured, orUnsecured. GenerateUMMailboxPolicy is True by default, which indicates that we want to createanExchange UM mailbox when the dial plan is created.9.6.2 Assign Tenant Dial Plan to All Available Exchange UM ServersAfter creating the Exchange UM dial plan you must associate it with anExchange UM server. To do this,user a command such as the following from the Exchange Management Console:Set-UmServer –Identity UMServer1 –DialPlans Fabrikam19.6.3 Update Exchange UM/Lync Server Integration ConfigurationMicrosoft provides the script exchucutil.ps1, located in the scripts subfolder of the Exchange installationfolder on Exchange UM servers, to automate the following tasks:Create anExchangeUM IP gateway representing each Front End pool. This allows calls to berouted between the Exchange and Lync Server platforms.Create an ExchangeUM hunt groups for each dial plan. This links the configuration of each dialplan to the Exchange UM IP gateway by creating hunt groups including each of theTenantAccessTelephoneNumbers.Grant Lync Server permission to read ExchangeUM Active Directory objects.During testing, this script was run repeatedly without damaging existing dial plans or other ExchangeUM configurations. For additional safety and efficiency, hosts may want to develop modified versions ofexchucutil.ps1 that perform only the functions specific to a new tenant.

×