Replacing DCV 3.5 Standard Registration with Token

Customer Will Require:

1. Assets should already exist on the SF account

2. XrayVision DCV 3.5.0.1 or higher (latest version preferable)

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

4. Access/Whitelist to registration servers if needed: 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 DCV
   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 DCV and navigating to Preferences > Advanced > Access Registration

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

Some offices may be using one registration code per install of DCV. If this is the case, collect all registration codes in use across the office from each workstation. Token count should reflect total number of licenses across all registration numbers. (For example, if the office has 5 local installs each with their own 1 user registration code, token count would be 5.)

Token Setup Steps

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

2. Click “Create New” in the upper left-hand corner to create a new entry (if using Sites dash instead of XVReg, navigate to Registration > Token Registration Licenses > Create new license)

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 = One of the primary registration codes in use by the office (MUST begin with 8C60 or DC60) DO NOT CREATE A NEW REG CODE, USE EXISTING 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 DCV 3.5 Token below:

(Note: When clicking create, the site may look like it is not doing anything, but in the background the registration is being created. To verify, open XVReg site in a new tab, and search for the practice SF account name or registration number)

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:

Installing token registration

NOTE: Make sure XrayVision DCV is not open on any workstation in the office. If on a server install, and any residual files prevent you from running the upgrader or renaming the ARI file, go to computer management > shared folders > open files on the server and close any open files within the /Apteryx/ folder.

1. If not already updated, download the XrayVision DCV 3.5.6 Upgrader from Current Imaging Downloads (https://apteryximaging.planetdds.com/hc/en-us/articles/4412758829595-Current-Imaging-Downloads)
   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 DCV now launches without issue from an existing workstation. If so, permanently delete the old .ARI file

Once complete, use the “DCV 3.5 Token::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

• ApteryxINI10.dll