The issue you're facing with SCOM (System Center Operations Manager) and PowerShell's
Import-SCManagementPack cmdlet appears to be related to case sensitivity in management pack file names and XML content identifiers. SCOM typically enforces case sensitivity in management pack identifiers and, consequently, can cause import failures when the case doesn't match the actual identifiers in the management pack XML. Unfortunately, this behavior is by design, and there are no specific settings in SCOM to change this behavior.
To address your specific questions:
Case Sensitivity with
Import-SCManagementPack and SCOM, in general, have known issues with case sensitivity for file names and XML content identifiers. SCOM expects the case of the identifiers in the XML content to match exactly with what is specified in the management pack file name.
Settings Impacting File Names Interpretation: SCOM itself does not have specific settings that control case sensitivity for PowerShell operations. The behavior is primarily based on how the management pack is authored, and it expects the case to match.
Workaround for Mixed-Case Names: To use mixed-case names for management pack files and identifiers, you may need to edit the XML content within the management pack file to ensure that the case matches exactly with the file name. This can be cumbersome, especially if you have many management packs to import.