#powershell7 — Public Fediverse posts

🚀 Still stuck on PowerShell 5.1? At #PSConfEU 2025, @[email protected] shared real-world guidance on moving to PowerShell 7.4 — even with Intune, ConfigMgr & PE in the mix. 🎟️ Early bird 2026 tickets → psconf.eu #PowerShell #Migration #ITPro #PowerShell7

- YouTube

Estoy contento porque la gente se baja mi package #PowerShell7 y empezó como una prueba porque el interfaz gráfico de #windows no deja editar #windowspath de más de 2047 caracteres...

https://www.powershellgallery.com/packages/WinPath-Clean/0.3.1

Estoy aprendiendo mucho la verdad y lo de los test me sigue pareciendo súpercomplicado 😅

🚀 Still stuck on PowerShell 5.1? At #PSConfEU 2025, @niehaus.bsky.social shared real-world guidance on moving to PowerShell 7.4 — even with Intune, ConfigMgr & PE in the mix. 🎟️ Early bird 2026 tickets → psconf.eu #PowerShell #Migration #ITPro #PowerShell7

- YouTube

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

I also finished work on my #powershell book. Covers using #powershell7 and #WindowsServer2022 . Even shows how to use #pwsh to manage WSUS!

4/4

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 ( @[email protected] ): 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

#PowerShell7 #DFIR #eventlogs #logging #artifacts

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

#powershell7 #powershellscripting

@cl alternatively, in #PowerShell7 change the value of $PSSessionConfigurationName to be a #PowerShell 7 one.
LIke this:

@cl
1. Determine #PowerShell7 Endpoints:
Enable-PSRemoting # to be safe
Get-PSSession Configuration
This gets you the endpoint names for #PowerShell 7 sessions. you should see two!

2. Then create tne New-PSSession using the Configuration Name parameter.

Looks like this:

@mondskiez The worst thing is that all of those choices are antiques. 😉 #powershell7

@bjompen @JeffHicks #powershell or #powershell7 works...

@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