Az.ContainerRegistry Azure PowerShell module wasn't fully featured. Sometimes, PowerShell users had to take advantage of the Az CLI. We want to allow PowerShell user to be able to fully manage container images. Starting with Az.ContainerRegistry version 2.2.1, we will gradually be rolling out new cmdlets and new parameters. In this release, you can now fully manage (Get-, Remove-, Update-) repositories, manifests, and tags with increased performance.

to version 1.8 and moves Windows Terminal to version 1.7. Both builds can be installed from the Microsoft Store as well as the GitHub releases page. Let's jump into what's new!

inside networks managed by a Windows DHCP server. The process is pr etty straight forward - Add a vendor class, add the option, and set it to the correct IP address. Unfortunately, that of course means a lot of clicking in the DHCP console on each Windows Server he manages....

shop but, like most enterprises these days, they have some apps and business units which use AWS. As I documented what I already knew and researched what I didn't, I was (once again) blown away by the capabilities of this massive cloud-scale network file system....

PowerShell and PowerShell 7. Sometimes I'm in a session with a loaded profile, sometimes not. Sometimes I have a PowerShell 7 Preview session running. And then there are the scheduled jobs which also run PowerShell. Over the years, I've written a number of variations of a PowerShell script or function to discover all of the running PowerShell sessions on my computer. But I think I have finally written the final version of a PowerShell process detection tool.

export a VM from your development workstation to a Hyper-V host in production? If so, you've come to the right place!...

session with customers that highlighted a problem.  If any of us change the local admin password of the servers or redeploys the environment with a password of their own.  We no longer can access it without contacting the group and request the new password....

on disk.

Client for PowerShell!

Enough Administration scenarios.

for a customer. For me these scenario's always go into scripting or templates. That means for every change I want to be redeploy the environment and see if everything is still working. For that I need random names. You could pick a name, add a number and up the number for every new deployment but, where's the fun in that?