Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
IPA/ProcessFlow
Change the sys cmd user to pfuser?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
35
Members:
0
Total:
35
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Integration / Customization
IPA/ProcessFlow
Change the sys cmd user to pfuser?
Please
login
to post a reply.
3 Replies
1
Subscribed to this topic
53 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
NHBB
New Member
Posts: 0
8/14/2018 3:19 PM
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
New Member
Posts: 0
8/14/2018 6:18 PM
Split
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
Helpful Replier
Thanks for being such a helpful replier!
MVP
You're an MVP!
8/14/2018 6:36 PM
Split
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
8/15/2018 11:58 AM
Split
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.
Please
login
to post a reply.