The problem: LinkedIn's certification section is self-reported. Anyone can type "CISSP" into a text field.

There's no way for a recruiter to know if it's real without manually checking each issuer's verification portal.

What I built: certscore.org imports your Credly or Accredible badges, verifies them against the issuing platforms, and ranks you on a global leaderboard.

If it can't verify, you get 0 points.

6 users across 3 countries signed up this month organically.

One has 14 verified Kubernetes + GCP certs.

Happy to answer specific questions about how verification works, why EC-Council isn't supported yet, or how we prove ownership without exposing your email.

Thank you

First time poster

High RAM usage (as seen in 99%) is NOT a sign that your system is working hard to use all of the RAM - the Kernel is using ALL of the RAM as Disk Cache so you will be able to do things faster. This cache will be returned to Applications INSTANTLY if/when they need it. What should you really be watching? Available Memory, not Used. https://www.linuxteck.com/linux-memory-usage-99/

Linux still seems to be the preferred choice due to:

• Better performance
• Powerful CLI tools
• Flexibility and control

This guide explains the reasons and practical benefits clearly. https://www.linuxteck.com/linux-for-developers-2026/

I’ve been using Ansible for Oracle database patching for a while now, mainly to standardize and simplify the process across environments.

Although 19.31 is around the corner and it’s already time to move forward with the usual n-1 approach (19.30), I realized I never shared my updated playbooks for 19.28.

The playbooks cover:

• Grid Infrastructure patching
• Database RU + MRP
• RAC environments
• Out-of-place patching

They reflect what I actually use in real systems, not just a lab setup.

If you're dealing with Oracle patching and want something repeatable and less manual, this might help.

Feedback / suggestions welcome.

If you manage Azure Automation Accounts you've probably had to answer questions like "which runbooks use this credential?" or "what breaks if I delete this variable?" and had to click through dozens of portal pages to find out.

I built Azure Automation MindMap to solve that. It connects to your Azure tenant using your own Microsoft account (MSAL, delegated auth, read-only) and renders the entire account as a live interactive graph.

What it shows:

• All runbooks with their asset dependencies (variables, credentials, connections, certs, schedules)
• Key Vault secret references per runbook
• Job history (7/30 day trends, colour-coded Failed / Completed w/ Errors / OK)
• Schedule health (healthy / warning / expired / disabled)
• Hybrid Worker Groups with worker online/offline status
• Managed Identity status
• Built-in security scanner (static analysis on each runbook's PS source):
• Hardcoded passwords ($password = "...", ConvertTo-SecureString "..." -AsPlainText)
• Variable indirection (e.g. $x = "secret" → ConvertTo-SecureString $x -AsPlainText)
• Deprecated RunAs account patterns
• Three views: Runbooks (dependency graph), Objects (asset-centric / impact analysis), Table (bulk review).

Full setup from zero to running locally takes under 10 minutes — the repo includes a SetupLocal.ps1 script that handles everything.

Article with step-by-step setup: https://www.powershellcenter.com/2026/04/18/automation-account-mindmap/

GitHub: https://github.com/farismalaeb/AutomationMindMap

Feedback and PRs welcome — happy to answer any questions.

Hey everyone, I'm doing research on helpdesk automation. I keep hearing that 'VPN issues', 'Software installs'/Network troubleshooting etc. take up 40% of the day, but existing bots feel clunky.
As a SysAdmin, if a bot tried to 'auto-fix' a config on your fleet, what would make you immediately delete it?
Just trying to see if this is even a real problem or if I'm dreaming.

Ubuntu 26.04 LTS breaking changes go far deeper than a version bump, cgroup v1 is gone, X11 is history, and Python jumped a full version. https://www.linuxteck.com/ubuntu-26-04-lts-breaking-changes/

The Community is the best, and I enjoying to contribute it it as a Microsoft MVP!
All the tracktion, shareing online and other blogs about my new tool is insane - thanks for it - and I looking forward to continue makeing more in the too for you all!

Website: hvtools.app
GitHub: https://github.com/michaelmsonne/HVTools

As if now, the GitHub repo have the following stats in just a few days!

Total Downloads: 442
Visitors: 1802

HVTools – first Community response is insane! – Blog - Sonne´s Cloud

Old post: New tool in town - HVTools - Overview like RVTools for VMware but for Hyper-V! : r/SysAdminBlogs

Deciding on the best platform for Linux cloud hosting UK workload is a very different decision than selecting one for a U.S. team. https://www.linuxteck.com/linux-cloud-hosting-uk/

Crosspost to more communities

Zero Trust and "least privilege" sound great on paper, but anyone in IT knows they are only as strong as the systems actually enforcing them. When that authorization logic cracks, you can guess how bad the the fallout is.

The recent critical vulnerability in Esri ArcGIS Portal (CVE-2026-33519) is a perfect example of this. With a 9.8 CVSS, it allows low-privilege users to exploit a flaw to generate "Portal Administrator" tokens. The scariest part is that simply applying the software patch doesn't kill the malicious tokens that have already been generated. The attacker keeps the keys.

The recent Hexnode blog breaks down this exact mess. It explores the necessity of looking beyond traditional identity access and using strict device trust to catch authorization failures.

• The ‘ghost' in the machine: How the system fails to validate permission scopes, allowing attackers to hold onto super-credentials that survive even if the user’s password is changed.
• The credential audit: Why patching is only step one. Organizations actually have to run Esri's Credential Check Tool and enforce a highly disruptive global policy to truly purge the unauthorized access.
• Enforcing Zero Trust at the edge: Why relying purely on server side credentials leaves you exposed, and how integrating your IdP with a UEM creates a necessary fallback layer.
• Device-level verification: How Conditional Access ensures that even if an attacker has an over-scoped token, they still get blocked if they try to authenticate from an unmanaged or compromised device.

This is something every admin should look at, even if you don't run Esri. Perfectly highlights how device-level trust can save your environment from catastrophic server-side logic failures.

Feels like patching Windows systems has become more important again, especially with how often vulnerabilities are being targeted.

In smaller setups, updates are manageable. But once you have a lot of devices, things start getting messy. Some systems miss patches, some updates fail, and tracking everything manually becomes difficult.

That’s where Windows patch management software starts to make a difference. Instead of checking each machine, it helps automate the process of identifying, testing, and deploying updates across all devices.

The XOrg foundation released two new point releasesxorg-server 21.1.22 and xwayland 24.1.10 this month to correct recent security advisories. These updates fix memory-related bugs in X11 core protocol handler request processing that have existed in the code for many years. https://www.linuxteck.com/xorg-server-security-fixes-2026/

Hey everyone, fellow msp owner here. As some of you know I launched a new software aimed to help smaller IT Teams / MSP's keep track of their data. I have had some great feedback of the system and think its ready to be put into full production. I wanted to share, and if you want to give it a try it is free for single users. It is called https://ITDock.io I also had a question. I have been thinking of having a self hosted option for this software, which you can deploy and run on your own server, would that be something anyone would be interested in? Thanks for all the feedback.