Automating the Configuration Wizard

In a previous post I said how to run multiple Orion installations without running the Configuration Wizard.  This is great if you have a new big installation planned.  So the last step is to actually run the configuration wizard.

The information below draws heavily from a document outlining the previous post and this step.

The first step requires us to write an XML file.  I’ve taken that one and added some comments, so you can use mine or the original one.  I have no skin in the game.

So now I have what I call a “Blank” Silent Config file.  It has entries, but most of them are nonsensical or generic.  I need to specialize this for my installation.  You can do this by copying and editing the file, but I prefer PowerShell (don’t I always?).

Truthfully, I only need a few things here:

  • Database Server (IP, Host, or FQDN)
  • Database user (and password) with sysadmin rights – here I’m using “sa” because I can
  • Database name for Orion – I’m using PorkChopExpress because of this post I read.
  • The Orion SQL Username (and password) – this will be created if it doesn’t exist.

Please note that anything that isn’t expressly overwritten by the $ConfigXML lines is kept as default from the “Blank” template.

So now I’ve got the Config file saved with content that I want.  All that’s left is to run the executable.  Yes, I’m also doing this in PowerShell… #BecauseICan.

Did it work?  Two quick ways to test.

Open a browser.


Did a new database get created?


Leave a Comment