OCM and sequence of software file activation

Question

Open Cities Map (Connect) 
 Once a user (logged in to their Connection Client) activates OCM, which software files (exe's, cfg's, workspaces etc) are accessed and opened? 
 What is the sequence? 
 Does anyone have any documentation/diagrams? 
 I would like to understand the interaction between OCM and Microstation Connect software files, 
 so that configuration variable pointers can set up correctly in the appropriate cfg file (or other) on a network environment. 
 Kind Regards 
 Conny Valeontis 
 Sydney, Australia

Marc Thomas · Answer

Bentley Configuration Explorer will also give you significant insight, just be aware that it has not been updated for a long time (sorry...) so if in doubt check variable values against those displayed in the Configuration Variables dialog. 
 
 For quick access to the Configuration Variables dialog try Using It! - Add Frequent Tools or Places to the Quick Access Toolbar

Marc Thomas · Answer

As Tim has just commented, that diagram has changed since the early CONNECT releases. 
 I've annotated the Configuration Explorer screenshot I posted previously. 
 System configuration files (1) are all in C:\Program Files\Bentley\Map CONNECT Edition\MapUltimate\config (similar path for other applications), these are Bentley's files and should not be modified, nor should anything be added in this location. 
 (2) is ConfigurationSetup.cfg which is used to direct the application to a shared custom configuration and is discussed in my blog: CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg? This is located in C:\ProgramData\Bentley\Map CONNECT Edition\MapUltimate\Configuration along with our example WorkSpaces and WorkSets. 
 Once redirected by ConfigurationSetup.cfg organization standards WorkSpaces and WorkSets (3) are all located on a network share, these are your files to edit as required. 
 
 Note that msconfig.cfg (starred) is repeatedly read during the load sequence, this is the file that controls the load sequence. For anyone who would like to fully understand the configuration sequence it can be informative to view this file but it must never be edited.