Verifying Deployment Settings

Browsium Controller provides a command-line function to query the system and identify the location of the Proton, Ion, and Catalyst configurations to be used the next time the Controller starts. The command BrowsiumController /WhichConfig is run from a Command Prompt.

In the following example, a system is setup with an Ion project file deployed to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Browsium\Ion with the value
”C:\Browsium\Ion project.bcx” stored in LocalFromFileName. (This example also contains a Catalyst project file and a Proton Server URL.)

The query uses registry reflection so the result ignores the Wow6432Node key on 64-bit systems, although it’s in the path of the registry value.

Executing this command …

… results in the configuration acknowledged as:

‘WhichConfig’ shows the Ion, Catalyst, and Proton configurations TO BE LOADED at the next Controller restart. The values shown may be different from the currently loaded configurations, if the values in the registry keys have been changed since the Controller was last started.

In addition to the command line option, administrators running Ion Configuration Manager can quickly check which configuration will load when the Controller is restarted by viewing About Box. Select ‘About Browsium Ion Configuration Manager’ from the Help menu. When the Ion About Box loads, press the Ctrl key to reveal the project file information. In addition to the LoadFromFileName registry location and project file path and name, you will see the installed .NET CLR version — another way to ensure the system is ready and working properly for testing.

In the following example, the project is read from the registry location written by Start Test Configuration, which takes precedence over all other registry locations as detailed in section 5.3.