Lync Server

Add -DomainController to New-CsCommonAreaPhone

Enable-CsUser has -DomainController, as do Get/Set-CsCommonAreaPhone. Being certain which domain controller a Common Area Phone is created on would enhance provisioning performance, enabling policies to be granted right after object creation.

 

This affects large environments with multiple DCs in far-flung locations.

 

This discrepancy is still present in Skype for Business Server.

Submitted by (@texmandie)
1 comment

Voting

0 votes

Lync Server

Enable Phones for use in Response Groups

The only supported clients for response groups are: Lync 2013

Lync 2010

Lync 2010 Attendant

Office Communications Server 2007 R2 Attendant Lync Phone Edition

 

We would like to use phones such as a Wifi phone or a CX600 phone, or possible a mobile phone with the Lync client. All of these are not supported scenarios.

Submitted by
4 comments

Voting

15 votes

Lync Server

Pool and User-level PIN Policies

In Lync 2010/2013, our only options for PIN policies are Site-based or the Global policy. The PIN policies should have the same applicable levels as all of the other policies available in Lync (Global -> Site -> Pool -> User). When setting up conference phones (with an associated Exchange resource account), we could disable "Enforce device locking" for these accounts and allow calendar access without affecting the rest ...more »

Submitted by
Add your comment

Voting

2 votes

Lync Server

Manage Common Area Phones from the Control Panel

Add a tab for managing Common Area Phones to the control panel

Submitted by
5 comments

Voting

25 votes

Lync Server

support standards based SIP phones

support standards based SIP phones without the need for 3rd parting software (smartsip) or gateway.

 

I would presume these phone would get limited lync functionality: basic presence like on a call and available, and some other limitations.

Submitted by
10 comments

Voting

9 votes