Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

Once more first. Really make always sure your environment is patched and up to date. Mainly if you have a slow Join Conference user experience. Validate your DFS or File Server. Just what we experienced during certain Skype for Business Updated, as well as support cases is: - Migration is slow - Join Conferencing experience is slow - Address Book generation is slow and more This is, if the Fileshare is not fast enough. What does this mean: You should ensure the IOPS as well as the network throughput is sufficient and not the bottleneck in your environment. Do a measurement on the file servers, see what is happen if DFS replication is kicked in, check if this is share file server, whats happen if other app's access the shares and monitor the IOPS/ bandwidth. Just this is not all, also just perfmon for CPU load, and Memory especially paging. If you experience slow conference joins, it will be the issues, mostly. (Sure the local SQL server also consumes performance ...

While your are installing and publishing a Skype for Business Server 2015 Topology, you have to create a File Share for all important services. In this example the File Share is located on the same server which will later host the Skype for Business Standard Server. But in larger or other setup, where the File Share is located on SAN, DFS or File Cluster, you might experience the same issue. File Share and Folder Prerequisites: The share name can either a normal share as well as a administrative share$ Share Permission: EVERYONE: READ ADMINISTRATORS: FULL CONTROL, CHANGE, READ Folder (Security Settings): SYSTEM and CREATOR: must be Windows Server default Installing user: FULL CONTROL local Server Administrators: FULL CONTROL Skype for Business Topology Builder: Must be started with: "Run as administrator" Example and problem description: This example applies to a Windows Server 2012 R2, where we are installing in Single Domain Forest with a...