File Based Discovery on Windows host might fail with "AuthorizationManager check failed" due to hard coded network path \\127.0.0.1DescriptionWhen running file based discovery on a Windows host, you might encounter the following error in discovery log: =====Error: & : AuthorizationManager check failed.At line:1 char:156+ ... catch {} & "\\127.0.0.1\admin$\temp\unregistered\psscript_executeRem ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : SecurityError: (:) [], PSSecurityException+ FullyQualifiedErrorId : UnauthorizedAccessHRESULT: [-2147024894]===== File-Based Discovery requires us to copy a script to the target and then we start a process on the target and invoke the script.In order to invoke the script on the target, we must know the local path to the script. The script is copied to the target's admin share folder.This logic is located in ExecuteRemote.psm1 MID server script file.In this file, $localHomeDir specifies the temp directory as if it was local to the target server, hence why in OOTB, the value starts with \\127.0.0.1.However, when running the PowerShell script, PowerShell believes that the script is coming from the internet since the path to the file is a network path (starts with \\{ip_address}) and we receive above "AuthorizationManager check failed" error.Steps to Reproduce 1. Activate File Based Discovery plugin2. Run it on windows host with certain security policy3. Observe the returned errorWorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available. In MID server script file ExecuteRemote.psm1, change the following:==================================$localHomeDir = "\\127.0.0.1\$homeDir"==================================To==================================$localHomeDir = "$env:temp\$instanceName"==================================Related Problem: PRB1504483