MicroStation CONNECT Installation Question

When you install CONNECT using the Custom Configuration and redirect the ORGANIZATION location, the MSDIR.CFG still points the ORGANIZATION installation location to _USTN_INSTALLED_CONFIGURATION=C:/ProgramData/Bentley/CONNECT Edition//Configuration/.  This contradicts what I pointed to during the installation, so my customized WorkSpaceInstalledSetup.cfg is never read.  Why doesn't this point to my redirected location? Are we really supposed to edit this after the fact?  I understand that you guys are putting a default installation in PROGRAMDATA location, that is a great idea, but I don't want to read anything from that location, I want to read from my custom CONFIGURATION location.

Parents
  • I combined your two posts.

    Unknown said:

    When you install CONNECT using the Custom Configuration and redirect the ORGANIZATION location, the MSDIR.CFG still points the ORGANIZATION installation location to _USTN_INSTALLED_CONFIGURATION=C:/ProgramData/Bentley/CONNECT Edition//Configuration/.

    This is correct as it is the installed location of the organization.  We will pick up your changes later on down in the processing of the Configuration in the WorkSpaceSetup.cfg which then has us load the changes you set which are stored in the WorkSpaceInstalledSetup.cfg.

    This contradicts what I pointed to during the installation, so my customized WorkSpaceInstalledSetup.cfg is never read.

    I am not sure what the organization has to do with us reading the WorkSpaceInstalledSetup.cfg file.  We process that file based off the Configuration location variable which is set in MSDIR.CFG "_USTN_INSTALLED_CONFIGURATION=C:/ProgramData/Bentley/CONNECT Edition//Configuration/" 

    Why doesn't this point to my redirected location?

    I am not sure why it would point there at that time in the processing.  We redefine the Organization location from the COnfiguration location when we process the WorkSpaceInstalledSetup.cfg

    Are we really supposed to edit this after the fact?

    No you are not, the new system is built to get away for users editing CFG files.

      I understand that you guys are putting a default installation in PROGRAMDATA location, that is a great idea, but I don't want to read anything from that location, I want to read from my custom CONFIGURATION location.

    When we process the WorkspaceSetup.cfg the last thing we do is check to see if you created a custom configuration in the Installer.  If you did it is stored in the WorkSpaceInstalledSetup.cfg file andwe we then pick up your custom locations if they exist.  Here is the snippet that does that.

    %if exists ($(_USTN_INSTALLED_CONFIGURATION)WorkSpaceInstalledSetup.cfg)
    %   include $(_USTN_INSTALLED_CONFIGURATION)WorkSpaceInstalledSetup.cfg
    %endif

    My WorkSpaceInstalled.cfg is in my custom location with the CONFIGURATION folder.

    Why is this file in you custom folder?  Why do you have a custom Configuration folder location. We are looking for 2 things that are your Organization and your WorkSpaces.

    I am trying to understand the logic here; but why wouldn't I just edit the MSDIR.CFG and bypass everything in PROGRAMDATA? Keeping one file there does not seem logical to me...can you enlighten me?


    For us to find the location of a custom configuration (Organization and WorkSpaces) we need to have a file that tells us where they are located.  You could change any file within the processing of the CFG's to tell us those locations we desire for users to not change content in the Program Files location.  The easiest location for us to then do this redirect is the Configuration location. The installer is built to accommodate what the user should do if they do it manually.  We are defining the best practice by making the UI follow it.  Note that th UI asks for the location of the Organization and WorkSpaces not for he location of the Configuration.

    A debug would help us understand what you are seeing.

Reply
  • I combined your two posts.

    Unknown said:

    When you install CONNECT using the Custom Configuration and redirect the ORGANIZATION location, the MSDIR.CFG still points the ORGANIZATION installation location to _USTN_INSTALLED_CONFIGURATION=C:/ProgramData/Bentley/CONNECT Edition//Configuration/.

    This is correct as it is the installed location of the organization.  We will pick up your changes later on down in the processing of the Configuration in the WorkSpaceSetup.cfg which then has us load the changes you set which are stored in the WorkSpaceInstalledSetup.cfg.

    This contradicts what I pointed to during the installation, so my customized WorkSpaceInstalledSetup.cfg is never read.

    I am not sure what the organization has to do with us reading the WorkSpaceInstalledSetup.cfg file.  We process that file based off the Configuration location variable which is set in MSDIR.CFG "_USTN_INSTALLED_CONFIGURATION=C:/ProgramData/Bentley/CONNECT Edition//Configuration/" 

    Why doesn't this point to my redirected location?

    I am not sure why it would point there at that time in the processing.  We redefine the Organization location from the COnfiguration location when we process the WorkSpaceInstalledSetup.cfg

    Are we really supposed to edit this after the fact?

    No you are not, the new system is built to get away for users editing CFG files.

      I understand that you guys are putting a default installation in PROGRAMDATA location, that is a great idea, but I don't want to read anything from that location, I want to read from my custom CONFIGURATION location.

    When we process the WorkspaceSetup.cfg the last thing we do is check to see if you created a custom configuration in the Installer.  If you did it is stored in the WorkSpaceInstalledSetup.cfg file andwe we then pick up your custom locations if they exist.  Here is the snippet that does that.

    %if exists ($(_USTN_INSTALLED_CONFIGURATION)WorkSpaceInstalledSetup.cfg)
    %   include $(_USTN_INSTALLED_CONFIGURATION)WorkSpaceInstalledSetup.cfg
    %endif

    My WorkSpaceInstalled.cfg is in my custom location with the CONFIGURATION folder.

    Why is this file in you custom folder?  Why do you have a custom Configuration folder location. We are looking for 2 things that are your Organization and your WorkSpaces.

    I am trying to understand the logic here; but why wouldn't I just edit the MSDIR.CFG and bypass everything in PROGRAMDATA? Keeping one file there does not seem logical to me...can you enlighten me?


    For us to find the location of a custom configuration (Organization and WorkSpaces) we need to have a file that tells us where they are located.  You could change any file within the processing of the CFG's to tell us those locations we desire for users to not change content in the Program Files location.  The easiest location for us to then do this redirect is the Configuration location. The installer is built to accommodate what the user should do if they do it manually.  We are defining the best practice by making the UI follow it.  Note that th UI asks for the location of the Organization and WorkSpaces not for he location of the Configuration.

    A debug would help us understand what you are seeing.

Children