NevTheDev

There is a USB desktop reader available for EntrySign which works with the back office suite for this exact purpose, and assuming you have the V5 software it also offers some additional functionality too. I'm trying to avoid promoting/advertising here but think the information is relevant to your question (if anyone disagrees I'm happy to remove this post). With reference to the pin numbers, it's possible for the support department to bulk update these for you to help with enrolment. Good luck with the first day back!

If the tokens are already in circulation, then users can perform a self-enrolment at the EntrySign screen to link their card/fob (there's also a bulk enrol feature on the screen as well which admins can use). If you have the full token numbers somewhere (i.e. in a file or in AD etc.) then they can usually be imported relatively easily.

Hi. There are several ways of importing the cards into EntrySign assuming that you have the full card numbers somewhere - they can be imported from a CSV file, sync'd from AD or even pushed into EntrySign through the API. The main thing is that you have the full numbers (not manipulated/truncated) and a unique 'key' to link the users in EntrySign with the card numbers. If your users were sync'd from an MIS or AD then then you will already have a unique ID in EntrySgin (MIS ID or Active Directory username) so this will probably be the key to use for the import. There is also a method to bulk enrol cards at the screen if you do not have the full card numbers anywhere or a unique key to use for an import. Feel free to send me a PM if you need any help or further information.

Yes, it's likely that EntrySign and Papercut are using the same token/format (unless the readers used on Papercut are configured to manipulate the token) as EntrySign doesn't normally manipulate the token in any way (although it can if needed), so it really shouldn't be painful at all. Also, you mention that you import the token into AD - EntrySign also has the ability to pull tokens from an AD attribute and then push into Paxton if required so it can actually make things really easy.

EntrySign actually utilises the full token number, it is usually the Paxton readers which are manipulating the number and truncating it. It is not possible to recreate the full token number from the number stored in Net2 since there is no way of recreating the 'missing' part. It is possible however to push the tokens (and in fact the users as well) from EntrySign directly into Paxton and you can also export these to CSV if required and even automate it completely to enable importing into other systems. I'd be more than happy to provide further information on this if required.

Whilst it is possible to pull users from Paxton into EntrySign (and the other way round) it isn't possible to export tokens from Paxton into EntrySign due to the way they're stored in Net 2. If you use Mifare cards however it's possible to do it the other way around - i.e. push the tokens from EntrySign into Paxton which can make administration a lot easier.