> For the complete documentation index, see [llms.txt](https://docs.enginsight.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-volatile-windows-vdi-environments.md).

# How can I automatically roll out the Enginsight Pulsar to volatile Windows VDI environments?

You can **automatically** roll out the Enginsight agent Pulsar in **volatile** or **non-persistent Windows VDI** (Virtual Desktop Infrastructure) environments based on a master image.

The steps described below apply to the following environments:

* *Volatile* or *non-persistent* virtual desktops (without persistent system changes; potentially provisioned dynamically on different physical hosts)
* User data is provided on a network drive by using Windows roaming profiles

{% hint style="success" icon="lightbulb" %}
For more information on how to roll out the Enginsight Pulsar *manually* or *automatically* to *persistent* (virtual) Windows environments, see the Knowledge Base: [How can I manually roll out the Enginsight Pulsar to multiple persistent Windows VMs?](/docs/knowledge-base/english/pulsar/how-can-i-manually-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-vms.md) and [How can I automatically roll out the Enginsight Pulsar to multiple persistent Windows systems?](/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-systems.md)
{% endhint %}

***

{% stepper %}
{% step %}

### Install Pulsar on a master host

1. Start the Windows system from which a master image with a prepared Pulsar installation is to be created.
2. Navigate to the Enginsight platform and follow the [Pulsar installation instructions](https://docs.enginsight.com/docs/manual/english/installation-und-konfiguration/installation-and-configuration/enginsight-components/pulsar) for the **automatic installation** *on* *Windows clients* as described in the Enginsight Manual.
   {% endstep %}

{% step %}

### Adjust the Pulsar configuration

1. Open the Pulsar configuration file on the master host at the following path:

```
C:\Program Files\Enginsight\Pulsar\config.json
```

2\. Make the following changes in the configuration file:

* Set the `environment` parameter to `vdi`.
* Set the `license` parameter to `client`.
* In the `host` section, remove the value of the `_id` parameter.

The configuration should now look as follows:

<pre><code>{
    "channel": "master",
<strong>    "environment": "vdi",
</strong><strong>    "license": "client"
</strong>    "host": {
<strong>        "_id": ""
</strong>    },
    "api": {
        "url": "https://*****",
        "proxy": "",
        "noProxy": "",
        "accessKey": {
            "id": "*****",
            "secret": "****"
        }
    }
}
</code></pre>

3. Save the changes to the configuration file and close the file.
   {% endstep %}

{% step %}

### Delete the master host from the platform

In the Enginsight platform, navigate to **Hosts** → **Overview** and delete the Windows client that was automatically created for the master image during the Pulsar installation.

{% hint style="warning" %}
**Please note**: Deleting hosts from the host overview does ***not*** directly uninstall the associated Pulsar.
{% endhint %}
{% endstep %}

{% step %}

### Save the master image

Save the master image with the prepared Pulsar installation.
{% endstep %}

{% step %}

### Automatic rollout of Pulsar

When a virtual desktop based on the master image is started for the first time, it is automatically added as a host in the Enginsight platform under **Hosts** → **Overview**.

A separate host is created for each user and named after the respective user account.

{% hint style="danger" %}
**Please note**: Each host that is created this way consumes one **Asset** license from your license package! If you need to free up licensed assets, you need to delete hosts from the host overview in the Enginsight platform accordingly.
{% endhint %}

{% hint style="warning" %}
**Please note**: In a volatile VDI environment, the configuration of each Pulsar is stored dynamically under `C:\Users\<UserName>\AppData\Roaming\Enginsight\Pulsar\config.json`.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## Further Resources

* [How can I manually roll out the Enginsight Pulsar to multiple persistent Windows VMs?](/docs/knowledge-base/english/pulsar/how-can-i-manually-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-vms.md)
* [How can I automatically roll out the Enginsight Pulsar to multiple persistent Windows systems?](/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-systems.md)
* [How can I roll out the Enginsight Pulsar via Windows Group Policy?](/docs/knowledge-base/english/pulsar/how-can-i-roll-out-the-enginsight-pulsar-via-windows-group-policy.md)

***