Knowledge Base

Applies To:

Browsium Ion 3.3 or later
Browsium Catalyst 3.0 or later

Summary

Starting with Browsium Ion 3.3 and Browsium Catalyst 3.0, configurations can no longer be stored in the registry. Instead, a single registry value points to the Ion or Catalyst project file (an XML-formatted flat file) – either on the local file system or on a central server. For system administrators deploying Ion or Catalyst via Group Policy, Browsium provides ADM and ADMX templates for both products. Although these can be edited after import into the Group Policy Editor, it is much easier to edit the .adm or .adml files with a text editor before import.

Details

The templates can be downloaded from the Browsium website. Once downloaded, choose the file(s) that correspond to your needs and follow the instructions below.

For ADM files:

1. Open the .adm file in the text editor of your choice.
2. Find the following line:DEFAULT “C:\Ion\ProjectFile.bcx ” for Ion, orDEFAULT “C:\Catalyst\ProjectFile.cax” for Catalyst
3. Replace the existing path with the path to your Catalyst or Ion project file.
4. Import the .adm file into the Group Policy Editor.

For ADMX files:

1. Open the .adml file (located in the “en-us” folder) in the text editor of your choice.
2. Find the following line:<defaultValue><![CDATA[C:\Ion\ProjectFile.bcx]]></defaultValue> for Ion, or<defaultValue><![CDATA[C:\Catalyst\ProjectFile.cax]]></defaultValue> for Catalyst
3. Replace the existing path with the path to your Catalyst or Ion project file.
4. Copy both the .admx file and corresponding .adml file to your Group Policy central store location.

Posted in: Catalyst Knowledge Base, Ion Knowledge Base,