Monthly Archives: March 2014

Why can’t Lync do it?

There may be a great answer, there are many things Lync doesn’t do and it’s part of the intentional design.  It may be to avoid stepping on third party toes, or it may be to keep the administrative experience simplified, or perhaps it’s not as technically simple as it appears on the surface.  But maybe you have a great idea and you want to get it to Microsoft.  What about a Lync bug report?  How do you submit a Lync feature request?  What do you do?  I always suggest starting with your Microsoft representative first.  Second?  Unfortunately there’s not a great official channel, however there is IdeaScale.  IdeaScale has been known to be frequented by Microsoft and as such it’s our best go-to at this time.

However, if it’s not a bug, but an interesting feature request, have you considered creating an add-on or utility?  Lync has an outstanding development community and platform.  Incidentally, if you do have a great idea, post it here in the comments, I might just develop it myself.


Difficulty removing a legacy trusted application pool.

I ran into this issue when I found myself trying to remove a server from the topology and realized there was no delete option. It turns out that there was a trusted application pool hanging around tied to this server, no big deal, I’ll just delete it.

PS C:\Users\acaragol> Get-CsTrustedApplicationPool -identity |Remove-CsTrustedApplicationPool
Remove-CsTrustedApplicationPool : Cannot remove legacy trusted application
pool. Use the legacy tools to remove the pool, then run Merge-CsTopology.
At line:1 char:89
+ … |Remove-CsTrustedApplicationPool
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Remove-CsTrustedApplicationPo
ol], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Microsoft.Rtc.Managemen

Today, I’m ashamed to admit I made this much harder than it had to be. The merge-cstopology usually reserved for OCS migrations triggered legacy thoughts of OCS 2007 R2 admin tools. OCS has been long gone in this environment. Rather that stopping to think about it, I was in a rush and ran to the search engines. There’s not a lot out there on this error at this time, perhaps because most figure it out more quickly than I did and don’t actually need to search. What does exist are references to exporting the topology and manually editing the XML (which is not a good idea in this instance). There is also a reference to hacking it out using ADSIEdit and some other handy tools which can be daunting. How did I get rid of it? I used the Lync 2010 PowerShell. This is my legacy tool, nothing to do with the old OCS implementation or a partially created object, nothing hard. Just rerun the command from a Lync 2010 server’s PowerShell and you’re done.

PS C:\Users\acaragol> Get-CsTrustedApplicationPool -identity |Remove-CsTrustedApplicationPool
One or more application or external servers have been deleted.
When you delete an application or external server, you delete all configuration state for the hosted applications. Do you want to continue?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(Default is “Y”):y
PS C:\Users\acaragol>

Bulk Lync User Addition via Powershell

When enabling users for the first time in Lync, we get a lot of requests for bulk enabling based on group membership or other factors.  If this is something you would like to do, you don’t need a tool, just check out the powerful get-csaduser and get-adgroupmember commands in Powershell:

Here’s a sample command to get you started on enabling users by group:

get-adgroupmember -identity “your group” |foreach {get-adus
er $_.samaccountname | foreach {enable-csuser -identity $_.userprincipalname -re
gistrarpool -sipaddresstype samaccountname -sipdomain}}


If you wanted to enable all users by OU try this:

Get-CsADUser -OU “ou=Your OU Name,dc=domain,dc=com” | enable-csuser -registrarpool “” -sipaddresstype emailaddress


(Note: Edited June 6, 2014 because I found a group enablement command that I liked better)


As many many other’s have blogged and TechNet has seen numerous posts, the February 2014 Lync update changed the emoticons to what appears to be a simpler more 8 bit looking version.  I shrugged when I saw this, but shortly thereafter protests were held and riots broke out.  People really seem to love their emoticons and I was shocked to see how upset it made many.  This ranged from the tongue-in-cheek to the downright enraged.  Do changes like this shake your faith in the product or do you see them as annoyances?   If you really hate it, you might want to head over to Ideascale and cast your vote.