Admin Guide Lync

Microsoft Lync Server 2010 Administration Guide

Microsoft Lync Server 2010Published: May 2011

This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.Copyright 2011 Microsoft Corporation. All rights reserved.Microsoft, Active Directory, ActiveSync, ActiveX, DirectX, Excel, Forefront, Groove, Hyper-V, Internet Explorer, Lync, MSDN, MSN, OneNote, Outlook, PowerPoint, RoundTable, SharePoint, Silverlight, SQL Server, Visio, Visual C++, Visual Studio, Windows, Windows Live, Windows Media, Windows PowerShell, Windows Server, and Windows Vista, are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

ContentsLync Server Administrative Tools ................................................................................................. 1

Administrative Tools Infrastructure Requirements .................................................................... 3 Requirements to Publish a Topology ..................................................................................... 3 Planning for Simple URLs ..................................................................................................... 4 DNS Requirements for Simple URLs .................................................................................... 7 Edit or Configure Simple URLs ............................................................................................. 9

Server and Tools Operating System Support ......................................................................... 15 Administrative Tools Software Requirements ......................................................................... 17 Administrator Rights and Permissions Required for Setup and Administration ...................... 19 Requirements to Publish a Topology ...................................................................................... 22 Install Lync Server Administrative Tools ................................................................................. 24 Open Lync Server Administrative Tools .................................................................................. 25

Lync Server Control Panel ......................................................................................................... 29 Managing Users ..................................................................................................................... 30

Search for Lync Server 2010 Users .................................................................................... 30 Add a New User to Lync Server 2010 ................................................................................. 31 Enable or Disable Users for Lync Server 2010 ................................................................... 32 Set, View, and Send a User's Dial-in Conferencing PIN ..................................................... 34 Move Users to Another Pool ............................................................................................... 36 Assign Policies to Users ..................................................................................................... 40

Assign a Conferencing Policy to Modify a User's Default Meeting Experience ................ 40 Specify Client Versions Supported for Sign-in by a User ................................................. 42 Assign Specific Dial-in Conferencing PIN Security Settings to a User ............................. 44 Apply External User Access Policies to Users ................................................................. 46 Configure Archiving of a User's Communications ............................................................ 48 Assign a Location Policy to a User .................................................................................. 49 Presence Policy Settings ................................................................................................. 51

Enable Users for Enterprise Voice ...................................................................................... 53 Configure Telephony for Users ............................................................................................ 56

Managing Computers in Your Topology .................................................................................. 58 View a List of Computers Running Lync Server 2010 ......................................................... 58 View the Status of Services Running on a Computer .......................................................... 60 View Details About a Service .............................................................................................. 61 Start or Stop Lync Server 2010 Services ............................................................................ 62 Prevent Sessions for Services ............................................................................................ 64 View Microsoft SIP Processing Language (MSPL) Server Applications .............................. 65 Enable or Disable a Microsoft SIP Processing Language (MSPL) Server Application ........ 67 Mark a Microsoft SIP Processing Language (MSPL) Application as Critical or Not Critical . 68 View a List of Trusted Applications ...................................................................................... 70 View the Simple URL Details .............................................................................................. 71

Filtering Instant Messages and Client Versions ...................................................................... 72 Configuring Filtering for Instant Messaging (IM) ................................................................. 72

Modify the Default File Transfer Filter .............................................................................. 75 Create a New File Transfer Filter for a Specific Site ........................................................ 76 Modify the Default URL Filter ........................................................................................... 77 Create a New URL Filter to Handle Hyperlinks in IM Conversations ............................... 78

Specify Client Versions Supported for Sign-in by a User .................................................... 79 Configuring Voice Routing ...................................................................................................... 81

Configuring Dial Plans and Normalization Rules ................................................................. 81 Create a Dial Plan ........................................................................................................... 83 Modify a Dial Plan ............................................................................................................ 85 Defining Normalization Rules .......................................................................................... 89 Create or Modify a Normalization Rule by Using Build a Normalization Rule .................. 89 Create or Modify a Normalization Rule Manually ............................................................. 91

Configuring Voice Policies, PSTN Usage Records, and Voice Routes ............................... 93 Configuring Voice Policies and PSTN Usage Records to Authorize Calling Features and

Privileges ...................................................................................................................... 93 Create a Voice Policy and Configure PSTN Usage Records ........................................... 93 Modify a Voice Policy and Configure PSTN Usage Records ........................................... 97 View PSTN Usage Records ........................................................................................... 100 Configuring Voice Routes for Outbound Calls ............................................................... 101 Create a Voice Route ..................................................................................................... 102 Modify a Voice Route ..................................................................................................... 104

Configuring Trunks and Translation Rules ........................................................................ 106 Configure Media Bypass on a Trunk .............................................................................. 107 Configure a Trunk Without Media Bypass ...................................................................... 110 Defining Translation Rules ............................................................................................. 113 Create or Modify a Translation Rule by Using the Build a Translation Rule Tool ............ 113 Create or Modify a Translation Rule Manually ............................................................... 115

Exporting and Importing Voice Routing Configuration ....................................................... 117 Export a Voice Route Configuration File ........................................................................ 117 Import a Voice Route Configuration File ........................................................................ 118

Test Voice Routing ............................................................................................................ 119 Create a Voice Routing Test Case ................................................................................. 120 Export Voice Routing Test Cases ................................................................................... 121 Import Voice Routing Test Cases ................................................................................... 121 Running Voice Routing Tests ......................................................................................... 122 Run Informal Voice Routing Tests .................................................................................. 122 Run Voice Routing Test Cases ...................................................................................... 124

Publish Pending Changes to the Voice Routing Configuration .......................................... 127 Configuring Incoming Call Handling Features ...................................................................... 128

Configure Phone Number Extensions for Parking Calls .................................................... 128 Create a Call Park Orbit Range ..................................................................................... 128 Change a Call Park Orbit Range ................................................................................... 130 Delete a Call Park Orbit Range ..................................................................................... 132

Configure Routing of Unassigned Phone Numbers .......................................................... 133 Create an Unassigned Number Range .......................................................................... 133 Change an Unassigned Number Range ........................................................................ 135

Delete an Unassigned Number Range .......................................................................... 136 Managing Response Groups ................................................................................................ 138

Managing Agent Groups ................................................................................................... 138 Create an Agent Group .................................................................................................. 139 Change Agent Group Settings or Members ................................................................... 141 Delete an Agent Group .................................................................................................. 144

Managing Response Group Queues ................................................................................. 146 Create a Response Group Queue ................................................................................. 146 Change a Response Group Queue ............................................................................... 148 Delete a Response Group Queue ................................................................................. 150

Managing Response Group Workflows ............................................................................. 151 Response Group Configuration Tool Requirements ....................................................... 151 Response Group Audio File Requirements .................................................................... 151 Design Call Flows by Using Interactive Voice Response ............................................... 152 (Optional) Define Response Group Business Hours and Holidays ................................ 155 Create a Response Group Workflow ............................................................................. 158 Create a Hunt Group Workflow ...................................................................................... 159 Create an Interactive Workflow ...................................................................................... 163 Change a Response Group Workflow ........................................................................... 170 Change a Hunt Group Workflow .................................................................................... 170 Change an Interactive Workflow .................................................................................... 175 Delete a Response Group Workflow .............................................................................. 181

Managing On-Premises Meetings ........................................................................................ 183 Configuring Conferencing Settings ................................................................................... 183

Modify the Default Conferencing User Experience ........................................................ 183 Create or Modify Conferencing User Experience for a Site or Group of Users .............. 186 Conferencing Policy Settings Reference ....................................................................... 190 Delete a Conferencing Policy for a Site or Group of Users ............................................ 191

Configuring the Meeting Join Experience ......................................................................... 192 Modify the Default Meeting Join Experience .................................................................. 193 Create or Modify Meeting Join Settings for a Site or Pool ............................................. 194 Delete Meeting Join Settings for a Site or Pool ............................................................. 196

Configure Settings for a Dial-in Conferencing Access Number ......................................... 197 Create or Modify a Dial-in Conferencing Access Number .............................................. 197 Delete a Dial-in Conferencing Access Number .............................................................. 200

Configure Dial-in Conferencing Personal Identification Number (PIN) Rules .................... 200 Modify the Default Dial-in Conferencing PIN Settings .................................................... 201 Create or Modify Dial-in Conferencing PIN Settings for a Site or Group of Users ......... 202 Delete Dial-in Conferencing PIN Settings for a Site or Group of Users ......................... 204

Configuring Support for Clients and Devices ........................................................................ 206 Specify the Client Versions Supported in Your Organization ............................................. 206 View the Status of Services Running on a Computer ........................................................ 208 Modify the Default Action for Clients Not Explicitly Supported or Restricted ..................... 209 View Software Updates for Devices in Your Organization ................................................. 211 Add a Device to Test Update Functionality ........................................................................ 212 Modify Settings for Log Files of Device Update Activity .................................................... 213

Configure Security Settings for Lync 2010 Phone Edition ................................................. 214 Configure Voice Quality of Service for Lync 2010 Phone Edition ...................................... 215 Configure Phone Lock for Lync 2010 Phone Edition ......................................................... 215

Managing External Connectivity ........................................................................................... 217 Enable or Disable External User Access for Your Organization ........................................ 218

Enable or Disable Remote User Access for Your Organization ..................................... 219 Enable or Disable Federation for Your Organization ...................................................... 220 Enable or Disable Anonymous User Access for Your Organization ............................... 222

Manage Communications with External Users .................................................................. 223 Manage Remote User Access ....................................................................................... 225 Manage Federated Partner Access ............................................................................... 226 Configure Policies to Control Federated User Access ................................................... 227 Enable or Disable Discovery of Federation Partners ..................................................... 228 Control Access by Individual Federated Domains ......................................................... 229 Enable or Disable Sending an Archiving Disclaimer to Federated Partners .................. 232 Manage IM Provider Support ......................................................................................... 233 Configure Policies to Control Access by Users of IM Service Providers ........................ 233 Specify Supported IM Service Providers ....................................................................... 236 Configure Conferencing Policies to Support Anonymous Users .................................... 239 Apply Policies for External User Access to Users .......................................................... 240 Apply External User Access Policies to Users ............................................................... 240 Apply Conferencing Policies to Support Anonymous Users ........................................... 241 Reset or Delete External User Access Policies ............................................................. 243 Delete a Site or User Policy for External User Access ................................................... 243 Reset the Global Policy for External User Access ......................................................... 244

Managing Monitoring ............................................................................................................ 245 Create a Site Policy for Call Detail Recording ................................................................... 245 Create a Site Policy for Quality of Experience .................................................................. 246 Enable Call Detail Recording ............................................................................................ 247 Enable Quality of Experience ............................................................................................ 248 Configure Call Detail Recording ........................................................................................ 249 Configure Quality of Experience ....................................................................................... 251 Delete a Site Policy for Call Detail Recording ................................................................... 251 Delete a Site Policy for Quality of Experience ................................................................... 252

Managing Archiving .............................................................................................................. 254 Configuring Support for Archiving of Internal and External Communications .................... 254

Change the Global Policy for Archiving of Internal and External Communications ........ 255 Create a Site Policy for Archiving .................................................................................. 256 Enable or Disable Archiving for a Site ............................................................................ 257 Create a User Policy for Archiving ................................................................................. 258 Enable or Disable Archiving for Users ........................................................................... 260 Delete an Archiving Policy ............................................................................................. 262 Apply an Archiving Policy to a User or User Group ....................................................... 262

Enable or Disable Archiving .............................................................................................. 264 Specify the Types of Communications To Be Archived ..................................................... 265 Enable or Disable Purging for Archiving ............................................................................ 266

Block or Allow IM and Web Conferencing Sessions If Archiving Fails ............................... 267 Enable or Disable Sending an Archiving Disclaimer to Federated Partners ...................... 268

Configuring Security ............................................................................................................. 270 Create a New Registrar .................................................................................................... 270 Modify an Existing Registrar ............................................................................................. 271 Delete a Registrar ............................................................................................................. 272 Create a New Web Service ............................................................................................... 274 Modify an Existing Web Service ........................................................................................ 276 Delete a Web Service ....................................................................................................... 278 Create a New PIN Policy ................................................................................................... 278 Modify an Existing PIN Policy ........................................................................................... 280 Delete a PIN Policy ........................................................................................................... 281

Configuring Your Network ..................................................................................................... 282 Enabling Call Admission Control ....................................................................................... 282 Enabling Media Bypass .................................................................................................... 283 Configuring Location Policy ............................................................................................... 284 Configuring Bandwidth Policy Profile ................................................................................ 288 Configuring Network Regions ........................................................................................... 290 Configuring Network Sites ................................................................................................. 292 Configuring Network Subnets ........................................................................................... 294 Configuring Network Region Links .................................................................................... 296 Configuring Network Region Routes ................................................................................. 297 Configuring Network Site Links ......................................................................................... 299

Change the Web Services URL ............................................................................................ 301 Administering the Address Book Service .............................................................................. 304

Windows PowerShell Cmdlets for Address Book Services ............................................... 310 New-CsAddressBookConfiguration for Address Book Management ............................. 310 Set-CsAddressBookConfiguration for Address Book Management ............................... 311 Get-CsAddressBookConfiguration for Address Book Management ............................... 311 Remove-CsAddressBookConfiguration for Address Book Management ....................... 312 Test-CsAddressBookService for Address Book Management ....................................... 312 Test-CsAddressBookWebQuery for Address Book Management .................................. 313 Update-CsAddressBook for Address Book Management .............................................. 313 New-CsClientPolicy for Address Book Management ..................................................... 314 Set-CsClientPolicy for Address Book Management ....................................................... 314 Get-CsService for Address Book Management ............................................................. 315 New-CsWebServiceConfiguration for Address Book Management ............................... 316 Get-CsWebServiceConfiguration for Address Book Management ................................. 317 Set-CsWebServiceConfiguration for Address Book Management ................................. 317 Remove-CsWebServiceConfiguration for Address Book Management ......................... 318

Prevent New Connections to Lync Server 2010 for Server Maintenance ............................. 319 Delegating Control of Microsoft Lync Server 2010 ............................................................... 320 Configure a New Trusted Application Server ........................................................................ 323 Troubleshooting Lync Server 2010 Control Panel ................................................................ 325

Configuring Federation Support for a Lync Online 2010 Customer ......................................... 327 Prerequisites for Federating with a Lync Online Customer ................................................... 327

Configure Domain Access for Federation with a Lync Online Customer .............................. 328 Configure Federation for a Lync Online Domain ............................................................... 328 Enable or Disable Domain Access for a Lync Online Customer ........................................ 330

Configure User Access for Federation with a Lync Online Customer ................................... 331 Configure User Access for Lync Online Users .................................................................. 331 Configure User Access for Internal Lync Users ................................................................. 332

Verify Communications with a Lync Online Customer .......................................................... 332

Lync Server Administrative ToolsThis topic describes the administrative tools for Microsoft Lync Server 2010.The administrative tools are installed by default on each Lync Server 2010 server. Additionally, you can install the administrative tools on other computers, such as dedicated administrative consoles. For procedures to install the administrative tools, see Install Lync Server Administrative Tools. For procedures to open the tools to perform management tasks, see Open Lync Server Administrative Tools. Ensure that you review infrastructure, operating system, software, and administrator rights requirements before you install or use the Lync Server administrative tools. For details about infrastructure requirements, see Administrative Tools Infrastructure Requirements. For details about operating system and software requirements to install the Lync Server 2010 administrative tools, see Server and Tools Operating System Support, Additional Software Requirements, and Additional Server Support and Requirements. The user rights and permissions required to install and use the tools are described in Administrator Rights and Permissions Required for Setup and Administration.The administrative tools consist of the following:

Lync Server Deployment Wizard Use to deploy Lync Server 2010 and to install all administrative tools. Lync Server Topology Builder Use to define components in your deployment. Lync Server Control Panel Use for ongoing management of your deployment by using a web-based interface. Lync Server Management Shell Use for ongoing management of your deployment by using the command line. Lync Server Logging tool Use to troubleshoot problems in your deployment.

You can manage your deployment by primarily using Topology Builder and Lync Server Control Panel.

Deployment WizardYou must use the Lync Server Deployment Wizard included on the installation media to install all administrative tools onto a computer on which you have not already installed Lync Server. During the administrative tools installation process, the Lync Server Deployment Wizard is installed locally along with the other tools so that you can later use it to install files for additional components or remove files for components that you do not want on the computer.For details about how to run the Lync Server Deployment Wizard for the first time from the Lync Server 2010 installation media, see Install Lync Server Administrative Tools.

1


Topology BuilderFor details about deployment tasks that you can you perform by using Topology Builder, see the Deployment documentation for each server role.

Lync Server Control PanelYou can use Lync Server 2010 Control Panel to perform most of the administrative tasks required to manage and maintain Lync Server 2010.For details about administrative tasks you can perform by using Lync Server 2010 Control Panel, see Lync Server Control Panel.

Lync Server Management ShellIn Lync Server 2010, the Lync Server Management Shell provides a new method for administration and management. Lync Server Management Shell is a powerful management interface, built on the Windows PowerShell command-line interface, that includes a comprehensive set of cmdlets that are specific to Lync Server 2010. With Lync Server Management Shell, you gain a rich set of configuration and automation controls. Topology Builder and Lync Server Control Panel both implement subsets of these cmdlets to support management of Lync Server 2010. The Lync Server Management Shell includes cmdlets for all Lync Server 2010 administration tasks, and you can use the cmdlets individually to manage your deployment. For details, see Lync Server Management Shell documentation or the command-line help for each cmdlet.

Logging ToolThe Lync Server Logging Tool facilitates troubleshooting by capturing logging and tracing information from the product while the product is running. You can use the tool to run debug sessions on any Lync Server server role. For details about the Logging Tool, see the Lync Server 2010 Logging Tool documentation on the TechNet Library at http://go.microsoft.com/fwlink/?LinkId=199265.

In This Section Administrative Tools Infrastructure Requirements Server and Tools Operating System Support Administrative Tools Software Requirements Administrator Rights and Permissions Required for Setup and Administration Requirements to Publish a Topology Install Lync Server Administrative Tools Open Lync Server Administrative Tools

See AlsoLync Server Control Panel

2

Microsoft Lync Server 2010 Administration GuideAdministrative Tools Infrastructure RequirementsThere are no additional infrastructure requirements for you to install Microsoft Lync Server 2010 administrative tools or perform most management tasks using these tools. For infrastructure requirements for specific scenarios, see the topics in this section.

In This Section Requirements to Publish a Topology Planning for Simple URLs DNS Requirements for Simple URLs Edit or Configure Simple URLs

Related Sections Lync Server Control Panel Lync Server Management Shell

See AlsoAdministrative Tools Software RequirementsAdministrator Rights and Permissions Required for Setup and AdministrationInstall Lync Server Administrative Tools

Requirements to Publish a TopologyThis topic describes the infrastructure and software requirements that are specific to publishing a topology, whether by using Topology Builder or the Lync Server Management Shell command-line interface. These requirements are in addition to the general operating system, software, and permissions requirements applicable to all Microsoft Lync Server 2010 administrative tools. Ensure that you satisfy all administrative tools requirements before you publish a topology.

You must run Topology Builder on a computer that is joined to the same domain or forest of the Lync Server 2010 deployment you are creating so that Active Directory Domain Services (AD DS) preparation steps are already completed, enabling you to use the administrative tools on that computer to successfully publish your topology.

Note: For details about preparing AD DS, see Preparing Active Directory Domain Services for Lync Server 2010 in the Deployment documentation.

The computers defined in the topology must be joined to the domain, except for Edge Servers, and in AD DS. However, the computers do not need to be online when you publish the topology. The file share for the pool must be created and available to remote users. In order to publish an Enterprise Edition Front End pool, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and configured with the appropriate firewall rules to make it available to remote users. For details about specifying firewall exceptions, see Understanding Firewall Requirements for SQL

3

Microsoft Lync Server 2010 Administration GuideServer. For other details about configuring SQL Server, see Configure SQL Server for Lync Server 2010.

Note: Standard Edition server has a collocated database that will accept the published configuration. You must first run the Prepare first Standard Edition server setup task in the Lync Server Deployment Wizard.

If you run Topology Builder on a computer where you plan to later install Lync Server, then you must install the Microsoft SQL Server 2005 backward compatibility components by running the first setup task in the Lync Server Deployment Wizard before you publish the topology. For details, see Install the Local Configuration Store or Install the Standard Edition Local Configuration Store.

Note: You do not need the Microsoft SQL Server 2005 backward compatibility components to publish the topology if you run Topology Builder on a dedicated administrative console or if you run Topology Builder on a computer where Lync Server is already installed. (Lync Server setup automatically installs the backward compatibility components along with other component files required by Lync Server.)

See AlsoAdministrative Tools Software RequirementsServer and Tools Operating System SupportAdministrator Rights and Permissions Required for Setup and Administration

Planning for Simple URLsSimple URLs make joining meetings easier for your users, and make getting to Microsoft Lync Server 2010 administrative tools easier for your administrators. Microsoft Lync Server 2010 communications software supports three simple URLs:

Meet is used as the base URL for all conferences in the site or organization. An example of a Meet simple URL is https://meet.contoso.com. A particular meeting URL might be https://meet.contoso.com/username/7322994. With the Meet simple URL, links to join meetings are easy to comprehend, and easy to communicate and distribute. Dial-in enables access to the Dial-in Conferencing Settings webpage. This page displays conference dial-in numbers with their available languages, assigned conference information (that is, for meetings that do not need to be scheduled), and in-conference DTMF controls, and supports management of personal identification number (PIN) and assigned conferencing information. The Dial-in simple URL is included in all meeting invitations so that users who want to dial in to the meeting can access the necessary phone number and PIN information. An example of the Dial-in simple URL is https://dialin.contoso.com. Admin enables quick access to the Microsoft Lync Server 2010 Control Panel. From any computer within your organizations firewalls, an admin can open the Lync Server 2010 Control Panel by typing the Admin simple URL into a browser. The Admin simple URL is

4

Microsoft Lync Server 2010 Administration Guideinternal to your organization. An example of the Admin simple URL is https://admin.contoso.com

Simple URL ScopeYou can configure your simple URLs to have global scope, or you can specify different simple URLs for each central site in your organization. If both a global simple URL and a site simple URL are specified, the site simple URL has precedence. In most cases, we recommend that you set simple URLs only at the global level, so that a users Meet simple URL does not change if they move from one site to another. The exception would be organizations that need to use different telephone numbers for dial-in users at different sites. Note that if you set a one simple URL (such as the Dial-in simple URL) at a site to be a site-level simple URL, you must also set the other simple URLs at that site to be site-level as well.You can set global simple URLs in Topology Builder. To set a simple URL at the site level, you must use the Set-CsSimpleURLConfiguration cmdlet.

Naming Your Simple URLsThere are three recommended options for naming your simple URLs. Which option you choose has implications for how you set up your DNS A records and certificates which support simple URLs. In each option, you must configure one Meet simple URL for each SIP domain in your organization. You always need just one simple URL in your whole organization for Dial-in, and one for Admin, no matter how many SIP domains you have.For details about the necessary DNS A records and certificates, see DNS Requirements for Simple URLs and Certificate Requirements for Internal Servers in the Planning documentation.In Option 1, you create a new SIP domain name for each simple URL.If you use this option, you need a separate DNS A record for each simple URL, and each Meet simple URL must be named in your certificates.

Simple URL Naming Option 1

Simple URL Example

Meet https://meet.contoso.com, https://meet.fabrikam.com, and so on (one for each SIP domain in your organization)

Dial-in https://dialin.contoso.com

Admin https://admin.contoso.com

With Option 2, simple URLs are based on the domain name lync.contoso.com. Therefore, you need only one DNS A record which enables all three types of simple URLs. This DNS A record references lync.contoso.com. Additionally, you still need separate DNS A records for other SIP domains in your organization.


Simple URL Example

5


Meet https://lync.contoso.com/Meet, https://lync.fabrikam.com/Meet, and so on (one for each SIP domain in your organization)

Dial-in https://lync.contoso.com/Dialin

Admin https://lync.contoso.com/Admin

Option 3 is most useful if you have many SIP domains, and you want them to have separate Meet simple URLs but want to minimize the DNS record and certificate requirements for these simple URLs.


Simple URL Example

Meet https://lync.contoso.com/contosoSIPdomain/Meethttps://lync.contoso.com/fabrikamSIPdomain/Meet



Simple URL Naming and Validation RulesTopology Builder and the Lync Server Management Shell cmdlets enforce several validation rules for your simple URLs. You are required to set simple URLs for Meet and Dialin, but setting one for Admin is optional. Each SIP domain must have a separate Meet simple URL, but you need only one Dialin simple URL and one Admin simple URL for your whole organization.Each simple URL in your organization must have a unique name, and cannot be a prefix of another simple URL (for example, you could not set lync.contoso.com/Meet as your Meet simple URL and lync/contoso.com/Meet/Dialin as your Dialin simple URL). Simple URL names cannot contain the FQDN of any of your pools, or any port information (for example, https://FQDN:88/meet is not allowed). All simple URLs must start with the https:// prefix. Simple URLs can contain only alphanumeric characters (that is, a-z, A-Z, 0-9, and the period (.). If you use other characters, the simple URLs might not work as expected.

Changing Simple URLs after DeploymentIf you change a simple URL after initial deployment, you must be aware of what changes impact your DNS records and certificates for simple URLs. If the change impacts the base of a simple URL, then you must change the DNS records and certificates as well. For example, changing from https://lync.contoso.com/Meet to https://meet.contoso.com changes the base URL from lync.contoso.com to meet.contoso.com, so you would need to change the DNS records and certificates to refer to meet.contoso.com. If you changed the simple URL from https://lync.contoso.com/Meet to https://lync.contoso.com/Meetings, the base URL of lync.contoso.com stays the same, so no DNS or certificate changes are needed.Whenever you change a simple URL name, however, you must run Enable-CsComputer on each Director and Front End Server to register the change.

6

Microsoft Lync Server 2010 Administration GuideSee AlsoDNS Requirements for Simple URLs

DNS Requirements for Simple URLsMicrosoft Lync Server 2010 introduces simple URLs, which make joining meetings easier for your users, and make getting to Microsoft Lync Server 2010 administrative tools easier for your administrators. For details about simple URLs, see Planning for Simple URLs. Lync Server 2010 supports the following three simple URLs: Meet, Dial-In, and Admin. You are required to set up simple URLs for Meet and Dial-In, and the Admin simple URL is optional. The Domain Name System (DNS) records that you need to support simple URLs depend on how you have defined these simple URLs. There are three different ways you can define the URLs.

Simple URL Option 1In Option 1, you create a new base URL for each simple URL.

Note: When a user clicks a simple URL meeting link, the server that the DNS A record resolves to determines the correct client software to start. After the client software is started, it automatically communicates with the pool where the conference is hosted. This way, users are directed to the appropriate server for meeting content no matter which server or pool the simple URL DNS A records resolve to.

Simple URL Option 1

Simple URL Example

Meet https://meet.contoso.com, https://meet.fabrikam.com, and so on (one for each SIP domain in your organization)



If you use Option 1, you must define the following: For each Meet simple URL, you need a DNS A record that resolves the URL to the IP address of the Director, if you have one deployed. Otherwise, it should resolve to the IP address of the load balancer of a Front End pool. If you have not deployed a pool and are using a Standard Edition server deployment, the DNS A record must resolve to the IP address of one Standard Edition server in your organization.If you have more than one SIP domain in your organization and you use this option, you must create Meet simple URLs for each SIP domain and you need a DNS A record for each Meet simple URL. For example, if you have both contoso.com and fabrikam.com, you will create DNS A records for both https://meet.contoso.com and https://meet.fabrikam.com.Alternatively, if you have multiple SIP domains and you want to minimize the DNS record and certificate requirements for these simple URLs, use Option 3 as described later in this topic.

7

Microsoft Lync Server 2010 Administration Guide For the Dial-in simple URL, you need a DNS A record that resolves the URL to the IP address of the Director, if you have one deployed. Otherwise, it should resolve to the IP address of the load balancer of a Front End pool. If you have not deployed a pool and are using a Standard Edition server deployment, the DNS A record must resolve to the IP address of one Standard Edition server in your organization. The Admin simple URL is internal only. It requires a DNS A record that resolves the URL to the IP address of the Director, if you have one deployed. Otherwise, it should resolve to the IP address of the load balancer of a Front End pool. If you have not deployed a pool and are using a Standard Edition server deployment, the DNS A record must resolve to the IP address of one Standard Edition server in your organization.

Simple URL Option 2With Option 2, the Meet, Dial-in, and Admin simple URLs all have a common base URL, such as lync.contoso.com. Therefore, you need only one DNS A record for these simple URLs, which resolves lync.contoso.com to the IP address of a Director pool or Front End pool. If you have not deployed a pool and are using a Standard Edition server deployment, the DNS A record must resolve to the IP address of one Standard Edition server in your organization.Note that if you have more than one SIP domain in your organization, you must still create Meet simple URLs for each SIP domain and you need a DNS A record for each Meet simple URL. In this example, while three simple URLs are all based on lync.contoso.com, an additional Meet simple URL for fabrikam.com is set up with a different base URL. In this example, you must create DNS A records for both https://lync.contoso.com and https://lync.fabrikam.com. Simple URL Option 3 shows another way to handle naming and DNS A records if you have multiple SIP domains.

Simple URL Option 2

Simple URL Example

Meet https://lync.contoso.com/Meet, https://lync.fabrikam.com/Meet, and so on (one for each SIP domain in your organization)



Simple URL Option 3Option 3 is most useful if you have many SIP domains, and you want them to have separate simple URLs but want to minimize the DNS record and certificate requirements for these simple URLs. In this example, you need only one DNS A record, which resolves lync.contoso.com to the IP address of a Director pool or Front End pool.

Simple URL Option 3

Simple URL Example

Meet https://lync.contoso.com/contosoSIPdomain/Meet

8


https://lync.contoso.com/fabrikamSIPdomain/Meet

Dial-in https://lync.contoso.com/contosoSIPdomain/Dialinhttps://lync.contoso.com/fabrikamSIPdomain/Dialin

Admin https://lync.contoso.com/contosoSIPdomain/Adminhttps://lync.contoso.com/fabrikamSIPdomain/Admin

Edit or Configure Simple URLsThis procedure does not require membership in a local administrator or privileged domain group. You should log on to a computer as a standard user.Microsoft Lync Server 2010 uses simple URLs to direct internal and external calls to services on the Front End Server or on the Director, if one has been deployed. The three simple URLs that can be created are:

Meet Connects users to the conferencing services Dialin Provides access for users to use dial-in conferencing Admin Optional URL that connects a user, typically an administrator for the Lync Server 2010 system, to Microsoft Lync Server 2010 Control Panel.

There are options to the format that you can define simple URLs. For details about these options, see DNS Requirements for Simple URLs in the Planning documentation. A brief summary of the three simple URL formats discussed are shown for reference here:

Simple URL Examples

Meet https://meet.contoso.com

Meet https://lync.contoso.com/Meet

Meet https://lync.contoso.com/contosoSIPdomain/Meet



Dial-in https://lync.contoso.com/contosoSIPdomain/Dialin

Admin https://admin



Admin https://lync.contoso.com/contosoSIPdomain/Admin

By default, simple URLs will be configured in the form of (for example, the dial-in simple URL): https://dialin.

9

Microsoft Lync Server 2010 Administration GuideWarning: Simple URLs can contain only English alphanumeric characters, defined as a-z, A-Z, 0-9, and the dot (.). If you use characters that are not part of the character set, the simple URLs may fail to work as expected.

To configure simple URLs

1. In Topology Builder, right-click the Lync Server 2010 node, and then click Edit Properties.

2. In the Simple URLs pane, select either Phone access URLs: (Dial-in) or Meeting URLs: (Meet) to edit. And then click Edit URL.

10


3. Update the URL to the value you want, and then click OK to save the edited URL. The example shown here has modified the Dial-in URL to https://pool01.contoso.net/dialin.

11


4. Edit the Meet URL by using the same steps, if necessary.

To define the optional Admin simple URL

1. In Topology Builder, right-click the Lync Server 2010 node, and then click Edit Properties.

12


2. In the Administrative access URL box, enter the simple URL you want for administrative access to Lync Server 2010 Control Panel, and then click OK.

Tip: We recommend using the simplest possible URL for the Admin URL. The simplest option is https://admin.

13


Important: If you change a simple URL after initial deployment, you must be aware of what changes impact your Domain Name System (DNS) records and certificates for simple URLs. If the change impacts the base of a simple URL, then you must change the DNS records and certificates as well. For example, changing from https://lync.contoso.com/Meet to https://meet.contoso.com changes the base URL from lync.contoso.com to meet.contoso.com, so you would need to change the DNS records and certificates to refer to meet.contoso.com. If you changed the simple URL from https://lync.contoso.com/Meet to https://lync.contoso.com/Meetings, the base URL of lync.contoso.com stays the same, so no DNS or certificate changes are needed. Whenever you change a simple URL name, however, you must run the Enable-CsComputer on each Director and Front End Server to register the change.

14


PowerShell supplement:

Configure Simple URLs

To configure simple URLs

To define simple URLs for dial-in conferencing and meetings, use the following set of commands:$urlEntry = New-CsSimpleUrlEntry -Url "https://dialin.fabrikam.com"$simpleUrl = New-CsSimpleUrl -Component "dialin" -Domain "*" -SimpleUrl $urlEntry -ActiveUrl "https://dialin.fabrikam.com"$urlEntry2 = New-CsSimpleUrlEntry -Url "https://meet.fabrikam.com"$simpleUrl2 = New-CsSimpleUrl -Component "meet" -Domain "fabrikam.com" -SimpleUrl $urlEntry2 New-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUrl,$simpleUrl2}

To define the optional Admin simple URL

To define an Admin simple URL use the following set of commands:$urlEntry = New-CsSimpleUrlEntry -Url "https://admin.fabrikam.com"$simpleUrl = New-CsSimpleUrl -Component "admin" -Domain "*" -SimpleUrl $urlEntry -ActiveUrl "https://admin.fabrikam.com"New-CsSimpleUrlConfiguration -Identity "site:Redmond" -SimpleUrl @{Add=$simpleUrl }

See AlsoPlanning for Simple URLs

Server and Tools Operating System SupportAll server roles support the same Windows Server operating systems. The required operating system support for other server roles, such as database servers, depends on what software you install on those servers.Microsoft Lync Server 2010 communications software administrative tools are installed by default on the server running Lync Server 2010, but you can install administrative tools separately on other computers running Windows operating systems. For example, you can use a client computer running Windows 7 as an administrative console for planning purposes.

Important: Lync Server 2010 is available only in 64-bit, which requires 64-bit hardware and 64-bit editions of Windows Server. Lync Server 2010 is not available in a 32-bit version. This

15

Microsoft Lync Server 2010 Administration Guidemeans that all server roles and computers running Lync Server administrative tools run a 64-bit edition operating system.

Operating Systems for Server RolesMicrosoft Lync Server 2010 supports the 64-bit editions of the following operating systems:

The Windows Server 2008 R2 Standard operating system (required) or latest service pack (recommended) The Windows Server 2008 R2 Enterprise operating system (required) or latest service pack (recommended) The Windows Server 2008 R2 Datacenter operating system (required) or latest service pack (recommended) The Windows Server 2008 Standard operating system with Service Pack 2 (SP2) (required) or latest service pack (recommended) The Windows Server 2008 Enterprise operating system with SP2 (required) or latest service pack (recommended) The Windows Server 2008 Datacenter operating system with SP2 (required) or latest service pack (recommended)

Notes: If you have an existing server running Windows Server 2008 with Service Pack 1 (SP1), you must upgrade it to either Windows Server 2008 SP2 (or latest service pack), or Windows Server 2008 R2 (or latest service pack) before deploying Lync Server 2010.Installation of any Lync Server 2010 server role on a computer running Windows Server 2008 Datacenter or Windows Server 2008 R2 Datacenter that has multiple processor groups configured is not supported. This is because SQL Server 2008 Express is required and automatically installed on each server role, and SQL Server 2008 Express does not support installation on a computer that is partitioned into multiple processors groups. After deploying the servers, you can upgrade the SQL Server 2008 Express RTC database on the Standard Edition server and RTCLocal databases on other server roles to SQL Server 2008 R2 Express by running the SQL Server 2008 R2 Express setup wizard and selecting the upgrade option, but SQL Server 2008 R2 also does not support installation on a computer that is partitioned into multiple processors groups.Lync Server 2010 is not supported on the following operating systems:

The Server Core installation option of Windows Server 2008 R2 or Windows Server 2008 The Windows Web Server2008 R2 operating system or the Windows Web Server2008 operating system Windows Server 2008 R2 HPC Edition or Windows Server 2008 HPC Edition

Operating Systems for Other ServersOperating system support for servers other than those on which you deploy Lync Server 2010 server roles is dependent on the software you plan to install on those servers. For details about requirements for Back End Servers and other database servers, see Database Software and

16

Microsoft Lync Server 2010 Administration GuideClustering Support. For details about requirements for reverse proxy servers (for edge deployment), see Internet Information Services (IIS) Support. For details about other software requirements, including infrastructure and virtualization support, see the other topics in the Server Software and Infrastructure Support section.

Additional Operating Systems for Administrative ToolsLync Server 2010 supports installation of the administrative tools, which includes the Topology Builder, on computers running any of the 64-bit editions of the operating systems supported for deployment of server roles (as described in the previous section). Additionally, you can install administrative tools on the 64-bit editions of the following operating systems:

The Windows 7 operating system (required) or latest service pack (recommended) The Windows Vista operating system with SP2 (required) or latest service pack (recommended)

Operating System for the Planning ToolLync Server 2010 supports installation of the Planning Tool on computers running any of the following operating systems:

The 32-bit version of Windows 7 operating system (required) or latest service pack (recommended) The 64-bit version of Windows 7 operating system (required) or latest service pack (recommended) using the WOW64 x86 emulator The 32-bit edition of Windows Vista with SP2 operating system (required) or latest service pack (recommended) The 64-bit edition of Windows Vista with SP2 operating system (required) or latest service pack (recommended) using the WOW64 x86 emulator The 32-bit edition of Windows XP with SP3 operating system (required) or latest service pack (recommended) The 64-bit edition of Windows XP with SP3 operating system (required) or latest service pack (recommended) using WOW64 x86 The 32-bit edition of Windows Server 2008 operating system (required) or latest service pack (recommended) The 64-bit edition of Windows Server 2008 operating system (required) or latest service pack (recommended) using WOW64 x86 The 32-bit edition of Windows Server 2008 R2 operating system (required) or latest service pack (recommended) The 64-bit edition of Windows Server 2008 R2 operating system (required) or latest service pack (recommended) using WOW64 x86

Administrative Tools Software RequirementsThis topic describes the software required to install and use Microsoft Lync Server 2010 administrative tools in addition to the operating system requirements.

17

Microsoft Lync Server 2010 Administration GuideMicrosoft .NET Framework 3.5 with Service Pack 1 (SP1)The 64-bit edition of Microsoft .NET Framework 3.5 with SP1 is required for Microsoft Lync Server 2010. Setup prompts you to install this prerequisite and it automatically installs it if it is not already installed on the computer. .NET Framework 4.0 can be installed on the same computer as well, but does not take the place of .NET Framework 3.5 with SP1, which is the required version for Lync Server 2010.After installing the .NET Framework 3.5 SP1 package, you should immediately install the following updates:

Microsoft Knowledge Base article 959209, An update for the .NET Framework Service Pack 1 is available, at http://go.microsoft.com/fwlink/?linkid=197396, which addresses a set of known application compatibility issues. Microsoft Knowledge Base article 967190, Update for .NET Framework 3.5 SP1 (KB967190), at http://go.microsoft.com/fwlink/?linkid=197397, which addresses a file association issue for XPS document types. Microsoft Knowledge Base article 981575, A memory leak occurs in a .NET Framework 2.0-based application that uses the AesCryptoServiceProvider class, at http://go.microsoft.com/fwlink/?linkid=202909. Microsoft Knowledge Base article 974954, FIX: When you run a .NET Framework 2.0-based application, a System.AccessViolationException occurs, or a dead-lock occurs on two threads in an application domain, at http://go.microsoft.com/fwlink/?linkid=205337.

Windows Installer Version 4.5Microsoft Lync Server 2010 uses Windows Installer technology to install, uninstall, and maintain various server roles. Windows Installer version 4.5 is available as a redistributable component for the Windows Server operating system.Download Windows Installer 4.5 from the Microsoft Download Center at http://go.microsoft.com/fwlink/?linkid=197395.

Windows PowerShell 2.0Windows PowerShell 2.0 command-line interface is automatically installed with the Windows Server 2008 R2 operating system and the Windows 7 operating system. On servers running the Windows Server 2008 SP2 operating system or Windows Vista operating system with Service Pack 2 (SP2), you must install Windows PowerShell 2.0 manually. Before doing so, you must remove any previous versions of Windows PowerShell from the computer.To install Windows PowerShell 2.0, see the Microsoft Knowledge Base article 968929, Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0), at http://go.microsoft.com/fwlink/?linkid=197390.

Microsoft Silverlight 4 browser plug-inMicrosoft Lync Server 2010 Control Panel is a web-based tool and requires that you install Microsoft Silverlight 4 browser plug-in version 4.0.50524.0 or the latest version. When you start

18

Microsoft Lync Server 2010 Administration GuideLync Server 2010 Control Panel, if this software is not installed or if an earlier version earlier than 4.0.50524.0 is installed, Lync Server Control Panel prompts you to install the required version.See AlsoServer and Tools Operating System SupportAdministrative Tools Infrastructure RequirementsAdministrator Rights and Permissions Required for Setup and Administration

Administrator Rights and Permissions Required for Setup and AdministrationSetup and deployment of Microsoft Lync Server 2010 requires that the person installing and deploying the software be a member of local or domain-level groups. Administrative tools for Lync Server 2010 can require additional permissions.

Group Membership RequirementsThe following table summarizes the group or groups that a person should belong to in order to successfully install, manage, and troubleshoot Lync Server 2010.

Lync Server Executable Group Membership Required

Setup.exe Executable that starts the installation of the Lync Server administrative tools.

Member of the Local Administrators group on the computer from which the executable is run. Member of Domain Users group to read information in Active Directory Domain Services (AD DS). This level of permission is required because the automatic installation of required MSI packages on the local computer requires privileges that allow reading from and writing to protected local computer resources such as Program Files directories, and protected registry such as the Local Machine hive.

Tip: You can also delegate setup permissions to users or groups to whom you do not want to grant membership in the Domain Admins group. For details, see Granting Setup Permissions in the Deployment documentation.

Deploy.exe Called by setup.exe, deploy.exe is responsible for the deployment of the software components for the server roles.

Member of the Local Administrators group on the computer from which the executable is run. Member of Domain Users group to read information in AD DS. This level of permission is required because the automatic installation of

19



required MSI packages on the local computer requires privileges that allow reading from and writing to protected local computer resources such as Program Files directories, and protected registry such as the Local Machine hive. Membership in RtcUniversalReadOnlyAdmins group is necessary to read the Central Management store.

Note: If you are running the Windows Vista operating system or Windows 7 operating system, you will be prompted by User Account Control (UAC) to proceed with installation. If you are logged on with a standard user account, you will need someone who is a member of the Local Administrators group to provide credentials when prompted for an account with permissions to install the software.

Bootstrapper.exe Called by setup.exe, bootstrapper.exe is responsible for deployment and configuration of server roles.

Member of the Local Administrators group on the computer from which the executable is run. Member of Domain Users group to read information in AD DS. This level of permission is required because the automatic installation of required MSI packages on the local computer requires privileges that allow reading from and writing to protected local computer resources such as Program Files directories, and protected registry such as the Local Machine hive.

OCSLogger.exe Administrative troubleshooting tool for capturing messages on server roles.

Member of the Local Administrators group on the computer from which the executable is run. The executable is manifested as requireAdministrator.

TopologyBuilder.msc Wizard-driven user interface to create, view, adjust, and validate Lync Server topologies.

Member of the Local Administrators group on the computer from which the executable is run to view the topology. Member of the RTCUniversalServerAdmins group to change configuration settings. Member of the

20



RTCUniversalServerAdmins group and Domain Admins group, or member of the RTCUniversalServerAdmins group (only if the group has been granted delegate setup permissions), to publish the topology. For details about delegating setup permissions to allow members of the RTCUniversalServerAdmins group to publish the topology without being members of the Domain Admins group, see Granting Setup Permissions in the Deployment documentation.

AdminUIHost.exe Web-based graphical user interface for managing Lync Server.

Member of CsAdministrator group or member of another role-based access control (RBAC) role to which the specific administrative task is assigned. Microsoft Lync Server 2010 Control Panel executes configuration changes by running Lync Server Management Shell cmdlets. For a list of predefined roles and the cmdlets members are permitted to run, see Role-Based Access Control in the Planning documentation.

PowerShell.exe with the Lync Server module loaded Command-line administrative tool with cmdlets specific to management of Lync Server.

Member of CsAdministrator group or member of another RBAC role to which the specific cmdlet has been assigned. For a list of predefined roles and the cmdlets members are permitted to run, see Role-Based Access Control in the Planning documentation.Or, member of one or more of the following groups, depending on the cmdlet:

RTCUniversalServerAdmins RTCUniversalUserAdmins RTCUniversalReadOnlyAdmins

The group memberships in the preceding table represent the minimum memberships. Other memberships which will grant the permissions necessary to initiate the setup and deployment are possible, including membership in the Domain Admins group or Enterprise Admins group.See AlsoInstall Lync Server Administrative Tools

21

Microsoft Lync Server 2010 Administration GuideRequirements to Publish a TopologyThis topic describes the infrastructure and software requirements that are specific to publishing a topology, whether by using Topology Builder or the Lync Server Management Shell command-line interface. These requirements are in addition to the general operating system, software, and permissions requirements applicable to all Microsoft Lync Server 2010 administrative tools. Ensure that you satisfy all administrative tools requirements before you publish a topology.

You must run Topology Builder on a computer that is joined to the same domain or forest of the Lync Server 2010 deployment you are creating so that Active Directory Domain Services (AD DS) preparation steps are already completed, enabling you to use the administrative tools on that computer to successfully publish your topology.

Note: For details about preparing AD DS, see Preparing Active Directory Domain Services for Lync Server 2010 in the Deployment documentation.

The computers defined in the topology must be joined to the domain, except for Edge Servers, and in AD DS. However, the computers do not need to be online when you publish the topology. The file share for the pool must be created and available to remote users. In order to publish an Enterprise Edition Front End pool, the SQL Server-based Back End Server must be joined to the domain in which you are deploying the servers, online, and configured with the appropriate firewall rules to make it available to remote users. For details about specifying firewall exceptions, see Understanding Firewall Requirements for SQL Server. For other details about configuring SQL Server, see Configure SQL Server for Lync Server 2010.

Note: Standard Edition server has a collocated database that will accept the published configuration. You must first run the Prepare first Standard Edition server setup task in the Lync Server Deployment Wizard.

If you run Topology Builder on a computer where you plan to later install Lync Server, then you must install the Microsoft SQL Server 2005 backward compatibility components by running the first setup task in the Lync Server Deployment Wizard before you publish the topology. For details, see Install the Local Configuration Store or Install the Standard Edition Local Configuration Store.

Note: You do not need the Microsoft SQL Server 2005 backward compatibility components to publish the topology if you run Topology Builder on a dedicated administrative console or if you run Topology Builder on a computer where Lync Server is already installed. (Lync Server setup automatically installs the backward compatibility components along with other component files required by Lync Server.)

See AlsoAdministrative Tools Software RequirementsServer and Tools Operating System Support

22

Microsoft Lync Server 2010 Administration GuideAdministrator Rights and Permissions Required for Setup and Administration

23


Install Lync Server Administrative ToolsThis topic describes how to install the administrative tools you need to use to deploy and manage Microsoft Lync Server 2010. The administrative tools are installed by default on each server running Lync Server 2010. Additionally, you can install the administrative tools on other computers, such as dedicated administrative consoles. We strongly recommend that you install the administrative tools on a computer that is in the same domain or forest as the Microsoft Lync Server 2010 deployment you are creating because by doing so you ensure that Active Directory Domain Services (AD DS) preparation steps are already complete, which enables you to use the administrative tools on that computer later to publish your topology.Ensure that you review infrastructure, operating system, software, and administrator rights requirements before you install or use the Lync Server administrative tools. For details about infrastructure requirements, see Administrative Tools Infrastructure Requirements. For details about operating system and software requirements to install the Lync Server 2010 admi

Admin Guide Lync

Documents

Transcript of Admin Guide Lync