Documentation Center

Installing the Language Weaver add-in for Microsoft Office (Silent Mode)

The installer (msi) can be used to install the Language Weaver MS Office plugin without showing a dialog box. This is useful for large scale roll-outs.

Before you begin

The full .exe installer checks for all prerequisites and installs them as required. The .msi installer does not do this, so you need to check if the following prerequisites are installed, and if not, download and install manually.

Procedure

  1. Remove existing login details

    Once a user has successfully logged in, the details are stored in one or more encrypted files, and will be reused after a reinstall; uninstall won't remove them. If you want to start from a clean slate, remove these files (2. and 3. may not be present):

    • C:\Users\%USERNAME%\AppData\Local\SDL\SDL MT Cloud for Microsoft Office\settings.dat
    • C:\Users\%USERNAME%\AppData\Local\SDL\SDL MT Cloud for Microsoft Office\ LoginDetails.default
    • C:\ProgramData\SDL\SDL MT Cloud for Microsoft Office\LoginDetails.txt
  2. Silent Installation without Login Details

    Running the MSI basically already does a silent install, but it may still pop up the request to close all Office applications. Since it is possible to install while an Office application is open (the add-in will then only show when app is next started), you can suppress the warning like this:

    msiexec /i installer.msi CHECKOFFICE=0
  3. Silent Installation with Login Details preconfigured

    For an automated roll-out, you can also install predefined authentication details. With that option, the add-in is ready for use when the user next starts an Office application.

    Language Weaver has three authentication modes, two of which can be used in a silent install (replace the sections in square brackets with your organization's details).

    • RWS ID login and password

      Since each user logs in with their own user name and password, there is no login preconfiguration. Just use the plain install script:

      msiexec /i installer.msi CHECKOFFICE=0
    • Federated login and password

      If you have a federated login set up with RWS, you will be redirected to your company's login page. To preconfigure that, pass the company name and connection code as parameters.

      • Company name can be any text and is used in the plugin, in a list of available authentication methods.

      • Connection code is the code used for the federation setup and is provided by RWS. It needs to be entered exactly as provided.

      • The installer call looks like this:
      msiexec /i installer.msi CHECKOFFICE=0 COMPANY=[AcmeInc] CONNECTIONCODE=[FED-AcmeInc]
    • Using Client ID / Client Secret authentication.

      To use a common login for all users you can install with Client ID and Client Secret codes: in that case, the installer call looks like the example below:

      msiexec /i installer.msi CHECKOFFICE=0
      LOGIN=[MyClientID] PASSWORD=[MyClientSecret]
    • Choosing the Server Location

      By default, Language Weaver services are hosted in the EU. Some customers prefer US hosting, and they can get US accounts. To choose the US servers instead of the default, add the CLOUDSERVER parameter. For example: to use RWS login on a US account, the installer call looks like this:

      msiexec /i installer.msi CHECKOFFICE=0
      CLOUDSERVER=[us.api.languageweaver.com]
  4. Silent Uninstall

    For a silent uninstall, add the CHECKOFFICE flag, like this:

    msiexec /x installer.msi CHECKOFFICE=0

    This may still ask you to confirm the installation. For a completely silent uninstall, run as an administrator and add the /qn flag, like this:

    msiexec /x installer.msi CHECKOFFICE=0 /qn

    It's important to use this flag only when running as an administrator. Putting the commands in a batch file and running that as administrator is not enough, you'd have to open a command window in admin mode and run. Errors are only reported in the installer log, superficially, it may look like all is OK.

  5. Log file

    All installation commands can be extended to write a log file, like the following, where logfile.txt can be replaced by any file name.

    msiexec /i installer.msi CHECKOFFICE=0 /L*V [logfile.txt]