![]() ![]() For the script to work, you need to make sure that remote management is enabled on all Lync servers. To help others with this issue, I've created a little Powershell script that will recycle the LyncIntFeature and LyncExtFeature app pools for all Lync servers. Recycling the aforementioned apppools resolved the issue. Less than 10 minutes later, all the servers processor utilization spiked. I confirmed this by updating the topology and publishing it. ![]() UPDATE: Thanks to dannydpa on Twitter, it appears the trigger may be Lync topology publishing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |