Skip to main content
All CollectionsJoyConnect Universal
Secondary Care Pilot: IT Team remote deploy - installing JoyConnect Universal
Secondary Care Pilot: IT Team remote deploy - installing JoyConnect Universal

Please follow this guide if you are a central IT Manager rolling out the installation of JoyConnect software to secondary care sites

Support at Joy avatar
Written by Support at Joy
Updated over 3 months ago

πŸ“Œ Note: If you have any questions or issues please reach out to our technical team via your Customer Success manager.

JoyConnect Universal is currently in a closed pilot. Please do not follow these instructions unless you have been provided with this information and asked to do so. The information is currently provided for broader context and current msis are not linked.
​
This content is subject to change.

  1. Joy is provided as an MSI comprised of its widget bundled with an auto-updater. 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)

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

  3. During the closed pilot there is an additional command parameter required to set location for the site. An example of this in powershell would be:

<br style="box-sizing: border-box;">msiexec /i JoyConnectUniversal.Installer.1.0.2.msi POSTCODE='"SW1A 2AA"'

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 $outFile

msiexec /i $outFile ALLUSERS=1 /q

Did this answer your question?