<?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 Issues with VSC in Powershell in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140807#M9315</link>
    <description>&lt;P&gt;Hello. We're trying to use CLI commands in Powershell to create a datastore and LUN the same way as we do in the VSC plugin in the vSphere client. Here is the command (specific names have been changed for security): "Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname -datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -svm svmname". Here is the output we're receiving:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PS C:\Users\Administrator&amp;gt; Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname -datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -blockSize 1 - svm svmname Add-VscDatastore : A parameter cannot be found that matches parameter name 'blockSize'. At line:1 char:200 + ... atastoresize 5 -blockSize 1 -svm svmname+ ~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Add-VscDatastore], ParameterBindin gException + FullyQualifiedErrorId : NamedParameterNotFound,VSC.AddDatastore PS C:\Users\Administrator&amp;gt; Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -svm svmname Add-VscDatastore : Objectreference not set to an instance of an object. At line:1 char:1 + Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostNam ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Add-VscDatastore], NullReferenceException + FullyQualifiedErrorId : System.NullReferenceException,VSC.AddDatastore".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any assistance would be appreciated.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 13:37:50 GMT</pubDate>
    <dc:creator>PeteK001</dc:creator>
    <dc:date>2025-06-04T13:37:50Z</dc:date>
    <item>
      <title>Issues with VSC in Powershell</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140807#M9315</link>
      <description>&lt;P&gt;Hello. We're trying to use CLI commands in Powershell to create a datastore and LUN the same way as we do in the VSC plugin in the vSphere client. Here is the command (specific names have been changed for security): "Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname -datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -svm svmname". Here is the output we're receiving:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PS C:\Users\Administrator&amp;gt; Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname -datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -blockSize 1 - svm svmname Add-VscDatastore : A parameter cannot be found that matches parameter name 'blockSize'. At line:1 char:200 + ... atastoresize 5 -blockSize 1 -svm svmname+ ~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Add-VscDatastore], ParameterBindin gException + FullyQualifiedErrorId : NamedParameterNotFound,VSC.AddDatastore PS C:\Users\Administrator&amp;gt; Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostName samplehostname datastoreProtocol VMFS -containerName samplevolume -isThin $true -datastoresize 5 -svm svmname Add-VscDatastore : Objectreference not set to an instance of an object. At line:1 char:1 + Add-VscDatastore -storageSystemId 701429001234 -datastoreName DS_testPS -hostNam ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Add-VscDatastore], NullReferenceException + FullyQualifiedErrorId : System.NullReferenceException,VSC.AddDatastore".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any assistance would be appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:37:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140807#M9315</guid>
      <dc:creator>PeteK001</dc:creator>
      <dc:date>2025-06-04T13:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VSC in Powershell</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140820#M9316</link>
      <description>&lt;P&gt;Which version of VSC is this?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jun 2018 08:26:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140820#M9316</guid>
      <dc:creator>satishv</dc:creator>
      <dc:date>2018-06-11T08:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VSC in Powershell</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140832#M9317</link>
      <description>&lt;P&gt;The VSC version is 6.2.1P1D5. We've been using the vSphere client plugin version through many versions for several years, but this is the first time we're attempting to use it via command line.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jun 2018 13:22:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140832#M9317</guid>
      <dc:creator>PeteK001</dc:creator>
      <dc:date>2018-06-11T13:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VSC in Powershell</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140880#M9323</link>
      <description>&lt;P&gt;Please note that we've made some progress and now have a new issue. The discussion is at:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-cmdlets-in-Powershell/m-p/140879#M9322" target="_blank"&gt;https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-cmdlets-in-Powershell/m-p/140879#M9322&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jun 2018 18:05:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Issues-with-VSC-in-Powershell/m-p/140880#M9323</guid>
      <dc:creator>PeteK001</dc:creator>
      <dc:date>2018-06-12T18:05:14Z</dc:date>
    </item>
  </channel>
</rss>

