Good timing to bring attention to this. The June 2026 deadline is closer than many environments think, and a lot of estates still don’t have clear visibility of their Secure Boot chain state.
🚨 The 2011 Secure Boot chain is running out of time. Ignore it and your fleet slides into a no‑updates boot posture — quietly, then suddenly.
Start with Part 1: Building the inventory, creating the visibility...
➡️ Secure Boot 2023 CA Certificate Update Rollout — Part 1
https://lnkd.in/g25UjZbj#Intune#MicrosoftIntune#SecureBoot#Windows11#UEFI
真的是最後一刻才更新 XD
Add Microsoft Option ROM UEFI CA 2023.
(Note) DB is not updated automatically. It is required to perform “Restore Factory Keys” in Secure Boot menu in ThinkPad Setup. BitLocker Encryption must be suspended/disabled before performing “Restore Factory Keys”
(Note) Certificate “Microsoft Option ROM UEFI CA 2023” is added to DB only when “Allow Microsoft 3rd Party UEFI CA” is set to On.
Issue Date 2025/03/09
https://lnkd.in/gNeGPB3v
This is a topic many environments are still underestimating. The Secure Boot certificate transition will require proper visibility and planning across the fleet.
How many organizations here have already started assessing their readiness?
5× Microsoft MVP · Enterprise Endpoint Architect · Managing 70K+ devices with Intune, Entra ID & Zero Trust · Author at joymalya.com
🚨 The 2011 Secure Boot chain is running out of time. Ignore it and your fleet slides into a no‑updates boot posture — quietly, then suddenly.
𝙿̶𝚊̶𝚛̶𝚝̶ ̶𝟷̶:̶ ̶𝙱̶𝚞̶𝚒̶𝚕̶𝚍̶𝚒̶𝚗̶𝚐̶ ̶𝚝̶𝚑̶𝚎̶ ̶𝚒̶𝚗̶𝚟̶𝚎̶𝚗̶𝚝̶𝚘̶𝚛̶𝚢̶,̶ ̶𝚌̶𝚛̶𝚎̶𝚊̶𝚝̶𝚒̶𝚗̶𝚐̶ ̶𝚝̶𝚑̶𝚎̶ ̶𝚟̶𝚒̶𝚜̶𝚒̶𝚋̶𝚒̶𝚕̶𝚒̶𝚝̶𝚢̶…̶
𝗣𝗮𝗿𝘁 𝟮: 𝗪𝗲 𝗴𝗼 𝗳𝗿𝗼𝗺 𝗩𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 → 𝘁𝗼 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻
Whether you 𝐦𝐚𝐧𝐚𝐠𝐞 𝟓𝟎 𝐝𝐞𝐯𝐢𝐜𝐞𝐬 𝐨𝐫 𝟓𝟎,𝟎𝟎𝟎…
Whether your estate is modern, ancient, or held together by BIOS updates from 2014…
This 𝗣𝗮𝗿𝘁 𝟮 post will 𝐡𝐞𝐥𝐩 𝐲𝐨𝐮 𝐭𝐫𝐢𝐠𝐠𝐞𝐫 𝐭𝐡𝐞 𝐒𝐞𝐜𝐮𝐫𝐞 𝐁𝐨𝐨𝐭 𝟐𝟎𝟐𝟑 𝐭𝐫𝐚𝐧𝐬𝐢𝐭𝐢𝐨𝐧 intentionally — not accidentally, and definitely not blindly.
➡️ Secure Boot 2023 CA Certificate Update Rollout — Part 2
https://lnkd.in/gbUgKhCh#Intune#MicrosoftIntune#SecureBoot#Windows11#UEFI
Today I had fun converting a drive volume from NTFS to ReFS.
It’s not a direct conversion unfortunately. Lots of moving data, drive shrinking, more data moving, formatting and… yep you guessed it… more data moving again (plus a few other steps here and there for data/uptime safety).
Once the primary partition was ReFS it was just a matter of moving data away from temp partitions, before expanding the drive to its original size again (like nothing had happened!).
Goal is to avoid data loss and/or downtime by using ReFS which self heals unlike NTFS.
It’s always a pain when a file needing chkdsk to fix something is locked and repairs can only be preformed during OS boot or the whole drive volume needs to be offline status inside the Windows OS (aka only the OS has access to the drive). This change should save us time and money while also protecting our data.
I will monitor for 1-2months before more rollouts of ReFS.
Personally I’m looking forward to Microsoft adding support for ReFS being supported on Windows Boot drive (I have seen screenshots of Win11 with this support for this from insider builds). ReFS = SoonTM ;)
#Convert#NTFS#ReFS
10,000 MCP servers.
18 months ago this protocol barely existed.
Today it's the connective tissue of the agent ecosystem.
But here's what actually matters:
Anthropic, OpenAI, and Block — direct competitors — all moved agent infrastructure into the Linux Foundation.
Together.
That's bigger than a partnership headline.
It signals the industry wants a common foundation.
The internet scaled because TCP/IP and HTTP became invisible infrastructure.
MCP is that layer for AI agents.
The plumbing is being standardised right now.
And the builders who understand it early won't just move faster —
They'll see where the ecosystem is heading before it becomes obvious.
If you're building automation workflows in n8n or Make — MCP is the one thing worth understanding this month.
Where are you with MCP right now? 👇
#MCP#ModelContextProtocol#AIAgents#Automation#n8n#ArtificialIntelligence#BuildInPublic#AITools
⚙️ How to Recover Data from RAID 0, RAID 1 and RAID 5 on the Adaptec ASR-6405 Controller
Hardware RAID controllers are widely used in servers and workstations to provide high performance and reliable data storage. One of the popular solutions is the Adaptec ASR-6405 controller, which supports RAID 0, RAID 1, RAID 5 and other configurations. However, even reliable hardware can fail. Controller errors, damaged RAID configuration, or failed drives may lead to loss of access to important data.
https://lnkd.in/g2qGv5Jd
🎥 In this video, we show a step-by-step process of recovering data from RAID arrays created on the Adaptec ASR-6405 controller. You will learn how to access the disks, reconstruct RAID parameters, and restore files even if the array becomes unavailable.
🔎 In this video you will learn:
• how RAID arrays on Adaptec controllers store service information
• how to detect RAID parameters after a failure
• how to rebuild RAID 0, RAID 1 and RAID 5
• how to safely recover lost data
💡 This guide will be useful for system administrators, IT specialists, and anyone working with RAID storage systems.
💬 Have you ever experienced a RAID controller failure? What was the most difficult part of recovering the data?
#DataRecovery#RAID#Adaptec#RAIDRecovery#Storage#ITInfrastructure#SysAdmin#DataProtection
Many people asked me how I started my F5 home lab.
So here is my simple setup 👇
I am using:
• VMware Workstation (for virtualization) 💻
• F5 BIG-IP Trial Version (Official Site) – 30 Days Free 🚀
• Basic laptop (8GB RAM — planning upgrade soon 🔧)
Steps I followed:
1. Installed VMware
2. Imported F5 BIG-IP image
3. Assigned management IP
4. Accessed via browser
Also, in my previous setup, I practiced automation for SNAT and basic configuration ⚙️🤖
That’s it. No complicated setup.
I am still learning, but practicing daily 👍
If you are starting in F5 / Networking, don’t wait for perfect setup. Start with what you have 💯
If you need help setting up, comment “LAB” — I’ll guide you 🤝
#F5#Networking#Automation#Homelab#Learning#CareerGrowth
Unlock the full potential of your storage management with Diskpart, the powerful command-line utility built right into Windows. While graphical tools are great, Diskpart offers a level of control that is essential for IT professionals and power users alike. Whether you're troubleshooting a "read-only" USB, converting partition styles between MBR and GPT for modern UEFI boots, or performing a clean wipe to reset a drive, this text-based tool is your go-to solution. By mastering a few core commands like select disk, clean, and create partition you can efficiently manage disks, partitions, and volumes even when the standard interface falls short. At #LvTS, we specialize in these advanced system optimizations to ensure your hardware is configured for peak performance and reliability. Remember, with great power comes great responsibility, always run list disk first to verify your selection, as these commands are irreversible!
#Windows10#Windows11#Diskpart#ITSupport#TechTips#StorageManagement#LvTS#SysAdmin#TechSolutions#ComputerRepair#fiji#laptoprepair
My SSD was failing — and still showed "Good (98%)".
My ThinkPad started blue-screening. At first it felt random — until CrystalDiskInfo told the real story:
15 media errors.
732 by the end of the day.
Health status? “Good — 98%.”
The SSD had only written 39TB — about 8% of its 480TB rated endurance.
This wasn’t wear. It was failure — and the health indicator didn’t care.
I focused on saving what mattered first:
- Checked 60+ repos for uncommitted work
- Dumped databases
- Backed up SSH keys and secrets
- Exported Docker volumes
All while writing restore steps between crashes, knowing any reboot could be the last.
When it came time to rebuild, I looked at my setup notes.
Half of it was workarounds:
- Portproxy scripts just to make SSH work
- Syncing Windows hosts files
- Docker Desktop sitting in between everything
- Fixing IPs every time WSL restarted
I’d accepted all that friction as “normal.”
But every tool I use runs on Linux anyway.
So I stopped compromising.
New SSD went in. Ubuntu went on.
No Windows. No WSL. No workarounds.
I booted the old drive one last time.
25,343 media errors.
Health status: “Good — 98%.”
Two takeaways:
- Don’t trust the headline number — check what it’s hiding
- Sometimes it takes losing your setup to realise how much of it was never necessary
The hardest part of building an MCP server isn’t the code.
It’s deciding the boundary.
One domain > One responsibility > Stateless tools.
If your MCP server needs a README longer than a page, it’s doing too much.
#MCP#AITooling#SoftwareArchitecture