Get folder size on Cluster Shared Volume (CSV) Hyper-v

In VMM or Failover cluster manager there is no way to view the total size of the directory’s on the ClusterSharedVolumes (CSV).
Ive made a simple script to determine the size of a folder.

Run this script against a Hyper-v node in a cluster.


Hyper-v VM migration with VMM Powershell

Somethimes you need to bulk migrate some Hyper-v virtual machines.
This is not possible with the VMM gui.

In this situation PowerShell can help:
Filter on VMname

Replace the $VM line when you need to migrate all the machines placed on a specified host:





List all Hyper-v snapshots with the VMM PowerShell Module

There is no place where you can find an overview from all Hyper-v snapshots in the VMM Gui.
In this situation PowerShell is your friend. With a few lines of PowerShell code is this overview simple to make.

Run this commands in an elevated PowerShell  prompt where you installed the VMM Console:



Get Hyper-v snapshot with Powershell

List Hyper-v VM Snapshots.
With this PowerShell command you can search for snapshots on a Hyper-v node.

List all snapshots within a Hyper-v cluster.
With this script you can search for all checkpoints on a Hyper-v cluster.

Extend Cluster shared volume (CSV) Hyper-v

The first step is to extend the lun on your storage device.
Then, look into your failover cluster manager to find the owner of the CSV.
This can be found in the Storage -> Disks section under Current Owner.

Log into the CSV owner node and type in a elevated command prompt:
1. Type Diskpart
2. Type Rescan
3. Type List volume
4. Type Select Volume (wich you have extended on the storagebox)
5. Type Extend


Enable disk performance counters Windows server 2012 / R2 taskmgr

In Windows server 2012 / R2 you doesn’t see the disk performance counters in Task Manager as you see in Windows 8.1.

Disk performance counters Windows 8

The simple solution for this is:

Open Powershell:
diskperf -y

Close the current taskmgr, and open a new one.
Voila. Really simple isn’t it?

IBM Storage management pack SCOM

With the SCOM management pack for IBM you can monitor the following systems:

  • DS8000
  • Flex Systems
  • SAN Volume Controller (SVC)
  • Storwize V3500
  • Storwize V3700
  • Storwize V5000
  • Storwize V7000 & Unified
  • XIV Systems

Logon to your storage system. Add a user for monitoring purpose in the monitoring user group.
Be sure that port 22 is open from the SCOM landscape to the IBM Management Addresses.

Download the newest IBM_Storage_MP_for_SCOM_#.#_Windows setup from the IBM site.
Install the IBM Storage SCOM-control utility.

Import the SCOM management packs, the setup placed them on:
C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\mps

Open the configuration utility command line.

Link IBM Storage SCOM-Control utility with SCOM:
scomu.cmd --sc-set --servername scomsrv01 --domain domain01 --username usr --password pass


  • Password authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode password --username ### --password ###
  • Public key authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode publickey --username ### --certpath c:\storwize.cert --passphrase xxxxx

List the added storage systems:
scomu.cmd --list

Delete a connection:
scomu.cmd --del -t storwize.v7000 --ip

Cannot access ADMIN$ share using a local administrator account

When the computer is not in a Domain and you must reach the admin$ share with a local administrator you have to edit the registry.

Test if you can access ADMIN$ share with a user who is member of the local administrators group.
If not, test it with the standard builtin administrator account. If this works try the following registry setting:

You need to add a new DWORD value in the registry.

Run -> Regedit
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Add a new DWORD Value called: LocalAccountTokenFilterPolicy and give it the value of 1.


Reboot the system.

Remove Temporary Template SCVMM

When you manually remove a .VHD file from the library, is it possible that you cannot remove the template from the SCVMM library. The template has some Temporary  Template dependencies on it. On the dependencies tab in your template configuration file you see the Object that is linked.


Double click on the linked object and copy the name.

Open a Virtual Machine Manager Powershell

remove-scvmtemplate -vmtemplate "Temporary Template1c2fe 00e-4d16-4975-b85b-8c4fad34fff5"

Once runned the linked temporary template has been removed and you are able te remove te template.