> 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-manually-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-vms.md).

# How can I manually roll out the Enginsight Pulsar to multiple persistent Windows VMs?

You can **manually** roll out the Enginsight agent Pulsar to multiple **persistent virtual machines** (VMs) with a Windows operating system based on a master image.

The steps described below apply to the following environments:

* *Persistent* *virtual* Windows environments (static VMs with dedicated hostnames)

{% hint style="success" icon="lightbulb" %}
For more information on how to roll out the Enginsight Pulsar *automatically* to persistent (virtual) Windows environments or to *volatile* Windows virtual desktop infrastructures, see the Knowledge Base: [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) and [How can I automatically roll out the Enginsight Pulsar to volatile Windows VDI environments?](/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-volatile-windows-vdi-environments.md) 
{% endhint %}

***

{% stepper %}
{% step %}

### Install Pulsar on a master host

1. Start the Windows system that will be used to create a master image with a prepared Pulsar installation.
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.
3. Save the installation script from **step 4** of the Pulsar installation instructions, as you will need it again later.
   {% endstep %}

{% step %}

### Stop the Pulsar services and adjust the startup type

1. After successful installation, stop the Pulsar services **Enginsight Pulsar** and **Enginsight Supervisor** via an administrator PowerShell using the following commands:

```
Stop-Service "Enginsight Pulsar"
Stop-Service "Enginsight Supervisor"
```

2. Set the startup type of the Pulsar services to **manual** using the following commands so that they do not start automatically when the image is created:

```
Set-Service -Name "Enginsight Pulsar" -StartupType Manual
Set-Service -Name "Enginsight Supervisor" -StartupType Manual
```

{% 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 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 %}

### Create a Pulsar configuration for each VM

You can now create a separate Pulsar configuration file for each required VM on the master image. 

To do so, follow these steps:

1. Navigate to the directory that contains the Pulsar configuration file `config.json`:

```
C:\Program Files\Enginsight\Pulsar\
```

2. Create a separate Pulsar configuration file for each VM. To do this, rename the existing configuration file each time. Ideally, use a naming scheme that allows you to clearly assign the generated configuration files to the corresponding host VMs later.
3. Then generate a new configuration file each time by running the following command in the Windows console or PowerShell:

```
ngs-pulsar-amd64.exe -install=true -accessKeyId <AccessKeyID> -accessKeySecret <AccessKeySecret> -api <API_URL> -license client -proxy <OptionalProxyParameter> -noProxy <OptionalNoProxyParameter> -tags <OptionalTags>
```

{% hint style="info" %}
Remember to replace the following parameters in `<>` with the values from the installation script saved in [step 1.3](#install-pulsar-on-a-master-host):

* `<AccessKeyID>`
* `<AccessKeySecret>`
* `<API_URL>`

The parameters `<OptionalProxyParameter>` and `<OptionalNoProxyParameter>` are only required if you [installed the Pulsar with a proxy](https://docs.enginsight.com/docs/manual/english/installation-und-konfiguration/installation-and-configuration/enginsight-components/pulsar#installing-pulsar-with-a-proxy).

The parameter `<OptionalTags>` is only required if you want to [add tags to the Pulsar during installation](/docs/knowledge-base/english/pulsar/how-do-i-add-tags-during-the-installation-of-the-enginsight-pulsar.md).
{% endhint %}

Each of these calls creates a new host in the Enginsight platform under **Hosts** → **Overview** and saves the corresponding configuration file in the program directory `C:\Program Files\Enginsight\Pulsar\`.

{% 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 %}

You can also automate this process by creating a script.

{% hint style="success" icon="lightbulb" %}
For more information on how to roll out the Enginsight Pulsar *automatically* to persistent Windows environments via script, see the Knowledge Base: [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 %}
{% endstep %}

{% step %}

### Distribute the generated configuration files to the host VMs

The newly generated Pulsar configuration files must now be distributed to the corresponding host VMs.

This depends on your setup and can be done in different ways, for example via an FTP server or manually.

Check which distribution method is best suited to your setup.
{% endstep %}

{% step %}

### Start the Pulsar services on each VM and adjust the startup type

On each VM where a Pulsar has been installed, the Pulsar services must now be started again and the startup type must be set back to **automatic**:

1. Start the Pulsar services **Enginsight Pulsar** and **Enginsight Supervisor** again using the following commands:

```
Start-Service "Enginsight Pulsar"
Start-Service "Enginsight Supervisor"
```

2. Set the startup type of the Pulsar services back to **automatic** using the following commands:

```
Set-Service -Name "Enginsight Pulsar" -StartupType Automatic
Set-Service -Name "Enginsight Supervisor" -StartupType Automatic
```

{% endstep %}
{% endstepper %}

***

## Further Resources

* [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 automatically roll out the Enginsight Pulsar to volatile Windows VDI environments?](/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-volatile-windows-vdi-environments.md)&#x20;
* [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)

***