Chapter 03 Client Administration, Darmowe ebooki Microsoft, pobierz pdf

[ Pobierz całość w formacie PDF ]

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.

Microsoft, Internet Explorer, Lync, Outlook, PowerShell, Silverlight, and Windows are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

This chapter is part of the Microsoft Lync Server 2010 Resource Kit book that is currently being developed. Chapters will be available for download while this book is being completed. To help us improve it, we need your feedback. You can contact us at nexthop@microsoft.com. Please include the chapter name.

For information about the continuing release of chapters, check the DrRez blog at http://go.microsoft.com/fwlink/?LinkId=204593.

Contributors

Project Manager: Susan S. Bradley

Content Architect: Rui Maximo

Chapter Lead: Michele Martin

Writers: Philipp Beck, Brandon Taylor

Contributing Writers: Paul Brombley

Sidebar Contributor: Paul Brombley

Technical Reviewers: Paul Brombley, Dave Howe, Antti Kiviniemi, Cameron Parker, Stefan Plizga, Jeffrey Reed, Nick Smith, Stephen Wong, Rob Young

Lead Editor: Janet Lowen

Client Administration

Microsoft® Lync™ Server 2010 introduces updated and enhanced tools for managing servers and clients. With the introduction of the Microsoft Lync Server 2010 Control Panel, all client management tasks are integrated into the same tool that is used to manage servers. You can centrally manage all policy settings and apply them at the global level, site level, or user level (single user or group of users). In addition, with the new Lync Server Management Shell, you can use Windows® PowerShell command-line interface commands to automate policies across the entire infrastructure.

The clients for Lync Server 2010 provide a full set of unified communications features for the enterprise information worker, the external meeting attendee (anonymous user or traveling enterprise member), the federated partner, and the occasional user who rarely connects to your infrastructure. In addition, the Microsoft Lync 2010 Attendant combines with the Response Group application features to cover a wide variety of receptionist scenarios.

This chapter covers details about the operational management of the following clients:

· Microsoft Lync 2010, the full-featured client that installs on client computers.

· Microsoft Lync 2010 Attendee, the meeting-only client for enterprise and non-enterprise attendees that installs on client computers.

· Microsoft Lync Web App, the web-based, meeting-only client for enterprise and non-enterprise attendees.

· Lync 2010 Attendant, the call-management client designed for receptionist or administrative assistant scenarios.

In this chapter, you will find information about managing the client experience, updating clients as needed, and configuring policies based on your administrative, compliance, and country/regional needs.

Note. This chapter focuses on Lync Server 2010 computer-based clients. For detailed information about using Microsoft Lync 2010 Phone Edition and devices, see Planning for Devices, available at http://go.microsoft.com/fwlink/?LinkId=204935, and Deploying Lync 2010 Phone Edition, available at http://go.microsoft.com/fwlink/?LinkId=204936.

Managing Lync 2010

Lync 2010 is the primary Lync Server client used in an enterprise. To ensure a consistent user experience across all endpoints, Lync Server uses in-band provisioning to propagate policies to clients. Client management settings that were previously controlled through Group Policy are moved into the shared Central Management store database. This enables policies and settings, for example, the Media Relay Authentication Server (MRAS) setting, to be sent to clients that are not joined to the domain in addition to Lync Phone Edition devices.

For endpoints such as Lync, an advantage of using in-band provisioning is that information critical to client functionality is stored on the server and not on the computer or the specific endpoint. This simplifies the application of policies and server settings across the organization because the settings apply to all clients that sign in to the server pool.

Most of the settings that determine client features and functionality are configurable through the Lync Server Control Panel or Lync Server Management Shell. These settings are then passed along to clients though in-band provisioning. However, cases remain for which Group Policy is required. Specifically, you must use Group Policy to set client bootstrapping policies that take effect before the client signs in to the server and receives in-band provisioning settings. For example, if you want to specify the server that a client should use during the sign-in process, you have to configure a Group Policy setting so that the server information exists on the client before the client signs into Lync Server.

The section “Server Settings versus Group Policy” later in this chapter discusses when to use Group Policy.

Automatic Discovery During Sign-in

When connection settings are set to Automatic Configuration, Lync 2010 and Lync 2010 Attendant use automatic discovery during sign-in to locate the Registrar server.

The client uses a sequence of DNS and DHCP information to find the Registrar server. If the DNS and DHCP settings are not configured correctly, the client cannot sign in automatically. As in previous versions of Microsoft Office Communications Server, in Lync Server 2010 you can still use Group Policy to specify the sign-in server that a client should use. However, Group Policy takes effect only for clients that are joined to the domain. For the mobile user who signs into the domain network infrequently, a change in Front End Server will prevent the user from signing in. In situations like these, it is essential to ensure that DNS and DHCP are configured correctly to enable automatic discovery. For details about configuring the client sign-in process, see the section “Lync Client Sign-in Process” later in this chapter.

Lync 2010 also uses the Autodiscover service of the Client Access server in Microsoft Exchange Server 2010 for Exchange Unified Messaging (UM) features, such as missed call logs, call history, and voice mail preview. The Exchange Autodiscover service must be configured properly for these features to be available in Lync 2010. For details about how Lync clients interoperate with Exchange, see the section “Exchange Web Services and Autodiscover Service” later in this chapter.

Managing Lync Versions

In Lync Server 2010, you can use the enhanced Client Version Check application to filter by client version and specify the action the server should take when certain client versions attempt to sign in. Among the options you can specify for Lync 2010 clients is the new Block and Upgrade option, which automatically updates clients by using Windows Server Update Service (WSUS) or Microsoft Update. Because WSUS and Microsoft Update are more scalable solutions, this option helps to simplify client version management in small and large deployments. The auto-update feature that was provided in Microsoft Office Communications Server 2007 R2, in which the client polled the auto-update service to determine if an update was available, is not included in Lync Server 2010.

Managing Lync Attendee

Attendee is a downloadable client that allows anonymous users or users with enterprise credentials to participate in meetings when they do not have Lync 2010 or Lync Attendant installed. This client is particularly useful when a meeting organizer wants to include external users and partners in a meeting. Attendee is also an essential client for users who have not yet moved to Lync Server 2010 during migration from a previous version of Office Communications Server.

Lync Attendee does not receive in-band provisioning settings from the server. Management of Attendee clients generally consists of the following:

· Using client version policy to specify versions of Attendee that are allowed in your environment.

· Determining whether or not you want to present Attendee as an option to users when they join Lync meetings.

Meeting Join Page

When a user clicks a meeting link in a meeting request, the meeting join page detects whether a Lync Server client is already installed on the user’s computer. If a client is already installed, the default client opens and joins the meeting. If a client is not installed, the meeting join page (the page that prompts the user to join the meeting) displays options for joining the meeting by using alternate clients.

The meeting join page always contains the option to use Lync Web App. In addition to this option, you can decide whether to show a link for downloading Lync Attendee or a link for joining by using a legacy Communicator 2007 R2 client. Both of these links are disabled by default. The Communicator 2007 R2 option allows users to join Lync meetings with some limitations. These users will be able to participate in the IM, voice, video, and sharing portions of the meeting, but other features such as PowerPoint upload, whiteboard, and polling features are unavailable.

Figure 1 shows how the meeting join page appears when the Attendee download is enabled.

Figure 1. Meeting join page

You can control the Lync Server 2010 clients that are available for joining scheduled Lync Server 2010 meetings by using the Lync Server Control Panel or the Lync Server Management Shell to configure the meeting join page. For details about how the meeting join page determines the options available for joining the meeting, see the section “Meeting Join Flow” later in this chapter.

Managing Lync Web App

Lync Web App is a browser based Microsoft Silverlight®-based application that enables access to Lync meetings. The Lync Web App requires a Silverlight enabled browser and runs on the operating system and browser combinations listed at http://go.microsoft.com/fwlink/?LinkId=211720. Users who do not have Lync, Lync Attendant, or Lync Attendee installed can use Lync Web App to attend meetings. Lync Web App does not require installation, although Silverlight is a prerequisite and a plug-in is required for the sharing features. As with Lync Attendee, the user may or may not have an account within the enterprise, which makes Lync Web App useful for external users or partners and during migration. Lync Web App is always an option on the meeting join page.

Lync Web App in Lync Server 2010 is analogous to Communicator Web Access in Office Communications Server 2007 R2. However, Lync Web App is a meeting client only, and it does not support presence, contacts, or audio/video capabilities. Deployment and maintenance is minimal with Lync Web App because it is provided by default as a service on the Front End Server.

Managing Lync 2010 Attendant

In Lync Server 2010, the Attendant is designed primarily for receptionist and administrative assistant scenarios. For receptionists and administrative assistants who must manage high volumes of calls and conversations, you can create an effective solution by combining the Response Group application in Lync Server with the Attendant client. This section describes the Lync Server features you should consider and ways that you can manage these features.

Managing the Lync 2010 Attendant is similar to managing Lync 2010. As with Lync, most of the settings that determine client features and functionality are configured by using Lync Server Control Panel and are passed along to Attendant clients through in-band provisioning. However, there are Group Policy settings you can configure to control the behavior of Attendant clients. ...

[ Pobierz całość w formacie PDF ]

Podobne