> For the complete documentation index, see [llms.txt](https://catchdocs.gitbook.io/catch-customer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://catchdocs.gitbook.io/catch-customer-documentation/catch-control/provisioning/automated-provisioning.md).

# Automated provisioning

## Auto-Provisioner

Depending on the method of installation of Catch Control, a customer may elect to add a `deploy.key` file to the installation directory. This key is a customer-specific identifer, allowing the catch control instance to communicate with the cloud in an unprovisioned state.

If this file is present **and** a `provisioning.json` file is **not** present, Catch control will ping Catch Cloud services every 5 minutes, with a report of identifiers and characteristics of the PC running Catch Control. A `fingerprint` is also included, a hash uniquely representing the contents of this report. Should any key/value change, the `fingerprint` will also change:

This system report aims to capture a set of (ideally persistent) identifiers about the PC itself, such as its MAC addresses, COM ports, as well as information retrieved from any detected `Media Player` instance running on that machine.

The data contained in these reports are visible to the customer in their `OOH Studio` dashboard before the instance is provisioned, and are designed to help customers identify remote PC installations based on other information they may have to hand to help map installations in the field to a corresponding catch `location_id`

Catch Control will continue to send these pings every 5 minutes until a ping response is received with a  provisioning instruction, or until the instance manually provisioned by other means. The provisioning repsonse contains the catch `location_id` that the instance should provision itself as, and is set as a mappaing between the `fingerprint` and `loaction_id` in OOH studio.
