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.
When you use the cmdlet, it spews a fair amount of verbose info to the screen, even when -verbose is not used. This is not expected behavior. It should only be displayed when -verbose is used. This is problematic for those who use this programmatically.
If you create a trusted application endpoint, and assign a SIP address where the "sip:" prefix is either capitalized or in all upper case, you don't get an error/warning. However, if you then try to send an IM to that endpoint, you get obscure errors. The solution is to change the "sip:" prefix to all lower case. It would be nice if Lync either errored when you try to assign it, or just corrected it to all lower case. ...more »
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.
http://social.technet.microsoft.com/Forums/lync/en-US/021bc23c-0ab1-4cc9-abb8-e6426a43e35e/lync-multiple-simultaneous-account-login?forum=ocsclients why connect to multiple logins from Lync client: - officer on duty (should have access to his real identity and OoD account -- in mobile phone solved by give phone to next person) -- and persisten chat or group chat not solve it). - supporting people on customer Lync ...more »
When adding a new user with EV through the Lync Control Panel or through powershell, you must add
"tel:" in front of the (required) telephone number. Since this requirement is there 100% of time lync should just go ahead and add "tel:" on its own.
The ability to "clone" a given policy from an existing policy. This would be great for when you want to create another policy that has the same settings, except one or two.
PLEASE!! Make Room # a property that you can set using New-CsCommonAreaPhone Both in Lync and the new AD Contact that it creates. We receive every type of doc possible PDF, JPGs, Excel spreads sheet galore. The ONLY thing they "ever" have in common is the Room #. P.S. I grant the phone # so that's a no go...
Lync should be able to provide better user identity management and AD integration through ADFS and DirSync or similar. This is currently a major limitation for LHP, hosted solutions when cloud AD integration is not possible. Current solutions involve complex, costly and often limited identity management solutions like FIM or third parties.
When running open federation the only way of checking which organizations that are federating with your organization is to go into your edge server (in that workgroup in that DMZ), open the event viewer and look for Event ID 14601. Here you will find a list of all active domains (organizations) that are currently federating with you. My suggestion is that this list should be visible in the Lync Server Control Panel ...more »
Sefautil is a nice tool for configuring call forwarding, delegates, group call pickup, etc. But it's quirky, lacks good reporting and error handling, and just plain difficult if you don't use it often. Having standard cmdlets to perform these tasks would be a blessing.
It would be nice if you could run Export-CsTopology and open the resulting file in topology builder. This would be great for consultants.