Parameter mid.powershell.local_mid_service_credential_fallback missing?

[anko_wolf]

The discovery log shows the MID server using its own Windows Service account for running PowerShell commands (when all other credentials have failed).

The SN Docs say, you can prevent this by setting MID Server mid.powershell.local_mid_service_credential_fallback to false.

But in my Paris instances, I seem to be unable to select that particular parameter:

I managed to add it via a workaround (by creating a different param and manipulating the param name through the list view). But it did not make a difference.

I have also tried adding it as a MID Server Property but that made no difference either. Any suggestions?

Thanks in advance!

[Rahul Priyadars]

try adding this using below URL

https://YourInstance.service-now.com/nav_to.do?uri=%2Fecc_agent_property_list.do%3Fsysparm_query%3D%26sysparm_first_row%3D1%26sysparm_view%3D

Restart mid server after using this.

Also even though this property is set still you need to correct your credentials to Run the discovery. 

Regards

RP

[anko_wolf]

Thanks for that. Had tried that already, but t did not work.

I know I need to add the missing credentials before Discovery can be successful. But at this moment, I am focussing at getting rid of this error message and the associated overhead.

[Rahul Priyadars]

i hope after adding you restarted the Mid Server?

Regards

RP

[anko_wolf]

I hope I made the changes BEFORE restarting the MID Server and not AFTER. But to be sure, I will try one more restart 😉

[anko_wolf]

Added the param as an Agent Property for both my MID Servers (already there) and restarted both MID Servers.

After that, I rediscovered a Windows host. Unfortunately, the log message is still there. 

Cheers,

Anko