Steps are:

1. Launch an instance of Windows Server 2019 through AWS

2. Run a PowerShell script that should launch a Passolo macro and do an update (Among other things), using "& $PSL_APP /runmacro=$MACRO /output:$LOCDIR\Logs\Passolo\Passolo.log /quit"

Results

1. On the AWS machine looking at Task Manager Passolo launches then terminates 2 seconds later.

Note: Running the Macro on it's own on the AWS machine works perfectly.

So my question to admin is does Passolo work when being called through an AWS instance or is there some sort of "rights" problem that prevents it?

This question goes beyond what can be done here in the forum and looks more like a consulting job, as it would involve unique customer IT infrastructure and tools that most forum members doesn't have access to.

The assumption that it could have something to do with rights is certainly a starting point. I would first want to ask what "running the macro on it's own" means? Is the macro started manually from the UI or automatically, and is a Windows user logged in? And is a Windows user logged in when the PowerShell script is started? If the automation is run without a user logged in, Passolo must be able to read settings data from directories, and you should look into the /profilefolder command line option.

Running the macro on it's own means on the machine generated by AWS I can either

1. Run the PowerShell script and have success launching Passolo and running the macro

2. Launch Passolo and run the macro through the IDE.

It sounds like I would need a support ticket, I just wanted to see if what I was trying to do was something Passolo supported before starting down that road. I will look into getting some support for this issue. Thanks Achim.

Running the macro on it's own means on the machine generated by AWS I can either

1. Run the PowerShell script and have success launching Passolo and running the macro

2. Launch Passolo and run the macro through the IDE.

It sounds like I would need a support ticket, I just wanted to see if what I was trying to do was something Passolo supported before starting down that road. I will look into getting some support for this issue. Thanks Achim.

I am pretty sure that support can't provide assistance in this case. Passolo is working effectively, the macro executes seamlessly, and the PowerShell automation of Passolo runs without any complications. Thus, everything appears to be well-organized.

It might be a bit complex for support to comprehend why the PowerShell script doesn't function when called from the Atlassian Bamboo project, as they might not possess the required infrastructure, tools, and expertise to reproduce the issue.

It would be beneficial to explore whether the issue could be associated with system rights and/or data context. It is crucial to ascertain if the Atlassian Bamboo project has the same system visibility as you do when initiating the PowerShell script manually.