{"id":2546,"date":"2012-11-01T09:20:42","date_gmt":"2012-11-01T13:20:42","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/?p=2546"},"modified":"2013-11-01T08:06:06","modified_gmt":"2013-11-01T12:06:06","slug":"powershell-hyper-v-memory-report","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/","title":{"rendered":"PowerShell Hyper-V Memory Report"},"content":{"rendered":"<p><a href=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport-150x150.png\" alt=\"\" title=\"happyreport\" width=\"150\" height=\"150\" class=\"alignleft size-thumbnail wp-image-2547\" \/><\/a> Since moving to Windows 8, I've continued exploring all the possibilities around Hyper-V on the client, especially using PowerShell. Because I'm trying to run as many virtual machines on my laptop as I can, memory considerations are paramount as I only have 8GB to work with. Actually less since I still have to run Windows 8! <\/p>\n<p>Anyway, I need to be able to see how much memory my virtual machines are using. The Get-VM cmdlet can show me some of the data.<\/p>\n<pre class=\"nums:false lang:batch decode:true \" >PS C:\\&gt; get-vm chi-dc03\r\n\r\nName     State   CPUUsage(%) MemoryAssigned(M) Uptime   Status\r\n----     -----   ----------- ----------------- ------   ------\r\nCHI-DC03 Running 0           559               23:29:12 Operating normally\r\n<\/pre>\n<p>Actually, there are more properties I can get as well.<\/p>\n<pre class=\"nums:false lang:batch decode:true \" >PS C:\\&gt; get-vm chi-dc03 | select *mem*\r\n\r\nMemoryAssigned       : 586153984\r\nMemoryDemand         : 491782144\r\nMemoryStatus         : OK\r\nMemoryStartup        : 402653184\r\nDynamicMemoryEnabled : True\r\nMemoryMinimum        : 402653184\r\nMemoryMaximum        : 1073741824\r\n<\/pre>\n<p>Those values are in bytes so I would need to reformat them to get them into something more meaningful like bytes. Not especially difficult, but not something I want to have to type all the time. Now, I can also get memory information with Get-VMMemory and this is formatted a little nicer.<\/p>\n<pre class=\"nums:false lang:batch decode:true \" >PS C:\\&gt; get-vmmemory chi-dc03\r\n\r\nVMName   DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)\r\n------   -------------------- ---------- ---------- ----------\r\nCHI-DC03 True                 384        384        1024\r\n<\/pre>\n<p>What I like about this cmdlet is that it also shows the buffer and priority settings.<\/p>\n<pre class=\"lang:batch decode:true \" >PS C:\\&gt; get-vmmemory chi-dc03 | select Startup,Buffer,Priority,Minimum,Maximum\r\n\r\nStartup  : 402653184\r\nBuffer   : 20\r\nPriority : 50\r\nMinimum  : 402653184\r\nMaximum  : 1073741824\r\n<\/pre>\n<p>In the end, I decided the best course of action was to build my own function that combined information from both cmdlets. The result is a custom object that gives me a good picture of memory configuration and current use. The function, Get-VMMemoryReport, is part of a larger HyperV toolkit module I'm developing but I thought I'd share this with you now.<\/p>\n<pre class=\"lang:ps decode:true \" >Function Get-VMMemoryReport {\r\n#comment based help is here\r\n\r\n[cmdletbinding()]\r\nParam(\r\n[Parameter(Position=0,Mandatory=$True,HelpMessage=\"Enter a VM\",\r\nValueFromPipeline=$True)]\r\n[alias(\"VM\")]\r\n[object]$Name,\r\n[ValidateNotNullorEmpty()]\r\n[string]$Computername=$env:COMPUTERNAME\r\n)\r\n\r\nProcess {\r\n    if ($Name -is [String]) {\r\n        Try {\r\n            $Name = Get-VM -name $Name -ComputerName $computername -ErrorAction Stop\r\n        }\r\n        Catch {\r\n            Write-Warning \"Failed to find VM $vm on $computername\"\r\n            Return\r\n        }\r\n    } #if\r\n    elseif ($name -isnot [Microsoft.HyperV.PowerShell.VirtualMachine]) {\r\n        Write-Warning \"You did not pass a string or a VM object\"\r\n        Return\r\n    }\r\n\r\n    #get memory values\r\n    $memorysettings = Get-VMMemory -VMName $Name.name -ComputerName $Computername\r\n\r\n    #all values are in MB\r\n    $hash=[ordered]@{\r\n        Name = $Name.Name\r\n        Dynamic = $Name.DynamicMemoryEnabled\r\n        Assigned = $Name.MemoryAssigned\/1MB\r\n        Demand = $Name.MemoryDemand\/1MB\r\n        Startup = $Name.MemoryStartup\/1MB\r\n        Minimum = $Name.MemoryMinimum\/1MB\r\n        Maximum = $Name.MemoryMaximum\/1MB\r\n        Buffer =  $memorysettings.buffer\r\n        Priority = $memorysettings.priority\r\n    }\r\n    \r\n    #write the new object to the pipeline\r\n    New-Object -TypeName PSObject -Property $hash\r\n    \r\n} #process\r\n} #end Get-VMMemoryReport\r\n<\/pre>\n<p>I wrote the function with the assumption of piping Hyper-V virtual machines to it. Although I can also pipe names to it and the function will then get the virtual machine.<\/p>\n<pre class=\"lang:ps decode:true \" > if ($Name -is [String]) {\r\n        Try {\r\n            $Name = Get-VM -name $Name -ErrorAction Stop\r\n        }\r\n        Catch {\r\n            Write-Warning \"Failed to find VM $vm\"\r\n            Return\r\n        }\r\n    } #if\r\n    elseif ($name -isnot [Microsoft.HyperV.PowerShell.VirtualMachine]) {\r\n        Write-Warning \"You did not pass a string or a VM object\"\r\n        Return\r\n    }\r\n<\/pre>\n<p>Once the function has the virtual machine object, it also gets data from Get-VMMemory.<\/p>\n<pre class=\"lang:ps decode:true \" >$memorysettings = Get-VMMemory -VM $Name<\/pre>\n<p>Finally, it creates a hash table using the new [ordered] attribute so that the key names will be displayed in the order I enter them. I use this hash table to write a custom object to the pipeline. I could have used the new [pscustomobject] attribute as well, but I felt in a script using New-Object was a bit more meaningful. With this command, I get output like this:<\/p>\n<pre class=\"lang:batch decode:true \" >PS C:\\&gt; get-VMMemoryreport chi-dc03\r\n\r\nName     : CHI-DC03\r\nDynamic  : True\r\nAssigned : 559\r\nDemand   : 469\r\nStartup  : 384\r\nMinimum  : 384\r\nMaximum  : 1024\r\nBuffer   : 20\r\nPriority : 50\r\n<\/pre>\n<p>Or I can explore the data in other ways. I can create an HTML report, export to a CSV or take advantage of Out-GridView.<\/p>\n<pre class=\"lang:batch decode:true \" >PS C:\\&gt; get-vm | where state -eq running | get-vmmemoryreport | out-gridview -title 'VM Memory Report'<\/pre>\n<p>Here's the report for my currently running virtual machines.<\/p>\n<p><a href=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/VMMemoryReport.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/VMMemoryReport-300x133.png\" alt=\"\" title=\"VMMemoryReport\" width=\"300\" height=\"133\" class=\"aligncenter size-medium wp-image-2548\" srcset=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/VMMemoryReport-300x133.png 300w, https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/VMMemoryReport.png 683w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>The function defaults to connecting to the localhost, but I am assuming that if you have an Hyper-V server you could use this from any system that has they Hyper-V module also installed. I don't have a dedicated Hyper-V server to test with so maybe someone will confirm this for me.<\/p>\n<p>In the meantime, download <a href='http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/Get-VMMemoryReport.txt' target='_blank'>Get-VMMemoryReport<\/a> and let me know what you think.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since moving to Windows 8, I&#8217;ve continued exploring all the possibilities around Hyper-V on the client, especially using PowerShell. Because I&#8217;m trying to run as many virtual machines on my laptop as I can, memory considerations are paramount as I only have 8GB to work with. Actually less since I still have to run Windows&#8230;<\/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":[401,359,8,380,407],"tags":[32,199,573,365,534,572],"class_list":["post-2546","post","type-post","status-publish","format-standard","hentry","category-hyper-v","category-powershell-3-0","category-scripting","category-windows-8","category-windows-server-2012","tag-functions","tag-hashtable","tag-hyper-v","tag-out-gridview","tag-powershell","tag-windows-8"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>PowerShell Hyper-V Memory Report &#8226; 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\/2546\/powershell-hyper-v-memory-report\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PowerShell Hyper-V Memory Report &#8226; The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Since moving to Windows 8, I&#039;ve continued exploring all the possibilities around Hyper-V on the client, especially using PowerShell. Because I&#039;m trying to run as many virtual machines on my laptop as I can, memory considerations are paramount as I only have 8GB to work with. Actually less since I still have to run Windows...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2012-11-01T13:20:42+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2013-11-01T12:06:06+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport-150x150.png\" \/>\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=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"PowerShell Hyper-V Memory Report\",\"datePublished\":\"2012-11-01T13:20:42+00:00\",\"dateModified\":\"2013-11-01T12:06:06+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/\"},\"wordCount\":440,\"commentCount\":6,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/11\\\/happyreport-150x150.png\",\"keywords\":[\"functions\",\"hashtable\",\"Hyper-V\",\"Out-Gridview\",\"PowerShell\",\"Windows 8\"],\"articleSection\":[\"Hyper-V\",\"Powershell 3.0\",\"Scripting\",\"Windows 8\",\"Windows Server 2012\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/\",\"name\":\"PowerShell Hyper-V Memory Report &#8226; The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/11\\\/happyreport-150x150.png\",\"datePublished\":\"2012-11-01T13:20:42+00:00\",\"dateModified\":\"2013-11-01T12:06:06+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/11\\\/happyreport.png\",\"contentUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/11\\\/happyreport.png\",\"width\":\"304\",\"height\":\"335\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/2546\\\/powershell-hyper-v-memory-report\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Hyper-V\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/hyper-v\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PowerShell Hyper-V Memory Report\"}]},{\"@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":"PowerShell Hyper-V Memory Report &#8226; 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\/2546\/powershell-hyper-v-memory-report\/","og_locale":"en_US","og_type":"article","og_title":"PowerShell Hyper-V Memory Report &#8226; The Lonely Administrator","og_description":"Since moving to Windows 8, I've continued exploring all the possibilities around Hyper-V on the client, especially using PowerShell. Because I'm trying to run as many virtual machines on my laptop as I can, memory considerations are paramount as I only have 8GB to work with. Actually less since I still have to run Windows...","og_url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/","og_site_name":"The Lonely Administrator","article_published_time":"2012-11-01T13:20:42+00:00","article_modified_time":"2013-11-01T12:06:06+00:00","og_image":[{"url":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport-150x150.png","type":"","width":"","height":""}],"author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"PowerShell Hyper-V Memory Report","datePublished":"2012-11-01T13:20:42+00:00","dateModified":"2013-11-01T12:06:06+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/"},"wordCount":440,"commentCount":6,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport-150x150.png","keywords":["functions","hashtable","Hyper-V","Out-Gridview","PowerShell","Windows 8"],"articleSection":["Hyper-V","Powershell 3.0","Scripting","Windows 8","Windows Server 2012"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/","url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/","name":"PowerShell Hyper-V Memory Report &#8226; The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#primaryimage"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport-150x150.png","datePublished":"2012-11-01T13:20:42+00:00","dateModified":"2013-11-01T12:06:06+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#primaryimage","url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport.png","contentUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/11\/happyreport.png","width":"304","height":"335"},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2546\/powershell-hyper-v-memory-report\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Hyper-V","item":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},{"@type":"ListItem","position":2,"name":"PowerShell Hyper-V Memory Report"}]},{"@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":4457,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/4457\/creating-a-hyper-v-vm-memory-report\/","url_meta":{"origin":2546,"position":0},"title":"Creating a Hyper-V VM Memory Report","author":"Jeffery Hicks","date":"July 20, 2015","format":false,"excerpt":"I use Hyper-V to run my lab environment. Since I work at home I don't have access to a \"real\" production network so I have to make do with a virtualized environment. Given budgetary constraints I also don't have a lot of high end hardware with endless amount of RAM\u2026","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4547,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/4547\/hyper-v-memory-utilization-with-powershell\/","url_meta":{"origin":2546,"position":1},"title":"Hyper-V Memory Utilization with PowerShell","author":"Jeffery Hicks","date":"October 6, 2015","format":false,"excerpt":"I really push the limits of my Hyper-V setup. I know I am constrained by memory and am hoping to expand my network before the end of the year. But in the meantime I have to keep close tabs on memory. I thought I'd share a few commands with you.\u2026","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4685,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/4685\/adding-some-power-to-hyper-v-vm-notes\/","url_meta":{"origin":2546,"position":2},"title":"Adding Some Power to Hyper-V VM Notes","author":"Jeffery Hicks","date":"December 15, 2015","format":false,"excerpt":"I use they Hyper-V virtual machine note to store system information. Here's how I get it and set with PowerShell.","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"System Information","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-1.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-1.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-1.png?resize=525%2C300 1.5x"},"classes":[]},{"id":4432,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/4432\/vmdk-to-vhdx-pdq\/","url_meta":{"origin":2546,"position":3},"title":"VMDK to VHDX PDQ","author":"Jeffery Hicks","date":"June 26, 2015","format":false,"excerpt":"I have a very old VMware ESXi server that has outlived its useful life. The hardware is at least 5 years old and my VMware license has expired. I can still bring up the server and see the virtual machines, but that's about it. I still keep the box so\u2026","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2657,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/2657\/hyper-v-id-hash-table\/","url_meta":{"origin":2546,"position":4},"title":"Hyper-V ID Hash Table","author":"Jeffery Hicks","date":"January 3, 2013","format":false,"excerpt":"In Hyper-V, one of the challenges (at least that I've run into) has to do with naming. In addition to a name, Hyper-V objects such as virtual machines, are identified with a GUID. Most of the VM-related PowerShell cmdlets will let you specify a virtual machine name. But sometimes you'll\u2026","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"Microsoft Hyper-V","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2013\/01\/hyperv.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":7047,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7047\/my-powershell-hyper-v-health-report\/","url_meta":{"origin":2546,"position":5},"title":"My PowerShell Hyper-V Health Report","author":"Jeffery Hicks","date":"December 5, 2019","format":false,"excerpt":"Over the last few years I've been using and tweaking a PowerShell script that generates an HTML report that provides information about a Hyper-V host and running virtual machines. This is another great use case for a PowerShell control script. The script helps me organize commands like Get-CimInstance, Get-VM and\u2026","rel":"","context":"In &quot;Hyper-V&quot;","block_context":{"text":"Hyper-V","link":"https:\/\/jdhitsolutions.com\/blog\/category\/hyper-v\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-8.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-8.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-8.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-8.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/2546","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=2546"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/2546\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=2546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=2546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=2546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}