Secure Deviceless Entry

I'm going to hijack this thread with a semi-related question/grievance.  We have been looking at TMS *forever*, and had finally picked a go-live date when...  I found something in documentation that said a machine can run with either emv or secure deviceless, but not both.  This would be fine for admin offices, but..  We have also have old-school box offices with bulletproof glass and no way to slide an emv device between customer and staff.  These locations also take calls in between walkup.  Has anyone else also run into this conundrum?  What have you done to get around it?

User can use both.  Format TR_MACHINE_SETTINGS table with the serial/model of their EMV and then the user will also be able to use SDE when EMV is not available.

If a user will never use an EMV, just leave the serial/model columns blank.

We do not own our own venue.  When we are performing we set-up our box office staff in the venue box office.  EMV devices cannot be passed through the window.  Patron hands card to box user who taps/chips/swipes card.  Luckily the window is big enough that this is visible to patron.

Also EMV has long cord and could be held up if patron requested actually seeing the transaction.


In TR_MACHINE_SETTINGS the same EMV Serial number can be assigned to multiple workstations, but can only be used by one workstation at a time.  There can only be one line in the table for each work station.  The table is very easy to update if you need to move an EMV.  However, the user should reboot their PC each time the TR_MACHINE_SETTINGS table is updated for that computer.

Hope that helps.


Also, I was told that the TR_MACHINE_SETTINGS set-up for SDE would be eliminated in v.15.2.35.  We're still on .2.33, but have finally managed to schedule our update to 2.35.  That'll go into TEST for us next week.  :-)

Hope this helps

I can confirm that TR_MACHINE_SETTINGS set up for v15.2.35 is no longer necessary for SDE.  We upgraded to v15.2.35 Friday night specifically to have it in place for our cutover yesterday.  Our remote phone room hasn't had any issues and they don't have an entry in TR_MACHINE_SETTINGS.

Nancy!  You had something like 8 million devices to deploy.  How'd it go?

Thank you!  That is what my brain was thinking, but seeing something different in Tess documentation had me doubting myself.

So far, so good (knock wood)!  One of my colleagues spent the week delivering our devices and showing users how to connect, and we invested an hour each day on a daily 'Zoom' for our users so they could ask questions about workflow and new refund procedures.  I also did a fair amount of SQL pre-work that updated our various payment methods, machine settings, etc.  We cutover at midnight, knowing that we'd have to put our website into maintenance mode in case of problems because Tessitura staffing wouldn't be available until 8 am.  Thankfully that wasn't necessary and by the time 8 am rolled around we were testing and ironing out just a few kinks. Now, I eagerly await our first payout so I can help our finance teams with reconciliation and reporting.  It was a lot of prep and work, but that part is over and it FEELS SO GOOD.

So far, so good (knock wood)!  One of my colleagues spent the week delivering our devices and showing users how to connect, and we invested an hour each day on a daily 'Zoom' for our users so they could ask questions about workflow and new refund procedures.  I also did a fair amount of SQL pre-work that updated our various payment methods, machine settings, etc.  We cutover at midnight, knowing that we'd have to put our website into maintenance mode in case of problems because Tessitura staffing wouldn't be available until 8 am.  Thankfully that wasn't necessary and by the time 8 am rolled around we were testing and ironing out just a few kinks. Now, I eagerly await our first payout so I can help our finance teams with reconciliation and reporting.  It was a lot of prep and work, but that part is over and it FEELS SO GOOD.