<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Powershell Toolkit API fails with error Cluster Admin required but cmdlet in vServer family in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Powershell-Toolkit-API-fails-with-error-Cluster-Admin-required-but-cmdlet-in/m-p/163065#M6309</link>
    <description>&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use powershell to manage volumes within a Vserver creating new clones, adding snapmirrors etc etc. We have recently decided to add the volumes into a QoS Policy Group and have amended the script to apply the relevant group when performing the volume operations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As an Example we use New-NCVolClone to create a volume clone, and have now added the -QosPolicyGroup option to the call. this commandlet is in the Vserver family, yet after adding the above option it fails with an error [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You cannot use Quality of Service (Qos) feature in Vserver Context. Qos is available to cluster administrators only.]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please clarify if this a bug in the API or documentation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems strange that Qos Policy Groups are defined and applied at the Vserver level, but volumes cannot be added to the group by the Vserver admin via a normally successful api call&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 10:38:19 GMT</pubDate>
    <dc:creator>bobalon</dc:creator>
    <dc:date>2025-06-04T10:38:19Z</dc:date>
    <item>
      <title>Powershell Toolkit API fails with error Cluster Admin required but cmdlet in vServer family</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Powershell-Toolkit-API-fails-with-error-Cluster-Admin-required-but-cmdlet-in/m-p/163065#M6309</link>
      <description>&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use powershell to manage volumes within a Vserver creating new clones, adding snapmirrors etc etc. We have recently decided to add the volumes into a QoS Policy Group and have amended the script to apply the relevant group when performing the volume operations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As an Example we use New-NCVolClone to create a volume clone, and have now added the -QosPolicyGroup option to the call. this commandlet is in the Vserver family, yet after adding the above option it fails with an error [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You cannot use Quality of Service (Qos) feature in Vserver Context. Qos is available to cluster administrators only.]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please clarify if this a bug in the API or documentation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems strange that Qos Policy Groups are defined and applied at the Vserver level, but volumes cannot be added to the group by the Vserver admin via a normally successful api call&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:38:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Powershell-Toolkit-API-fails-with-error-Cluster-Admin-required-but-cmdlet-in/m-p/163065#M6309</guid>
      <dc:creator>bobalon</dc:creator>
      <dc:date>2025-06-04T10:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Toolkit API fails with error Cluster Admin required but cmdlet in vServer family</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Powershell-Toolkit-API-fails-with-error-Cluster-Admin-required-but-cmdlet-in/m-p/163076#M6310</link>
      <description>&lt;P&gt;just to add from further testing NC-NewVol and NC-NewVolclone both fail with the error defined, but update-NCvol does not report an error, but fails to assign the required QoS&amp;nbsp; policy provided in the VolumeQosAttributes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So appears to be an inconsistent approach to this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 16:14:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Powershell-Toolkit-API-fails-with-error-Cluster-Admin-required-but-cmdlet-in/m-p/163076#M6310</guid>
      <dc:creator>bobalon</dc:creator>
      <dc:date>2021-01-20T16:14:37Z</dc:date>
    </item>
  </channel>
</rss>

