Propagation Scripts over Devolutions Gateway
Hello.
Is it possible to do propagation scripts over Devolutions Gateway? I can't seem to find any way to configure it, and as i understand it, the actual scripts are running from the Devolutions Server? So the Propagation Scripts require line of sight to the servers it should run on, if the propagation script requires remote configuration to be set on remote computers?
Br, Tony
All Comments (4)
Hi @tonyfredriksson,
Yes it is possible, in Administration -> Privileged Access Management -> Propagation, under the template your want to use, you can create a new configuration and then in PowerShell Settings the option will appear once you type in a Hostname. 
Luc Fauvel
d0f80461-a30f-4196-b527-af7df0f0b1b4.png
Screenshot 2026-05-08 at 9.57.51 AM.png
Hi Luc.
I can't seem to find the Powershell settings you refer to.
Just to try things out, i imported the "Scheduled task" template that's present on the gihub repo.
And for the "legacy" version:
We are at the moment running DVLS version 2025.1.13, if that matters.
cef2da98-3978-412f-a118-c9ae996b3ed5.png
ec4a9530-6423-4ac9-966d-de5ddc0b24cd.png
Apologies, I should have validated your current version. This was added in DVLS 2025.2 I believe, so you would need to update to that version at least to have these settings available.
Luc Fauvel
Hi again.
That explains why it's not showing.
I've now tried on our test environment that is on 2025.3.18 and i'm able to configure the script and add a configuration.
However, when it launches the script, it is not successful:
Propagation: Error
Error while executing the script Scheduled Task with the configuration Scheduled Task ADm: websocket closed
Propagation: Error
websocket closed
The PAM provider is working over the Devolutions Gateway, it is able to reset the password for the account.
In the DVLS Console, i can only find the following logs:
A Devolutions Gateway token has been generated from the gateway 'ADM Gateway #1' towards the host 'tcp://[FQDN-OF-REMOTE-SERVER]:5985' by 'System Operation'.
Powershell: Using new WinRM Client
I did try to "Test" the script with the built in functionality to "test" the script on the propagation script entry, but there were no options to use a Devolutions Gateway there, so i don't think it's trying over the Devolutions Gateway, and thus can't replicate it there either.
I can also add that we are using egress web proxy in our environment, but have added proxy bypass configurations for the FQDNs the Devolutions Gateway is part of, both on the DVLS host itself, but it's also added to the web.conf configuration file for DVLS.
I don't really know where to further look for what's causing this.
Br, Tony