When I create a virtual machine, there are always a few things I do prior to the first use of the machine. These include installing the integration services and configuring dynamic memory.<\/p>\n
Note<\/b> Admin rights are required to use the Hyper-V module.<\/p>\nChecking integration services<\/h2>\n
One of the things I always do is ensure that the virtual machine additions (integration services) install properly. In the past, checking this seemed to involve attempting a new installation, and then watching for messages. In the Hyper-V module, I decide to look for cmdlets that are related to the additions. Following is the command I use. (gcm<\/b> is an alias for the Get-Command<\/b> cmdlet. I use –mod<\/b> instead of typing the longer Module<\/b> <\/i>parameter. I also use a wildcard (*integ*<\/b>) to help me look for cmdlets that are related to the virtual machine integration services.)<\/p>\n
PS C:\\> gcm -mod hyp* -Noun *integ*<\/p>\n
<\/p>\n
CommandType Name ModuleName<\/p>\n
———– —- ———-<\/p>\n
Cmdlet Disable-VMIntegrationService Hyper-V<\/p>\n
Cmdlet Enable-VMIntegrationService Hyper-V<\/p>\n
Cmdlet Get-VMIntegrationService Hyper-V<\/p>\n
This command shows me that I could enable or disable the integration services by using a cmdlet. I can also check to ensure that they are enabled.<\/p>\n
I decide that I will use the Get-VMIntegrationService<\/b> cmdlet to ensure the presence of the integration services. I know that a well-planned cmdlet accepts pipelined information. So I use the Get-VM<\/b> cmdlet and pipe the results to the Get-VMIntegrationService<\/b> cmdlet. I give it a whirl to see what happens. The command is shown here.<\/p>\n
get-vm | Get-VMIntegrationService<\/p>\n
The command and associated output are shown in the image that follows.<\/p>\n
I assume that the Primary and Secondary status descriptions have something to do with whether a virtual machine runs, because only DC1 is up right now. The output, although impressive, is a bit much to read, so I group the information to make things easier to understand. The revised command is shown here.<\/p>\n get-vm | Get-VMIntegrationService | group name –NoElement<\/p>\n The following output tells me that all four virtual machines contain each of the integration services.<\/p>\n PS C:\\> get-vm | Get-VMIntegrationService | group name -NoElement<\/p>\n Count Name<\/p>\n —– —-<\/p>\n 4 Time Synchronization<\/p>\n 4 Heartbeat<\/p>\n 4 Key-Value Pair Exchange<\/p>\n 4 Shutdown<\/p>\n 4 VSS<\/p>\n I conjecture that I will need a cmdlet that uses the verb of Set<\/b> <\/i>to permit configuring dynamic memory. In addition, I surmise that the noun will have something to do with memory. I use the following command to find the cmdlet I need to use (you can see that my guess was pretty close).<\/p>\n PS C:\\> gcm -Verb set -Noun *mem* -Mod *hyper*<\/p>\n <\/p>\n CommandType Name ModuleName<\/p>\n ———– —- ———-<\/p>\n Cmdlet Set-VMMemory Hyper-V<\/p>\n Now I use the Get-Command<\/strong> cmdlet to look at the syntax of the Set-VMMemory<\/strong> cmdlet. This command is shown here.<\/p>\n gcm -Syntax Set-VMMemory<\/p>\n The command and its associated output are shown in the image that follows.<\/p>\n The syntax of the Set-VMMemory<\/b> cmdlet tells me that there are three ways to use the cmdlet. The first is to supply one or more virtual machine names as strings. The third way is to supply one or more virtual machines (I assume I can get these via the Get-VM<\/b> cmdlet). I am not sure what the second syntax does, but it does not matter, because I need to supply a virtual machine name.<\/p>\n Note<\/b> The fact that I can supply arrays for input is awesome, and it can lead to extremely powerful Hyper-V management scenarios.<\/p>\n I decide to configure my virtual machine with dynamic memory, a minimum value of 512 MB of RAM, and a maximum of 2048 MB of RAM. I also set a 20% buffer. The following command accomplishes these tasks.<\/p>\n Set-VMMemory -VMName c7 -DynamicMemoryEnabled $true -MinimumBytes 512MB -MaximumBytes 2048MB -Buffer 20<\/p>\n I can use the Get-VMMemory cmdlet to ensure my changes took place. This command appears here.<\/p>\n PS C:\\> Get-VMMemory -VMName c7<\/p>\n <\/p>\n VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)<\/p>\n —— ——————– ———- ———- ———-<\/p>\n c7 True 512 512 2048<\/p>\n Remember, this is still Windows PowerShell I am using. So I can look for additional information by piping the cmdlet to the Format-List<\/b> cmdlet and using a *<\/b> to look for all properties. Here is the command.<\/p>\n Get-VMMemory -VMName c7 | fl *<\/p>\n In addition, I can use pipeline cmdlets into the Get-VMMemory<\/b> cmdlet. I use the following command to verify that I have dynamic memory enabled on all the virtual machines on my laptop.<\/p>\n PS C:\\> get-vm | Get-VMMemory<\/p>\n VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)<\/p>\n —— ——————– ———- ———- ———-<\/p>\n c1 True 512 512 1024<\/p>\n C2 True 512 512 1024<\/p>\n c7 True 512 512 2048<\/p>\n DC1 True 512 512 1024<\/p>\n I see that I have allocated too much memory for my c7 virtual machine. I use the Set-Virtual MachineMemory<\/b> cmdlet to make the change. I only need to specify the revised value. The command is shown here.<\/p>\n Set-VMMemory -VMName c7 -MaximumBytes 1024MB<\/p>\n I use the Get-VM | Get-VMMemory<\/b> command to ensure that the change worked. It does, as shown here.<\/p>\n PS C:\\> get-vm | Get-VMMemory<\/p>\n VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)<\/p>\n —— ——————– ———- ———- ———-<\/p>\n c1 True 512 512 1024<\/p>\n C2 True 512 512 1024<\/p>\n c7 True 512 512 1024<\/p>\n DC1 True 512 512 1024<\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Microsoft Scripting Guy, Ed Wilson, discusses using Windows PowerShell 3.0 to configure a virtual machine on his laptop. Microsoft Scripting Guy, Ed Wilson, is here. One of the things I really appreciate is weekends. Most of the time, I do not even open my email. Freedom from email is something I dream about. Recently, my […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[373,362,3,130,61,367,45],"class_list":["post-4827","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-hyperv","tag-powershell-3","tag-scripting-guy","tag-servers","tag-weekend-scripter","tag-windows-8","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Scripting Guy, Ed Wilson, discusses using Windows PowerShell 3.0 to configure a virtual machine on his laptop. Microsoft Scripting Guy, Ed Wilson, is here. One of the things I really appreciate is weekends. Most of the time, I do not even open my email. Freedom from email is something I dream about. Recently, my […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4827","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=4827"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4827\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=4827"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4827"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4827"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/7215.wes-10-14-12-1.png\" "\\"Image")
<\/a><\/p>\nConfigure dynamic memory<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/5618.wes-10-14-12-2.png\" "\\"Image")
<\/a><\/p>\n