![]() When you define the users issue, you should also run the, Office 365 Support and Recovery Assistant (aka SaRA) on the client to have a good view of configuration that can impact their experience. Understanding the full client experience and effect can help determine the logging and troubleshooting path. In every case, it's best to spend some time understanding what the user is experiencing. It can be a bit overwhelming, sure, but depending on the depth that you need to get into – it might be all worth it! ![]() This post is not meant to be a post that you necessarily read from start to finish, but rather serve as a guidance for when you need to troubleshoot hard to find issues related to client connectivity. There are too many potential underlying causes to cover them all but hopefully this will serve as a good starting point for troubleshooting. In this post we will focus on methods and tools to troubleshoot these. There are many factors that can contribute to these symptoms, and each one can lead down a completely different troubleshooting path.
0 Comments
Leave a Reply. |