I've so far found it most helpful to do things I'm less skilled at. "Put some Windows Forms crap over this Powershell for people who don't CLI". Versus arguing with it about hallucinating or pulling old MS documentation from 3 years ago about which cmdlets are valid in 2026

Obviously the goal here was to optimize the *Rust* cmdlets compiled to .NET in hope of coming close to the .NET native ones, and the lazy way to optimize is to avoid doing the hard thing, which is to optimize how the Rust code compiles to MSIL and is bridged with .NET APIs

For instance, I have an experimental Rust to .NET compiler tool chain, and one sample is a Rust equivalent of ConvertTo/From-Json cmdlets wrapping a Rust crate for JSON. I asked it to optimize the cmdlets, and it proceeded to drop the Rust crate to use the built-in .NET JSON APIs

Not sure if you have seen my other tweets, but build 29610 does introduce some more cmdlets that are a direct replacement for slmgr

Build 29610 introduces new cmdlets for getting and setting the OS License. Which I assume is for moving away from slmgr.vbs

It might just be for compatability reasons as Secure KMS has been added in various areas around the system, including the new cmdlets

Guide COMPLET pour lister, installer, réinstaller et désinstaller des applications avec PowerShell, gérer les applications Appx, supprimer plusieurs applications en une seule opération et résoudre les erreurs les plus fréquentes liées aux cmdlets Appx. malekal.com/powershell-insta…

Watch it Wednesday ▶️ 🧠 Okta Admins: PowerShell is your friend when managing federation with Microsoft Office 365! 💡 Master the cmdlets you need to disable manual federation and streamline your identity management workflow. Watch now: bit.ly/4urkxP8

That is not a PowerShell module 😉 but seriously, you're just calling the .NET APIs directly from #PowerShell with no cmdlets to wrap things and make it more ergonomic or discoverable for scripting?

I found that the new Get-BrokerMachineV2 doesn't work with -MaxRecordCount greater than 1000. It is an Int32, so it should work, as all the other Citrix cmdlets do, with the maximum Int32 value of 2147483647, but it does not. [DBG]: PS C:\CVADScript>> [string[]]$propertiesWanted = @('DnsName') <snip a lot of testing> [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1500 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1250 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1125 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1060 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1030 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1020 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1010 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1001 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines [DBG]: PS C:\CVADScript>> $Machines = @(Get-BrokerMachineV2 -ea 0 -adminaddress "LocalHost" -MaxRecordCOunt 1000 -CatalogName $Catalog.Name -SortBy DNSName -Property $propertiesWanted) [DBG]: PS C:\CVADScript>> $machines DnsName ------- testvm01.webstertest.lab [DBG]: PS C:\CVADScript>>

Most devs still treat them like interchangeable shells; PowerShell's object pipeline and built in cmdlets alone make it worth a quick read.

I'm used to having to rely on curl and raw http / POST / GET / etc. calls in Microsoft hell but that's just because the Graph API sucks shit through a PVC pipe with broken cmdlets and broken documentation and constantly deprecating modules and on and on. Anyway my assumption was just everyone is going with curl calling .sh files for installation just to avoid having to think at all about package management across a huge sprawl of environments 🤷🏻‍♂️ also in general in the 2020s the craftsmanship from software dev is dead. This isn't like the 00s when you were expected to supply an entire library and extensive documentation and a wiki for everything you shipped.

Absolutely agree! PowerShell is pretty slick, i've heard...most Windows Sysadmins and Developers, people built their utilities around its concept of Cmdlets...they said it embraced the philosophy of "tiny tools that can be chained to perform larger tasks" from the Unix sphere. My point is that it's great that they ported coreutils to Windows. But it still doesn't fix the larger point about that Windows uses a completely different filesystem layout, pathname conventions, environment variables, permission scheme, etc....and unless it fully embraces the POSIX standard, there's always going to be differences...so what is this Windows coreutils actually trying to solve? Looks like a case of Microslop throwing the baby with the bath water to me...or maybe I'm missing something? 🤷🏻‍♂️

Intelligent Terminal for Windows seems really cool, I would love a small local agent that could tell me what cmdlets I was messing up without using any tokens.