Change the sys cmd user to pfuser?

 3 Replies
 1 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
NHBB
Basic Member
Posts: 10
Basic Member
    We have a system command node configured to invoke Windows PowerShell on the application server and run a PowerShell script file.  We need to use the PowerShell Active Directory module to update Active Directory. Currently pfuser is the account that can update Active Directory.  The system command node runs as Lawson so we get a security violation when the PowerShell script runs.  Can the system command node be configured to run as a different user?  Configuring the Sys Cmd tab in Process Server Configuration Set appears to apply specifically to an LSF connection.  We tried it anyway and it didn't help.  The sys cmd node is set for automatic execution mode and the command is "powershell  -File  <!--PowerShellScript-->".  Thank you.  Barbara
    NHBB
    Basic Member
    Posts: 10
    Basic Member
      I opened an incident with Infor asking the same question.  They have responded that Lawson is the standard account to use for this, so we are going to stick with that.
      Kwane McNeal
      Veteran Member
      Posts: 479
      Veteran Member
        Barbara,
        I know Infor gave you an official answer, but another way that may work is wrap the powershell command inside of a runas.exe command. You may have to include some call to a third party tool to elevate permissions, if that is also needed.

        Kwane
        Joan Herzfeldt
        Veteran Member
        Posts: 74
        Veteran Member
          That's what we had to do too. I didn't write the powershell script so I can't provide details, but we had to define the user who we wanted it to run as in the powershell script.
          I think we need an enhancement request with infor that allows the configuration for a sys cmd to create the run as user. The more requests they get for the same thing the better our chances they will include it in a future release.