NOTE: If looking for instruction to convert a DG, XV4, or DCV user to token, please reference Token Conversion Processes instead.
If token access is required to provide registration for several local installs, use the following instructions to create and distribute this kind of alternate registration. Use caution when creating token access as it should only be distributed to the local installs, and not to any client. We do not create token access and give it away to clients. This is for internal use only.
You will need:
Name of practice
Registration code(s) of the product(s)
Telephone number of practice
E-mail address of practice
Number of tokens required [match salesforce record, if record is unlimited=# of w/s] (KK: "limit 10 per location to start, unless office specifies otherwise")
Customer able to reach 10.0.100.77 for token access
To start:
Navigate to https://xvreg.azurewebsites.net/License
Use your normal user login for the computer to access the site
Click “Create New” in the upper left-hand corner to create a new entry
Reseller = Apteryx (This must be Apteryx or else the Token will not work)
Account = The name of the practice
Product = The primary registration code for the product
Salesforce Account = Account number as shown in Salesforce
Phone = Telephone number
Email = E-mail address if they can provide one
Allowed Active Tokens = Number of tokens we are creating (MUST match number of current licenses, no more no less)
Click Create and it will make an entry like the one seen below
Update the INI file:
Grab the ApteryxINI.INI file from their install
Open the file in Notepad
Change the content of the ApteryxINI.INI file to match the below figure
Edit the customer name to match the website entry
-
Edit the registration code
Grab the ApteryxINI.INI file from their install
Open the file in Notepad
Change the content of the ApteryxINI.INI file to match the below figure
Edit the customer name to match the website entry
Edit the registration code
Installing the token:
If XV4, update to build 15 and verify latest INI10.dll is in use. If DG, update to latest build and verify latest INI10.dll is in use
Add the edited INI file into the local install directory of the program
Rename .ARI file(s) to .OLD (if applicable)
Run the program to test, if successful, delete old .ARI files
Article Version 1.0 8/20/2026