Case Status
Log In


Kappris v1.x Installation (LEG…
  • RSS Feed

Last modified on 10/2/2017 12:58 PM by User.


Kappris v1.x Installation (LEGACY)

back to Kappris...


IMPORTANT: The "bitness" of the installation msi you use must match the "bitness" of the Windows operating system on which it is being installed.

For x64 (64-bit) operating systems the MSI will have "x64" in its filename

For x86 (32-bit) operating systems the MSI will have "x86" in its filename

Windows XP, Windows Server 2003

As long as you have Admin rights on the machine you intend to install Kappris on, you can install it just by double-clicking its MSI file in Windows Explorer. Or if you prefer to use the Command prompt, just cd to the folder containing the MSI and just run it. Windows file association sees that the file is of type MSI and automatically runs msiexec to do the installation. Either of these options will run the interactive installation; you get the familiar MSI wizard that prompts you for required information.

Windows 7, Windows Server 2008 R2

It's slightly more awkward to run MSI files as Administrator if User Account Control (UAC) is enabled, which is the default for these operating systems. MSI files don't have a 'Run as Administrator' context menu item. But unless you're running as Administrator, the installation will not succeed. In order to install the MSI running as Administrator:

  • In Windows explorer, type %TEMP% in the Address field and Explorer will automatically expand the token to the actual folder path. Copy the Kappris MSI file to this %TEMP% folder.
  • Start a Command prompt running as Administrator. The icon that starts Command prompt has a right-click context menu item allowing you to 'Run as Administrator'.
  • At the Command prompt, cd to the folder containing the local copy of the MSI file and just run it.

Windows Server 2008

Install as per Windows Server 2008 R2.

However, Kappris installer cannot register some of its 32-bit components under Windows Server 2008 (Windows Server 2008 R2 is fine). Kutana does not provide a fix for this but the problem can be circumvented by running Microsoft.NET\Framework\<version>\regasm.exe to complete the missing 32-bit registry entries. Skeleton command lines are as follows.

Run (or script) these commands AFTER installing Kappris

"{FRAMEWORK}\regasm" /codebase "{KAPPRIS_FOLDER}\carson.dll"
"{FRAMEWORK}\regasm" /codebase "{KAPPRIS_FOLDER}\KappConf.dll"
"{FRAMEWORK}\regasm" /codebase "{KAPPRIS_FOLDER}\KSupport.dll"

Run (or script) these commands BEFORE uninstalling Kappris

"{FRAMEWORK}\regasm" /unregister "{KAPPRIS_FOLDER}\carson.dll"
"{FRAMEWORK}\regasm" /unregister "{KAPPRIS_FOLDER}\KappConf.dll"
"{FRAMEWORK}\regasm" /unregister "{KAPPRIS_FOLDER}\KSupport.dll"

Windows 8/8.1, Windows Server 2012

If you're installing v1.7.12 or later, the Kappris software suite should be installed in the same fashion as for Windows 7 (above).

If you're installing Kappris before v1.7.12 then an extra command line option needs to be specified, which will cause Kappris to install without the Kappris virtual printer driver, which will need to be installed separately afterwards:

  • From a Command prompt, running as Administrator, run msiexec, specifying the MSI file and INSTALLDRIVER=0;
  • After successful installation, run
    %PROGRAMFILES%\Kutana\Kappris\KInstaller -i -u

    to install the printer driver.

Unattended Installation

If you want an unattended or silent install, you can run msiexec and specify the Kappris MSI as one of its arguments. Here's how:

Command-line MSI Switches

/l log installation messages and events (/l*vx is log everything, extra verbose). Follow this switch with a space and then the name of an output text file to receive the UNICODE log. 

/q quiet or silent installation with no dialog prompts.

/i Install from the msi file whose name follows the switch.

/fa Do a full repair from the msi file whose name follows.

Kappris-specific Arguments

Argument Name Default Value Description/Comments
KAPPRIS_CONFIG_FOLDER C:\Program Files\Kutana\Kappris in which folder will the configuration file kappris.ini be found? Users need read access to this folder. Kappris administrators need to be able to write to it too.
INSTALLDRIVER 1 should the Kappris driver be installed as part of Kappris software installation? Some versions of Windows require this to be 0 so the installer does not attempt to install the Kappris driver at the same time as the rest of the Kappris suite. The driver then has to be installed separately. You don't need this for Kappris v1.7.12 onwards.

Sample Unattended Installation Command Line for Windows 8 and Kappris prior to v1.7.12

msiexec /q /l*v logfile.txt /i \\path\to\msi\Kappris.msi   KAPPRIS_CONFIG_FOLDER=\\server1\kappris INSTALLDRIVER=0

Installing Additional Features


Kappris can be uninstalled in a variety of ways:

Using the control panel

r-click the Kutana Kappris item in the Programs and Features list and select Uninstall from the context menu.

Using the command line

Provided you have the original msi file that you installed, you can run this command:

msiexec -x path\to\original\kappris.msi

Or if you know the exact name of the installed Kappris, which incorporates a version number and platform 32/64 id, then you can use a command like this:

msiexec -x"Kutana Kappris ( (64-bit)"


  1. In Windows Explorer, MSI files don't have a 'Run As' option. But you can run a Command Prompt as an Admin, and then just run the MSI file. You may find that the Admin can see different network folders to the regular user, so you may need to log in as the regular user and copy the MSI down to a local folder, then run the MSI as Admin.

  2. Beware if you do run an unattended install; you need to check the log to make sure that the installation was a success—don't just assume that it was.

  3. If your msiexec command line contains the /i switch and Kappris is already installed, then msiexec will want to throw a dialog allowing you to Modify, Repair or Remove the installation. But if the /q switch is also present, msiexec cannot proceed because it cannot get the user input it requires, so it exits without changing the installation at all. It will not attempt to do a repair. If you need to automate the Repair, specify /fa instead of /i. There is no collection of command line switches which will do this: '{if installed} then {repair} else {install}'.

  4. If you are using Office 2003/2007 you will need install a different Outlook integration and disable integration for Outlook 2010/2013 because it does not work with Office 2003/2007. Notes...

  5. The generated logfile.txt is in UNICODE format. If you subsequently use a program like findstr to search a folder of logfiles for particular content, it won't find anything, because findstr searches on ANSI rather than UNICODE.

  6. A quirk of implementation means that if you specify every available msiexec logging switch you'd write msiexec /lvoicewarmupx. But for shorthand you can just write /l*vx instead.