fg

Hello,

I have now looked into the Topic again and have come to the following conclusion:

The addon in RDM uses the old Barracuda start arguments like -c -n which are executed with the CMD.

In the newer versions this is solved using the Powershell module "BarracudaNetworkAccessClient"

See source: NAC PowerShell for Windows | Barracuda Campus

Would it be possible to include the PS Module in the next version of RDM?

I have now solved it differently - thanks anyway

Hello everyone,

is there anything to consider? for me the ps script does not work properly - I have the following stored at my RDP:

Properties - VPN / SSH / Gateway:

Type: User defined

Connect: Always connect

Close: After session end

Settings (Custom):

Host: Name of the Barracuda VPN profile

Executable file: here I put a .bat which executes the powershell script.

As soon as I can try to connect, the powershell opens and an error message comes up with $profileID is null?

Is this script outdated? I have seen that the parameters have changed

e.g. $HOST$ is now $VPN_HOST$ - I have already changed this, but it still does not work.

Is there already a "better" solution?

Even if the post is a bit older I hope for feedback

Thanks in advance