TechOnTip Weblog

Run book for Technocrats

Archive for the ‘MsHyper-V’ Category

Find All Domain Joined Hyper-V Hosts

Posted by Brajesh Panda on September 18, 2012

Hyper-V publishes service connection point objects (SCP) under their computer accounts. If we can query for those objects we will able to find out hyper-v hosts.

Get-QADObject -Name ‘Microsoft Hyper-V’ -Type serviceConnectionPoint | Get-QADComputer -Identity {$_.ParentContainerDN}

Get-VMHost from Codeplex Hyper-V module will also pull out registered hyper-v host servers.

Here is my earlier post to find out all domain joined hyper-v virtual machines.

Posted in MsHyper-V | Tagged: | 1 Comment »

Find All Domain Joined Hyper-V Virtual Machines

Posted by Brajesh Panda on September 18, 2012

Curtsy Ask the Core Team Blog

Hyper-V Integration service “Hyper-V Heartbeat Service” always create a Service Connection Point (SCP) Object under the Computer Account. This SCP is named as “Windows Virtual Machine”. You will able to see it in ADSI Edit or using Powershell.

This object is used to differentiate the computer object from other Physical computers & virtual machines (created by other platforms). So we can query for this service connection point object, which will give us all Hyper-v Virtual Machine name in domain.

In case the object is deleted, it will be automatically re-created when the VM is restarted or the “Hyper-V Heartbeat Service” is restarted. On each restart of the service or virtual machine the integration service checks if the machine is domain joined and if it is domain joined, it checks if the service Connection Point (SCP) object exists in the domain. If the object doesn’t exist it will attempt to recreate the object.

Get-QADObject -Name ‘Windows Virtual Machine’ -Type serviceConnectionPoint | Get-QADComputer -Identity {$_.ParentContainerDN}


Get-ADObject –LDAPFilter “(&(objectClass=serviceConnectionPoint)(CN=Windows Virtual Machine))”


Get-QADObject –LDAPFilter “(&(objectClass=serviceConnectionPoint)(CN=Windows Virtual Machine))”


dsquery * Domainroot –Filter “(&(objectClass=serviceConnectionPoint)(CN=Windows Virtual Machine))”

In case of Work Group computers we have to use other query methods like WMI; Win32_ComputerSystem Class. Manufacturer property will return Microsoft Corporation & Model property will return “Virtual Machine”

Here is my another post to find out all domain joined hyper-v hosts.

Posted in MsHyper-V | Tagged: | 1 Comment »

Convert WIM to VHD or VHDX

Posted by Brajesh Panda on July 17, 2012

I hope you must have heard about WIM files. From the release of Vista these files are very much common in the OS installation process. WIM stands for Windows Imaging Format, means it is a file based disk image format. If you browse Vista, Win 7, Win 2k8 (R2) or Windows 2012 install media you will find boot.wim & Install.wim file. There are bunch of good articles about different benefits of WIM file like single instance image for multiple things, hardware independent etc. There are two tools which can be very usefull while working with wim images;

ImageX: To Create, Edit & Deploy WIM Images.

DISM: Deployment Image Service Management. Used to modify contents insides or retrieve what it contents.

So when we are installing Vista or later operating system, you don’t do file based installation like XP or older operating systems; where each file related to OS version get copied to hdd. Here OS installer just applies the WIM file to the disk. You may remember ghost images, it is somewhat same, apply the image to the target disk 😉 So technically we can apply the image file to a USB Drive or thumb drive & make it bootable. Only thing your hardware need to support to boot from that device.

Now days we are creating a lot virtual machines. Well we create golden virtual machine images & keep in our library (VHD/VMDK). And then we clone/deploy new virtual machines out of those images. But if we want to install brand new naked Windows virtual machines, we don’t need to go thru all the way thru installation process. We can convert the WIM file to a VHD file, it will create an out of factory syspreped VHD .

Let’s convert a Wim file to VHD;

You can download Convert-WindowsImage.ps1 script to convert the boot.wim file to a VHD/VHDX file. While you are downloading make sure you go thru the release notes which describes about each PowerShell parameters.

There used to be an old version called WIM2VHD.wsf script. But it has been re-written in PowerShell with VHDX support & lot of easy syntax.

If you don’t want to remember all PowerShell parameters, there is a GUI option;

  • Open PowerShell, change the directory to the folder where you downloaded above convert-windowsimage.ps1 script and run below command
  • .\Convert-WindowsImage.ps1 –ShowUI
  • It will open below UI image, populate/select necessary information & options & click make my vhd.
  • While it converting to VHD, you can see the process & progress in your PowerShell window. It took 3min to create my Windows 2012 VHDX file.
  • Then I used “new-vm -name Test2 -Path E:\VMStore\ -MemoryStartupBytes 512MB -SwitchName VM_Network -VHDPath e:\VMStore\test2\Win2k12DC.vhdx” to create my Windows 2012 VM
  • There is an “Unattended” Option; where you can input an unattended file so it will do necessary config in the target VM. We can club the conversion & VM creation to a single script. Bottom-line is we can do nice automation. Isn’t it awesome?? 😉

Posted in MsHyper-V | 8 Comments »

Hyper-v Error: A device attached to the system is not functioning (0x8007001F)

Posted by Brajesh Panda on June 25, 2012

It happened after we installed backup software & tape autoloader in the parent partition of Windows 2008 r2 hyper-v server. In our case we were using Dell equipment i.e. PowerEdge 510 & PowerValut Autoloader & Symantec 2010 R3 as backup software.

After a little bit digging I found this KB2013544 article.

Cause mentioned in this article as follows;

“There is a timing issue with FSDepends.sys and with VHDMP.sys. This timing issue occurs when certain backup programs are installed on computers that are running Windows Server 2008. By default, the FSDepends.sys start value in the registry is set to Manual. When any third-party backup software loads its tape device driver, the software can sometimes result in FSDepends.sys and VHDMP.sys not initializing correctly.”

Here is little more about FSDepend.sys & VHDMP.sys files.

I changed the registry key as stated in KB article and resolved the issue on next reboot.

Open “HKLM\SYSTEM\CurrentControlSet\Services\FsDepends”; Under the “FsDepends” key, change REG_DWORD value “Start” from “3” to “0”



Posted in MsHyper-V | Leave a Comment »

Hmm – Take it easy boys!

Posted by Brajesh Panda on June 14, 2012

Neither am I a MVP nor vExpert. I am just a technologist who loves technology & the best deal in town…

This picture is from a TechEd 2012 Slide!! Neither I am scouting for Hyper-v nor diminishing my hopes on VMware. VMware is great & I just love it. In same time Hyper-v is trying to catch up. You know, I think this competition will bring a real boost to the Virtualization era. Expecting VMware will also come back with some cool announcement during VMWorld 2012. Till then finger crossed!!

Just to note; MS Hypver-V Server 2012 is FREE, it is just the hyper-v hypervisor, not the full OS based Windows Server.

Other video & presentations;

Posted in MsHyper-V, VMware | Tagged: | Leave a Comment »

“Memory Demand” is not showing up any value in Windows 2008 R2 SP1 Hyper-v instance

Posted by Brajesh Panda on April 9, 2012

I was consolidating our RnD virtual machines to a new Windows 2008 R2 SP1 Hyper-v server. After I imported all virtual machines, configured dynamic memory minimum & maximum range for all of them! Then installed new integration pack in them because I imported those VMs from other 2008 & R2 hyper-v servers. Thought they will start using dynamic memory.

Later couple of days I got a complaint from one of my colleague his VM is pretty slow. Saw two VMs are not showing memory demand values. As these are Windows 2008 R2 Virtual machines, I was not thinking these machines don’t have SP1 installed in them. I was only concentrating on integration pack. Then I referred to my old dynamic memory notes & realized SP1 need to be installed on them. Seems like as these are test virtual machines my colleague forget to install SP1 and I overlooked them.


Posted in MsHyper-V | Leave a Comment »

VHD compact error: This request operation could not be completed due to file system limitation

Posted by Brajesh Panda on April 6, 2012

I was trying to compact my dynamically expanding VHD file of a hyper-v virtual machine. Here the error what I got;

“The system failed to compact <MyDrive>.VHD. Error code: The requested operation could not be completed due to a file system limitation.”

Event viewer error looks like below

The system failed to compact ‘S:\Virtual Machines\<server_name>\Virtual Hard Disks\VHD_C.vhd’. Error Code: 2424869

So this means we have some volume shadow copies for the drive inside the operating system. We have to remove them.

# Vssadmin list shadows

# vssadmin delete shadows /all

Well I don’t have that backup software anymore. In windows 2008 R2 there is a inbuilt command to delete shadows forcefully i.e. Diskshadow.exe.

Now I am able to compress my vhd from 130GB to 50GB. WOOOT!!

Posted in MsHyper-V | 1 Comment »

Virtual Machine Template Build & Customization

Posted by Brajesh Panda on June 29, 2011

My notes to create a VM Template & deployment method in virtual environment!

Anything else I should do – buzz me!

  1. Gold Template Configuration  – Windows 2008 R2 STD
  • Removed virtual floppy drive & other virtual parallel devices from virtual machine configuration
  • Disabled IPv6 & other ISATAP tunnel adapters completely using registry key
  • Disabled User Access Control
  • Disabled IE Enhanced Security
  • Disabled Windows Firewall for all profiles
  • Configured Windows Update to “Download updates but let me choose whether to install them” option
  • Enabled Remote Desktop using “Allow Connection from Computers running any version of Remote Desktop” option
  • Configured Time Zone to EST
  • Disabled Server Manager Auto start at logon
  • Disabled Initial Server Configuration Window Auto Start at Logon
  • Configured Task Bar as Locked
  • Configured Best Performance Option at Computer properties – >advance –> performance tab
  • Configured IE’s Default page to Blank Page
  • Cleared C:\Users\Administrator\AppData\Local\Temp folder.
  • Defragged the C drive
  • Installed VMware Tools
  • Install McAfee Base Antivirus Software. (If we plan to deploy forefront to servers right now, we can do that too)
  • Installed SP1 & latest hotfixes
  1. Run Once script – For After deployment configurations like follows;  
  • Disables Windows Firewall for Domain Profile after domain join
  • Uncheck below check marks from Network Applet’s Local Area Connection
    • QoS Packet Scheduler
    • Internet Protocol Version 6 (TCP/IPv6)
    • Link-Layer Topology Discovery Mapper I/O Driver”
    • Link-Layer Topology Discovery Responder
  • Install McAfee EPO Agents
  • Start Auto Windows Update from Command Prompt & Ask to whether to install or not! Hence even if the template is old, you will not forget to update the windows 😉
  1. vSphere Specification Manager
  • Asks NETBIOS name for the Virtual Machine & rename the Virtual Machine
  • Asks only IP Address for the Virtual Machine
  • Configures DNS, Gateway etc automatically
  • Generate New SID  for the virtual machine
  • Joins to Domain Automatically – For this job we need to create a permanent service account

Posted in MsHyper-V, VMware | Leave a Comment »

How to KILL a Hyper-v Virtual Machine?

Posted by Brajesh Panda on May 13, 2011

All virtual machines usually run as a process instance under process “vmwp.exe”. So to kill any specific virtual machine we need to find the Process ID or Virtual Machine GUID f. Then you can use Windows Task Manager /Powershell/Commadline to kill the same

I have already mentioned how to find process id or virtual machine GUID in another post. Here it is! Now let’s go ahead kill this bumpy virtual machine. As soon as you kill the virtual machine vmwp.exe will restart the same. So if you want to turn it off use turn off parameters too.

Killing Virtual Machine Using Powershell

You can save below 3 lines in a ps1 (Powershell file) & utilize the same directly.

$VMName = read-host -Prompt “Enter Virtual Machine Name”

$kill = (gwmi -q “SELECT * FROM Msvm_ComputerSystem WHERE ElementName = ‘$VMname'” -n root\virtualization).ProcessID

Stop-Process -id $kill –F

Killing Virtual Machine Using Windows Task Manager

After you found the VM GUIDs, open up Windows Task Manager, Go to Performance Tab, Click on View Menu, Click Select Columns & make sure you select PID & Command Line.

Now from Command Line Colum find out the VMWP.exe process which is referring to the above GUID. And you can kill the process afterwards. Refer to the below screenshot

Posted in MsHyper-V | Tagged: , | 4 Comments »

Hyper-V Virtual Machine Process ID & GUID

Posted by Brajesh Panda on May 12, 2011

You can find the server GUID from the VM config XML file. Usually the XML file is named as the VM Name. And you will find the config file in the Virtual Machine folder. But if you have not changed the default path for the virtual machine config folder in Hyper-V Management console you will end up having all XML config files in the same folder. Then it will be difficult to find out which file is pointing to which server.

Here are some easy methods to find out all virtual machines, their operational state, and their process ID & GUID. All these information are usually stored in WMI namespace root\virtualization & class msvm_computersystem. So we are going to query the WMI namespace & retrieve all these info. Screenshots were taken on different times after multiple time of kill operation, so process ID may be different in each screen shot ;-(

Using Powershell

Get-WmiObject -Namespace root\virtualization -class msvm_computersystem | select elementname, operationalstatus, processid, name| ft -auto

Here is another method; you can query for a specific virtual machine too.

(gwmi -q “SELECT * FROM Msvm_ComputerSystem WHERE ElementName = ‘brajesh'” -n root\virtualization).ProcessID

Where “brajesh” is the Virtual Machine Name displayed in the Hyper-v console.

Using VB Script

Here is the WMI script created by Michael which retrieves the VM GUID, BIOS GUID. Save this script as a VBS file & run it as “cscript <filename>”


Option Explicit
Dim WMIService
Dim KvpComponents
Dim VMList
Dim VMSettingList
Dim VM
Dim item
Dim setting
Dim component

‘Get instance of ‘virtualization’ WMI service on the local computer
Set WMIService = GetObject(“winmgmts:\\.\root\virtualization”)
‘Get all the MSVM_ComputerSystem object
Set VMList = WMIService.ExecQuery(“SELECT * FROM Msvm_ComputerSystem”)
For Each VM In VMList
if VM.Caption = “Virtual Machine” then
WScript.Echo “========================================”
WScript.Echo “VM Name: ” & VM.ElementName
WScript.Echo “VM GUID: ” & VM.Name
WScript.Echo “VM State: ” & VM.EnabledState

  ‘ Now get the BIOS GUID for this VM
Set VMSettingList = WMIService.ExecQuery(“SELECT * FROM Msvm_VirtualSystemSettingData”)
For Each setting In VMSettingList
Dim tempVMname
tempVMName = “Microsoft:”  + VM.Name
if setting.InstanceID = tempVMName then
WScript.Echo “VM BIOS GUID: ” & setting.BIOSGUID
end if
end if

Using this script I found my VM as “D756AC93-6711-4854-A6CE-E42B4978A505”

Posted in MsHyper-V | Tagged: , , | 1 Comment »

Windows 2008 R2 SP1 – Dynamic Memory

Posted by Brajesh Panda on May 9, 2011

Microsoft Official Article:

  1. System Requirements
    1. Install Windows 2008 R2 Service Pack 1 on Hyper-V Server – Reboot
    2. Install Service Pack 1 & new SP1 version Integration pack on Windows 2008 R2 & Windows 7 Virtual Machines – Reboot
    3. Install Security Hot fix KB2230887 & New SP1 version Integration pack on Windows 2008 SP2 Virtual machines – Reboot
    4. Upgrade (Install) Hyper-v Integration Software on Windows 2003 virtual machines – Reboot
    5. Shutdown Virtual Machine & Configure Dynamic Memory i.e. Startup RAM & Maximum RAM for the Virtual Machine.

Dynamic Memory Config

  1. Right Click virtual machine, go to settings, click on Memory; you will able to see Dynamic Memory details i.e.

Startup RAM: How much memory required for this virtual machine to boot up?

Maximum RAM: What is the maximum memory this virtual machine should scale up to in case demanded?

Memory Buffer: What is the % of physical memory on the top of the CURRENT Memory Demand this hyper-v should reserve for this VM? It can be defined between 5-2000%.

Memory Weight: Define priority of virtual machine to get their share of memory in-competition with other virtual machines When there is less physical memory available in the server for operation.

Dynamic Memory Usage Monitoring

  1. You will able to see 3 new Information tabs in the Hyper-V GUI;

    Assigned Memory:    How much memory has been assigned to this virtual machine?
    Memory Demand:    How much memory this machine needs to perform correctly; as per running workload!
    Memory Status:    It represents the memory assigned status; When VM is configured with Dynamic Memory & running; it presents three statuses i.e. OK, Warning, Low.

Assigned Memory = Memory Demand + (Memory Demand x Memory Buffer/100)

As per above formula if VM is assigned all of memory demand & memory buffer, Memory Status reports as OK.

As per above formula if VM is assigned all of memory demand & part of memory buffer, Memory Status reports as Low.

As per above formula if VM is assigned part of memory demand, Memory Status reports as Warning. This is the time when virtual machines will be experiencing performance issue. Because due to lack of physical memory it will start paging to it’s hard drive.

Here is an example;

Below VM’s Memory Demand is 2079 & Memory buffer is 5%. So theoretically Hyper-v should assign 2182.95MB (2079+(2079×5/100)) of memory. And we can see Hyper-v assigned the same to the VM.

Now to simulate more memory demand, I have elevated the buffer value to 2000%. It mean’s Hyper-v should allocate 41580MB memory. But as per available physical memory in hyper-v server, it pulled out 9000MB to assign the VM.

But assigned value is still below than the demand, so memory status went to Low.

If you want to simulate Warning, you can elevate all virtual machines maximum memory to 65536, it will allow all virtual machines to grab as much as memory available from the server, if usage of all virtual machines are high you will observe the same.

Or you may like to reserve a high amount of memory for the Hyper-v host using memory reserve concept (discussed below), so less physical memory will be available for virtual machines & they will report warning.

  1. If you like to see what is the current memory demand or how much assigned or how much committed etc. Never
    use traditional Windows TASK MANAGER inside the Virtual machine. Only refer to hyper-v GUI.

    Here is a screenshot which may clear your doubt; In Hyper-V Gui it is reporting Memory Demand is 2130MB & Assigned Memory is 2219MB. However Task manager is reporting 12945MB.

    Actually this 12945MB is the maximum amount of memory assigned to this VM till when it is started. Dynamic Memory driver inside the VM never release/update the same value for task manager.

  1. Here are some new performance counters for Dynamic Memory in the hyper-v server to track server/virtual machine usage!

  1. Memory Reserve is a new registry key has been released with Service Pack 1 to reserve certain amount of memory for the hyper-v host itself. Sometime people end up using all available physical memory in the server for Dynamic Memory, leaving no memory for the parent domain host i.e. hyper-v host itself. And management work from this partition face issues due slow response. In this case you may like to reserve certain amount of memory for the host itself. You have to create a REG_DWORD value & reboot the server for its effectiveness

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization

    RED_DWORD value

    Name = MemoryReserve

    Define the value in Decimal, reserve will be in MB.

Posted in MsHyper-V | Tagged: , , , , | 1 Comment »

Assign Pass-through or Physical Disk to Hyper-v Virtual Machine

Posted by Brajesh Panda on April 20, 2011

To assign a pass-through disk to your hyper-v virtual machine you must have a free drive/disk allocated to your hyper-v host. It can be a local drive or SAN LUN. Just to note if you have a hyper-v cluster & you are assigning pass-through disks to hosted virtual machines there are some extra steps you have to perform. I will touch upon those steps in another article.

In below picture I have assigned a new drive to my hyper-v server. And I will assign the same to my virtual machine as a pass-through physical disk.

  • Right click “Initialize the Disk”, you may like to select GPT Style for Large partition.

  • Right click & bring the disk to offline state

  • Shutdown the VM where you like to add the Pass-through Disk.
  • Go to Virtual Machine Settings, Select Disk Controller & Add HDD, Select “Physical Disk” radio button, Drop down & select the disk.

  • Start Virtual Machine & Open Disk Management tool, you will able to see Online New Drive. Below picture refer to Disk 1. Now you can create partition & start using them.

Posted in MsHyper-V | Tagged: | 3 Comments »

Extend Pass-through physical disks in Hyper-v Virtual machines

Posted by Brajesh Panda on April 20, 2011

I have a virtual machine allocated with a pass-through physical disk. I like to extend the size. How to do??

In below screen shot Disk 0 & Disk 1 both are pass-through disks. These two are two SAN Luns allocated to my Hyper-v hosts. Disk 0 pass-through disk is used for operating system & Disk 1 is used for data.

In normal circumstances if we extend the local drive or SAN LUN & we do a Disk SCAN in the operating system. After that disk management usually show us new free new space available for extension.

In case pass-through disks you will able to see new size from virtual machine settings. But virtual machine operating system will not able to see the extension free space in the pass-through drive. You have to reboot the virtual machine to see the extension.

In my lab I have extended the 9GB LUN to 19GB. Here is the screen shot of virtual machine settings


After VM reboot you will able to see the free space on Disk 1. Now you can extend the same.

Posted in MsHyper-V | Tagged: , | 3 Comments »

Configuring Live Migration & Cluster Shared Volume – Part 1

Posted by Brajesh Panda on April 15, 2011


Microsoft Failover Cluster 2008 or Microsoft Cluster Services 2000 or 2003 are designed on the basis of Nothing Shared Architecture. Hence if we want to move the virtual machines from one cluster node to other cluster node we can’t do that. Because none of the Virtual Machine LUNs are shared between two cluster nodes at the same time. In this architecture complete LUN will get transferred in case of host dies & virtual machines can be restarted. But they can’t be migrated while they are up & running like vMotion.

New Hyper-V architecture was released with Windows 2008 R2 Server which supports shared volume between nodes. It called as Clustered shared volume. This volume can be used by all nodes at the same time. All virtual machines located in this LUN can be started on any of the host. If one node dies virtual machine will get started in any other available nodes. And can be live migrated (like vMotion) to other available nodes.

In this article we will be discussing how we can enable cluster shared volume & implement live migration to make our hyper-v cluster full proof. As we discussed above to implement Live Migration we need to have Clustered Shared Volumes i.e. CSV first we will configure CSV & then live migration.

Enable Cluster Shared Volume


  1. Shared Disk Volume between cluster nodes. Make sure each node can mount this volume using cluster validation tool.
  2. Dedicated Network for CSV communication traffic in case we have large number of virtual machines are running out of the cluster. Make sure you enable “Microsoft File & Print Sharing” & “Client for Microsoft Network” features on the CSV network card

Add a Shared Storage Volume as CSV

  • Open Failover cluster manager. Right click the server name & click on Enable cluster shared Volumes

  • Accept the supportability notice & click okay. Just to note CSV only supported in Hyper-v application & this volume only should contain virtual machine config & vhd files.

  • Now you will able to see Cluster Storage Volume feature has been enabled in your failover cluster. However to make it work, we have to assign shared volume & a network adapter (optional)
  • Right click the CSV & select Add Storage

  • Select available storage volume & click okay

  • Verify configuration clicking on cluster shared volumes.
  • You can see this cluster storage disk has been mounted as a volume to C:\ClusterStorage\Volume1

  • Use windows explorer & verify the same folder from all nodes. You should able to browse around the volume1 folder from both servers. If not check the event logs for any error. Here is one of them


  • Update Hyper-V configuration to use this LUN
  • Open Hyper-V Manager Console, right click the server & go to Hyper-v settings. Update default virtual Disk & configuration location to C:\ClusterStorage\Volume1\

Add a Network Card for CSV Communication Traffic

  • You can use Get-ClusterNetwork to see all used cluster network cards in this cluster
  • If this cmdlet didn’t work you can use Import-Module Failover Clusters cmdlet to import power shell cmdlets.
  • Out of box Private Network is always configured to use for primary CSV Traffic. However there are some caveats ;-), keep reading.

  • Metric & AutoMetric attribute on each network card used to define or determine their participation in CSV Communication Network Traffic

  • The Metric setting is used to determine the priority of the network. The network with the lowest value is the most preferred for CSV
  • The AutoMetric setting identifies whether the Metric setting was set manually or automatically by the failover cluster. True means it is default

Change Values: ( Get-ClusterNetwork “Cluster Network 1” ).Metric = 1100

  • The AutoMetric setting changes from True to False after you manually change the Metric setting. This is to prevent the failover cluster from automatically assigning a Metric setting. If you want the cluster to start automatically assigning the Metric setting again, change the AutoMetric setting back to True.

Posted in MsHyper-V | Tagged: | 3 Comments »

Cluster Shared Volume ‘volume1’ (‘cluster Disk 1’) is no longer available on this node because of ‘STATUS_BAD_NETWORK_PATH(c0000be)’. All I/O will temporarily be queued until a path to the volume is reestablished.

Posted by Brajesh Panda on April 14, 2011

Symptom: You can access Volume1 from one node but not from other node. This node will through below error in the event log

Cluster Shared Volume ‘volume1’ (‘cluster Disk 1’) is no longer available on this node because of ‘STATUS_BAD_NETWORK_PATH(c0000be)’. All I/O will temporarily be queued until a path to the volume is reestablished.

Solution: Verify if you have forget to enable “Microsoft File & Print Sharing” & “Client for Microsoft Network” features on the CSV network card. This is the requirement for CSV communication.

Mostly we forget to enable these two things when we use traditional cluster private network card for csv communication.

Posted in MsFailOverClustering, MsHyper-V | Tagged: , | Leave a Comment »

%d bloggers like this: