Support Center

37-Bit H10302 Workaround

Last Updated: Feb 01, 2017 05:18AM PST
Article 5.00-kdb-0006 

New HID H10302 cards are being distributed with card numbers with 11 digits or more.  Some earlier versions of NLSS Mercury devices are unable to read these cards correctly.  A Generic Card Profile needs to be created in order for the Mercury devices to read these cards correctly within the NLSS System.

Hardware Affected: GW5000, GW4500, GW4000, GW3000, GW500
Software Affected: 3.2.4 or and earlier

NOTE: This issue was resolved for versions after v3.2.4.



 
Calculate Facility Code and Card Number 

 



  Open the attached Excel spreadsheet 

 Enter the HID H10302 card number into the “Card Number H10302â€� column. 

 The Facility Code and Card Number will be calculated accordingly. 

  
Create Card Profile 


Create a card profile for your particular situation.  If you have many cards and are using only Mercury devices, choose the Generic Card Profile.  If you have a mixed device environment, it is recommended to create a H10304 Card Profile using the facility code calculated in previous section.

  Create the necessary Card Profile in Configuration > Identity > Card Profiles 

 Use this as an example of how to set up a Generic Card Profile using the data calculated in previous section:




  Save Card Profile 

  
Apply Card Profile to Badge Profile 


Create Badge Profile (see image for example):

 
Apply Badge Profile to Card Holder 


Create Card Holder using new Badge Profile (see image for example):


NOTE: The card number is entered as the calculated number from the first section.  The embossed number can be any number and is not required.  In this example, the number on the card was used and first 2 digits were removed.

Contact Information
For more information, please see https://support.nlss.com or email support@nlss.com
0d564f32803c60bd6a0a0c8b3b3ea9d9@nextlevelsecurity.desk-mail.com
http://assets2.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete