u/Fatel28

We only label laptops. Asset ID is the service tag / serial number. Using anything else is a little silly and will just be arbitrary. Our labels aren't automatically when a tech images a machine (it's part of the imaging process). They have a barcode on them with the serial, but we've never used it. It's there if we need it though.

Labels primary purpose is to have our support number/email on it so users know who to call. Machine name, customer, and serial are just nice to haves.

That's the tool for it. Just export their browser passwords first if they care about those. They'll be invalidated. Otherwise you should have few issues other than your standard Microsoft sign in annoyances with office apps.

BCDR strategy is updating the resume and finding another job (and probably a lawyer)

You can only positively reinforce the model. You can't say "this is not Jim" only "this is Jim"

I had an issue where my partner was constantly being misidentified (or rather, random people were being identified as my partner) and I could not figure out why. Turned out I had a couple blurry ass images in the examples and it made it think any blurry face with glasses was her. I have less than 15 images for both of us and the hit rate is almost 100%. Never had a false positive, only false negatives on rare occasions

Wait for someone to get comped because of an external call and use it. Never waste an emergency.

External meetings continue to function, we just block direct dms and calls. There is a whitelist option to re allow an org to communicate

No we just block them via ninja. Crowdstrike and it's SIEM also does a good job at catching unusual remote access tools and odd behavior.

Weve blocked quickassist and external teams calls/chats. Seems like most impersonation attempts involve one of those two.

We also have avanan set to alert on mail bombs, which is another common vector in those scams (among several others)

That's nuts. We have 5 figure spend and have had the same TAM for about 3 years now. They even offered to send us to reinvent for free this year

Might take that up with your TAM. I have not had this experience

Also production is down and this is a huge deal I have critical systems running with customers

What? Support plan? No I don't have one. Need help asap.

Yes it's very easy. You can get it from Amazon artifact once logged into an AWS account

Bedrock Agentcore Runtime is your friend, as is CDK. You can use an entra app proxy to handle the auth for you to go easy mode.

We did it on Amazon bedrock but not azure

Ntmk. My opinion and recommendation for the solution is that it's good for lob apps that you just want to access quickly in the browser, but require a whole desktop environment. In those situations multi monitor isn't really what you want. E.g, QuickBooks desktop, sage, nav etc

You can do it with one server. Install all the necessary roles on the one. Then it can be the gateway to either itself (if you want it to be your jump box) or to any other server on the network

This is the answer. Put it behind an entra app proxy for web RDP protected by MFA.

Most likely wasn't even AI lol

I'm of the opposite opinion. We prefer people just call. Can fix the issue right then and there. Our first call close rate is in the 90+% rate. Tickets are for less urgent issues.

Our workflow is built around it and its VERY frequently one of the first things customers mention after switching to us. They hate tickets. Tickets are for us (the msp) not so much the user. We have a system that transcribes every call and makes it into a ticket for our own tracking.

AI has it's place, we use it extensively internally to improve technician productivity and automate a lot of our monotony, but a hard rule we have is that it NEVER interacts with the customer directly. That's not what they pay us for. Customers want to call or make a ticket, and have a human help them with their problem.

We just have ours say a generic after hours message with a button for emergency calls to leave a VM. Voicemails left go to opegenie which pings the on call tech. No AI needed.

No, we like our customers and they like us

If this is your approach to false positives, I don't recommend you resell ANY dns filtering products. Your expectations do not match reality. Whitelisting IS the answer, and expecting immediate reclassification from support is not realistic. For all you know the site WAS parked for a very long time and now isn't, it'll just take some time to get reindexed.

False positives will happen on any filtering product. That's what whitelisting is for. The fact that you don't want to go click some buttons a few times for each client, and instead want to spend the time and energy fighting dnsfilter is.. odd. You're doing more work and directly holding up your clients as a result.

Your complaints about the AI support are valid (though, I'm kind of glad lifting a global categorization isn't as simple as contacting AI support), your method of dealing with it is questionable.

I think it was both 10dlc and also just getting the account out of sandbox for sending to any number.

If you only want to send to verified numbers, I think you can do something much easier. We needed the flexibility of changing numbers on the fly so we did the whole production access setup.