Right now, if you run this cmdlet, there is no output to the console unless you use -verbose. And even then, it's limited. It would be nice if there was standard test cmdlet output. It would be really nice if this cmdlet also supported pipelining, such as Get-CsKerberosAssignment | Test-CsKerberosAssignment.
Right now there are no synthetic tests for OWAS. It would be nice if there were to help streamline deployments, health checks, and troubleshooting.
For ease of installation, it would be nice to have the Deployment Wizard be able to install the prerequisites, such as hotfixes, features, and roles that are necessary for installation.
Similar to Exchange, SQL and SharePoint.
Some cmdlets don't support this, such as the *-CsCommonAreaPhone cmdlets. It would be nice if -DomainController was supported to assist with deployment scripts in environments where AD replication comes into play.
Right now, if you want custom presence for your org, you must create an XML file, place it in an accessible location (such as 'C:\Program Files\Microsoft Lync Server 2013\Web Components\External Website' on each of your Front Ends), then configure Lync by using Set-CsClientPolicy. I think a better solution would be cmdlets that let you add/set/remove customer presence settings, and the XML file management would be automatic. ...more »
The Lync Attendant Console desperately needs the ability for create, store and share centralised notes. The issue we are facing is that our receptionist rely on a feature of a previous consoles we were using with out legacy PBX that is not available in the current Attendant console. This the ability to store notes on a user or number, and have them available to all receptionists. I know that you can take a note on an ...more »