NEW #Microsoft First Surface Book Laptop #Windows10 #SurfaceBook #Surface

More Information here : Watch and Compare devices like the Surface Pro4 and the Surface Book Laptop

Source: NEW #Microsoft First Surface Book Laptop #Windows10 #SurfaceBook #Surface

VMM Host performance counters report 0 Cpu and Memory

Goedemorgen! as the Dutch say,

Often Virtual Machine Manager Hyper-V hosts will report 0% CPU and 0KB Memory, I have seen this issue for VMM 2012, 2012 SP1, and 2012 R2.

A restart will often fix the issue but its often easier to restart the virtual machine manager agent.

If an agent restart doesn’t fix the issue then you can try the steps documented by Kristian Nese here: http://kristiannese.blogspot.nl/2012/12/vmm-doesnt-show-hosts-performance.html

Be aware that when the performance counters are not working then this could potentially have an affect on things like Dynamic Optimization (VMM) or other 3rd party resource optimization tools (such as VMTurbo) – this is to be confirmed.

Hope this helps.

Daniel

Windows Core – Check MPIO Path State by command line

First post in a while, since my last post I have driven across the USA, and settled in Europe.

A great way to check the MPIO path states on Windows Server Core is to use the mpclaim command. I never realized that this command would pull such great information back.

So if we want to check the MPIO path state via the GUI we would open computer manager, right click the disk -> properties, and the select the MPIO tab.

MPIO in local Disk Manager

This information will show how the state of the paths between the LUN and the SAN.

The same information can be queried via mpclaim

first start with

mpclaim -s -d

this will return a list of MPIO supported disks

then mpclaim -s -d #

this will return the pathing policy and state of the disk #

Thanks to Eric Siron for helping me with this one.

VMM – One Liner to dismiss failed state

A colleague asked me today about a one line command to remove the ‘failed’ state of all VMs, I thought I’d share this in case anyone else has had this problem:

(remember to run from VMM powershell)

Get-SCVirtualMachine | Repair-SCVirtualMachine -Dismiss

VMM Version Numbers

To identify the version of VMM you are running find the about information as per the screenshot below:

vmm

This will pull up version information including Service Pack and Version number:

vmm2

The Version number can be converted to a KB article (Update Rollup) by using this site: List of Build Numbers for System Center Virtual Machine Manager (VMM)

 

2008 R2 SP1

 

Build Number Knowledge Base Article ID Comment
2.0.4276.0 n/a System Center Virtual Machine Manager 2008 R2 Service Pack 1 RTM
2.0.4571.0 2562466 Update Rollup 1 for System Center Virtual Machine Manager 2008 R2 Service Pack 1
2.0.4600.0 2691812 Update Rollup 2 for System Center Virtual Machine Manager 2008 R2 Service Pack 1

 


2012

 

Build Number Knowledge Base Article ID Comment
3.0.5007.0 n/a System Center 2012 Virtual Machine Manager RC
3.0.6005.0  n/a System Center 2012 Virtual Machine Manager RTM
3.0.6019.0 2686249 Update Rollup 1 for System Center 2012 Virtual Machine Manager
3.0.6040.0 2706783 Update Rollup 2 for System Center 2012 Virtual Machine Manager
3.0.6055.0 2785681 Update Rollup 4 for System Center 2012 Virtual Machine Manager
3.0.6057.0 2822776 Update Rollup 5 for System Center 2012 Virtual Machine Manager
3.0.6060.0  2861038 Update Rollup 6 for System Center 2012 Virtual Machine Manager
3.0.6062.0 2888943 Update Rollup 7 for System Center 2012 Virtual Machine Manager

 

2012 SP1

 

Build Number Knowledge Base Article ID  Release Date Comment
3.1.1042.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 CTP1
3.1.3010.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 CTP2
3.1.3612.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 Beta
3.1.5016.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 RC
3.1.6011.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 RTM
3.1.6018.0 2785682 Update Rollup 1 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6020.0 2802159 Update Rollup 2 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6027.0 2836751 Update Rollup 3 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6032.0 2879276 Update Rollup 4 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6038.0  2904727  Update Rollup 5 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6046.0 2932860 Update Rollup 6 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6084.0 2965089  2014-07-29 Update Rollup 7 for System Center 2012 Virtual Machine Manager Service Pack 1

2012 R2

 

Build Number Knowledge Base Article ID Comment
3.1.7200.0 n/a System Center 2012 R2 Virtual Machine Manager Preview
3.2.7510.0  n/a System Center 2012 R2 Virtual Machine Manager RTM
3.2.7620.0 2904712 Update Rollup 1 for System Center 2012 R2 Virtual Machine Manager
3.2.7634.0 2932926 Update Rollup 2 for System Center 2012 R2 Virtual Machine Manager
3.2.7672.0 2965414  Update rollup 3 for System Center 2012 R2 Virtual Machine Manager
3.2.7768.0 2992024 Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager
3.2.7828.0 3011473 Update Rollup 5 Preview for System Center 2012 R2 Virtual Machine Manager

VMM 2012 – Cluster Overcommit algorithm

The Cluster overcommit algorithm can be used to explain when VMs will not start on a cluster (even when it appears there is enough memory to start),

http://support.microsoft.com/kb/3023928

VMM Error 25122

This error can occur after manually adding a Hyper-V cluster to VMM 2012 R2. It appears to occur because the Cluster Virtual IP address exists in the IP pool

 

VMM 25122

The script is below, credits to vNikkas who has also blogged about this (there was another version floating around last year too I believe).

$ID = Enter the ID found in the error message (you can copy the text, paste into notepad and then copy the ID

$IPPoolName = Enter the name of the IP pool associated with the error message


If (-not (Get-Module virtualmachinemanager)) {
Import-Module virtualmachinemanager }

$IP = Get-SCIPAddress | Where-Object {$_.ID -eq $ID}
$IPPool = Get-SCStaticIPAddressPool -Name $IPPoolName
# Looking up DNS Name based on IP Address
$VMHostClusterName = [System.Net.Dns]::GetHostbyAddress($IP.Name)
$VMHostCluster = Get-SCVMHostCluster -Name $VMHostClusterName.HostName

# Giving the IP Address back to the IP Pool
Get-SCIPAddress -IPAddress $IP | Revoke-SCIPAddress

# Allocating the IP Address to the VM Host Cluster
Grant-SCIPAddress -GrantToObjectType HostCluster -GrantToObjectID $VMHostCluster.ID -IPAddress $IP.Name -StaticIPAddressPool $IPPool -Description $VMHostCluster.Name

Follow

Get every new post delivered to your Inbox.