![]() ![]() The goal of this document is to give you a troubleshooting framework for WSUS and at the same have a single location for you to add new troubleshooting scenarios and techniques for WSUS. Make sure to document all those details, this way you can go back and review your notes while analyzing the data to double check the scenario and the details of it. For example: is WSUS behind a firewall? Is the firewall allowing anonymous access from WSUS to the Internet? These are following up questions that can assist you while scoping the issue and understanding the problem. Drawing the topology will help you to identify potential points of failure and will assist you asking follow up questions. It is also important to mention that during phase 1 (understanding the problem) it is highly recommended that you have a clear understanding of the topology where WSUS is located. Sometimes data gathering phase must be done in both locations (client and server) at the same time in order to better understand what’s happening. While troubleshooting a technology such as Windows Server Update Services (WSUS) you also need to identify where the issue is located (client or server) in order to correctly perform data gathering. ![]() Elaborate another data gathering plan and move back to step 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |