> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/crates/existing-crate-documentation/ad-hoc-install-uninstall-software-via-chocolatey-crate.md).

# Ad-Hoc Install/Uninstall Software via Chocolatey Crate

{% hint style="info" %}
If you’re new to Crates, read through our introductory Crate documentation [here](https://docs.rewst.help/prebuilt-automations/crates). Find the Ad-Hoc Install/Uninstall Software via Chocolatey Crate in our Crate Marketplace.
{% endhint %}

## What does the Ad-Hoc Install/Uninstall Software via Chocolatey Crate do?

Our Ad-Hoc Install/Uninstall Software via Chocolatey Crate enables technicians to manage software installations directly from PSA tickets. It connects your PSA system with Chocolatey package management, allowing you to remotely install or uninstall software packages on specific client devices without manual intervention.

This Crate focuses on simplifying common software management tasks, but doesn't handle complex configuration management or application settings. You can extend its functionality by connecting it to other automation workflows in Rewst.

## Why use the Ad-Hoc Install/Uninstall Software via Chocolatey Crate?

* Quickly respond to software installation requests from clients
* Remove unauthorized or problematic software from client devices
* Deploy standard software packages across client environments
* Maintain accurate software inventory by logging all changes in PSA tickets
* Reduce technician time spent on routine software management tasks
* Ensure consistency in software deployment methods across your team

## Crate prerequisites

* Your [PSA integration](/documentation/integrations/top-5-integration-types-get-started-with-integrations-in-rewst.md#psa-integrations) with Rewst must be set up
* [RMM integration](/documentation/integrations/top-5-integration-types-get-started-with-integrations-in-rewst.md#rmm-integrations) with Rewst that supports PowerShell script execution

## Unpack the Ad-Hoc Install/Uninstall Software via Chocolatey Crate

1. Navigate to **Crates** **>** **Crate Marketplace** in the Rewst platform.
2. Search for `Ad-Hoc Install/Uninstall Software via Chocolatey`.\
   \
   ![](https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FhrKKRVGNuncyoqHTnWR3%2Fimage.png?alt=media\&token=09777c77-efa9-4d97-b9ef-d69d44a8adb4)
3. Click on the Crate tile to begin unpacking and ensure that the required [org variables](/documentation/integrations/organization-variables.md#what-is-an-organization-variable) of `default_PSA` and `default_RMM` are added.\
   \
   ![](https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FnSeiGwxu4QgVyrulSekN%2Fimage.png?alt=media\&token=3374b6e0-2e4d-4f52-b127-949e5d58b6a0)
4. On the configuration form, select your PSA Integration from the drop-down menu.\
   \
   ![](https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FjlsP2IxnVhQjv8RicbzZ%2FCleanShot%202025-03-05%20at%2023.00.24%402x.png?alt=media\&token=7a291545-ba3b-452e-a467-86d95887a1ab)
5. Click **Unpack Crate** to complete the installation.

### Test the Crate

1. Navigate to **Automations > Forms** in the left side menu of your Rewst platform.
2. Search for `[ROC] RMM- Install Chocolatey Package`.
3. Click **⋮ > Usages > View Direct URLs.**
4. Click on the link for the organization which contains the user you wish to manage. This will launch the form in a new tab.
5. In the workflow form, select the following:
   1. Action type - Install or Uninstall
   2. Client
   3. Target device or devices
   4. Software package name
6. Click **Submit** to run the workflow. The workflow will run and automatically add notes to your PSA with the results of the software operation.
7. Verify that the software has been successfully installed or uninstalled on the target device.

## Troubleshoot the Ad-Hoc Install/Uninstall Software via Chocolatey Crate

* For software installation failures, check that the package name is correct and available in the Chocolatey repository.
* For connectivity issues, ensure the target device has internet access to download packages from the Chocolatey repository.
* Check your RMM's script execution logs for detailed error messages if the workflow reports a failure.

{% hint style="info" %}
Got an idea for a new Crate? Rewst is constantly adding new Crates to our Crate Marketplace. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/crates).
{% endhint %}


---

# 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.rewst.help/documentation/crates/existing-crate-documentation/ad-hoc-install-uninstall-software-via-chocolatey-crate.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.