<?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 Automatic import of HPE 3PAR PowerShell Toolkit modules? in HPE 3PAR StoreServ Storage</title>
    <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7033938#M4863</link>
    <description>&lt;P&gt;First, I admit to being a Power Shell newb. I've downloaded the new 3PAR toolkit. I copied the HPE3PARPSToolkit folder into my PSModulePath, %UserProfile%\Documents\WindowsPowerShell\Modules, so I now have the .psm1 files in %UserProfile%\Documents\WindowsPowerShell\Modules\HPE3PARPSToolkit.&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Get-Module -ListAvailable&lt;/FONT&gt; shows my &lt;EM&gt;system&lt;/EM&gt; Modules directory and the modules within. It doesn't show my personal Modules folder nor the 3PAR .psm1 files.&lt;BR /&gt;While I &lt;EM&gt;can manually import&lt;/EM&gt; the 3PAR modules explicitly entering the path, I'd like to have the 3PAR modules automatically available whenever I start PS.&lt;/P&gt;&lt;P&gt;What am I doing wrong?&lt;/P&gt;</description>
    <pubDate>Thu, 07 Feb 2019 16:17:26 GMT</pubDate>
    <dc:creator>Sheldon Smith</dc:creator>
    <dc:date>2019-02-07T16:17:26Z</dc:date>
    <item>
      <title>Automatic import of HPE 3PAR PowerShell Toolkit modules?</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7033938#M4863</link>
      <description>&lt;P&gt;First, I admit to being a Power Shell newb. I've downloaded the new 3PAR toolkit. I copied the HPE3PARPSToolkit folder into my PSModulePath, %UserProfile%\Documents\WindowsPowerShell\Modules, so I now have the .psm1 files in %UserProfile%\Documents\WindowsPowerShell\Modules\HPE3PARPSToolkit.&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Get-Module -ListAvailable&lt;/FONT&gt; shows my &lt;EM&gt;system&lt;/EM&gt; Modules directory and the modules within. It doesn't show my personal Modules folder nor the 3PAR .psm1 files.&lt;BR /&gt;While I &lt;EM&gt;can manually import&lt;/EM&gt; the 3PAR modules explicitly entering the path, I'd like to have the 3PAR modules automatically available whenever I start PS.&lt;/P&gt;&lt;P&gt;What am I doing wrong?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 16:17:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7033938#M4863</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2019-02-07T16:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic import of HPE 3PAR PowerShell Toolkit modules?</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7033989#M4864</link>
      <description>&lt;P&gt;I have the same problem. The older version works like expected. The install guide of the older version includes "Copy the files to &amp;lt;psmodule-path&amp;gt;". This part is missing in the new version, but even when you do it, it does not work. I tried the "old" system wide path in system32, the new one in program files, and the personal one. And the manual import takes too long to include a "import-module ..." in every script.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 06:26:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7033989#M4864</guid>
      <dc:creator>apol</dc:creator>
      <dc:date>2019-02-08T06:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic import of HPE 3PAR PowerShell Toolkit modules?</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7034447#M4874</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;A "well-formed" module is a module that is stored in a directory that has the same name as the base name of at least one file in the module directory. If a module is not well-formed, Windows PowerShell does not recognize it as a module.&lt;/P&gt;&lt;P&gt;The "base name" of a file is the name without the file name extension. In a well-formed module, the name of the directory that contains the module files must match the base name of at least one file in the module.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/powershell/developer/module/installing-a-powershell-module" target="_blank"&gt;https://docs.microsoft.com/en-us/powershell/developer/module/installing-a-powershell-module&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I also had to right click the .psm1 files, go to Properties, and check the "unblock" since these files were downloaded from teh evil internets.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2019 14:16:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/automatic-import-of-hpe-3par-powershell-toolkit-modules/m-p/7034447#M4874</guid>
      <dc:creator>rmay_bk</dc:creator>
      <dc:date>2019-02-12T14:16:17Z</dc:date>
    </item>
  </channel>
</rss>

