<?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: Types.ps1xml and Format.ps1xml in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52622#M2465</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Glenn and Andy.&amp;nbsp; Yes, the Toolkit can be information overload when using it as a CLI, and while it's hard to know which fields are important to any given user, there are some that aren't terribly interesting.&amp;nbsp; We'll consider including type formatters in the future for common object types, but the examples y'all have posted work fine and should help others tailor Toolkit output to serve their needs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Jul 2010 20:20:32 GMT</pubDate>
    <dc:creator>cknight</dc:creator>
    <dc:date>2010-07-13T20:20:32Z</dc:date>
    <item>
      <title>Types.ps1xml and Format.ps1xml</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52602#M2458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I Understand that this is still a very early release, and you're still working you're way through the OnTAPI, but we need some formatters make the toolkit usable as a CLI.&amp;nbsp;&amp;nbsp; I've used PoshOnTAP as my primary means of managing our filers for over two years now.&amp;nbsp; I tried to switch to the supported toolkit, but the output is of no use from the CLI.&amp;nbsp; It's simply information overload... because I've been through this once already with PoshOnTAP, I wrote an example for you...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a template I've always used FilerView.... I know, I know... but *most* Windows sysadmins don't administer NTAP Full time, and FilerView is their interface (SystemManager is getting there).&amp;nbsp; The closer you mimic FilerView's data the easier it is for them to translate the GUI to the CLI.&amp;nbsp; Everything is still available for scripting, but if you trying to manage a volume, lun, snapshots, etc from the CLI it's much easier.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attached is what I'll be using until you fix it &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.0.8/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;~Glenn&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:12:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52602#M2458</guid>
      <dc:creator>glenn_sizemore</dc:creator>
      <dc:date>2025-06-05T07:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Types.ps1xml and Format.ps1xml</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52608#M2461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Glenn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your input is greatly apriciated.&amp;nbsp;&amp;nbsp; You are correct that the Data ONTAP PowrShell Toolkit is in it's infancy.&amp;nbsp; Any advice you have to give can only make it better going forward.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;J&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jul 2010 18:48:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52608#M2461</guid>
      <dc:creator>fjohn</dc:creator>
      <dc:date>2010-07-06T18:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: Types.ps1xml and Format.ps1xml</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52617#M2463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I definitely agree with Glenn. I went ahead and created a PSD1 file, a types and a format file for the DataOntap module. For our stuff, we are working with Luns and Volumes more than anything else so I just have entries for their corresponding types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've attached what I put together.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jul 2010 20:04:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52617#M2463</guid>
      <dc:creator>aschneider146</dc:creator>
      <dc:date>2010-07-13T20:04:56Z</dc:date>
    </item>
    <item>
      <title>Re: Types.ps1xml and Format.ps1xml</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52622#M2465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Glenn and Andy.&amp;nbsp; Yes, the Toolkit can be information overload when using it as a CLI, and while it's hard to know which fields are important to any given user, there are some that aren't terribly interesting.&amp;nbsp; We'll consider including type formatters in the future for common object types, but the examples y'all have posted work fine and should help others tailor Toolkit output to serve their needs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jul 2010 20:20:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Types-ps1xml-and-Format-ps1xml/m-p/52622#M2465</guid>
      <dc:creator>cknight</dc:creator>
      <dc:date>2010-07-13T20:20:32Z</dc:date>
    </item>
  </channel>
</rss>

