Overview
Migrating Intella Connect/Investigator from one machine to another can be necessary for various reasons, including upgrading to better hardware, transitioning from an on-premise setup to a cloud-based environment, or moving from a trial version to a dedicated machine. Intella Connect and Intella Investigator are primarily the same program from the point of configurations. Unless specifically pointed out, Connect and Investigator configuration steps are the same. This article outlines the steps for a successful migration, while emphasizing the importance of ensuring the integrity of your cases throughout the process.
Reasons for Migration
- Hardware Upgrade: Moving to a machine with better specifications can enhance performance, especially for resource-intensive tasks involved in case management.
- Cloud Transition: Shifting from an on-premise installation to a cloud environment can offer improved accessibility, scalability, and cost-effectiveness.
- Trial to Production: Transitioning from a trial version to a dedicated machine can ensure stability and provide access to all features necessary for professional use.
Pre-Migration Considerations
Before beginning the migration process, it is crucial to leave Intella Connect/Investigator and all cases intact on the original machine until you confirm that everything is functioning properly on the new machine. This minimizes the risk of data loss.
Important Files and Settings (Key considerations)
(Optional) Application Configuration: If you want to move configuration settings these two folders will have to be moved. The configuration settings contain user accounts, case lists, case assignments, system settings, case templates, SSL configuration, and other related aspects. (Note: Backup original data first.)
It is important to understand that [User] means the windows user account in which Connect/Investigator is installed under. If running as a Windows Service you also need to specify the correct account it has been installed under.
1.
Intella Connect Home Folder: C:\Users\[User]\AppData\Roaming\Intella Connect
Intella Investigator Home Folder: C:\Users\[User]\AppData\Roaming\Intella Investigator
2.
Intella Home Folder: C:\Users\[User]\AppData\Roaming\Intella
Service Installation
If the previous Intella Connect/Investigator instance was installed as a service, it is advisable to replicate this configuration on the new server to ensure consistency in operation and accessibility.
SSL and DNS Considerations
-
SSL
Certificates: Ensure that SSL certificates are properly configured on
the new machine, especially if secure connections are used. Follow the SSL
setup guide for detailed steps.
https://www.vound-software.com/docs/connect/2.7.2/Intella%20Connect%20Administrator%20Manual.html#_ssl_setup_guide
Licensing Transfer
The licensing process must be addressed during migration:
- Physical Dongles: If using a hardware dongle for licensing, simply move the dongle to the new machine.
- Software-Based Licenses: For software-based licenses, you will need to transfer the license from the existing machine to the new one. This process is done using the haspupdate.exe tool located in the bin folder of the installation directory.
Migration Steps
1. Install Intella Connect/Investigator: Begin by installing Intella Connect/Investigator on the new machine. You can obtain the latest installer file from our website or have it transferred over from the original machine. https://www.vound-software.com/software-downloads
2. Un-share Cases: On the original machine, un-share any cases you wish to migrate. This step is crucial as ongoing changes during the copy process may corrupt the data.
3. Copy Cases and Evidence Files: Transfer all relevant cases and original evidence files to the new machine.
4. Move Configuration Settings (Optional): If you wish to transfer configuration settings, copy the two necessary folders mentioned below. Make sure to back up the original files first.
1.
Intella Connect Home Folder: C:\Users\[User]\AppData\Roaming\Intella Connect
Intella Investigator Home Folder: C:\Users\[User]\AppData\Roaming\Intella Investigator
2.
Intella Home Folder: C:\Users\[User]\AppData\Roaming\Intella
5. Set the desired port for Intella Connect/Investigator by appending ServerPort property in file C:\Users\[USER]\AppData\Roaming\Intella Connect\user.prefs.
ServerPort=8081
Or for Investigator
C:\Users\[USER]\AppData\Roaming\Intella Investigator\user.prefs.
Note that steps 4 and 5 will only take effect after Connect/ Investigator is restarted.
6. License Transfer: (Optional if you are
using SL keys)
1. On the machine that will receive the license, open bin\haspupdate.exe >
Transfer License.
2. In the "Step 1" panel, enter a file name in the "Save recipient information to" field.
3. Click Collect and Save Information. This will generate a fingerprint of this target machine, to which the SL key will be bound.
4. Move this .id file to the machine that currently holds the SL key.
5. On that machine, open haspupdate.exe > Transfer License.
6. In the "Step 2" panel, select the SL key that you want to migrate.
7. In the "Read the recipient information file from" field, enter the path of the ID file that was transferred here in step 4.
8. In the "Generate license transfer file to" field, enter the name of a .h2h file that is to be generated.
9. Click the Generate License Transfer File button.
WARNING: doing so will immediately remove the SL key from this machine. Furthermore, loss of the generated .h2h file will result in an inability to restore the SL key to the target machine. Create a back-up of this file as soon as you can.
10. Move the generated .h2h key to the target machine.
11. Open haspupdate.exe > Apply License File on the target machine.
12. Select the .h2h file and click Apply Update.
The selected SL key will now be present on the target machine.
For a smooth transition, I recommend that you configure your application VMs to reference both old and new license VMs on http://localhost:1947/_int_/config_to.html, prior to migrating the SL keys. They will then automatically switch their "active" license VM when they notice that the license is gone in the old VM and has emerged in the new VM.
7. Start Intella Connect/Investigator: Launch the application on the new machine. (If you have installed as a Windows Service the application will start right after installation)
8. Configure Hostname & SSL: Set the appropriate machine hostname and configure SSL settings as needed. Refer to the SSL section in the administrator manual
Note: If the Home folder was copied over you may skip this step. SSL configuration is stored in the Intella home folder, so moving that folder to a new machine preserves your SSL settings. This is crucial if you’ve changed URLs (e.g., from trial.mycompany.com to connect.mycompany.com). Admins should be mindful of hostname changes if previous certificates were issued for a different domain. Additionally, if using a self-signed certificate, they may need to update cacerts with the Root CA certificate (as detailed in the UM).
9. Import Cases: Open Intella Connect/Investigator Dashboard on the new machine, navigate to 'Cases' → 'Import' to import each case. If configuration files were moved, you can skip this step, as the cases list will already be populated. But if drive letters have changed, those cases might not be accessible on the new server. For example if the Trial server had cases in "E:\cases" but the new machine doesn't have a drive "E".
10. Check Evidence Paths: Navigate to 'Cases', click on 'Sources' for each case, and verify that the evidence paths are correctly configured.
Troubleshooting Common Issues
While migrating Intella Connect, you may encounter some common issues. Here are potential solutions:
- Different User Account: Ensure that the user accounts on both machines are consistent to avoid access issues. Home folders are kept inside the [User] subdirectory, if installed for a different user account then you will end up with a black configuration.
- Wrong Port: Double-check the ServerPort setting in user.prefs to confirm that it matches the intended port for the new installation.
- Lack of SSL Certificates: If SSL connections are not functioning, verify that the SSL certificates have been correctly installed and configured on the new machine.
- Logs If you experience issues where Connect/Investigator seems to not be running you can review the server logs. The link below will give you an insight on how to read and interpret those logs.
Conclusion
Migrating Intella Connect/Investigator to a new machine can significantly enhance your system's capabilities and performance. By following these guidelines and ensuring all steps are carefully executed, you can achieve a smooth transition. Always verify that everything is working properly on the new machine before decommissioning the original setup.