Discovery MID Server Username Case Mismatch<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Question: Why does Discovery fail when the MID server user appears valid but errors still occur? Answer: This can happen when the username casing reported by Windows differs between system commands and Java properties used by the MID. For example: whoami /user may return mid-user The Java property may return Mid-user Because the casing does not match exactly, the system treats them as different accounts, causing Discovery errors such as authentication failures or SID not found. Troubleshooting Steps: Run whoami /user directly on the MID host to see the exact string Windows provides. Compare that to the username value reported in the MID logs (Java property). Check whether the Discovery logs include SID or credential mismatch errors. If a mismatch exists, adjust the account so the casing is consistent across system and Java returns.