DMZ MID Server unable to scan itself.Issue DMZ MID Server could not discover itself.ReleaseQuebec Patch 4CauseBased upon the debugging on the production instance we have found the following information below. - Classification phase is where we detect Admin share access and powershell access (for any Windows Host we're scanning) in order for remote execution - We detected Admin Share access: 08/31/21 19:29:37 (811) PowerConsole-e9868c0a1b5e301089e3ca65624bcb1f>stdout DEBUG: STDOUT 9db19112-3a1b-4f20-91d2-d377ef815c29: <SNC_LOG>2021-08-31 19:29:37 admin share access: True</SNC_LOG> - Next step is to check for Powershell Access. When performing this check, we need to create output file and error file in temp dir \\<IP_ADDRESS>\admin$\temp\psscript_output_14eb9e0f-6f6a-44f2-93c6-3c9037ab4776.txt \\<IP_ADDRESS>\admin$\temp\psscript_err_14eb9e0f-6f6a-44f2-93c6-3c9037ab4776.txt - Then we launch Powershell process to write a simple string "execute remote test passed" to the console. Our Console reader would read this and write to the output "psscript_output_14eb9e0f-6f6a-44f2-93c6-3c9037ab4776.txt" file - After execution is done we check to see if either output file or error file exists. Debug statement shows neither does: 08/31/21 19:29:40 (018) PowerConsole-e9868c0a1b5e301089e3ca65624bcb1f>stdout DEBUG: STDOUT 9db19112-3a1b-4f20-91d2-d377ef815c29: <SNC_LOG>2021-08-31 19:29:40 SNCDEBUG - \\<IP_ADRESS>\admin$\temp\psscript_output_14eb9e0f-6f6a-44f2-93c6-3c9037ab4776.txt - EXISTS? False </SNC_LOG> 08/31/21 19:29:40 (018) PowerConsole-e9868c0a1b5e301089e3ca65624bcb1f>stdout DEBUG: STDOUT 9db19112-3a1b-4f20-91d2-d377ef815c29: <SNC_LOG>2021-08-31 19:29:40 SNCDEBUG - \\<IP_ADDRESS>\admin$\temp\psscript_err_14eb9e0f-6f6a-44f2-93c6-3c9037ab4776.txt - EXISTS? False </SNC_LOG> - If Output file exist, we should be able to read the content and confirm Powershell access. However, since the file doesn't exist we mark Powershell Access as false. - Since Powershell access is false and proceed to run Classify Command using local connection. However, due to credential exist, when making local connection with credential, the OS threw the error.ResolutionNEXT STEP: - Please to check to see why PROD MID Server service Logon user was unable to write to \\<IP_ADDRESS>\admin$\temp\ - You can compare user permission with DEV MID Server service Logon user was able write to the same dir - If PROD Service Logon User is unable to write to"\\<IP_ADDRESS>\admin$\temp\" and there is another temp dir that the user can write to, you can configure the MID Server config param "mid.powershell.target_base_dir"