The following instructions are based on the MicroStation CONNECT readme and has been modified for the OpenRoads Designer installation.

Deployment Guide

About Deployment Image

The deployment image is created by the system administrators for installing the application with the same installation configuration on multiple machines. The installation configuration includes the installation location, features, shortcuts, additional packages, and so on. Once created, users will be able to double-click Setup_OpenRoadsDesignerx64_10.xx.xx.xxx.exe available in the deployment image to install the application with the set configuration without the need of any user interaction or internet connection for component downloads. The deployment image can be shared in the network as a UNC path or pushed using SMS/SCCM.

Advantages of Using a Deployment Image

Conceptually, the deployment image can be considered as a pre-configured offline installer. Following are the advantages of using a deployment image:

• Internet connection is not required.
• Separate pre-requisite pack or set of packages before installing product are not required.
• The installation location can be decided and set in deployment image. Once defined, the product will be installed at the same location on all the machines.
• The components to be installed are preselected at the time of creating deployment image. This results in all machines having exactly same set of installations.

If different installation options are required multiple deployment images can be created. Examples of such variations could include:

• Installation of Companion Features; currently Descartes is available, GenerativeComponents will be available as a Companion Feature in future updates.
• Exclusion of new Technology Preview (beta) features
• Different Custom Configuration locations

Contents of Deployment Image

The deployment image contains all the files that are packaged with the product as well as the downloadable files, including Companion Features and Applications.  The image does not analyze the system on which it is created. It simply saves all the components for installation. The deployment image also saves the installation configuration.

Before You Start

Using non-root drive:

If the installation drive set in the deployment image configuration settings is other than the root directory (usually c:\), make sure that the drive exists on the machine on which the application is to be installed.

These are the pre-requisites for creating a deployment image:

• Internet connection - Since the setup is running in/layoutmode an internet connection is required to download all installable components.
• Write access to the location where the deployment image will be created.
• Currently a minimum 4 GB disk space at the deployment image location for each image that will be created, this (plus additional space for custom packages if required).

Deployment Image Settings

The deployment settings are displayed when you run the setup in/layoutmode. Following deployment image settings are displayed in the Installation Wizard.

• 'Full UI Mode' - Displays all the installer windows when you install using the deployment image. 'Full UI Mode' is not recommended as full user interaction is needed to run the installation. This is only of value in an atypical situation where individual installations require different options.
• 'Passive UI Mode' - Installs the application in passive mode from the deployment image. In this mode, the installation wizard and the progress dialog are displayed but the installation takes place automatically. The installer takes the options selected while creating the deployment image and you cannot select any options in this mode. The user has full visibility of the installation process.
• 'No UI Mode' - Installs the application in silent mode and is for use with deployment tools as mentioen above, e.g. Microsoft SCCM. No dialogs will be displayed and successful completion of the installation will only be confirmed by reports back to those tools or local event log messages. If an error occurs during installation this may not be obvious to the machine user.

To Create a Deployment Image

Follow these steps:

1. In the command line, go to the folder that contains the setup executable and run the executable with the /layout command. **Please note there's a space between the "exe" and "/layout" characters.
   
   
   
   
2. The Installation Wizard opens.  Click OpenRoads Designer CONNECT Edition > Configure to change the installation options.
   
   
   
3. (Optional) To change the application installation location, click the Browse button next to the Application Path.
   We recommend that you accept the default install location unless there is a particular reason not to:
    
   In the Browse For Folder dialog that opens, browse to the drive and folder you want to install the product in, then click OK.
   Note that help is available during installation from the icon at the top right.
   
   

4. In the following (optional) step we have added a new option which sets the location of the Custom Configuration during installation. This eliminates the need to run additional procedures to deploy customised configuration files to each installation.

   Select the 'Custom Configuration (plus Delivered Configuration)' option. Browse to the folder where your Custom Configuration will be located, then click next:
   

   The Custom Configuration location does not need to have been populated with content or even to exist for the deployment image to be created successfully. OpenRoads Designer will still run without them but only with the delivered configuration.
   Obviously the Custom Configuration location and content will be required for production installation to be completed.
   Note that this is a change from pre-update 4 versions where other options were offered at this point. Organization and Workspace settings are now applied in the copy of WorkSpaceSetup.cfg that will be located in the Custom Configuration.
   Click Next to continue 
   
   
   
5. Select the installation mode, see the "Deployment Image Settings" paragraph above for a description of each option.
   Browse to and select the Deployment Image Location, creating a separate sub-folder for each deployment image:
   
   
   
6. In the Features stage the optional features that are installed can be modified.
   
   
   
7. Click Done to accept the choices made or back to review.
   
   
8. Check state of Companion Feature and Applications selections then click Layout to create the delpoyment image. The usual installer dialogs will appear, required (or potentially required) components will be downloaded including the Companion Features and applications
   
   
9. Click Finish to exit the Installation Wizard.
   
   The deployment image is created at the selected location.
   
   
   
10. The resulting files created will be similar to this:
    
    Observe that in addition to the 1.6Gb OpenRoads installation file, there is also the 1.8GB LumenRT installation file and a 0.5Gb CONNECT Shared Content file that contains installation files for companion features and other shared content.
    These files are included in the deployment image so that all required files are available on the local network during installation without the need for further online downloads speeding up the installation and avoiding repeated downloads of the same files.
    
    
    
11. Run Setup_OpenRoadsDesignerx64_10.0n.00.0nn.exe to install. This can be done:
    
    
    1. Manually on the machine where the CONNECT Edition application will be installed by browsing to the deployment image location
    2. Using installation management software as mentioned above.