none
Change ConfigStoreRootPath value

    Question

  • I changed the ConfigStoreRootPath value using the command:

    $path = "C:\ClusterStorage\Volume1\SharedVHDMetaForBackup"

    Get-ClusterResource "Virtual Machine Cluster WMI" | Set-ClusterParameter -Name ConfigStoreRootPath -Value $path

    Now I want to change it to be "C:\ClusterStorage\Volume3\SharedVHDMetaForBackup"

    When I run the command again with the new value I keep getting an error, I trie to run the command with the old value plus the -Delete switch, nothing happens.

    Originally the parameter had a null value.

    Any advise how to change it or just get it back to the null value?


    Please remember to mark the replies as answers if they help.

    Tuesday, May 30, 2017 8:22 AM

Answers

  • I opened a premier case with Microsoft and it is now closed as a bug. However, a workaround was offered as follows,

    • Stop the cluster service on  ALL node
    • From one node, open up the registry key
    • Click on HKEY_LOCAL_MACHINE and then click on file, then select load hive
    • Browse to c:\windows\cluster, and select CLUSDB
    • Click ok, and then name it DB
    • Expand DB, then expand Resources
    • Select the GUID of Virtual Machine WMI
    • Click on parameters, on (configStoreRootPath) you will find the value
    • Double click on it, and delete it
    • Start the cluster service
    • Then start the cluster service from all nodes, node by node

    In a future update we should be able to reset the value using PowerShell without shutting down the cluster, but for now this works.

    P.S. Running this command makes VM Groups (a new feature in 2016 that allow host level backup of VMs with shared storage) be created as shared between all cluster nodes instead of local to the host they are created on. Which is a requirement to perform the backup for guest clusters with shared storage on a Hyper-V cluster. however, for now, there's another bug so even with the store root path centralized it is still not possible.

    see this thread: https://social.technet.microsoft.com/Forums/en-US/0d6cddde-3ff3-4a50-a627-6ad7bf7667fd/cannot-create-checkpoint-when-shared-vhdset-vhds-is-used-by-vm-not-part-of-a-checkpoint?forum=winserverClustering


    Please remember to mark the replies as answers if they help.

    Monday, July 3, 2017 1:58 PM

All replies

  • You state you are getting an error.  What is the text of the error?

    What version of clustering are you running?


    tim

    Tuesday, May 30, 2017 1:43 PM
  • Hi Willy,

    Just to check if you got any progress with the issue? Welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 31, 2017 9:32 AM
    Moderator
  • I opened a premier case with Microsoft and it is now closed as a bug. However, a workaround was offered as follows,

    • Stop the cluster service on  ALL node
    • From one node, open up the registry key
    • Click on HKEY_LOCAL_MACHINE and then click on file, then select load hive
    • Browse to c:\windows\cluster, and select CLUSDB
    • Click ok, and then name it DB
    • Expand DB, then expand Resources
    • Select the GUID of Virtual Machine WMI
    • Click on parameters, on (configStoreRootPath) you will find the value
    • Double click on it, and delete it
    • Start the cluster service
    • Then start the cluster service from all nodes, node by node

    In a future update we should be able to reset the value using PowerShell without shutting down the cluster, but for now this works.

    P.S. Running this command makes VM Groups (a new feature in 2016 that allow host level backup of VMs with shared storage) be created as shared between all cluster nodes instead of local to the host they are created on. Which is a requirement to perform the backup for guest clusters with shared storage on a Hyper-V cluster. however, for now, there's another bug so even with the store root path centralized it is still not possible.

    see this thread: https://social.technet.microsoft.com/Forums/en-US/0d6cddde-3ff3-4a50-a627-6ad7bf7667fd/cannot-create-checkpoint-when-shared-vhdset-vhds-is-used-by-vm-not-part-of-a-checkpoint?forum=winserverClustering


    Please remember to mark the replies as answers if they help.

    Monday, July 3, 2017 1:58 PM
  • I opened a premier case with Microsoft and it is now closed as a bug. However, a workaround was offered as follows,

    • Stop the cluster service on ALL node
    • From one node, open up the registry key
    • Click on HKEY_LOCAL_MACHINE and then click on file, then select load hive
    • Browse to c:\windows\cluster, and select CLUSDB
    • Click ok, and then name it DB
    • Expand DB, then expand Resources
    • Select the GUID of Virtual Machine WMI
    • Click on parameters, on (configStoreRootPath) you will find the value
    • Double click on it, and delete it
    • Start the cluster service
    • Then start the cluster service from all nodes, node by node

    This workaround won't work because Cluster Service won't start. Rebot host restored old configuration ( at least) :/ In logs got "Cluster API call failed with error code: 0x80070005. Cluster API function: OpenClusterEx Arguments:  "

    My workarround which works on my environments:

    1. On all hosts update regedit value ConfigStoreRootPath in  "HKEY_LOCAL_MACHINE\Cluster\Resources\<YOUR-GUID>\Parameters"

    2. On owner cluser host update regedit value ConfigStoreRootPath in  "HKEY_LOCAL_MACHINE\0.Cluster\Resources\<YOUR-GUID>\Parameters"

    3. Restart Cluster Service on not owner host.

    4. Migrate VMs to host in 3 step

    5.Restart Cluster Service on Owner host


    Tuesday, September 12, 2017 10:35 AM
  • Question regarding step 4. Migrate VMs to host in 3 step.

    What do you mean by that?

    Should we try Live Migrating VM's to all other than Owner host, before we restart the Cluster Service on the owner host?

    Right now - we cannot change the ConfigStoreRootPath - https://www.veeam.com/kb2194

    And we cannot Live Migrate any VM's between hosts - due to this error : 

    Live migration of 'Virtual Machine SERVER1' failed.

    Virtual machine migration operation for 'SERVER1' failed at migration destination 'HOST2'. (Virtual machine ID F8AF3B95-DCA7-4756-8F85-2EC0EDBB34E8)

    'SERVER1' Failed to create Planned Virtual Machine at migration destination: The object already exists. (0x80071392). (Virtual machine ID F8AF3B95-DCA7-4756-8F85-2EC0EDBB34E8)

    The operation failed because a virtual machine with the same identifier already exists. Select a new identifier and try the operation again.


    • Proposed as answer by ianc3 Friday, August 17, 2018 9:19 PM
    Friday, May 4, 2018 10:30 AM
  • So, I still cannot change this value due to this error : 

    PS C:\Windows\system32> $path = "C:\ClusterStorage\Volume5\Hyper-V\Shared"
    PS C:\Windows\system32> Get-ClusterResource "Virtual Machine Cluster WMI" | Set-ClusterParameter -Name ConfigStoreRootPa
    th -Value $path
    Set-ClusterParameter : Unable to save property changes for 'Virtual Machine Cluster WMI'.
        The request is not supported
    At line:1 char:53
    + ... ster WMI" | Set-ClusterParameter -Name ConfigStoreRootPath -Value $pa ...
    +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Set-ClusterParameter], ClusterCmdletException
        + FullyQualifiedErrorId : Set-ClusterParameter,Microsoft.FailoverClusters.PowerShell.SetClusterParameterCommand

    Have tried to take the Virtual Machine Cluster WMI offline, no luck :(

    Would be awesome if Microsoft found a fix for this bug.

    Monday, May 7, 2018 6:34 AM
  • I faced the same issue, only worked from registry.

    Please remember to mark the replies as answers if they help.

    Monday, May 7, 2018 9:29 AM
  • I faced the same issue, only worked from registry.

    Please remember to mark the replies as answers if they help.

    So exactly how did you solve this?
    Monday, May 7, 2018 10:42 AM
  • Hi Guys,

    I'm getting the same error. Willy, how did u solve this in registry?

    Thursday, July 5, 2018 3:03 PM
  • MichalKropiwnicki's solution worked for me,

    ianc

    Friday, August 17, 2018 9:20 PM