Jérôme Bezet-Torres (#MVP x6 #MCT)

This thing always saves me troubleshooting time github.com/microsoft/play…

Renforcez la sécurité de Windows Server 2025 avec OSConfig it-connect.fr/windows-server…

PowerShell 7.6.0 released! Uses. NET 10 github.com/PowerShell/Pow…

WINDOWS SERVER 2025 GROUP POLICY UPDATES: Administrative Templates (.admx) for Windows Server 2025 (March 2026 release) microsoft.com/en-us/download… Group Policy Settings Reference Spreadsheet for Windows Server 2025 (March 2026 release) microsoft.com/en-us/download… HT: Abbodii on the PatchManagement.Org DL

CML, Cisco Packet Tracer, GNS3, EVE-NG : quel outil choisir pour vos labs réseau ? it-connect.fr/cml-cisco-pack…

I wish all Microsoft MVP’s a save travel to Redmond for the Global MVP Summit 2026 and Enjoy next week #mvpsummit with Awesome NDA sessions 👍🚀 #MVPBuzz #Azure #WindowsServer #Security #Copilot @azure @windowsserver @MVPAward

@mniehaus Done

Tomorrow/Wednesday, 12:00pm EDT, 16:00 GMT, still time to register. 🚨

Windows Server 2025 Native NVMe: Storage Stack Overhaul and Benchmark Results storagereview.com/review/windows…

CMTrace Open v0.4.0 is out. New: More DSRegCMD diagnostics rules, live endpoint connectivity testing, SCP queries, registry evidence collection, and event log analysis for Entra ID join troubleshooting. All running locally on your machine with zero telemetry. Open source, Rust + React, runs on Windows, macOS, and Linux. github.com/adamgell/cmtra…

Guess now it's official: M365 E7 "Frontier Suite" is coming. Poor @AaronDinnage of m365maps.com 😊 blogs.microsoft.com/blog/2026/03/0…

@_Flavien @awakecoding Yes

@JM2K69 @awakecoding On Linux ? 👽

What if you could script cross-platform desktop GUIs in #PowerShell using Avalonia UI instead of WinForms? AvaloniaUIShell just came out, and it's the real deal! Try it now: github.com/mdgrs-mei/Aval…

#SecureBoot needs to be update #CA_Microsoft_2023 #MVPBUZZ

How to properly boot a migrated Windows #vSphere VM in #Proxmox by @nolabnoparty nolabnoparty.com/en/how-to-prop…

3/4/26 ViaMonstra Academy - Updates and Q&A for ConfigMgr / OSD / Intune x.com/i/broadcasts/1…

Venez nombreux une session sur #DeployR pour découvrir ses possibilités dans le déploiement de système d'exploitation moderne. #Cloud #Onpremise #Hybride. #Mvpbuzz #NeverStopLearning.

In Active Directory, there is a method that’s been around for many years which changes the password last set date but not the actual password. This is what I call a “fake password change” since the account appears to have a recent password when scanning for old passwords based on password last set, but the underlying password hasn’t actually changed. I spoke about this in my 2015 @BSidesCharm talk which was my first conference talk. More details including step-by-step screenshots are here: adsecurity.org/?p=4969 Why does this happen? There are times where service account (or admin accounts) need to have password changes, but someone doesn’t want to do the work to change them. The ability to fake a password change requires modify rights on the pwdLastSet attribute which provides the ability to check/uncheck the setting “User must change password at next logon”. This setting is enabled when you want the user to change their own password when they logon. How does this work? This is simple to do when you have rights on the target account (in this example the password last changed in August 2025). We open up Active Directory Users and Computers (ADUC), double-click on the target account to open up the account properties and then click on the Account tab. From here we check the box for “User must change password at next logon” and click Apply. The PasswordLastSet date is now blank. Which makes it seem like the account has never had a password set. We continue with our process where we uncheck the box for “User must change password at next logon” we checked and then click Apply. After performing this action, the password change date has now been set to the current date and time even though the password itself hasn’t been changed since August 2025. We have successfully faked a password change! Why does this happen? This happens because the “User must change password at next logon” option is used to force a user to change their password at next logon. With it checked, Active Directory is waiting for the user to attempt to logon which is when the user is directed to change their password. During this time the PasswordLastSet value is blank since it is waiting for a new password. Once the user changes their password, the checkbox is effectively removed and the current date and time are set for the user’s passwordlastset property (technically this is the “pwdlastset” attribute, but the AD PowerShell cmdlets use that property). An attacker could use this technique for an account with an old password they discover and have control of the account (with the ability to flip this bit). This would show that the password changed without it actually changing. Detect fake Active Directory password changes at scale I wrote a PowerShell script that will scan either the Active Directory Admins or All Users in the domain to see if there’s a fake password change that has been performed on them. github.com/PyroTek3/Activ…

Discovering PowerShell provider dynamic parameters oofhours.com/2026/03/03/dis…

📢 C'est avec plaisir que j'annonce la publication de la 2ᵉ édition de mon livre « Débuter avec PowerShell », co-écrit avec @JM2K69 et publié aux éditions ENI 👍 Avec 850 pages, ce guide complet est idéal pour débuter 📖 Version papier et en ligne 🔍 Disponible partout