Customer Will Require:
Assets should already exist on the SF account
DataGrabber (or Rebranded/OEM Version)
ApteryxINI10.dll file version 1.0 Build 27 or newer (1.0.0.27), newest INI is provided below, DG is on 2.3 build 35 (Use DataGrabber Upgrader available on Legacy Downloads page to update the dll and exe)
Ability to remote us into the server with administrative access.
We are not allowing customers to do this themselves.Static IP addresses for each PC that is to use DG
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 tokenAccess/Whitelist to registration servers if needed: https://apteryximaging.zendesk.com/hc/en-us/articles/5468460151451-Whitelisting-for-Apteryx-Software
Collecting Information
Registration number can be collected by right clicking DG > About. Current reg code in use will appear in scrolling window. If DataGrabber was migrated, grab registration code from Salesforce account under Assets.
Customer will need to let you know how many workstations DG needs to be used on in order to determine token count.
Search reg code in Zendesk to confirm code was not already converted to token previously.
Token Setup Steps
Navigate to https://sites-pdds.Apteryx.net/ Registration > Token Registration Licenses (do not use “Generate Registration Number”)
Click Create New License, then:
Reseller = Apteryx (This must be Apteryx or else the Token will not work)
-
Account = The name of the practice as it is shown in SF NOTE: If ticket came from a reseller, do not use Reseller name in this field - use the dental practice’s name
If ticket came from reseller/3rd party IT, search the registration number they provided in Salesforce to locate practice’s account name.
Product = The office’s primary registration code for DataGrabber as shown within the application or within SF
Salesforce Account = The account number of the office as shown in SF
Phone = Telephone number
Email = E-mail address if they can provide one, otherwise use email address the ticket came from
Allowed Active Tokens = Number of workstations needed as documented earlier (before step 1) note: pad token count with +5 more tokens than necessary to mitigate “out of tokens” issues and account for growth.
Click Save
Example of correct DG token below:
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:
Downloadable copy of blank INI:
You can use the above INI token file to start with
Once complete, use the “DG Token::Token Registration Completed” macro, paste the code converted to token under “<Primary code TO BE FILLED OUT BY TECH>” within the comment body, attach the ApteryxINI file you’ve created, and solve the ticket out.
The macro will provide the client with steps on how to self-install the token registration.
Installing token registration
NOTE: Below steps are only needed if we’re facilitating the token conversion remotely. See steps above on how to create token license and preferably, use macro to send the INI and self-install instructions to the client.
NOTE: Make sure DataGrabber 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 DataGrabber and related files within the /Apteryx/, /Shared Files/, or /DataGrabber/ folder. Be sure the folder containing DataGrabber is not open in File Explorer as well.
If not already updated to version 2.3 build 35, download the DataGrabber upgrader from Legacy Downloads (https://apteryximaging.zendesk.com/hc/en-us/articles/4412764698779), located under the “DataGrabber and OEM versions” tab. If running an OEM version, download and install the upgrader corresponding to the name of the OEM version.
o Run and install the upgrader as needed, “yes to all” when prompted (AS ADMIN)
Place token INI (ApteryxINI.ini) into the application’s directory
Rename any .ari and .reg file to .old
Verify DataGrabber now launches without issue from an existing workstation. If so, permanently delete the old .ARI file