{"id":615,"date":"2010-04-05T14:09:23","date_gmt":"2010-04-05T19:09:23","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/2010\/04\/remote-powershell-performance-comparison\/"},"modified":"2010-04-05T14:09:23","modified_gmt":"2010-04-05T19:09:23","slug":"remote-powershell-performance-comparison","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/","title":{"rendered":"Remote PowerShell Performance Comparison"},"content":{"rendered":"

Fellow Windows PowerShell MVP Marco Shaw<\/a> clued me in on a Microsoft blog post<\/a> that did a terrific job of comparing, from a performance perspective the different PowerShell 2.0 techniques you can use when managing remote computers. The results are pretty much as I would expect. <\/p>\n

<\/p>\n

Cmdlets with a \u2013computername parameter tend to perform the best.  Using Get-WMIObject<\/a> tend to be the slowest. Certainly your mileage may vary depending on network, servers, and the exact PowerShell expression. In between, you get pretty decent performance using Invoke-Command<\/a>.  Sometimes, using Invoke-Command is the only way to accomplish a remote management task. One major point I want to re-iterate from the original blog posting is that if you need to invoke multiple commands on a remote server, create a saved PSSession and reuse the session.  Otherwise you are incurring a lot of overhead in setting up and tearing down WinRM sessions when using \u2013computername.<\/p>\n

My performance testing confirms the original findings. When you use \u2013computername, when you use WMI and when you use Invoke-Command depends on what you have to accomplish. To help make it easier to calculate performance, I put together a little script that executes a PowerShell command for a remote computer a certain number of times, and calculates the average time it takes to complete.<\/p>\n

\n
\n
   1:<\/span> #requires -version 2.0 <\/span><\/pre>\n
<\/p>\n
   2:<\/span>  <\/pre>\n
<\/p>\n
   3:<\/span> Function Get-PerfTime {<\/pre>\n
<\/p>\n
   4:<\/span> Param ([scriptblock]$expression,<\/pre>\n
<\/p>\n
   5:<\/span>        [int]$interval=1,<\/pre>\n
<\/p>\n
   6:<\/span>        [int]$max=10<\/pre>\n
<\/p>\n
   7:<\/span>       ) <\/pre>\n
<\/p>\n
   8:<\/span>  <\/pre>\n
<\/p>\n
   9:<\/span>     1..$max | foreach<\/span> {<\/pre>\n
<\/p>\n
  10:<\/span>         $i=($_\/$max)*100<\/pre>\n
<\/p>\n
  11:<\/span>         Write-Progress -Activity "Performance Testing"<\/span> `<\/pre>\n
<\/p>\n
  12:<\/span>         -Status "Repeat: $max Interval: $interval MS"<\/span> `<\/pre>\n
<\/p>\n
  13:<\/span>         -CurrentOperation $expression `<\/pre>\n
<\/p>\n
  14:<\/span>         -PercentComplete $i<\/pre>\n
<\/p>\n
  15:<\/span>         (Measure-Command -Expression $expression).TotalMilliseconds<\/pre>\n
<\/p>\n
  16:<\/span>         sleep $interval<\/pre>\n
<\/p>\n
  17:<\/span>     }<\/pre>\n
<\/p>\n
  18:<\/span> } #end function<\/span><\/pre>\n
<\/p>\n
  19:<\/span>  <\/pre>\n
<\/p>\n
  20:<\/span> $computername="coredc01"<\/span><\/pre>\n
<\/p>\n
  21:<\/span> #sleep interval in seconds<\/span><\/pre>\n
<\/p>\n
  22:<\/span> $sleep=1<\/pre>\n
<\/p>\n
  23:<\/span> #max number of tries<\/span><\/pre>\n
<\/p>\n
  24:<\/span> $max=100<\/pre>\n
<\/p>\n
  25:<\/span> #create a PSSession for later<\/span><\/pre>\n
<\/p>\n
  26:<\/span> $session=New-PSSession -ComputerName $computername<\/pre>\n
<\/p>\n
  27:<\/span>  <\/pre>\n
<\/p>\n
  28:<\/span> #define a standard scriptlblock with a cmdlet that supports -computername<\/span><\/pre>\n
<\/p>\n
  29:<\/span> $Test1={get-process<\/span> -ComputerName $computername }<\/pre>\n
<\/p>\n
  30:<\/span> #define a WMI equivalent<\/span><\/pre>\n
<\/p>\n
  31:<\/span> $Test2={Get-WmiObject -Class win32_process -ComputerName $computername}<\/pre>\n
<\/p>\n
  32:<\/span> #define a test using Invoke-Command<\/span><\/pre>\n
<\/p>\n
  33:<\/span> $Test3={invoke-command -ComputerName $computername -ScriptBlock {$scriptblock}}<\/pre>\n
<\/p>\n
  34:<\/span> #define a test with Invoke-Command and PSSession<\/span><\/pre>\n
<\/p>\n
  35:<\/span> $Test4={invoke-command -Session $session -ScriptBlock {$wmiscriptblock}}<\/pre>\n
<\/p>\n
  36:<\/span> $Test5={invoke-command -Session $session -ScriptBlock {$scriptblock}}<\/pre>\n
<\/p>\n
  37:<\/span>  <\/pre>\n
<\/p>\n
  38:<\/span> $Test1,$Test2,$Test3,$Test4,$Test5 | foreach<\/span> {<\/pre>\n
<\/p>\n
  39:<\/span>     $raw=Get-PerfTime -max $max -expression $_ -sleep $sleep <\/pre>\n
<\/p>\n
  40:<\/span>     $avg=($raw | Measure-Object -average).Average<\/pre>\n
<\/p>\n
  41:<\/span>  <\/pre>\n
<\/p>\n
  42:<\/span>     New-Object PSObject -Property @{<\/pre>\n
<\/p>\n
  43:<\/span>         Computername=$computername<\/pre>\n
<\/p>\n
  44:<\/span>         Repeat=$max<\/pre>\n
<\/p>\n
  45:<\/span>         Expression=$_<\/pre>\n
<\/p>\n
  46:<\/span>         Average=$avg<\/pre>\n
<\/p>\n
  47:<\/span>         RawData=$raw<\/pre>\n
<\/p>\n
  48:<\/span>     } <\/pre>\n
<\/p>\n
  49:<\/span> }<\/pre>\n
<\/p>\n
  50:<\/span> #clean up the PSSession<\/span><\/pre>\n
<\/p>\n
  51:<\/span> Remove-PSSession $session<\/pre>\n
<\/p>\n
  52:<\/span> write-host "Finished!"<\/span> -ForegroundColor Green<\/pre>\n
<\/p>\n
  53:<\/span> #end<\/span> of script<\/pre>\n
<\/div>\n<\/div>\n
You know I love objects, so my little script writes a custom object to the pipeline for each tested expression. <\/p>\n
Average      : 19.406741
\n    
RawData      : {18.6137, 19.1951, 19.4136, 20.8938...} <\/p>\n
Expression   : get-process -ComputerName $computername <\/p>\n
Computername : coredc01 <\/p>\n
Repeat       : 100<\/font><\/p>\n
I also added a sleep interval for whatever it might be worth. I know there\u2019s some caching with WMI, but you\u2019d probably likely need a sleep interval of several minutes for it to clear. The object also returns the raw response times if you want to do something else with them. I already calculate the average using Measure-Object<\/a>. You might use the script like this.<\/p>\n
PS S:\\> $results=.\\PerfCompare.ps1<\/font><\/p>\n
PS S:\\> $results | sort Average | format-table Average,Expression -AutoSize <\/font><\/p>\n
   Average Expression
\n    
   ------- ---------- <\/p>\n
  11.87756 invoke-command -Session $session -ScriptBlock {$Test1} <\/p>\n
12.119081 invoke-command -Session $session -ScriptBlock {$Test2} <\/p>\n
19.406741 get-process -ComputerName $computername <\/p>\n
64.133741 Get-WmiObject -Class win32_process -ComputerName $computername <\/p>\n
593.375884 invoke-command -ComputerName $computername -ScriptBlock {$Test1}<\/font><\/p>\n
 One interesting thing to note here is that Invoke command with the original script block ({get-process}) was faster than calling Get-Process \u2013computername. This was over a 100 count loop with a sleep interval of 1 second. I\u2019d be very curious to see how your numbers compare.<\/p>\n
\n
Download PerfCompare.ps1<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Fellow Windows PowerShell MVP Marco Shaw clued me in on a Microsoft blog post that did a terrific job of comparing, from a performance perspective the different PowerShell 2.0 techniques you can use when managing remote computers. The results are pretty much as I would expect.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[75,8],"tags":[122,177,178,179,534,87],"class_list":["post-615","post","type-post","status-publish","format-standard","hentry","category-powershell-v2-0","category-scripting","tag-invoke-command","tag-measure-command","tag-measure-object","tag-performance","tag-powershell","tag-remoting"],"yoast_head":"\nRemote PowerShell Performance Comparison • The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Remote PowerShell Performance Comparison • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Fellow Windows PowerShell MVP Marco Shaw clued me in on a Microsoft blog post that did a terrific job of comparing, from a performance perspective the different PowerShell 2.0 techniques you can use when managing remote computers. The results are pretty much as I would expect.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2010-04-05T19:09:23+00:00\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Remote PowerShell Performance Comparison\",\"datePublished\":\"2010-04-05T19:09:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/\"},\"wordCount\":406,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"keywords\":[\"Invoke-Command\",\"Measure-Command\",\"Measure-Object\",\"Performance\",\"PowerShell\",\"remoting\"],\"articleSection\":[\"PowerShell v2.0\",\"Scripting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/\",\"name\":\"Remote PowerShell Performance Comparison • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"datePublished\":\"2010-04-05T19:09:23+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/615\\\/remote-powershell-performance-comparison\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell v2.0\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell-v2-0\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Remote PowerShell Performance Comparison\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Remote PowerShell Performance Comparison • The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/","og_locale":"en_US","og_type":"article","og_title":"Remote PowerShell Performance Comparison • The Lonely Administrator","og_description":"Fellow Windows PowerShell MVP Marco Shaw clued me in on a Microsoft blog post that did a terrific job of comparing, from a performance perspective the different PowerShell 2.0 techniques you can use when managing remote computers. The results are pretty much as I would expect.","og_url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/","og_site_name":"The Lonely Administrator","article_published_time":"2010-04-05T19:09:23+00:00","author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Remote PowerShell Performance Comparison","datePublished":"2010-04-05T19:09:23+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/"},"wordCount":406,"commentCount":2,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"keywords":["Invoke-Command","Measure-Command","Measure-Object","Performance","PowerShell","remoting"],"articleSection":["PowerShell v2.0","Scripting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/","url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/","name":"Remote PowerShell Performance Comparison • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"datePublished":"2010-04-05T19:09:23+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/615\/remote-powershell-performance-comparison\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell v2.0","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},{"@type":"ListItem","position":2,"name":"Remote PowerShell Performance Comparison"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":7908,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7908\/measuring-powershell-profile-performance\/","url_meta":{"origin":615,"position":0},"title":"Measuring PowerShell Profile Performance","author":"Jeffery Hicks","date":"November 25, 2020","format":false,"excerpt":"Today's topic is one of those things that I don't know why I've never addressed before. Well, I have for myself in a manual process. Hopefully you'll find it useful. As you probably know, PowerShell uses a set of profile scripts. These scripts have hard-coded paths and PowerShell runs them\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/11\/ps7profiles.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":1687,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/1687\/filter-left\/","url_meta":{"origin":615,"position":1},"title":"Filter Left","author":"Jeffery Hicks","date":"October 14, 2011","format":false,"excerpt":"When writing WMI queries expressions in Windows PowerShell, it is recommended to use WMI filtering, as opposed to getting objects and then filtering with Where-Object. I see expressions like this quite often: [cc lang=\"PowerShell\"] get-wmiobject win32_process -computer $c | where {$_.name -eq \"notepad.exe\"} [\/cc] In this situation, ALL process objects\u2026","rel":"","context":"In "Best Practices"","block_context":{"text":"Best Practices","link":"https:\/\/jdhitsolutions.com\/blog\/category\/best-practices\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2011\/10\/talkbubble.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":6308,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6308\/ultimate-powershell-telemetry-prompt\/","url_meta":{"origin":615,"position":2},"title":"The Ultimate PowerShell Telemetry Prompt","author":"Jeffery Hicks","date":"December 20, 2018","format":false,"excerpt":"Well, I knew I wouldn't be satisfied. The other day I shared a PowerShell prompt function that could display telemetry like information for a few remote servers. One of the drawbacks was the limited amount of information I could display. I've revised that function and have a new version that\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-15.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-15.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-15.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-15.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6336,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6336\/building-a-powershell-process-memory-tool\/","url_meta":{"origin":615,"position":3},"title":"Building a PowerShell Process Memory Tool","author":"Jeffery Hicks","date":"December 28, 2018","format":false,"excerpt":"This week I've been testing out a new browser, Brave, as a possible replacement for Firefox. One of the reasons I switched to Firefox from Chrome was performance and better resource utilization. Brave may now be a better choice, but that's not what this article is about. In order to\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-20.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-20.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-20.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/12\/image_thumb-20.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6840,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6840\/making-sense-of-parallel-foreach-object-in-powershell-7\/","url_meta":{"origin":615,"position":4},"title":"Making Sense of Parallel ForEach-Object in PowerShell 7","author":"Jeffery Hicks","date":"October 7, 2019","format":false,"excerpt":"By, you've most likely heard about the new -parallel parameter with ForEach-Object in the latest preview of PowerShell 7 Personally. I've been waiting for this for a long time. I used to only use PowerShell workflows because it offered a way to run commands in parallel. Having this feature as\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/10\/image_thumb.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/10\/image_thumb.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/10\/image_thumb.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/10\/image_thumb.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":8499,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/8499\/using-the-powershell-ise-as-a-remote-management-console\/","url_meta":{"origin":615,"position":5},"title":"Using the PowerShell ISE as a Remote Management Console","author":"Jeffery Hicks","date":"July 20, 2021","format":false,"excerpt":"Way back before the days of PowerShell Core, or even VS Code for that matter, the PowerShell ISE was the center of my PowerShell world. I spent a lot of time finding ways to make it easier for me to use and to push it to its limits. Naturally, the\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/07\/ise-remotetab-form2.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=615"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/615\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}