Default behavior in VBR (incl. v11!): When a VM gets application-aware backed up, runtime components gets installed at start of job and are removed at the end. With v11 we have the option to install them persistent!
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/a36283be-ab7a-44f4-a4bd-805d48566fb6.png)
This increases security! No Admin-Share and VIX-access is necessary any more. But it is required to deploy the Veeam Installer Service on the VMs you want to use persistent components.
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/acd13e24-48b1-485c-bbe5-433f6c8e0707.png)
This can be done by manual installation, Group policy roll-out, or by adding the VM to managed Servers.
When everything works fine, components are installed persistently:
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/da55630c-9935-44e3-9d2d-c398069ec2d0.png)
If you enable this feature and something does not work (as installer is not deployed, ..), VBR tries to run non-persistent components.