This article outlines the full process of updating XVCapture from version 3.4 to version 3.5. Internal use only.
There are four main parts to updating XVCapture from 3.4:
Updating the application itself
Updating all hardware extensions
Updating to token registration/changing token registration number to use a non-lead tools code
Updating the DICOM definition to use a .PFX certificate instead of a .PEM certificate
Prerequisites
To successfully perform the update, you will need the following:
The updated INI file for the office (Obtained by going to https://sites.Apteryx.net , selecting their site, selecting “registration licenses,” clicking “view” next to the 3.5 registration entry (reg code will begin with DC67), then clicking “Download INI.” More info on registration in a later section of this guide)
The office’s certificate files (obtained by going to https://sites.Apteryx.net , selecting their site, and selecting “download certificates”)
“xvcapture_3-5-6_upgrader.exe” (located here https://apteryximaging.planetdds.com/hc/en-us/articles/4412758829595-Current-Imaging-Downloads under “XVCapture and Rebrands”
All hardware/extensions that the office uses (obtained by checking what IXDLLs are currently installed in 3.4, or by asking the office what devices they use)
Getting Started
If the office runs a server installation of 3.4, you will need access to the server. If the office is running local installs, you will need access to all workstations that use XVCapture. For local installs, you can perform the update on only one PC, then copy the updated XVCapture folder to all the other PCs as needed.
After this, take note of what IXDLLs are installed currently. Go to https://apteryximaging.zendesk.com/hc/en-us/articles/4412758829595-Current-Imaging-Downloads on the PC you’re updating and download each extension that needs to be updated. The currently installed IXDLLs for 3.4 will not work, so each one must be updated. Do not run the updaters yet.
Updating the application itself
Once you are connected and have all needed information/updaters, run XVCapture as admin once, then close the program. Once done, run “xvcapture_3-5-6_upgrader.exe” to update the version to build 3.5.6. If needing to update to 3.5.9 or higher, Copy in the respective XVCapture.exe, ApteryxINI10.dll, and Axlib.dll manually after the update.
Updating the extensions
Once the application has been updated, run each necessary IXDLL upgrader to update the currently installed extensions. For example, if a client uses Schick sensors and a Vatech pan, the Schick IXDLL and vatech IXDLL will both need to be updated. This also applies to extensions such as Directvideo, Image Importer, TWAIN, and other general use extensions.
Updating the registration
Once the application and extensions have all been updated to the correct version, the registration will need to be updated next. If the client is using legacy registration (ARI file), locate and delete the ARI file first. If the client is already using token registration but is using a 3.4 code (begins with DC7C), you will not need to remove an ARI file.
To update the registration, go to https://sites.Apteryx.net , select the site you are updating, then click “registration licenses.” Find the entry containing a registration code beginning with DC67, click “View,” then click “Download INI.”
If you do not see a 3.5 code under “registration licenses” yet, follow the steps below to create one:
Select “generate new capture license”
Leave reseller as “Apteryx”
Leave Salesforce ID as whatever is automatically generate
Set allowed tokens to however many tokens the office needs. If they are on Apteryx Starter, set it to 3. If on Apteryx Standard, set it to 5. If on Pro Limited, set it to 10. If on Apteryx Pro Unlimited, set to slightly higher than however many PCs the office is using XVCapture on.
Click Save
Once saved, download the INI for the newly created entry. Place this new INI into the root directory of XVCapture and overwrite the old one.
Additional Resources: Token Conversion Process
Example of a correct INI file:
Datagrabber token registration
If the client uses an install of Datagrabber that runs from the XVCapture directory, and needs to use Token registration, see steps below.
Update the build of Datagrabber to the latest version
Open ApteryxINI.ini, and enter the DG token information into it (see screenshot below)
If a token registration code does not exist for the client yet, it will need to be generated. This can be done by going to https://sites.Apteryx.net , selecting “registration” from the left menu. It should take you to a page where you can generate a registration number.
Enter the practice name exactly as it appears under their Apteryx account within Sites. Name should match with what is in the new INI you pasted in earlier.
Vendor should be left on “apteryx”
Set product to “Datagrabber”
Set Type to “Subscription”
Set allowed licenses to match however many PCs will be using Datagrabber
-Click generate, copy the code that is generated
Paste the code into “add existing capture license” under “registration licenses,” found in the client’s Apteryx site
Copy the practice name and registration code into the fields highlighted below.
Updating the DICOM Definition
Once the program, extensions, and registration have all been updated, you will need to then update the DICOM definition.
Paste the client’s PFX file into the root directory of XVCapture (see prerequisites section to find where to obtain this)
Open XVCapture and go to Advanced User Tools > Preferences > DICOM
Select “Configure DICOM servers”
Select the Apteryx entry and click “Update”
Go to the Encryption tab, make sure the drop down is set to TLS, then specify the path to the PFX file. If on the server install, make sure this is a UNC path so the workstations can access the file as well.
Click OK all the way back out.
Finalizing the update
Once all the above has been completed, set the configuration as default. (Advanced user tools > preferences > Advanced > Set this configuration as default. Overwrite any previous default that may have been applied.
If using local installs, copy the newly updated XVCapture folder to yourself or place on a networked location at the office, then copy it down to each workstation that needs it, overwriting the previous XVCapture folder. Launch XVCapture and click “yes” to use default settings.
If this was a server install, just launch XVCapture from the UNC path and click “yes” to use default settings on each workstation.
You can double check all is well by checking the registration number displayed in the top-left corner of XVCapture and checking to make sure the DICOM definition connects.
At this point, the office can go ahead and test their devices to make sure everything still works as intended, and they should be good to go.