# Troubleshooting For troubleshooting information and tasks, select **Troubleshooting** in the navigation bar. The data displayed in the **Troubleshooting** view is retrieved by the RAS Management Portal directly from the RD Session Host, not through the RAS Connection Broker. This view can show data important to troubleshoot issues with the RAS RD Session Host Agent even if the agent cannot be reached by the RAS Connection Broker or is currently registered with a different RAS Connection Broker. The following data is displayed: * **Host**: The RD Session Host name. * **Agent**: Agent status (e.g. OK). * **Version**: Agent version. * **RDS role**: Whether RDS role is enabled on the RD Session Host. * **OS type**: Operating system type installed on the host. * **Status**: Displays a long version of the agent status. If the agent is OK, it will say so. If there's an issue, this field explains what is wrong with the agent. You can use this information to troubleshoot the issue. You can also perform the following actions in the **Troubleshooting** view: * **Retrieve logs**: Retrieve host logs as a single ZIP archive. * **Configure logs**: Allows you specify a log level for Parallels RAS Components. Note that you should use Extended and Verbose logging for troubleshooting only. When selecting one of these levels, you can also set the time period after which the log level will go back to Standard. * **Clear logs**: Clear all existing logs. * **Reboot agent**: Reboot the RAS RD Session Host Agent. * **Uninstall agent**: Uninstall the agent. * **Refresh**: Refresh the agent information. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.parallels.com/landing/ras-mp-guide/infrastructure/rd-session-hosts/manage-an-rd-session-host/troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.