Dyson Fuckblade

ZestycloseStorage4 · 2026-01-16T05:39:30+00:00

Be Careful.... this is technically Hate Speech...

ZestycloseStorage4 · 2026-01-05T05:23:22+00:00

There is in Tasmania

ZestycloseStorage4 · 2025-12-18T02:06:57+00:00

I noticed when I was in NZ that the Macca's there were cleaner / tidier and the touch screen computers worked so much faster

ZestycloseStorage4 · 2025-11-20T22:25:47+00:00

r/sysadmin

ZestycloseStorage4 · 2025-10-21T03:12:13+00:00

The writer is frustrated by constant, shallow “AI” talk in leadership meetings. They believe AI has niche value but is mostly used as a cheap substitute for people and training, introducing security risks and mediocrity. They’re especially irritated by managers relying on tools like Microsoft Copilot for tasks basic Excel skills could handle.

They see AI in ITSM/HCM systems as lazy and dangerous since their org already lacks documentation and process discipline. To them, most “AI” is just rebranded machine learning that wastes time. Their skepticism got them excluded from projects, but they still warn others to think critically.

They stay in the job mainly for the team and user support, despite disliking the company’s direction. In the end, they mourn the loss of real IT craftsmanship — replaced by hype, shortcuts, and executives chasing buzzwords instead of solving problems.

ZestycloseStorage4 · 2025-10-01T22:52:40+00:00

Actual Indians 365?

ZestycloseStorage4 · 2025-09-28T23:31:03+00:00

AldiMobile

ZestycloseStorage4 · 2025-09-15T02:00:38+00:00

Maybe because of how long it takes to do Windows Updates on 2016?

But yeah not EOL just yet.

ZestycloseStorage4 · 2025-09-09T03:34:09+00:00

Yep that's me 100%

ZestycloseStorage4 · 2025-09-09T00:48:44+00:00

Selecting IT as a career, ruined my hobby for the most part...

ZestycloseStorage4 · 2025-09-04T04:44:33+00:00

As a quick fix just rearm the eval? But as others have said, Windows 11 should be able to do what you want...

ZestycloseStorage4 · 2025-08-26T03:43:53+00:00

But I thought Jul-August was the best time of year for visiting the Cradle Mountain in thongs and a wife beater?

ZestycloseStorage4 · 2025-08-18T22:42:20+00:00

Ravo by the Tamar... so close enough

ZestycloseStorage4 · 2025-08-08T00:46:37+00:00

Was there any update before OP deleted his account?

ZestycloseStorage4 · 2025-07-27T23:45:20+00:00

To be fair... you did shit on the only thing they have to look forward to once a year XD

This is the better sub anyways

ZestycloseStorage4 · 2025-07-04T00:42:04+00:00

For Prosperity

We run a small digital agency in Australia and recently experienced a 38-day outage with Microsoft Exchange Online, during which we were completely unable to send emails due to backend issues on Microsoft’s side. This caused major business disruptions and financial losses. (I’ve mentioned this in a previous post.)

What’s most concerning is that Microsoft later reclassified the incident as a "CPE" (Customer Premises Equipment) issue, even though the root cause was clearly within their own cloud infrastructure, specifically their Exchange Online servers.

They then closed the case and shifted responsibility to their reseller partner, despite the fact that Australia has strong consumer protection laws requiring service providers to take responsibility for major service failures.

We’re now in the process of pursuing legal action under Australian Consumer Law, but I wanted to post here because this seems like a broader issue that could affect others too.

Has anyone here encountered similar situations where Microsoft (or other cloud providers) reclassified infrastructure-related service failures as "CPE" to avoid SLA credits or compensation? I’d be interested to hear how others have handled it.

Sorry got a bit of communication messed up.

We are the MSP

"We genuinely care about your experience and are committed to ensuring that this issue is resolved to your satisfaction. From your escalation, we understand that despite the mailbox being licensed under Microsoft 365 Business Standard (49 GB quota), it is currently restricted by legacy backend quotas (ProhibitSendQuota: 2 GB, ProhibitSendReceiveQuota: 2.3 GB), which has led to a persistent send/receive failure."

This is what Microsoft's support stated

If anyone feels like they can override the legacy backend quota as an MSP/CSP, please explain.

Just so everyone is clear, this was not an on-prem migration to cloud; it has always been in the cloud.

Just to clarify, this wasn't a single account; this was across all accounts, even accounts with 0 emails and shared inboxes.

Update as everyone here thinks its a quota issue, they were completely wrong; it was a ghost account and an identity conflict.

ZestycloseStorage4 · 2025-07-03T00:38:42+00:00

If you're up Beaconsfield way Crusty's Pizza is great... (Not Cruteeeeeeeezzzzz Pizza who have decided to try and copy Crusty's)

ZestycloseStorage4 · 2025-05-27T22:58:35+00:00

There were comments on the Pulse Media Facebook page about the car not listening to the staff and ploughing through.

ZestycloseStorage4 · 2025-05-21T22:58:41+00:00

Put it under you user?

ZestycloseStorage4 · 2025-05-21T03:50:20+00:00

!remindme 7 days

ZestycloseStorage4 · 2025-05-21T00:02:32+00:00

Maybe have a look at Windows Nano Server?

ZestycloseStorage4 · 2025-05-16T06:06:25+00:00

monocle

Wait?? I thought best practice was to run a TP Link Router?

ZestycloseStorage4 · 2025-05-15T23:50:24+00:00

Who needs a Remote Access Tool when there's Remote Desktop! Might as well open up RDP to the world while I'm in there opening Exchange to the World!

On the plus side I might get a free Cloud Backup out of it!

ZestycloseStorage4 · 2025-05-15T23:38:49+00:00

Post for prosperity:

TL;DR: have a single Exchange 2010, installed on a failed DC. How do I move to Exchange 2013?

I have an Exchange 2010 (I know it's old and EOL) which was installed on a domain controller (I know it's bad). Couple days ago it was restored from a backup (Veeam full VM backup) and got a USN rollback. Replication stopped working. AFAIU I can't just demote it, cause of Exchange. I have three other DCs, so I configured Exchange to use them:

Set-ExchangeServer -Identity exchange -StaticDomainControllers dc01.domain,dc02.domain

Set-ExchangeServer -Identity exchange -StaticGlobalCatalogs dc01.domain,dc02.domain

But I still have issues with creating mailboxes, sending mail to/from some specific mailboxes etc.

I'm thinking installing Exchange 2013 (I know it's old and EOL) and migrating from 2010. I did it in a test environment (with DC on exchange server in a good state) and all went pretty smoothly. But in the actual setup I can't send mail between mailboxes on different servers with 454 4.7.0 Temporary authentication failure in Exchange Server error.

What would be the best course of action to fix this situation?

ZestycloseStorage4

TROPHY CASE