{"id":4245,"date":"2013-01-28T00:01:00","date_gmt":"2013-01-28T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/01\/28\/use-powershell-to-configure-hyper-v-resource-metering\/"},"modified":"2013-01-28T00:01:00","modified_gmt":"2013-01-28T00:01:00","slug":"use-powershell-to-configure-hyper-v-resource-metering","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-configure-hyper-v-resource-metering\/","title":{"rendered":"Use PowerShell to Configure Hyper-V Resource Metering"},"content":{"rendered":"

Summary:<\/strong> Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to configure Hyper-V Resource Metering on Windows Server 2012.<\/span><\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Well, today is Monday, and the first thing I do on Monday is update the Help on Windows PowerShell 3.0. I use the command that is shown here.<\/p>\n

Update-Help -Module * -Force<\/p>\n

Note<\/strong>   I need to open the Windows PowerShell console with admin rights to update Help.<\/p>\n

Once I have updated Help, I am prepared to start the week.<\/p>\n

Exam note<\/strong>   One of the objectives on the Exam 70-410: Installing and Configuring Windows Server 2012<\/a> <\/em>is configure Resource Metering, <\/em>and so if you are working on your new MCSE for Server Infrastructure<\/em><\/a>, you will want to know this material. Of course, if you are running or thinking about running Hyper-V on Windows Server 2012, you will want to know this information as well. The Introduction to Resource Metering<\/a> <\/em>blog post written by Lalithra Fernando on the Virtualization Blog is an excellent place to start. Lalithra also wrote a blog post called How to Use Resource Metering with PowerShell<\/a>, <\/em>which is also a good introduction.<\/p>\n

Use PowerShell to configure Resource Metering<\/h2>\n

One of the things is a bit confusing about Hyper-V Resource Metering on Windows Server 2012 is that I must enable Resource Metering on the individual virtual machine, but if I want to set the Resource Metering interval, I need to do that on the server that hosts the virtual machines.<\/p>\n

Note<\/strong>   This is the second article in a series about Hyper-V and Windows PowerShell. It is also the fourth article in a series I have written about the MCSE exam 70-410<\/a>.<\/p>\n

Therefore, to configure the Resource Metering interval, I need to use the Set-VMHost<\/strong> cmdlet. I can do this remotely, if my logged on account has rights to the remote Hyper-V server. This is because the cmdlet has a –computername<\/strong> parameter, but no –credential<\/strong> parameter. Of course, I can wrap the thing by using Windows PowerShell remoting, and run the command on multiple remote Hyper-V servers.<\/p>\n

The thing that is really confusing about configuring Resource Metering is that the ResourceMeteringSaveInterval<\/strong> parameter requires a TimeSpan<\/strong> object as the input parameter. Also, the parameter only accepts whole hour values—couple this with an error in the Help example, and it is really a challenge to get this thing to work properly. (Oh, did I say that it will accept lots of things, not generate an error, and not make the change?)<\/p>\n

So, the first thing I do is follow the example in the Help, but an error occurs. Here is the command I typed:<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval 02: 00:00<\/p>\n

\"Image<\/a><\/p>\n

Well, maybe I do not need to do all that. Besides, it only accepts values from 1 – 24 hours, in whole numbers, so why should I type all those colons and stuff. So I try the following command:<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval 3<\/p>\n

Cool, no errors come back. But when I check the VMHost<\/strong>, I see the ResourceMeteringSaveInterval<\/strong> has not changed. These commands are shown here.<\/p>\n

16:52 C:\\> Set-VMHost -ResourceMeteringSaveInterval 3<\/p>\n

16:56 C:\\> Get-VMHost | select resource*<\/p>\n

ResourceMeteringSaveInterval<\/p>\n

—————————-<\/p>\n

01:00:00<\/p>\n

So, I try it with a leading zero. Again no error returns, but no change either.<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval 03<\/p>\n

First create a legitimate TimeSpan<\/h2>\n

Well, dude, this is NOT really that hard. Because I KNOW how to create a new TimeSpan, in fact, the cmdlet is New-TimeSpan<\/strong>, as shown here.<\/p>\n

17:00 C:\\> New-TimeSpan -Hours 3<\/p>\n

Days              : 0<\/p>\n

Hours             : 3<\/p>\n

Minutes           : 0<\/p>\n

Seconds           : 0<\/p>\n

Milliseconds      : 0<\/p>\n

Ticks             : 108000000000<\/p>\n

TotalDays         : 0.125<\/p>\n

TotalHours        : 3<\/p>\n

TotalMinutes      : 180<\/p>\n

TotalSeconds      : 10800<\/p>\n

TotalMilliseconds : 10800000<\/p>\n

So, all I have to do is store the TimeSpan in a variable and use that variable to configure the Resource Metering save interval, as shown here.<\/p>\n

$rm = New-TimeSpan -Hours 3<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval $rm<\/p>\n

Get-VMHost | select resource*<\/p>\n

The image shown here illustrates using these commands, as well as the output associated with each cmdlet.<\/p>\n

\"Image<\/a><\/p>\n

Simplify the process<\/h2>\n

Well, so I found out I could actually change the value—that is good news at least. So now, of course, I want to see if I can simplify the process. The first thing I decide to do is to put the New-TimeSpan<\/strong> cmdlet in the ResourceMeteringSaveInterval<\/strong> parameter slot. Once I make the change, I use the up arrow and retrieve the Get-VMHost<\/strong> command where I choose the Resource*<\/strong> property. The output shows that the command was successful.<\/p>\n

17:04 C:\\> Set-VMHost -ResourceMeteringSaveInterval (New-TimeSpan -Hours 2)<\/p>\n

17:09 C:\\> Get-VMHost | select resource*<\/p>\n

ResourceMeteringSaveInterval<\/p>\n

—————————-<\/p>\n

02:00:00<\/p>\n

Well, that is cool, what about if I cast it to a TimeSpan<\/strong> object? I love casting stuff in Windows PowerShell. I think it is both elegant and useful. So, I use the [timespan] type accelerator to cast 01 to a TimeSpan<\/strong> object. The results appear here.<\/p>\n

17:09 C:\\> [timespan]01<\/p>\n

Days              : 0<\/p>\n

Hours             : 0<\/p>\n

Minutes           : 0<\/p>\n

Seconds           : 0<\/p>\n

Milliseconds      : 0<\/p>\n

Ticks             : 1<\/p>\n

TotalDays         : 1.15740740740741E-12<\/p>\n

TotalHours        : 2.77777777777778E-11<\/p>\n

TotalMinutes      : 1.66666666666667E-09<\/p>\n

TotalSeconds      : 1E-07<\/p>\n

TotalMilliseconds : 0.0001<\/p>\n

Well, it worked, but the problem is that I created a TimeSpan that is equal to 1 tick, and not to 1 hour. Bummer. So I add some zeros and look to see what happens. The output appears in the following image.<\/p>\n

\"Image<\/a><\/p>\n

I now know that I can use [timespan]”01:00:00″ and create a legitimate TimeSpan that measures 1 hour. But can I make it any easier? I drop a couple of zeros, and as shown here, it works.<\/p>\n

17:14 C:\\> [timespan]”01:00″<\/p>\n

Days              : 0<\/p>\n

Hours             : 1<\/p>\n

Minutes           : 0<\/p>\n

Seconds           : 0<\/p>\n

Milliseconds      : 0<\/p>\n

Ticks             : 36000000000<\/p>\n

TotalDays         : 0.0416666666666667<\/p>\n

TotalHours        : 1<\/p>\n

TotalMinutes      : 60<\/p>\n

TotalSeconds      : 3600<\/p>\n

TotalMilliseconds : 3600000<\/p>\n

Groovy, that worked as well. I am confident that it will work for the Set-VMHost<\/strong> cmdlet as well, but the only way to ensure that is to use it directly. So here goes:<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval [timespan]”12:00″<\/p>\n

Bummer, an error occurs. I modify the command and group the [timespan]”12:00”. The revised command is shown here.<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval ([timespan]”12:00″)<\/p>\n

This time the command does not generate a command, so I use the Get-VMHost<\/strong> cmdlet to see if it worked. As shown in the following image, the command works fine.<\/p>\n

\"Image<\/a><\/p>\n

Well, I know that Windows PowerShell does automatic type conversion, and I also know from the previous errors that the –ResourceMeteringSaveInterval<\/strong> expects a TimeSpan<\/strong> object. If I can convert 01:00 to a TimeSpan, will the parameter accept it? Let’s see …<\/p>\n

17:18 C:\\> Set-VMHost -ResourceMeteringSaveInterval 01:00<\/p>\n

17:22 C:\\> Get-VMHost | select resource*<\/p>\n

ResourceMeteringSaveInterval<\/p>\n

—————————-<\/p>\n

01:00:00<\/p>\n

Yep, it works.<\/p>\n

Summary<\/h2>\n

I typed a lot of commands in this article. What worked? Well, storing a TimeSpan<\/strong> object in a variable works, as shown here:<\/p>\n

$rm = New-TimeSpan -Hours 3<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval $rm<\/p>\n

Also, creating the TimeSpan<\/strong> object at the ResourceMeteringSaveInterval<\/strong> also worked, as shown here:<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval (New-Timespan -Hours 2)<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval ([timespan]”12:00″)<\/p>\n

Because Windows PowerShell does automatic type conversion, I can also supply a value that casts to a TimeSpan<\/strong> object, as shown here.<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval 01:00<\/p>\n

I can also drop the leading zero if I wish, because the following command also works.<\/p>\n

Set-VMHost -ResourceMeteringSaveInterval 5:00<\/p>\n

Join me tomorrow when I will talk about more cool Windows PowerShell stuff.<\/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<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to configure Hyper-V Resource Metering on Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, today is Monday, and the first thing I do on Monday is update the Help on Windows PowerShell 3.0. I use the command that is shown here. Update-Help -Module […]<\/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":[271,402,362,3,45,368],"class_list":["post-4245","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-hyper-v","tag-mcse","tag-powershell-3","tag-scripting-guy","tag-windows-powershell","tag-windows-server-2012"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to configure Hyper-V Resource Metering on Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, today is Monday, and the first thing I do on Monday is update the Help on Windows PowerShell 3.0. I use the command that is shown here. Update-Help -Module […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4245","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=4245"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4245\/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=4245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}