This is another old WMI function I have rewritten to use CIM instead. This one queries computers for memory information.
in PowerShell
This is another old WMI function I have rewritten to use CIM instead. This one queries computers for memory information.
RichardImenes.com
Share what I know or discovered when working with Windows PowerShell.
C#, Game Design, Performant Programming, .NET, Vulkan, Multithreading
Scripting | Automation | Efficiency
Spreading the gospel of powershell scripting
An insight into my workings and inner most thoughts.Mainly PowerShell but some other tech and non-tech too
Flynn Bundy
Technology, Cloud computing and Automation...
Een opbergkast meer niet
Automate, Accelerate, Accurate
de parvis grandis acervus erit
Tech | Career | Musings
What is this Powershell of which you speak?
Passionate people that gather together, and create awesome things!
Just Another PowerShell Blog
up in the trees
Nice! Really fast on my laptop! I like how it catches the errors gracefully. A bit against the best practices that huge “try{}catch{}” block, but why follow these guidlines if it is only to be a *$¨!# in the but!? (I actually know the answer: It is to have a more precise error handeling, and specifically, to be able to use the finally{} scriptblock).
I personally like to add a “Get-Credential” right after my credential variable when I use it. (But it will make it mandatory).
[System.Management.Automation.Credential()] $Credential = (Get-credential)
Great work!
LikeLike
Thanks. Yeah, I tend to use large try-catch blocks. For me it’s enough that I catch any exceptions. If I’m working on a really complicated script, I’ll do it differently of course, but these functions are really just meant to do small things, so it works well I think.
LikeLike