Runbook Tester vs Run in Runbook Designer vs Run in Orchestrator Console

Question

Hi! Everyone,

I have hit another brick wall, but as usually, I'm clueless and hope I can get some knowledge here.

I have completed the creation of a Runbook to unlock AD User accounts following the workflow attached. The steps includes;

1. Initialize Data - Get user input for AD User login ID
2. Run .Net Script (Powershell) - Check Input for null value in entry
3. Run .Net Script (Powershell) - Check whether Inputted user login ID user object exist in AD
4. Run .Net Script (Powershell) - Check whether Inputted user login ID user object is enabled and lockout status is true
5. Run .Net Script (Powershell) - Check whether Inputted user login ID user object is in the same AD Group as the Runbook user
6. Run .Net Script (Powershell) - Unlock Inputted user login ID

I test run this Runbook in 3 ways;

1. Runbook Tester - Completed successfully
2. Using Run in Runbook Designer - Failed, no pop-up screen to request for input
3. Using Run in Orchestrator Console - Failed, while executing the below script less the quotes

"$CurrentUserGroupObj = Get-ADUser -Identity $CurrentUser -Properties MemberOf"

Can someone shed some light what is going on?

Thank you and best regards.
Ronald

Answer 1

The options are:

• SCSM -> "shoot sparrows with cannons"
• 3rd party solution -> not allowed
• Enter the user in the Initialize Data as a second input parameter

Answer 2

Morning! Andreas,

Yes, I am currently left with only 2 solutions and have to wait for management decision. I will accept as "Answered" for now.

Thank you so much everyone and have a great evening.

Best regards.
Ronald