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.
My suggestion is that this list should be visible in the Lync Server Control Panel... more »
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...
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.
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.
It would be nice if you could run Export-CsTopology and open the resulting file in topology builder. This would be great for consultants.
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.
The resource kit for OCS provided a script that allowed administrators to add and remove contacts and groups to users (LCSAddContacts.wsf ).
Please, provide this functionality "out-of-the-box".
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 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.
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.