Skip to main content

Replacing XrayVision 4 Standard Registration with Token

Michael Satterfield
Updated

Customer requests token

Support takes ticket

                Confirms customer is XV4 user

Use “Convert Registration to Token” Macro

                Advises office of requirements prior to call:

                                Token server whitelisted

                                Static IP addresses

                                Server has ability to connect us

                                Downtime during changeover                                        

                Actions required by customer from support

                                Provide all registration codes currently in use (support can obtain during call) 

Support creates token using current registration codes, using primary code as the token code

Updates XV4 if needed

Installs new INI and renames ARI files to .OLD

Confirms token reg is working, removes ARI file completely if so

Use “Token Registration Completed” macro to CC accts

Paste codes converted to token in comment section of ticket

Accounts will void and update SF

Customer Will Require:

  1. Assets should already exist on the SF account

  2. XrayVision 4
    This is not offered to XV3 or XVL customers.

  3. ApteryxINI10.dll file version 1.0 Build 27 or newer (1.0.0.27), newest INI is provided below, XV4 is on build 4.0.0.15

  4. Access/Whitelist to registration servers if needed: https://apteryximaging.zendesk.com/hc/en-us/articles/5468460151451-Whitelisting-for-Apteryx-Software

  5. Ability to remote us into the server with administrative access.
    We are not allowing customers to do this themselves.

  6. Static IP addresses for each PC that is to use XrayVision 4
    We do not set this up for offices. Offices should have a knowledgeable IT professional set this up for them.
    If IP addresses are not static, computers have the potential for soaking up >1 token

Collecting Information

Remote in and document existing registration numbers in use into the Zendesk ticket for public comment (DO NOT GO OFF OF WHAT SALESFORCE REFLECTS)

Registration codes can be collected by opening existing install of XV4 and navigating to Help > Display Registration Information

If ticket was submitted to us by a reseller or the client provided the reg numbers within the ticket, use the Registration Manager VM to determine how many total users each registration code is for. Also check to make sure these codes were not split or voided. (Plug the codes into “Get Registration Information”)

Search code(s) in Zendesk to verify these registration codes have not already been tokenized

Token count should reflect how many total licenses the office has across all registration numbers. For example, if they have one 5 user primary code, and two 1 user additional codes, the token count would be 7.

Heavily recommend taking screenshots for ticket. Ensure they include license total and registration numbers used.

If SF reflects registration numbers that are not in use in the install, do not add/use them in any capacity.

Token Setup Steps

  1. Navigate to https://sites-pdds.Apteryx.net/ Registration > Token Registration Licenses (do not use “Generate Registration Number”)

  2. Click “Create New License” in the upper left-hand corner

  3. Reseller = Apteryx (This must be Apteryx or else the Token will not work)

  4. Account = The name of the practice as it is shown in SF

  5. Product = The office’s primary registration code as shown within the application or within SF (code generally begins with 8C, 9C, or DC - do not use an additional (BC) reg code)

  6. Salesforce Account = The account number of the office as shown in SF

  7. Phone = Telephone number

  8. Email = E-mail address if they can provide one, otherwise use email address the ticket came from

  9. Allowed Active Tokens = Number of total licenses across all registration numbers as documented earlier (before step 1)

Example of correct XV4 Token below:

xv4tokenexample.JPG

Click “Save”

Create an ApteryxINI.INI file that contains the token information just entered

Customer field should match what was entered in the customer field when creating the token

RegNum should match be the code entered in the Product field during token creation

Example below:

xv4 token example.JPG

Blank INI, if needed:

Installing token registration


NOTE: The below steps should be followed on the client’s server. Make sure XrayVision v4 is not open on any workstation in the office. If any residual files prevent you from running the upgrader or renaming the ARI file, go to computer management > shared folders > open files and close any open files within the /Apteryx/ folder.

  1. If not already updated, download the XrayVision 4 upgrader from Apteryx Legacy Upgraders > XV4 4.0.0.15 Upgraders, located in the Files tab of the Apteryx CX - Customer Support Teams channel and copy the upgrader to the client’s server via LogMeIn
    o Run and install the upgrader as needed, “yes to all” when prompted

  2. Place token INI (ApteryxINI.ini) into the application’s directory

  3. Rename any .ari file to .old

  4. Delete any .REG files found

  5. Verify XrayVision now launches without issue from an existing workstation. If so, permanently delete the old .ARI file

If they fail to reach our registration server and cannot immediately rectify the issue. You will need to revert the steps and put them back on legacy registration for the time being.

Once complete, use the “XV4::Token Registration Completed” macro to tie Accounts into the ticket, paste the codes converted to token under “<Primary code TO BE FILLED OUT BY TECH>” within the comment body, and solve the ticket out.

Accounts will void the legacy registration numbers and update Salesforce at this point.

Attachments