I'd like to see an improvement, both in topology builder and in the front end server to automatically generate the DNS Records that should be plumbed in. Id like to see the service also self reparing. As an example of how this can be done - thik about the netlogon service of AD. If you break the DNS records, the netlogon service recreates the needed records. Result! I'd like the Topology builder to generate either a ...more »
It would be nice if there were some test-cs* cmdlets that could be used for coexistence during migration scenarios, such as OCS 2007 R2 and Lync 2010 migrations to 2013.
In Exchange 2010, when you perform actions from the Exchange Control Panel that involve a "wizard" process (e.g. enable a user for UM), the final screen shows the PowerShell commandlet that was executed and offers the ability to copy it to the clipboard.
It would be beneficial if the Lync Control Panel would also behave in a similar fashion.
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 »
It would be nice if you could run Export-CsTopology and open the resulting file in topology builder. This would be great for consultants.