Secure Deviceless Entry

Hey Clarke,

We did go live! It was reasonably smooth - just make sure that if you are setting people up to only use Secure Deviceless Entry (ie no EMVs for their computer) that you still get their computer name into the system table where you set up the EMVs - that was a step missed during our cutover and all of our box office reps were then frantically trying to figure out why SDE didn't work for them! The steps to get scheduled pledge billing utility up and running again with the new, tokenized cards also didn't work so trying to figure what went wrong there. Otherwise, has been pretty good so far.

I haven't heard from anyone that they have problems using SDE. The Box Office doesn't like that having to agree to T&C adds yet another button to click (they'd prefer if they were able to just hit "enter" to accept). The SDE box doesn't automatically close but I believe that is fixed in the most recent service pack? 

Oh and we are on v15.2.33 and use TNEW for both of our sites

Thank you so much, Kathryn!

We went live May 1.  I will echo most of what Dana said.  We're not using SDE as much as I anticipated, but it does help in a pinch with some users that need just the bare bones.  We have found for most of the Alliance Theatre staff they really needed devices, not as much for the High Museum of Art.  We just went on 15.2.35 last night so I'll let you know what I hear about that.  I believe it still registers the transaction as ecommerce, as opposed to MOTO, so that can be a little tricky.

Thanks, Henry. This is all useful information for us.

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.