While the Lync room system is extremely easy to use there are cases where it would be nice to enable protected meeting participation. A possible example would be to have a checkbox in the meeting schedule options that protects room system. When a person joins from a room the system prompts them for the passcode. The passcode should be easy to remember like maybe a conferencing PIN.
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 »
Right now you can only assign this globally or per site. It would be great to see this as a user policy so we could define it for Common Area Phones.
When users are enabled for the Dial-in conferences "EnableDialInConferencing = $true" you need to enable "AllowAnonymousParticipantsInMeeting = $true" as well because otherwise PSTN participants needs Lync account to be able to join meeting by phone. If you think the security level between participants coming through the edge or they are coming through the PSTN conference they are night and day. So it is wrong that these ...more »
I have encountered scenarios where customers due to Security concerns need to Control what users can share, but not remove the possibility entirely. In such a case the Desktop/Application/None feature within Conferencing Policy is not enough. This could be implemented the same way that the TrustModelData registry key is used for domain trust, so that GPO or ADMX could be Applied by admins. Preferably both an included/allowed ...more »
It would be good to see a conferencing policy option that has a time limit setting for how long someone is able to control a machine, once they have passed the time limit they can request control again, This would be a useful security feature, as users may forget someone has control to their machine leaving the machine exposed.