Hi @GWynn, Are you saying that its still passing more that 1 user to the ad-reset-password command? I think there might be some extra information in your context, I thought the DeleteContex might help. Keep at it and it should work. Maybe try re-creating the playbook 1 step at a time. Add print task to output context keys before passing them to the next task. Validate if the value in the print task matches your expectation for the next task input.
For manual input, you can leave a mandatory field blank. It will halt the playbook process and allow you to enter the value
In the screenshot below, delete the value of username field in the ad-set-new-password task(1). Run the playbook, wait for it task to fail (2). Open the failed task, add the new run-time value (3) and click "Run automation now"(4).
Another, more complex method is to implement a Data Collection task.
Hi @GWynn, Need to see what the actual command looks like. Can you send the full command with its passed parameters?
Hello @jfernandes1 As shown here it tries to reset the password for everyone, which fails! How do I specify just james?
Here is a screenshot of the sub-playbook with some skipped tasks, but when I run from the incident it STILL runs these??! What am I missing?! Yes I am saving when I make these changes.
Hi @GWynn, the task skip button only works during the playbook debug process. The task will be included when run in an incident.
Looking at the command input, it looks like your passing all the user names to the command. So it working as expected. There must be something wrong with the input.
Check the playbook task input, you can set it like below, where the value is hardcoded.
Or you can set it like below, where the value is grabbed from the context. Remember, the playbook debugger uses a different context than the incident so you might experience different behaviours. You can select an existing incident or choose a new mock incident.
When you use this method, if the previous command (AD Get User) returned more than 1 result or the playbook was run multiple times it could pass more usernames. You can check value by copying ${ActiveDirectory.Users.sAMAccountName} to the Context Data search. Like below.
Added the !DeleteContext all=true task to the start of your playbook is a good way to ensure that playbooks work as designed.
Error!
And results:
You can see here, in the sub-playbook it is all manually inputted apart from the expire password task. So... it still tried to reset all users passwords!!
Hello @jfernandes1 I think I have solved the problem. In the playbook when you override the input it must only be for de-bugging the playbook not for the actual incident! Same thing as the break-point. It only works in debugging mode.
Hi @GWynn, Are you saying that its still passing more that 1 user to the ad-reset-password command? I think there might be some extra information in your context, I thought the DeleteContex might help. Keep at it and it should work. Maybe try re-creating the playbook 1 step at a time. Add print task to output context keys before passing them to the next task. Validate if the value in the print task matches your expectation for the next task input.
For manual input, you can leave a mandatory field blank. It will halt the playbook process and allow you to enter the value
In the screenshot below, delete the value of username field in the ad-set-new-password task(1). Run the playbook, wait for it task to fail (2). Open the failed task, add the new run-time value (3) and click "Run automation now"(4).
Another, more complex method is to implement a Data Collection task.
