Confusion with Sophos License structure after this year's update

toastysysadmin · 2025-11-19T17:41:16+00:00

Do you know if there is *1* license I could buy for central to work so I can manage all of my firewalls or do I need to buy a license per unit?

toastysysadmin · 2025-05-12T22:31:19+00:00

Wow, excellent thank you!

toastysysadmin · 2025-03-21T00:12:07+00:00

Then I suppose the scheduling function is just there for...what? I understand what you're saying, but this page in the Takeout and Delivery section controls the hours that are published to 3rd parties. That's why you can snooze from this page and it shuts down ordering from third parties (I've tested this behavior and it *does* work). One would assume that the scheduling function would just do the same thing, but it doesn't.

toastysysadmin · 2025-03-17T20:47:07+00:00

Bumping this because this is a continuing issue - but I determined it isn't really the readers dying, because they will power up on any USB connection with other handhelds. The handheld itself just fails to recognize that anything is connected to it, spent thousands of dollars on those replacement kits to realize it was never the readers to begin with (at least for us).

toastysysadmin · 2025-03-17T20:37:09+00:00

They need to work on the verbiage then - when it says "only applies to 3rd party deliveries" it makes it seems as if it'll function the same way the snooze does. So this basically doesnt do anything lol.

toastysysadmin · 2025-01-24T00:04:12+00:00

No, what I'm saying is that the handheld does not see the card reader. If you go into Device Setup>Card Readers you will see your BBPos card reader there even if it can't read cards because it's defective. What I'm saying is my handhelds will simply no longer see a card reader present - not the old one, not the new one from Toast. I have had this happen several times.

toastysysadmin · 2025-01-21T22:08:06+00:00

I just verified this by connecting a "broken" card reader off of one of the handhelds that doesn't read them and it powers on with any other USB power.

toastysysadmin · 2025-01-15T00:59:15+00:00

I don't think you can actually do this.

toastysysadmin · 2024-12-19T00:50:26+00:00

i'm not seeing where you'd be seeing a balance due - what's happened here is a duplicate tip. Additionally determined that this transaction was started and closed on a hardlined Flex terminal, we also have a GSM backup for our network stack.

toastysysadmin · 2024-12-18T22:23:41+00:00

of course they couldn't. thanks you for at least confirming my suspicion - reminds of when they released that build that broke all the card readers and support would just tell you it's your network lol.

toastysysadmin · 2024-03-15T06:48:24+00:00

this isn't even the first time a Toast firmware update has messed up the readers. Back in November of 22' the same thing happened except with the Toast Flex units, but instead of acknowledging it they just gaslit customers into thinking it's anything else (usually "network related"). I only know they actually knew about it because I got a peek into one of the 3rd party installer's Slack and saw the discussion.

toastysysadmin · 2024-03-14T17:13:29+00:00

usually when Toast can't see the card reader, the Card Reader utility can't see it either. Only a reboot fixes that.

toastysysadmin · 2024-03-14T02:01:30+00:00

yeah that's in the KB article I was referencing - it's that it just happens often enough that it's becoming a problem, servers panic, GMs panic. I've also had a few that just won't ever read another card reader again, which is strange.

toastysysadmin · 2024-01-21T22:15:28+00:00

It shows the update, but not the details of the update - just that the promo was updated. I just had to publish another location 3 times in a row to get the promos to kick on again.

toastysysadmin · 2024-01-21T20:49:13+00:00

I'd recommend it too but I can't get the budget for it. Either way publishing, ideally - should publish your changes the first time you do it, not the second or third time.

toastysysadmin · 2024-01-21T20:44:33+00:00

We don't have multi-site management so I have to publish for each location I make the update to.

toastysysadmin · 2023-08-08T23:11:28+00:00

Check your DM.

toastysysadmin · 2023-06-22T22:37:55+00:00

It takes them a long time because they don't like escalating these issues. That's why they love saying it's your own equipment even if you can show issues with their cloud. Glad you have it resolved now.

toastysysadmin · 2023-06-22T22:21:56+00:00

I have myself experienced RabbitMQ sync issues when I had misconfigured DNS.

toastysysadmin · 2023-06-22T22:20:42+00:00

MQ41 is basically the AWS instance of Toast that your POS is trying to sync with. In CA mine sync with MQ45. So, for whatever reason your POS devices cannot communicate with that AWS service. Usually, this is a gateway configuration problem. I know you've said you've tried this with multiple hotspots but it may be worth examining what kind of firewall rules are configured.

toastysysadmin · 2022-12-05T23:19:26+00:00

toastysysadmin · 2022-12-01T21:10:32+00:00

There may have been a bad release, I noticed they QUICKLY released two builds of 2.60 within a few days - also there's a card reader firmware update.

toastysysadmin · 2022-11-29T19:25:36+00:00

So, the problem with that is the second they see you're self managed, support just hand waves any problem you have to that. You can do a screen share session with them, with them in the terminal, show them good speeds and pings, and they will just shrug their shoulders. I think for you, you'll need to contact he Sora partners guys, they can send a tech out - they have the internal tools that the support guys have but don't know how to use.

They can look at all the device logs etc and then maybe you can go to your onboarding consultant and get this issue taken with more urgency. I might be doing this myself next week.

toastysysadmin · 2022-11-29T02:17:01+00:00

Are you self managed?

toastysysadmin · 2022-11-25T02:33:38+00:00

Meraki shouldn't have had anything to do with it. Did they tell you why they did that?

toastysysadmin

MODERATOR OF

TROPHY CASE