Skip to main content
Sign in MENU

FDMS TLS 1.2 Update for Version 8 and Version 9

MS Info
  • Updated

Version 8 and Version 9 sites using the integrated First Data module MUST be updated for the new TLS standards immediately

*You must use Version 8.0.3000 or higher to be compliant with the new TLS standards for First Data.

You must use Version 9.0.1080 or higher to be compliant with the new TLS standards for First Data.

*After the update to Version 8, you need to upgrade the TLS as well.

 

FDMS will shut off all credit card processing for sites that are not upgraded to the TLS 1.2 encryption.

 

Procedure for version 8 follows;

  1. Configure Windows environment according to the setup documentation.
  2. Make a backup of the Micro$ale directory before making any changes so any changes can be reversed, if necessary.
  3. *Delete, rename, or move the following files out of the Micro$ale directory (to ensure there are no file conflicts during the upgrade):
  4. DebitCards.dll
  5. EmpClockInOut.dll
  6. EmpSchedule.exe
  7. FinancialDll.dll
  8. Frequency.dll
  9. HistoryLib.dll
  10. Micro$ale.exe
  11. ProcessCreditCards.dll
  12. SystemMaintenance.dll
  13. Upgrade to MicroSale version 8.0.2712 (ftp - MSaleDealer\Version 8.0 Archive\) 5. Copy the files to patch to version 8.0.3000 into the Micro$ale directory.
  14. Register the DebitCards.dll file in the Micro$ale directory using the regsvr32.exe utility.
  15. Register the ProcessCreditCards.dll file in the Micro$ale directory using the regsvr32.exe utility.
  16. Launch MicroSale on the file server first so that the shared databases will be upgraded.
  17. Verify that the terminal has a unique “Reg-#” assignment in Register Options, Save the Register Options, and Exit to Windows.
  18. Launch MicroSale on the other terminals, one at a time.
  19. Verify that the terminal has a unique “Reg-#” assignment in Register Options, Save the Register Options, and Exit to Windows.
  20. Test a charge, a return, and a batch settlement.

*The files in step 3 are normally updated automatically during the upgrade (step 4) and patch (step 5), but this manual step has been added to ensure that nothing prevents those files from being replaced with the newer files.

If you have questions, please contact support.