Skip to main content
All CollectionsJoyConnectInstalling JoyConnectJoyConnect Central IT Installation
SystmOne Part 1: IT Team install JoyConnect across all devices

SystmOne Part 1: IT Team install JoyConnect across all devices

Please follow this guide if you are an IT Manager rolling out the installation of JoyConnect to GP practices with SystmOne.

Support at Joy avatar
Written by Support at Joy
Updated this week

πŸ’‘ If you have any questions or issues please reach out to our technical team via your Customer Success manager.

πŸ’‘ Joy requires an active connection on a machine within the practice to write-back (after working with S1). To prevent connectivity issues we strongly recommend a machine-level installation rather than per-user unless every user on each machine has Joy installed.

  1. Before users begin interacting with Joy please make sure an ODS code is set within S1 (requires S1 administrator). If this is not set to your ODS code, please let your Customer Success manager know the correct value to identify the practice/PCN.
    ​

  2. Joy is bundled with an auto-updater and we would recommend downloading and installing an older version to validate that the automated patch process is working.

    1. Latest Version. (installation will update to this)
      ​

  3. For a per-machine installation, execute the file with the following command: msiexec /i JoyConnect.Installer.[installation_version].msi ALLUSERS=1
    ​

Please note that we do not support the use of Administrative Installation Images as they interfere with the automated patch process. We recommend that you download and execute the installer directly on the machine instead.
The patch process requires that the original msi installer is available at the location it was last executed (the windows installer cache is not enough!). We therefore recommend that you copy and execute the installer in a safe place on the user's harddrive. If this is not possible and you have to move/rename/delete the original installation file, it is your responsibility to provide a reliable alternative location, e.g. by specifying a persistent network location using the SOURCELIST attribute."

Sample powershell script for a machine wide installation:


​# jcinstallation.ps1 - requires elevated privilleges to run$msiName = 'JoyConnect.Installer.[installation_version].msi'$outFile = "$env:SystemDrive\$msiName"Start-BitsTransfer -Source https://builds.thejoyapp.com/joyconnect/installers/$msiName -Destination $outFilemsiexec /i $outFile ALLUSERS=1 /q

Did this answer your question?