Version 23 - 23.09.2020 - GoEdit Administrator|0 Comments|0 Attachments| More Details



GoEdit Windows Installer Package (MSI) allows easy installations in a variety of ways.

Single User

You will not need any administration rights or any advanced permissions.

Just double-click on the installation file "GoEdit-windows.msi" and complete the installer.

"Per Machine"

This is only available for administrators of your machine, since you will need administrative permissions on your machine

Run this in and ADMIN shell to install GoEdit for all users of your machine:

msiexec /i GoEdit-windows.msi /qn ALLUSERS=1 INSTALLDIR="C:\Program Files (x86)\KontextWork\GoEdit"

Company Wide

This enables you to install GoEdit on all computers in your company in an automated fashion - this is based on normal GPO rules of a Windows Domain Controller

Via GPO rules of a Windows Domain Controller

Please follow along this guide. Please note that publishing is not supported right now from the GoEdit MSI. Only the assigning functionality is working right now.

Via "Microsoft System Center Configuration Manager"

As GoEdit already comes as MSI package it can easily be installed via Microsoft System Center Configuration Manager.

Microsoft has a good description how to "Create and deploy an application with System Center Configuration Manager"

Disable "Open with GoEdit" Dialog

This dialog can be disabled via GPO: Browser Settings for Microsoft Edge, Google Chrome

Upgrading GoEdit Native Client

Upgrade 1.2.1 to 3.0.0

Case: User Installation

If you have an existing user installation and you want to upgrade it, just install the new version by double-clicking on the installer, it will replace the old version automatically.

Case: Per Machine installation

When upgrading a "Per Machine" installation, you will need to uninstall the old GoEdit version by using this command in an ADMIN shell:

# Remove GoEdit 1.2.1
msiexec /x {5303BC56-DBD5-4852-B641-9B5C1E1C88F3}

You can run this per GPO or using a computer startup/shutdown script for the same command (see here).

After that, you can install the new GoEdit Native Client MSI as usual using GPO or and ADMIN shell

msiexec /i GoEdit-windows.msi /qn ALLUSERS=1 INSTALLDIR="C:\Program Files (x86)\KontextWork\GoEdit"
Case: User Installation to Per Machine migration

Please follow the migration steps under "Migrate from "User Installation" to "Per Machine" Installation"

Migrate from "User Installation" to "Per Machine" Installation

For this process, you will need to

  1. Uninstall GoEdit using the procedure described below for "User Installation" first ( logon/logoff script ). You need to take care of removing this old installation on your own before installing "Per Machine"
  2. Then you install GoEdit machine wide using GPO or an ADMIN shell as usual
If you skip step one, you will be able to install "Per Machine" but it will have no effect on the users, which already have a "User Installation", since it will take precedence over the "Per Machine" Installation.
Deploying the application globally will always persist an  existing "User installations" (if the MSI was used to install GoEdit in advance)

Uninstall GoEdit Native Client

Case: User Installation

You can automatically uninstall per User installations by executing this command via Group Policy Scripts. Make sure this is performed in a USER CONTEXT (see here). Otherwise the per machine installation will be removed instead.

Again, you can use Group Policy User Logon/Logoff scripts to remove the application before you deploy the MSI the first time. Simply run the same command as mentioned above, from within a user logon/logoff script.

wmic product where name='GoEdit' call uninstall

Case: Per Machine Installation

If you have installed GoEdit per machine with the old installer, just switch to a computer startup/shutdown script for the same command (see here).

wmic product where name='GoEdit' call uninstall


What happens if a user tries to install a "User Installation"  although the "Per Machine" installation is deployed?

The "User Installation" will take precedence over the "Per Machine" Installation, so whatever the user installs, will be used for him, but only for him alone. All other users will still use the version and installation deployed "Per Machine"

No attachments yet