Powershell activity credential tagging

[stephmcl303]

I have a run powershell activity that has a custom script to create DHCP reservations I'm attempting to use credential tagging to send credentials loaded into the instance with the correct level of access to the powershell script to run as that user on a remote server. however im running into problems with the set up. The credential tagging seems to work fine as i can see in the logs the credential is correct but the script results coming back differ depending on the account that is running the MID server process.

if I run the mid server process as the same account as the credentials passed using the tagging the script completes as i would expect

if I run the mid server as any other account (local or domain) the script runs but doesn't return the same result (its not running the commands correctly)

My understanding was that credential tagging would allow an activity to run on a remote server using specific credentials held in the instance regardless of the account used to run the mid server itself.

Any help on this would be appreciated

[stephmcl303 · Accepted solution]

Managed to resolve this by importing the correct cmdlets

My understanding was that in windows server 2012 you dont need to import modules into the session if they are already installed on the machine. I guess this doesnt apply to remote sessions.

[chengsam]

Hello Stephen,

Hope you are doing great!

I got the same issue here, and we need to let powershell acitivity use the credential table for execution instead of the MID server service logon account.

can you please help explain more about "importing the correct cmdlets"?

thanks so much!