Installing Server Using the Silent Installation

Scenario: You have acquired the software distribution for Desigo CC containing all the required folders including:
- Brand,
- EM folder with the required extensions along with their EULA and other required files/folders, for example, PostInstallation folder containing post-installation steps enabled
- GMS folder containing Languages and Prerequisites folders along with other required files including the post-installation step for LicenseActivatation enabled
- Instructions folder containing the GMS Platform.xml file for the setup type that you want to install along with all the required extensions and their post-installation steps enabled, if any, in order to execute them.
For setting up setting up the Setup type – Server/Client/FEP with local web server (IIS), you have enabled the ConfigureIIS = True tag in the selected GMS Platform.xml file. To skip IIS installation, set the value as False.
- (Optional) Languages folders for additional language packs
- Gms.InstallerSetup.exe.

NOTE:
During a silent or semi-automatic installation, if a Desigo CC EULA or EM EULA is accepted in an XML file, it automatically accepts the EULA. In this case, it is mandatory to hand over the EULA as a file or printout to the end customer and ensure the acceptance of the EULA, duly signed by the end customer.

On a fresh computer, where no prerequisites are installed, you want to install the Setup type – Server/Client/FEP with or without web server (IIS) using the silent installation mode.

QualityUpdates and Hotfixes, if available, are installed.

If a patch for an extension is not installed due to non-installation or upgrade of the extension, then such patches are copied to the installed system and when the corresponding extension is selected for installation, these patches are also installed.
Patches from Quality Updates folder are copied to, GMSProjects > GMSMainProject > Patches > QualityUpdates
Patches from Hotfixes folder are copied to, GMSProjects > GMSMainProject > Patches > Hotfixes

You also want to have the license for the Desigo CC Server automatically activated. Furthermore, you want to have the project, with the linked HDB, started and activated and then display the logon dialog box for working with the Installed Client.

For working with the Windows App Client you want to have the website/web application URL created and the web application linked to the started project.

Furthermore, as a part of the silent installation, you also want to have executed the post-installation step for extensions selected for installation such as additional software installation, template synchronization, web application creation.

During installation of the Platform or extension, the Post Installation folder is copied to ..\GMSMainProject and the post installation steps are executed from ..\GMSMainProject\PostInstallation\GMS or ..\GMSMainProject\PostInstallation\EM\[EM Name].

 

Reference: For background information, see the reference section.

 

Workflow diagram:

 

 

Prerequisites:

 

Steps:

1 – Start the Command Prompt as an Administrator
  • Select Windows Start > All Programs > Accessories and select the Command Prompt menu, right-click it and then select Run as administrator.
  • A User Account Control message may display if your UAC settings are set to Default or Always Notify, asking you if you want to allow this installation program to make changes to the computer. Click Yes.
  • The Command Prompt displays.

 

2 – Run the Command in the Command Prompt
  1. Run the following command in the Command Prompt:
    “<Full path of the file Gms.InstallerSetup.exe>” /q <Full path of the silent Installation XML>

  • A error message may display, if the operating system is not supported by Desigo CC . Click OK to abort the installation. Click View Log to open the log file, which informs you about the supported operating systems.
  • The Desigo CC icon displays in the taskbar with the notification Installation started.
    As the installation proceeds, the taskbar icon tooltip displays in the Notification area. It informs you about the installation status including the status of the post-installation steps that are configured.
    The taskbar icon also informs you of the automatic restart, if this was configured in the XML file. However, if the installation does not continue after the restart, you must run as administrator the following command in the Command Prompt:
    <Full path of the file Gms.InstallerSetup.exe> /q <Full path of the silent Installation XML>.
    Alternatively, you can get approval from IT to change the UAC settings. (See Changing User Account Control Settings).
  1. After the silent installation and configured post-installation steps are executed, right-click the taskbar Desigo CC icon to display the following context menu options:
    Exit: Click this menu to exit the taskbar. Otherwise, the icon is removed from the taskbar notification area 15 minutes after the installation is completed.
    View Log: Click this menu to open the Installer Log file.
  1. (Optional and applicable only for the selected XML file for a setup type, with tag ConfigureIIS = True and when no IIS components are already installed on your machine) On the configured setup type, IIS is installed and configured. However, if any component is already installed, a warning informing you to proceed with manual IIS configuration is added in the log file, having the extension _SILENT for silent installation, located at the path
    [System drive]:\ProgramData\[company name]\GMS\InstallerFramework\GMS_Installer_Log.
    In case when all required IIS components are correctly installed and configured, the silent installation proceeds with installation.
    In both cases, when no IIS component is installed or when all IIS components are correctly installed and configured, the prerequisite ARR is installed, if not already installed.
    Also, the currently logged-in user is added as a member of the IIS_IUSRS group.
    The default website deleted from IIS manager and hence does not display in SMC.
    NOTE: In case when no IIS components are configured but ARR is installed and enabled, installer displays a warning message and once the installation along with IIS configuration is completed you need to uninstall existing ARR and re-install ARR and enable it. For more information, see Install Application Request Routing (ARR) in Manually Install and Configure IIS on Different OS Types.
  • By default, the prerequisite Microsoft SQL Server 2019 - Express Edition is installed. If you want to use another SQL server, use the modified GMS Platform.xml file, where the SkipInstallation section is enabled to skip the installation of Microsoft SQL Server 2019 - Express Edition.
    However, the three prerequisites, Microsoft SQL Server 2012 - Native Client, Microsoft SQL Server 2016 - System CLR Types, and Microsoft SQL Server 2016 - Management Objects are installed on the server in this given order. Installing these prerequisites, helps create an HDB remote server using SMC, when no SQL exists on the server.
  • (Optional and applicable only for post-installation step – License Activation) The licenses are activated based on the license files (.lic) available and/or Activation/Entitlement IDs specified. You can verify license activation of these files in LMU.
    For already active licenses, expired licenses, invalid file format or missing files, and so on a notification is displayed for the notification area icon. For more information, refer to installer log file located, having the extension _SILENT for silent installation, located at the path
    [System drive]:\ProgramData\[company name]\GMS\InstallerFramework\GMS_Installer_Log.
  • (Optional and applicable only for post-installation step – Project Setup) In addition to the automatic project startup, HDB and LTS creation, a website and a web application is created. If you have configured an existing Windows local/domain user, you must provide the password in the command prompt window that displays during website creation. It is added as a member of the IIS_IUSRS group. Otherwise, a new website/web application user is created and added as a member of the IIS_IUSRS group.
    Internally this user is assigned access rights on virtual directories (graphics, libraries, documents, shared, and devices folders) inside the Server project folder. Also, a default self-signed certificate used for securing communication between the Windows App Client and the web server (IIS) is created.
    The web application is linked to the project and the website and web application https URLs are provided in the installation log file, having the extension _SILENT for silent installation, located at the path
    [System drive]:\ProgramData\[company name]\GMS\InstallerFramework\GMS_Installer_Log.
    For any invalid website/web application configuration, missing IIS configuration, invalid domain user and so on, a notification is displayed. For more information, refer to the SMC log when required at the following path
    [Installation drive]:\[installation folder]\GMSMainProject\log.
  • (Optional and applicable only for post-installation steps of other extensions) The post-installations steps of other extensions, when correctly configured, enabled (modified the .txt file to .xml) are executed as well successfully.
  • (Optional and applicable only for Quality Updates and Hotfixes) The patches for prerequisites, platform, mandatory extensions, and the non-mandatory extensions, as applicable are installed. For any errors during the patch installation, refer to the (_ELOG) file.

NOTE 1:
During the silent installation, the Installer ensures that all parent extensions of the configured extensions are installed, even if they are not explicitly mentioned in GMS Platform.xml file. Moreover, a mandatory extension and its parent extension (mandatory or non-mandatory) even if they are not explicitly mentioned in GMS Platform.xml file are also installed.
To configure the extension from other location than the distribution media, you need to configure the path of those extension in the attribute <ExternalEMsPath> of the GMS Platform.xml file.
NOTE 2:
If there is a prerequisite conflict, the Installer, by default, takes the action by selecting the default set option as in the custom installation and resolves the conflict automatically. In case of Abort, please see the Installer Log. For example, if a higher compatible version of the software is installed, the Installer skips the installation of the prerequisite.
NOTE 3:
If a lower compatible version is installed, then the Installer upgrades the prerequisite, generally for a prerequisite ALM. However, for a non-mandatory prerequisite, the Installer completes the installation, but fails to install the non-mandatory prerequisite and informs you with a notification in the task bar notification area.
NOTE 4:
If a lower incompatible version is installed, by default, the Installer installs the prerequisite.
NOTE 5:
If the installation fails, you must click Exit in the context menu that displays when you right-click the taskbar icon.