Prerequisites to performing installation #
Planning your upgrade #
We strongly encourage all of our clients to engage in testing toxiCALL® 5 to ensure the required features are available. This will help your poison center determine when is the best time to upgrade. This will also give your poison center the opportunity to provide feedback and requests during the design process. Testing can be done using data on our SQL Server. When you are ready, you can setup your own testing environment to perform testing with your own data.
Before upgrading your production environment, migration testing is required. Feedback will be important as we want to ensure data are migrated properly. We also want to try and identify unique data collection methods of poison centers, such as EMR and DOB, to accommodate ways to migrate this information, when possible.
Test to see if the .NET Libraries are already installed #
The installer will automatically check to see if the necessary .NET Desktop Runtime v6.0.11 or later is installed. If not, the installer will attempt to install the required runtime. This will require administrator rights to complete the installation. The following shows the command “dotnet –list-runtimes” and the results of a system which has already been updated. Please note the command must be run from the Windows Command Prompt, or Powershell.
C:\Windows\System32>dotnet –list-runtimes
Microsoft.AspNetCore.All 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Manually Install the .NET Libraries #
.NET Desktop Runtime v6.0.11 or later is required for installation. If this requirement is not met, the installer will attempt to download and install the runtime. Please note that Administrator Rights are required to install the .NET Desktop Runtime. This can be installed manually using the following link.
Installation Options #
toxiCALL® 5 can be installed per-workstation or per-user. The advantages are detailed below.
If you are setting up a temporary testing or demo environment, using our demo server, we suggest using the per-user installation as this does not require administrator rights after the .NET Desktop Runtime has been installed.
Per-workstation Installation #
Per-workstation installation requires administrator rights to complete the installation. This will make the toxiCALL® application available to all users on the workstation. The application will typically be stored in: C:\Program Files (x86)\CAS\ToxicallWin
Per-user Installation #
Per-user installation does not require administrator rights to complete the installation. This will make the toxiCALL® application available only to user who installed the application. The application will typically be stored in: C:\Users\(username)\AppData\Roaming\CAS\ToxicallWin
The per-user installation type is most common for pre-release testing where users would like to update new versions without the need to get IT staff involved. This is generally used with our demo database so it will not impact your production environment.
Migration Tools Installation #
During the installation process, you will be given the option to install the Migration Tools. We suggest only installing these tools on one workstation as most users should not have access to these tools.
The Migration Tools will allow you to perform the migration on your historical data. During testing you will be able to migrate sections of data then manually validate to confirm migration is performing as expected.
Migration testing is required before moving your production environment to toxiCALL® 5.
Performing the Installation #
This section will walk through the installation screens and provide information regarding the options available.
Choose per-user (Only for me) or per-workstation (Everybody) installation type. As a reminder the Everybody option requires administrator rights on the workstation.
Select the “Install Migration Tools?” option if you wish to install the migration tools on the selected workstation.
Here you can confirm the location where toxiCALL® 5 will be installed. We recommend using the default location unless your organization has specific rules for installation. Also note that the installation location is different when installing per-workstation.
Error 1625: Installation is forbidden by system policy. #
The following was identified in a testing environment while performing a per-user installation.
The specific cause of this error is currently unknown. However, to work around this error, we were required to perform the installation as a per-workstation installation. This required administrator rights but did allow the installation to complete.
