> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/remote-actions/setting-up-and-managing-remote-actions/application-control-and-remote-actions.md).
# Application control and remote actions
Microsoft allows organizations to deploy application control policies using AppLocker. It helps you control what executables files, scripts, Windows Installer files, dynamic-link libraries (DLLs), packaged apps, and packaged app installers can run on supported Windows operating systems.
Learn more about [AppLocker](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-overview) (external link) and its [requirements](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/requirements-to-use-applocker) (external link) directly on the Microsoft documentation website.
## AppLocker compatibility mode
Starting from the Collector version 6.27.2.186, the Remote Actions scripts can be executed under the current interactive user session, even when AppLocker is running on the machine.
To ensure everything is working as expected, the scripts must be allowed to run by the AppLocker policy. This is not specific to Nexthink and you can learn more about it on the Microsoft documentation website.
To activate the AppLocker compatibility mode add the following registry key.
| Key | **HKLM\Software\Nexthink\RemoteActions** |
| ---------- | ---------------------------------------- |
| Value name | **applockercompat** |
| Value type | **DWORD** |
| Value data | **1** |
The change will take effect straight away, there is no need to restart the Collector or the operating system.
## Important guidelines
When Remote Actions runs in AppLocker compatibility mode, make sure to follow these specific guidelines impacting the format of the input parameter names:
* The first character must be a letter or an underscore.
* The subsequent characters must be alpha-numeric, a hyphen or an underscore.
* The parameter name must not exceed 255 characters.
---
# 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.nexthink.com/user-guide/remote-actions/setting-up-and-managing-remote-actions/application-control-and-remote-actions.md?ask=&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.