Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Lync Server 2013 : Configuring Persistent Chat (part 1) - Administrative Access, Persistent Chat Policies

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
12/4/2014 8:34:00 PM
With Lync Server 2013, Persistent Chat configuration is performed using the standard Lync Server administration tools, greatly simplifying the entire process of configuring and maintaining the Persistent Chat environment. Both the Lync Server Control Panel and the Lync Server Management Shell can be used to perform Persistent Chat configuration tasks. The following sections provide details on the primary tasks that are necessary for a Persistent Chat deployment.

Administrative Access

The first task in configuring the Persistent Chat environment is granting administrative permissions to the accounts that will be managing the environment. With all Lync Server roles, RBAC (role-based access control) is used to grant privileges by assigning users to predefined Lync Server administrative roles represented by Active Directory security groups, and this includes Persistent Chat. One such group is provided specifically for the administration of the Persistent Chat environment, the CsPersistentChatAdministrator group. This security group, along with the rest of the predefined Lync security groups, is located by default in the top-level Users container in the forest root AD domain. Members of the CsPersistentChatAdministrator group are granted access to the Lync Persistent Chat cmdlets, which can be executed using either the Lync Management Shell or the Lync Server Control Panel.


Note

While the CsPersistentChatAdministrator group grants specific access to the Persistent Chat portion of the Lync environment, two other groups also have administrative access to much of the Persistent Chat configuration as part of their broader administrative scope: CsAdministrator and CsUserAdministrator. Therefore, in smaller organizations where one group of administrators manages the entire Lync environment including Persistent Chat, it might not be necessary to populate the CsPersistentChatAdministrator group.


By default, there are no members of the CsPersistentChatAdministrator group, and therefore the group must be populated with user accounts to delegate administrative rights to the Persistent Chat configuration.

Persistent Chat Policies

Persistent Chat policies are used to determine which Lync users are enabled for Persistent Chat. There are four levels of policies that can be used: global, pool, site, and user. There is only one global policy, which is automatically created when Persistent Chat is deployed, and is simply named Global. This default Global policy does not need to be used, but it cannot be deleted.

Only one Persistent Chat pool policy can be created per Lync pool, and it affects all users within that pool. Similarly, one Persistent Chat site policy can be created per Lync site, and it affects all users in that site. On the other hand, multiple Persistent Chat user policies can be created, and applied on a user-by-user basis as needed. Pool and site policies override the global policy, and user policies override the pool and site policies.


Tip

Only a single setting exists in a Persistent Chat policy; it simply allows users that are assigned to the policy to be enabled for Persistent Chat. For this reason, at most only a few Persistent Chat polices are typically needed. If it is determined that all users in the environment will be enabled for Persistent Chat, this can be accomplished using just the global policy. If, on the other hand, Persistent Chat will be assigned to specific users, then the pool, site, or user policies will be useful.


The following example shows the steps for creating a user policy and then assigning the policy to a user:

1. Log on to a system where the Lync administrative tools are installed using an account that is a member of the CsAdministrator or CsPersistentChatAdministrator security groups, and open the Lync Server Control Panel.

2. In the left pane, select Persistent Chat, and then click the Persistent Chat Policy tab at the top.

3. From the New drop-down menu, select User Policy.

4. At the New Persistent Chat Policy screen, enter a name and description for the policy, and then select the Enable Persistent Chat setting, as shown in Figure 1.

Image

Figure 1. Creating a Persistent Chat user policy.

5. Click Commit to save the policy.

6. In the left pane, select Users.

7. Type a portion of the target user’s name in the search field at the top of the screen, and then click Find to list all users that meet the search criteria.

8. Select the target user account in the bottom pane, and then from the Edit drop-down menu click Show Details.

9. Scroll down to the bottom of the user properties, and then use the Persistent Chat Policy drop-down menu to select the user policy created previously.

10. Click Commit to save the setting.

Other -----------------
- Microsoft Lync Server 2013 : Persistent Chat Deployment (part 3) - Installing the Persistent Chat Server Role
- Microsoft Lync Server 2013 : Persistent Chat Deployment (part 2) - Topology Update
- Microsoft Lync Server 2013 : Persistent Chat Deployment (part 1) - Topology Options and Scaling
- Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 2) - Processing meeting requests according to policy
- Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 1) - Providing policy direction to the Resource Booking Attendant
- Microsoft Exchange Server 2013 : Mailbox management - Mail-enabled contacts, Mail users
- Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 2) - Processing moderation requests, Moderated mailboxes
- Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 1) - Moderated groups
- Microsoft Exchange Server 2013 : Mailbox management - Shared mailboxes , Recalling messages
- SQL Server 2012 : Transact-SQL - Functions, Triggers
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server