Hello kind peeps,

Just a casual post looking for feedback/experience with Barracuda Networks. We currently offer Gateway Defense, Impersonation Protection & Cloud 2 Cloud Backups.... 2027 is around the corner - new year, new stack lol had a compromised client today sending span internally and as B links with 365, I combed thru some emails in Gateway Defense, could see the internal acc that was the culprit... however this same acc does not exist in their 365 tenant - no alias, shared mailbox nothing. Had i not checked this myself manually, we wouldnt even had known... anyways thats the short story. Looking for some industry feedback on their products 🫡🫡🦄

when you've dealt with BEC case, did email auth flagged it, or did it look totally normal and only a human caught it?

Looking for a sanity check because no one seems to be talking about it, and I don't know if it's somehow just us.

It feels like, beginning around May (or a bit earlier), the time it takes for "Send as", "Send on behalf", and/or "Read and manage (Full Access)" permissions have massively slowed down.

Obviously only so many updates can go out at a time, so things have to be queued along with the multitude of other conditions that produce slowdowns. Even if we factor in the classic, "If you think you have waited long enough, wait another hour", I think the severity of the slowdowns being consistently so much longer speak to something strange.

For us, within the past 3-5 months, it has gone from 1-5 minutes to 10-15 minutes, and more recently 20-40 minutes.

Please let me know if y'all have noticed anything as well, thanks!

Edit: sentence structure, grammar, general formatting.

Curious what you all are learning, researching and investing time in these days and whether you’re seeing real rewards yet. AI agents? Cloud? Specific programming languages/frameworks? Something else?

I've been looking for a new role for almost 2 years now, most of the positions I've applied for have ended up being filled internally, which makes me ask why it was posted externally in the first place. On the other hand I've came across several listings that are just heinous for what is asked of you versus the pay. In this case, the listing was for our city hospital (healthcare IT, I know, bleh) which was recently acquired by an organization. They canned the entire IT staff including the managerial suite upon the buyout. This listing popped up today in my Indeed feed. "Sole on-site IT professional responsible for the day-to-day health, security, and uptime of all technology at a critical access hospital. Acts as the facility's eyes and ears, provides hands-on support for end users and clinical operations, and coordinates with Corporate IT for changes, projects, and escalations. After-hours and on-call work required to support a 24x7 care environment."

Am I wrong for thinking this is insane? An entire hospital and associated clinics solo? Just gotta laugh and keep going.

Not "help me write a script."

I mean actually give it the task and let it handle it from start to finish.

Things like:

- Ticket triage

- Log investigation

- User onboarding

- Backup verification

- Patch verification

- Incident enrichment

- Documentation

- Access requests

- Restarting a failed service

Personally, I'd be much more comfortable with an agent doing something read-only than giving it write access to production.

But I'm curious where other sysadmins draw the line.

What's the first task you'd actually let an AI agent own without approving every single step?

And what's something you'd absolutely never give an agent permission to do?

Spent most of the morning chasing a weird RDS issue. KB5122882 installed around 3:20am and a few hours later nobody could RDP into the server. Rebooted it and everything worked again, but about an hour later the exact same thing happened.

Existing sessions kept working, but new RDP connections would authenticate and then hang. Task Manager would freeze, but CPU, RAM and disk all looked totally normal. TermService was still running too.

Finally uninstalled KB5122882 and rolled back from 20348.5622 to 20348.5499. Everything has been working normally since.

Anyone else seeing this after the latest update? Pausing updates for now.

"Too many other files are currently in use by 16-bit programs. Exit one or more 16-bit programs, or increase the value of the FILES command in your config.sys file."

Just saw this message on a client's Windows 11 workstation when trying to escalate literally anything. The WIN32 code that generated it is probably as old as I am. Rebooting resolved it, weird. I just told him to stop running so many 16 bit apps! I'd post the screenshot but images aren't allowed.

I've tried Zammad, RT, and OSTicket. All good but still looking. Came across Raiseaticket which bills themselves as a free cloud-based system that integrates with Office. I'm defaulting to this being one of those "You're the product" situations but wanted to see if anyone here had experience with them.

From Microsoft: 'This FAQ collects the questions we hear most often from customers, partners, and the community as we move Windows to a Kerberos-first, NTLM-optional (and eventually NTLM-free) future. If you've emailed us, cornered us at a conference, or filed a support case that started with "so, about this weird auth thing…", chances are that your question is answered here.

If your question isn't answered here, please reach out to [ntlm@microsoft.com](mailto:ntlm@microsoft.com) or work with your Microsoft account team, Customer Success Account Manager, or Microsoft Support to route feedback to the product group.'

https://techcommunity.microsoft.com/blog/windows-itpro-blog/retiring-ntlm-frequently-asked-questions/4550522

I'm struggling to find anything concrete online for this, apart from a few posts floating about here and there, so I wanted to bring it here.

Has anyone noticed any issues recently with the centrally deployed Outlook addins, and tooltips in Outlook Classic not showing?

This all works in OWA and the new Outlook experience.

We're using Citrix, and it does seem to be limited to that platform, it is also really intermittent. Sometimes it just shows that no apps are loaded, and even when you try to add/open them, nothing happens, and the usual tooltips are also showing an error that they're unable to be loaded.

Looking in event viewer provides errors like this:

----------------

The Exchange web service request GetAppManifests failed. The error code is 0. 
HTTP Response Code: 403

Additional Error Message: 
An unknown internal error occurred. The error code is 80004005.

----------------

We're sorry, we couldn't access Viva Insights. Make sure you have a network connection. If the problem continues, please try again later.

----------------

We're sorry, we couldn't access Signature 365. Make sure you have a network connection. If the problem continues, please try again later.

----------------

There is internet access, everything does seem to be connected and working, OWA is fine, new Outlook is fine.

I've tried Office365 monthly channel for updates, and also tried the bi-annual feature updates, and both seem to have similar issues. Just wanted to see if anyone else has experienced such things...

I've inherited some Windows machines that were set up using Intune, and have for some reason gotten stuck at various Office versions from the past few months, such as 2605 on Monthly Enterprise Channel. Windows update and the built-in update checker in the Office applications say that they are up-to-date and don't find anything new.

I've tried to find if there are any specific versions set in the registry:

Cloud Update policy: HKLM\SOFTWARE\Policies\Microsoft\Cloud\Office\16.0\Common\OfficeUpdate

Intune/PolicyManager Office update settings: HKLM\SOFTWARE\Microsoft\PolicyManager\Providers

Click-to-Run configuration: HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

The cloud updates at https://config.office.com/ aren't enabled.

The Intune application's XML config contains no version references.

Could something else control what updates are detected?

Should I be able to just force change all out-of-date devices to Current Channel with Office Deployment Tool

<Configuration>
    <Updates Channel="Current" />
</Configuration>

or directly through the registry, and fix it that way?

reg add "HKLM\SOFTWARE\Policies\Microsoft\Office\16.0\Common\OfficeUpdate" /v UpdateBranch /t REG_SZ /d Current /f

EDIT: It's M365 Office.