This article may help you with updating service account credentials in an existing CQD deployment.

I blog may help you to understand the default behavior on emergency notification to a distribution group when calls are initiated from polycom vvx 500. I have created an exchange DL and added four members to the group for testing.

I don’t have the user photo set in AD or share-point. Test SFB client looks like below before adding the photo.

This blog is just for reference. Most of the steps are same as Lync 2013/2015. My CMS database is located in SFB 2015 pool. CMS replication is uptodate.

This is just for awareness, I have a SFB 2015 deployment on Hyper V with limited memory. My SFB users are assigned with address book web search policy. When you have high memory utilization, address book search may not return anything while searching for a keyword.

I have deployed a SFB 2019 and Lync 2013 pools in the same AD forest. Persistent chat is enabled on Lync 2013 server and it is not supported in SFB 2019 pool. This blog will test the client operation between the environments. Here is the topology for reference;

This blog may help you to test and implement static registration expiry for SFB mobile devices. Static registration configuration is populated in web.config file under following location. Usually, Microsoft do not support any configuration changes to webconfig file until or unless recommended by support.

This blog may help you to understand the expected workflow for troubleshooting the on-premise PPT sharing issues with SFB 2015 deployment.

First of all,  tri co-existence is not supported by Microsoft. This article doesn’t endorse any unsupported configuration.

There are many cases where in user left the company and rejoined or migrated from resource forest etc can cause AD SID mismatch in FE server SQL express database. Later, user may not be able to signin to SFB client. Following steps may help you to delete the orphan object and clean the FE database.