Is there a way to locate the entire MicroStation CONNECT edition configuration on the network?

Is there a way to locate the entire MicroStation CONNECT edition configuration on the network? Something like the -WR command line parameter in V8i? 

I can do a custom-configuration to the network, but even then MicroStations writes the <workspace>.cfg to the local ProgramData directory. In most cases with my customers, the local disk is not accessible for writing for the users or the workstation is a Virtual Machine or a sealed image.

Paul

 ~~

Parents
  • The easiest and recommended method is to specify the location of the custom configuration during installation (the MicroStation install dialog is identical to this one from OpenBuildings):

    That modifies ConfigurationSetup.cfg, once the user selects a WorkSpace from the Custom Configuration everything other than the installed system files is accessed from the specified location.

    I respectfully suggest that the IT teams that you are working with should be given this as Bentley's recommended solution and that use of -WR is a legacy solution. For existing installations either a simple edit or replacement of ConfigurationSetup.cfg with an updated version, as discused in the link, is a quick and robust solution.

    You may also be able to make IT teams' life simpler by directing them to our guidance on Deployment Images that would have this step pre-set.

    Marc

Reply
  • The easiest and recommended method is to specify the location of the custom configuration during installation (the MicroStation install dialog is identical to this one from OpenBuildings):

    That modifies ConfigurationSetup.cfg, once the user selects a WorkSpace from the Custom Configuration everything other than the installed system files is accessed from the specified location.

    I respectfully suggest that the IT teams that you are working with should be given this as Bentley's recommended solution and that use of -WR is a legacy solution. For existing installations either a simple edit or replacement of ConfigurationSetup.cfg with an updated version, as discused in the link, is a quick and robust solution.

    You may also be able to make IT teams' life simpler by directing them to our guidance on Deployment Images that would have this step pre-set.

    Marc

Children
No Data