> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/getting-started/install-guardware-server/whitelist-guardware-management-console.md).

# Whitelist GuardWare Management Console

Anti-virus, EDR, and XDR solutions can block or quarantine Management Console processes and files. This may interrupt web requests, reporting, monitoring, and database access.

Add the following process and folder exceptions to your security solution's exclusion or trusted applications list. Configure these exclusions before installing the Management Console where possible.

{% hint style="warning" %}
Configure exclusions before installation. Security tools may block or quarantine components while the installer creates them.
{% endhint %}

### Web and service processes

Allow these processes so IIS, PHP, and Redis can support the Management Console.

* `w3wp.exe`
* `php-cgi.exe`
* `php.exe`
* `RedisService.exe`

### Folders

Exclude these folders to prevent security software scanning the Management Console web content and MySQL data.

* `C:\ProgramDataMySQL\MySQL Server 8.4` — if version 8.4 is installed
* `C:\inetpub\wwwroot`

### Management Console processes

Allow these GuardWare processes to ensure Azure Key Vault handling, cloud monitoring, and reporting continue without interruption.

* `GWAKVHandler.exe`
* `GWCloudMonitorV5.exe`
* `GWPhpReportHandler.exe`
* `InsightReportEngine.exe`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guardware.com/getting-started/install-guardware-server/whitelist-guardware-management-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.