> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pd-ag/parallels-desktop-business-administrators-guide/deploying-parallels-desktop-for-mac-business-edition/alternative-mass-deployment-via-deployment-package/deploying-the-package-to-macs/using-a-script-to-change-vm-options.md).

# Using a Script to Change VM Options

When you need to change configuration settings of all virtual machines that are already registered on a Mac computer, you can use the Parallels desktop command-line interface. To do so, you first need to create a script to perform a desired configuration modification. You can then execute the script on a Mac computer using one of the remote Mac management tools described earlier in this chapter.

The following is a script example that disables the auto pausing option for all virtual machines registered on a Mac computer:

```
for i in $( prlctl list -a --info | grep "ID" | sed 's/.....//;s/.$//' ); do 
  prlctl set $i --pause-idle off 
done
```

The script above uses the `prlctl list` command to first obtains a list of registered virtual machines and then (inside the loop) sets the `--pause-idle` option for every VM to "off", which disables pausing of an idle virtual machine.

The complete command-line reference is documented in the [**Parallels Desktop Developer's Guide**](https://docs.parallels.com/landing/parallels-desktop-developers-guide/).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.parallels.com/landing/pd-ag/parallels-desktop-business-administrators-guide/deploying-parallels-desktop-for-mac-business-edition/alternative-mass-deployment-via-deployment-package/deploying-the-package-to-macs/using-a-script-to-change-vm-options.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 `build a script that syncs our docs to a CMS` 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.