Automating Configuration wizard

wlouisharris2000

1)We are trying to automate and create a silent configuration wizard using these steps:

https://documentation.solarwinds.com/en/success_center/orionplatform/content/install-silent-mode.htm?cshid=orioncoresilentinstall

2)We created the silent config using this command successfully:

"H:\ProgramFiles\SolarWinds\Orion" ConfigurationWizard.exe -CreateSilentConfig-cfgOutput:h:\tools

3)Next I try to run the command line to run with silent config:

"H:\ProgramFiles\SolarWinds\Orion\ConfigurationWizard.exe" /SILENT /FORCE -cfg"h:\tools\silentconfig.xml"

4)I keep running into this issue in the log:

2026-02-06 15:01:34,313 [1] INFO  OipClient - Tracking event: ConfigurationWizard - System.ArgumentException - System.ArgumentException: You have to specify -cfg parameter with a value

   at SolarWinds.ConfigurationWizard.Host.Utils.ArgsHelper.GetValueFromArgs(String[] args, String argName)

   at SolarWinds.ConfigurationWizard.Host.ProgramStarter.RunSilent(String[] args, IOrionConfigHost configHost)

   at SolarWinds.ConfigurationWizard.Host.ProgramStarter.Start(String[] args)

   at SolarWinds.ConfigurationWizard.Host.Program.Main(String[] args) - False - 0

5)We have a support case - Case # - 02086325. Support had a few recommendations and none of these worked. I get the same error.

"

1. Parameter Syntax:
   The parameter must be exactly -cfg (lowercase, with a dash), followed immediately by the path enclosed in quotes if it contains spaces, like:
   Raw code
   -cfg "H:\tools\silentconfig.xml" 
   Your command looks correct, but try removing the /SILENT and /FORCE switches temporarily to see if the config file is recognized without them:
   Raw code
   "H:\Program Files\SolarWinds\Orion\ConfigurationWizard.exe" -cfg "H:\tools\silentconfig.xml" 
   If this works, add switches back one by one.
2. File Encoding and Format:
   Ensure the XML file is saved with UTF-8 encoding without BOM (Byte Order Mark). Some parsers fail if BOM is present.
   Also, verify the XML is well-formed and matches the expected schema exactly. Even small syntax errors can cause the wizard to reject it.
3. File Accessibility:
   Confirm the user running the command has read access to H:\tools\silentconfig.xml. Try opening the file manually from that account.
4. Path and Drive:
   If H: is a network or removable drive, try copying the XML file to a local drive (e.g., C:\temp\silentconfig.xml) and run the command pointing there.
5. Check for Hidden Characters:
   Sometimes copying XML content can introduce hidden or special characters. Use a text editor like Notepad++ to show all characters and clean the file.
6. Minimal Config Test:
   Create a minimal valid silent config XML with just the required elements and test if it is accepted. Gradually add your full config back.
7. Log Files:
   Review the configurationwizard.log file in the SolarWinds installation directory for more detailed error messages.

Has anyone had success with this method? Support is telliing me they don't support this method.