IT Support Blog — Tips, Guides and News from Zeeflex
Plain-English IT advice, written by the people who do the work
No vendor talking points and no filler. Every article answers a question we get asked on the phone, and every claim that can be checked links to the Government guidance or vendor documentation behind it.
The first articles are being written
In the meantime, the FAQ and the glossary answer most of what we get asked, and the phone is answered by an engineer.
What we write about
Everything here comes out of work we actually did. A technician hits a problem, works out the answer, and the answer gets written down so the next person does not have to pay for the same discovery. That is why the posts are specific — a particular Microsoft 365 setting, a particular scam doing the rounds in Tasmania, a particular reason a quote came out higher than the client expected.
Four subjects come up most:
- Security — what a threat looks like before it becomes an incident, written for the person who has to decide, not for a security engineer.
- Microsoft 365 — licensing, mail flow, backup and the settings Microsoft does not switch on for you.
- Costs — what IT work actually costs in Australia, and where the money usually goes to waste.
- Fixes and failures — including the recoveries that did not work. A blog with no failures in it is a brochure.
How it is published
Posts go up when there is something worth saying — usually once or twice a month, and always written by the person who did the work.
If you would rather receive this by email, the newsletter archive shows exactly what gets sent and how often. Nothing is gated, there is no lead-capture form in front of an article, and no advertising.
Spotted something out of date? Tell us and we will correct it — a wrong article is worse than no article, and we would rather fix it than quietly leave it up.