As you can see from the screenshot below; when you run a task you get an option to “Don’t prompt when running this task in the future”. Checking this box can lead to complications if the details you enter in the task box are incorrect (or go out of date) and there is no way in the console for you to go back and update the credentials. This question came up on the SCOM Reddit group so here is a walk through to remedy the situation.
Kevin Holman explained on that post that all console “personalizations” are stored locally on each console server – in HKCU\Software\Microsoft\Microsoft Operations Manager\3.0\Console. You can even delete everything under Console and it will reset the SCOM console back to factory settings. Or you can find the GUID for each item (views, tasks, etc.) and modify just those things. I’ll run through the second of those options to find the personalisation via the GUID and just update that personalisation.
So let’s start off with a view in a dashboard …. Operations Manager, Management Server -> Management Server State as shown below.
I’ll select the top right view – Management Server State – and run the first Health Service task – “Check Health Service Startup Configuration Diagnostics”
Notice that I have checked the box “Don’t prompt when running this task in the future” (I have also entered an incorrect password for the administrator account which causest the task to fail).
If I now re-run the task; I don’t get prompted for credentials and the task itself appears to execute fine although when you scroll to the bottom of the task output you will see that it actually failed.
So how do I get back the ability to enter credentials for executing the task?
You need to find the Task Id
Get-SCOMTask -DisplayName 'Check Health Service Startup Configuration*' | Select Id, DisplayName
Then go into the registry on the machine you are accessing the console from and reset the Prompt key \ value to 1.
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager\3.0\Console\**GUID** and the GUID in this case is 7e6d6210-5a30-295f-d9a5-faa72b98114b
Change the Prompt value to 1 and then re-run the task (there is no need to restart the console). You’ll see that the prompt is back.
