Yesterday Microsoft released a new version of Microsoft Assessment and Planning toolkit 9.2 and the new key features are
Azure VM Capacity assessment to include assessment for A8 and A9 Azure VMs
MAP 9.2 updated Windows Azure VM Capacity assessment to include assessment for A8 and A9 Azure VMs. A8 and A9 Azure VMs are processor intensive and thus have a base processor of an Intel Xeon E5-2670 2.6 GHz.
Included Windows Server 2008(x86/x64) under Legacy Server Discovery
Windows Server 2008(x86/x64) included under Legacy Server Discovery in addition to Windows Servers 2000, 2003 and Itanium. For example, before MAP 9.2 the discovery of the Legacy Servers which were added are Windows Server 2000, Windows Server 2003(x86/x64) and Itanium Windows Server. Now MAP 9.2 includes the discovery of Windows Server 2008(x86/x64) as well to the collection of Legacy Server Discovery.
Improved Legacy Server Discovery reporting by including OS Architecture
In this version of MAP we included OS Architecture(32 or 64 bit) as an expansion in the Legacy Server Discovery reporting.
Collection of additional performance counters and included CPU speed
In this version of MAP we added four new performance counters Disk Queue Length, Disk Read Queue Length, Disk Write Queue Length, Disk Bytes/sec and expanded performance collection process to accomodate the new counters and assessment process. Added CPU Speed(GHz) to Performance Metric Summary report.
After working with a customer and showing them the PowerShell scripts and functions I had made for automating their VMM 2012 R2 environment I realized that I needed a way to actually let them easily get them loaded and ready for use.
And when you put it in your VMM library it looks like this, I have added some description to make it more clear what it does 😉
And you can then run it from the console with the Run button and once the PowerShell console is loaded you can see which functions have been loaded and what names they have
And in the folder I have added the files containing the functions that I made with .psm1 ending ( I am converting some of the scripts that I made earlier to functions and will add them later, that is why it is quite few yet). You will also have to check and edit the permissions on the share and the SCVMM_Library folder so the user trying to run the script will be able to.
Also, I added the server in trusted sites otherwise I got this digital signed error and I do not at this moment have a cert to sign the scripts
So to get around that one you add in Internet Explorer Trusted SItes: *://vmm02.vmmserver.se (or of course what your VMM server FQDN is)
Last of all, to be able to run some of the functions that need elevation you can start the VMM GUI Console with “Run As Administrator” but you still use your Windows Credentials:
Happy automating within VMM
And yes SMA has been thought of but right now the customer do not need that extra complexity with WAP,SMA,SPF and runbook workers…..
I have been working with a customer and was going to do an upgrade of one of their Hyper-v clusters to 2012 R2. During my preparations and looking at the particular hosts I found several VM´s that was residing on local storage on the hosts and not on the cluster storage.
The reason for this was two things, first of all that it was allowed to put VM´s on local disks and second that when someone created the VM´s forgot to use the appropriate HW-template that makes them highly available by default. If you create a new VM with a new HW profile make sure that it is configured correctly under the Availability tab.
The Hyper-V hosts have been deployed with Bare-Metal deploy from VMM and that is why they have a D:\
Looking at the properties for a host you can see what storage that is available for placement:
and as you can see the VM is not configured as highly available and have the virtual disk on local storage:
I have made a simple script that configures all hosts within a cluster and set all storage that is not cluster shared to not available for placement.
# Disable all Available for placement on local drives on hosts,
# Save this in a .ps1 file and run with disable-SCLocaldisk.ps1 -Cluster " cluster01"
I got a question from a customer how they could limit a VM´s bandwidth from VMM as it was too noisy and devoured the bandwidth from the host for the other VM´s. There are both a way to set priority and also bandwidth in Hyper-V 2012 and later.
In Hyper-V Manager you can find the setting on the VM´s configuration and the virtual network adapter tab,
And here I can enable bandwidth management and set both a minimum and maximum, and in this case I want just a limit
But how do I accomplish the same in VMM? As you might have noticed there is no possibility to edit this on the VM´s settings on the virtual nic, this is a setting that I configure with a Port profile instead and apply on selected VM/VM´s, and by doing it this way I can easily just configure the same profile for several VM´s instead of configuring each VM. There are some configured by default and I can also add new with the particular setting that I need.
First there is the port classification:
And then the actual port profiles:
These two combined is used in the Logical Switch for the virtual port,
Easiest is to use Powershell to create a new port classification and profile and then update the logical switch to be able to use it for the VM´s that needs it, I have made a function that takes care of all the steps including adding it to the logical switch as a virtual port:
This function is for creating profiles and adding a port in a Logic switch in VMM
Today I was contacted by a customer regarding an issue they had with all their VM´s in their main cluster reporting “Unsupported Cluster Configuration”
The reason was that two of the nodes in their cluster had in VMM 2012 R2 lost their virtual switch and vnics and that resulted in the cluster saying that it did not have a HA-Virtual Switch and thus the VM`s had network connections that was not available on the cluster…
Searching a bit and checking the hosts and VM´s outside of VMM there was no issues on them and the logical switch and vnics was still there, the vm´s was able to reach the network so clearly a VMM issue.
I tried to refresh the cluster and nodes and also restart the VMM agent on the hosts but that did not help. Looking at the properties in VMM on a host showed nothing where it should be both the switch and the management vnics:
Using the failover cluster manager and live-migrating the vm´s and then restart the host did though help,
After reboot I refreshed the cluster and the network appeared again, I have been searching for a reason for the issue but have not found anything yet in the logs on either the VMM server or the hosts..
To refresh the VM´s on the cluster to remove the “Unsupported cluster configuration” after I had got the virtual switch back I used powershell
If you have had this issue or similar I would like to know so please comment the post
I will search some more and see if I can find the reason for this. It should be said that the customer have two 2012 hyper-v clusters and one 2012 R2 cluster and I have not seen this happen on the R2 cluster yet so maybe it is a 2012 issue… And yes we are working eagerly to move the VM´s to the R2 cluster 😛 , the VMM 2012 R2 server is also updated with the latest UR4
There is no better way than to start the year and enlighten you with a error I had this autumn at a customer…
After I updated the VMM server to UR3 at a customer I noticed that it started to give a warning (Completed w/ Info) during refresh of the cluster. And when digging into it you can see the reason for it…
When I set up the Hyper-V cluster I did it outside of VMM, I had though set up the hosts with logical switches and host vNics in VMM network fabric and the different cluster networks was configured with IP-Pools. And for the record, the VMM server have been upgraded from 2012 SP1.
So what was the reason for this, well when I did the cluster setup I used an IP from the Management-IP pool range for the cluster management and had not reserved it, yes I know I should have taken care of it then but did not…
Consensus is that from UR3 the VMM team has fixed the bug and now it reports this when doing a refresh on the cluster object 😛
So how did i mitigate this issue?! I searched and found a german blogpost by Michel Luescher where he solves the issue with powershell, and as you can see when reading the lines is that we find the IP-address object that is of the wrong type and change it to a HostCluster object instead:
One year passes so fast and today was the day when it was my renewal date for the Microsoft Most Valuable Professional award. This is my second time that I get the award!
I have been working quite hard in the communities during the year with live presentations, webcasts, blog posts etc and was hoping that it was enough. In the afternoon I got a bit nervous and started thinking that maybe there was someone else that have made a bit more contributions and took my place but,
At the magic time 04:29 PM CET I got the longing mail :
I am in good company with about 50 other Hyper-V MVP´s and learn stuff every day from my friends and expertise-colleagues and 2015 will ROCK, so see you around and most certainly at Ignite in Chicago in May!
keep following my blog and twitter and I will try to keep up and post information and help when I encounter problems or smart solutions that you can benefit from