This will provide all the information needed to configure a silent installation of the CONNECTION Client for those administrators who are looking to make the process less impactful.
*Please note: When deploying CONNECTION Client using the local system account (such as with SCCM), include the NoStartPostInstall=1 argument to prevent an elevated instance of the Bentley Licensing Service from interfering with user licensing traffic. If deploying another Bentley product via SCCM, it may ignore the NoStartPostInstall=1 argument and still start CONNECTION Client during product installation. As a workaround, perform a silent installation of CONNECTION Client with the NoStartPostInstall=1 argument immediately after the product installation to close any running licensing components.
Here's the full list:
cs=Czechde=Germanes=Spanishfi=Finnishfr=Frenchit=Italianja=Japaneseko=Koreannl=Dutchpl=Polishpt-br=Portugueseru=Russiantr=Turkishzh-cn=Simplified Chinesezh-tw=Traditional Chinese
If removing or downgrading CONNECTION Client, silently uninstall CONNECTION Client by passing /uninstall and /s arguments to the original installer like the example below:setup_connectionclientx64_11.00.xx.xx.exe /uninstall /s
The following parameters enable organizations to configure the Application Update functionality to best suit their needs.
*Please note: Implemented in CONNECTION Client 10.00.13.xx or latersetup_connectionclientx64_11.00.xx.xx.exe BeCheckUpdateOption=X - Replace X with options below
Use this option if you want to prevent users from seeing updates available under "Applications" but allow them to configure the "Updates" section of "Preferences" to receive the information (i.e. they can then alert their admin if they require the update, but do not have installation rights).setup_connectionclientx64_11.00.xx.xx.exe BeCheckUpdateOption=3 /q
Use setup_connectionclientx64_11.00.xx.xx.exe BeCheckUpdateOption=3 BeCheckUpdateIsEnabled=0 /q Use this option if you want to prevent users from seeing any updates available under "Applications" and disable the "Updates" option in "Preferences".
Location in the registry is the UpdateClient value in HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\BentleyDesktopClient\Install
Change the values:
Note: This requires you to be federated with Bentley's Identity Management System and is only required if the domain provided by your machine does not match the domain that set up for federation. You can check this by opening command prompt and typing "echo %USERDNSDOMAIN%". The returned value should match a domain federated with Bentley. You can check this by trying to sign in with that domain in a web browser on https://connect.bentley.com/. A federated domain will redirect you back to your server for authentication, rather then keeping you on the Bentley authentication page and prompting you for a password.
A domain hint kick starts the federation process by providing the federated domain in the initial request to IMS from the CONNECTION Client. This will automatically redirect the login screen back to your identity provider where the user will perform your method of authentication. Note that this does not guarantee that you will be automatically signed in at your identity provider.
setup_connectionclientx64_11.00.xx.xx.exe SsoDomainHint=mydomain.com /q (change mydomain.com to your domain name)
*Please note: Implemented in CONNECTION Client 10.00.14.xx or later
The following options can be specified in HKEY_LOCAL_MACHINE\Software\Bentley\BentleyDesktopClient\Install by an administrator to mandate preference settings used by CONNECTION Client. These can be viewed by a user in the CONNECTION Client Preferences window, but they cannot be changed:
Each of the string values above can have a value of either True or False.