<?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 Re: New-Naigroup causes panic on 8.0.3 Sim in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57673#M2717</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Clinton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Personally, I would prefer that the it either failed, or prompted for a response.&amp;nbsp; Failing would be consistent with the CLI, prompting would be slightly more useful as it wouldn't stop a whole script running just for a small &lt;SPAN style="color: #575757; font-family: &amp;amp;quot;Arial&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 10pt;"&gt;omission.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a lot of different LUNs, VMware, Windows &amp;amp; Linux, so defaulting to Windows wouldn't be the correct response for more than 50% of our responses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not specific to Powershell, but one of biggest annoyances with NetApp user interfaces at the moment is the lack of consistency!&amp;nbsp; (e.g. useradmin user add&amp;nbsp; vs&amp;nbsp; CIFS shares -add!)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Apr 2012 07:54:39 GMT</pubDate>
    <dc:creator>david_ovenden</dc:creator>
    <dc:date>2012-04-30T07:54:39Z</dc:date>
    <item>
      <title>New-Naigroup causes panic on 8.0.3 Sim</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57665#M2715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you run New-NaIgroup and forget to put in the type it causes the 8.0.3 simulator to Panic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. if you run "New-NaIgroup igroupname -protocol iscsi".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same happens on both of my Sims, haven't tried it on a filer for obvious reasons!&amp;nbsp; The command line equivalent comes back with the an error to say the type is required.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:28:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57665#M2715</guid>
      <dc:creator>david_ovenden</dc:creator>
      <dc:date>2025-06-05T06:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: New-Naigroup causes panic on 8.0.3 Sim</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57670#M2716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, David.&amp;nbsp; This was recently brought to our attention, and yes, real 8.x filers will panic, too.&amp;nbsp; New-NaIgroup in the forthcoming Toolkit release will set the igroup type to "windows" if not otherwise specified.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Apr 2012 00:45:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57670#M2716</guid>
      <dc:creator>cknight</dc:creator>
      <dc:date>2012-04-30T00:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: New-Naigroup causes panic on 8.0.3 Sim</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57673#M2717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Clinton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Personally, I would prefer that the it either failed, or prompted for a response.&amp;nbsp; Failing would be consistent with the CLI, prompting would be slightly more useful as it wouldn't stop a whole script running just for a small &lt;SPAN style="color: #575757; font-family: &amp;amp;quot;Arial&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 10pt;"&gt;omission.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a lot of different LUNs, VMware, Windows &amp;amp; Linux, so defaulting to Windows wouldn't be the correct response for more than 50% of our responses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not specific to Powershell, but one of biggest annoyances with NetApp user interfaces at the moment is the lack of consistency!&amp;nbsp; (e.g. useradmin user add&amp;nbsp; vs&amp;nbsp; CIFS shares -add!)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Apr 2012 07:54:39 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-Naigroup-causes-panic-on-8-0-3-Sim/m-p/57673#M2717</guid>
      <dc:creator>david_ovenden</dc:creator>
      <dc:date>2012-04-30T07:54:39Z</dc:date>
    </item>
  </channel>
</rss>

