You can extend access to other parts of the Orchestrator server file system by modifying the js-io-rights.conf Orchestrator configuration file. If the js-io-rights.conf file does not exist on your system, you can create it manually with the default content.


Manually creating the js-io-rights.conf file is applicable only for Windows systems. The recommended way to generate the js-io-rights.conf file is to run a workflow attempting to access the Orchestrator server file system, for example, the Export logs and application settings workflow from the Troubleshooting folder in the Orchestrator workflow library.


Log in as an administrator to the machine on which the Orchestrator server is installed.


Navigate to the Orchestrator configuration directory.



If you installed Orchestrator with the vCenter Server installer

Go to install_directory\VMware\Infrastructure\Orchestrator\appserver\server\vmo\conf.

If you installed Orchestrator standalone

Go to install_directory\VMware\Orchestrator\appserver\server\vmo\conf.


Create the js-io-rights.conf file and open it in a text editor.


Type the default js-io-rights.conf file content.

-rwx C:/

+rwx C:/orchestrator
+rx ../../configuration/jetty/logs/
+rx ../server/vmo/log/
+rx ../bin/
+rx ./
+rx ../server/vmo/conf/
+rx ../server/vmo/conf/plugins
+rx ../server/vmo/deploy/vmo-server/vmo-ds.xml
+rx ../../apps/
+r ../../version.txt

Save and close the file.

You can now set the access to the server file system for workflows and JavaScript.