Ha! Received my new gaming rig, installed Fedora and was immediately thankful for past me documenting kernel module signing: https://janhendrikpeters.de/en/post/obs-virtual-camera-secure-boot/
At that time to sign the v4l2 module, but today the old post helped me once again in signing the Nvidia modules. For some reason - which I did not care to troubleshoot longer than necessary - the documented akmods procedure did not work. Or rather: Did not sign the modules with the enrolled key.

Anyone who had their first experience with computers in the 80s often did so on a Commodore 64. The nostalgia of turning on the blue screen lasts to this day. That is why I have adapted my PowerShell environment so that it looks like a C64. How you can customize your shell as well I described here. Have fun with it.

https://blog.greenbrain.de/2023/03/the-retro-terminal-looking-good-in-8.html

Do you run PowerShell Core in production?
#powershell #PowerShell7

So my latest PowerShell book is actually published:
https://tfl09.blogspot.com/2023/02/my-latest-last-powershell-book-is.html

Still looking for reviewers
#PowerShell
#PowerShell7

Got #PowerShell 7 and not seeing event logs in your triage? N.B. for PowerShell 7: Windows PowerShell logs events to "Microsoft-Windows-PowerShell/Operational"), but PowerShell 7 now logs events to "PowerShellCore/Operational." Detailed (e.g., Script Block) logging is NOT enabled by default.

PowerShell 7 includes Group Policy templates and an installation script in $PSHOME. Specifically, you can use the "RegisterManifest.ps1" and "InstallPSCorePolicyDefinitions.ps1" scripts in the PS7 installation directory to enable logging.

Also, ISE doesn't support PS7 :( --> but there is an official Visual Studio Code extension that does, and it even has an "ISE Mode."

H/T Nasreddine Bencherchali ( @nas_bench@twitter.com ): https://twitter.com/nas_bench/status/1616211194934882304

I also consulted https://learn.microsoft.com/en-us/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.3

How often are you using classes instead of pscustomobjects in #powershell?

For me, using classes, you have better control over your data.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_classes?view=powershell-7.3

@shwalsh13 Hardest ch was the last. Trying to manage #WSUS in #PowerShell 7. The WSUS team could not have shipped such a ore Powershell unfriendly module and object model if that was their aim. Even the RSAT tool feature name is different to ALL the rest. And I suspect MSFT will never revise it to use more modern protocol and support #.NET. Still with #Powershell7 there are ways around this

#PowerShell and #git just got a bit better:

Another version of ugit is out! https://github.com/StartAutomating/ugit

ugit updates git and lets it work well with the object Pipeline in #PowerShell7

New in this version:

Install-Module ugit -Scope CurrentUser -Force
Import-Module ugit
git diff | Select-Object -ExpandProperty File