Remote profile

Never V2V a domain controller. Converting a DC's disk risks USN rollback, and the only recovery from that is rebuilding the domain.

What I did instead when moving off Hyper-V was a leapfrog:
1. Move all 5 FSMO roles to DC2
2. Delete DC1, build fresh on Proxmox, promote, let AD replicate
3. Move the roles to the new DC1
4. Repeat for DC2

Run repadmin /showrepl after every step. Both DCs moved with no downtime.

The writeup covers the rest: Linux V2V, DFS ripped out for GPO drive maps, UniFi moved into an LXC, SCCM swapped for FOG, and the Wazuh/Cortex/TheHive/MISP stack. 4 standalone hosts plus a 6-node cluster. Hypervisor licensing: $0.

https://solomonneas.dev/blog/hyperv-to-proxmox-migration-guide

#HomeLab #Proxmox #SysAdmin

If you're not running routine security reviews of your PRs, you need to rethink your workflow. Use more than one model to review work and propose fixes.

Opus 5.5, Daybreak Blue, and GLM 5.3 are all excellent to use in tandem. Time to update your AGENTS.md.

Give each model a clear scope, ask for concrete failure cases and fixes, then verify the fixes before merging. Opus 5.5 is great for correctness and if you don't have access to Daybreak Blue, request it, and use GLM 5.3 in the meantime.

#InfoSec #AppSec #AISecurity

#introduction, round two. I'm Solomon: retired chef, network and systems engineer, CySA+, finishing an M.S. in cybersecurity at USF.

I build Brigade, open-source tooling that keeps AI coding agents honest: verified runs with signed exit codes, a code graph agents check before editing, and an evidence log of what they did. I also run a homelab SOC on Wazuh, TheHive, and MISP.

Here for blue team, agent security, and homelabs.

https://brigade.tools

#infosec #blueteam #aisecurity #homelab