Get Guestos hollow Powercli

Similar Questions

• Get-PAF * commands PowerCLI 5.8 R1 throws the error message "State HTTP 400: bad request".

  I've recently updated to PowerCLI 5.8 R1 and wanted to try the new cmdlts of PAF, but however, I go to this topic I seem to get error regardless of what below PAF Get * cmdlet I run:

  Get-SpbmStoragePolicy: 2014-12-11 14:04:50 Get-SpbmStoragePolicy therequest failed stateful HTTP 400: bad request.

  On line: 1 char: 1

  + Get-SpbmStoragePolicy

  + ~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: NotSpecified: (:)) [Get-SpbmStoragePolicy], VimExreception )

  + FullyQualifiedErrorId: Core_BaseCmdlet_UnknownError, VMware.VimAutomatio n.Storage.Commands.Cmdlets.Spbm.GetStorageProfile

  I tried to connect to the VC with the HTTPS setting - but same error Protocol.

  I thought that maybe the snap of storage had not been imported but it seems to be there:

  PowerCLI C:\ > Get-PSSnapin. Select name

  Microsoft.PowerShell.Diagnostics

  Microsoft.PowerShell.Core

  Microsoft.PowerShell.Utility

  Microsoft.PowerShell.Host

  Microsoft.PowerShell.Management

  Microsoft.PowerShell.Security

  Microsoft.WSMan.Management

  VMware.VimAutomation.Core

  VMware.VimAutomation.Vds

  VMware.VimAutomation.License

  VMware.DeployAutomation

  VMware.ImageBuilder

  VMware.VimAutomation.Storage

  I run PS4.0 with PCLI 5.8R1:

  PowerCLI C:\ > Get-VIToolkitVersion

  PowerCLI Version

  VMware vSphere PowerCLI 5.8 Release 1 build 2057893

  ---------------

  Versions of the snap

  VMWare AutoDeploy PowerCLI component 5.5 build 1983942

  VMWare ImageBuilder PowerCLI component 5.5 build 1983942

  License of VMware PowerCLI component 5.5 build 1265954

  VMware Storage PowerCLI component 5.8 build 2057894

  VMware PowerCLI VDS component 5.8 build 2031581

  VMware vSphere PowerCLI component 5.8 build 2031581

  VSphere VMware Update Manager PowerCLI 5.5 build 1302474

  PowerCLI C:\ > $psversiontable

  Value name

  PSVersion 4.0

  WSManStackVersion 3.0

  SerializationVersion 1.1.0.1

  CLRVersion 4.0.30319.18063

  BuildVersion 6.3.9600.16406

  PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}

  PSRemotingProtocolVersion 2.2

  I am running PowerCLI on a Win2k8Ent server, not locally on the vCenter.

  Any ideas? Why should he use HTTP? 5.5 and older commands work properly.

  It seems that you use vCenter 5.1, is that correct?

  Please note that the PAF for PowerShell support is for vCenter 5.5 and higher.  Prior to 5.5, the PAF API was not public.

  Alex

• I can't use the get-vdswitch cmdlet powercli

  Hey, guys:

  When I finished installing the powercli, I can use a cmdlet powercli, but when I want to get the information of VDS, FDI noticed that «the term 'get-vdswitch' is not recognized as a cmdlet, function, file, or operaable script program» \

  can someone thell me what wrroy thereon.

  THX.

  What this does?

  Get-PSSnapin-name VMware * | Select name

• Get-vmswitch causes PowerCLI HyperV query instead of vCenter

  I hope someone can shed some light on that I can't find a similar question elsewhere.

  I recently accidentally typed a powershell "get-vmswitch" command in my window PowerCLI.  Each Get-* I typed after that comes the Hyper-V installed locally instead of the vCenter server, I had been connected to the order information.

  I can repeat the behavior every time.

  PowerCLI opened on my laptop 2012 R2

  to connect-VIServer 192.168.0.16

  Get - VM displays the virtual machines managed by my vCenter Server

  Get-VM-Server 192.168.0.16 #also works

  Get-vmswitch #displays the network cards on my laptop 2012R2

  Get - vm #displays Hyper-V virtual machines on my laptop

  Get-vm-Server 192.168.0.16 # an error no parameter matches Server

  $displayviserver #displays IP address of vCenter expected

  to connect-viserver #appears to work, but all orders always work against the local machine

  My lab is a collection of portable computers running Hyper-V and ESXi.

  I know that get-vmswitch is a powershell for Hyper-V command, but how he reverse my PowerCLI session?

  Is there a way to recover the session other than powerCLI of closing and reopening it?

  LucD,

  Thank you!.  Your answer is correct.  I asked the same question about powershell.com and got the biggest part of your answer, but Peter Jurgens added:

  /********************************************************************************

  Powershell is as easy as loading the snap to access VMware cmdlets from a session:

  Add-PSSnapin vmware *.

  Who will be snap-ins starting with vmware.

  I hope this helps.

  EDIT: I came across a blog from Jeffrey Hicks on this exact issue...

  http://mcpmag.com/articles/2013/08/20/PowerShell-name-duplicates.aspx

  *******************************************************************************/

  http://PowerShell.com/cs/forums/p/19916/42912.aspx

  I added your extra bits to this thread too so anyone falling on each thread will get the most complete answer.

  Between the two of you, I learned a lot about PS and PowerCLI this week.  As an old bash-head pass to Windows/VMware, I need to continue this trend.

  enjoy,

  Von

• Get NFS via PowerCLI performance counters

  Hello

  I hope someone can help me or perhaps shed some light on my problem and I hope to propose a solution or a path to a solution.

  I need to be able to monitor the performance of e/s NFS (mainly the latency to read/write, but also the flow). I tried with the PowerCli using Get-Stat on ie. disk.deviceWriteLatency.average, but I get only for my stores of data non - NFS. I read in several places that there are some measures NFS deleted in an earlier version of vSphere, but also that some of them may actually be available again.

  I found that the statistics are available through the vSphere Client (go to an ESX host specific, Performance, advanced and click on build a graph with only my NFS data stores and only read/write latency counters.) This will produce a graph with also live-data and historical data. So I recon the ESX (or vSphere) actually knows NFS performance.

  I tried on 5.0.0 ESXi and ESXi 5.1.0 and with PowerCLI 5.1 Release 2.

  I've seen some proposals we should probe the VMs (and not the ESXi) for this information, but this seems an exaggeration of the probe of hundreds of virtual machines for more information the vSphere/ESXi server is apparently already?

  Does anyone have any suggestions or pointers to how I can get this information?

  Concerning

  Thomas

  If you want to use my Get-Stat2 function, you can do something like this

  $stat = "datastore.totalWriteLatency.average"$start = (Get-Date).AddDays(-5)
  
  Get-Datastore | where {$_.Type -eq "NFS"} | %{  $dsName = $_.Name  $uuid = $_.ExtensionData.Info.Url.Split('/')[-2]  $_.ExtensionData.Host | %{Get-View $_.Key |     Get-Stat2 -Stat $stat -Instance $uuid -Start $start -Interval HI2 |    Select Timestamp,CounterName,Interval,Instance,Value,Entity,@{N="Datastore";E={$dsName}}  }}
  

  You can do this with the ordinary Get-Stat

  $stat = "datastore.totalWriteLatency.average"$start = (Get-Date).AddDays(-5)
  
  Get-Datastore | where {$_.Type -eq "NFS"} | %{  $dsName = $_.Name  $uuid = $_.ExtensionData.Info.Url.Split('/')[-2]  Get-VMHost -Datastore $_ |    where {$_.Instance -eq $uuid} |     Select Timestamp,MetricId,IntervalSecs,Instance,Value,@{N="Entity";E={$_.Entity.Name}},@{N="Datastore";E={$dsName}}}
  

• Get-Content are PowerCLI to apply the settings to the OPS / s on all LUNS

  Hello

  I want to change the settings of IOPS / s by default all LUNS, I found it a bit tedious to do it for each LUN. What I want to do is put all the WWN LUN name to a file and read the file to apply

  esxcli storage nmp psp roundrobin deviceconfig set --type=iops --iops 1  --device=
  

  Get-Content C:\LUNPaths.txt | esxcli I do not know how to do it in esxcli.

  Thank you

  You can read the name WWN in a table and then use the Contains operator to check if the current device belongs to your list of targets.

  Something like that

  $wwn = Get-Content -Path C:\WWN.txt
  $esxHosts = Get-VMHost -Location $mycluster | Sort Name foreach($esx in $esxHosts)
  {
      $esxcli = Get-EsxCli -VMHost $esx    $esxcli.storage.nmp.device.list() | where {$wwn -contains $_.Device}| %{
          $esxcli.storage.nmp.psp.roundrobin.deviceconfig.set($null,$_.Device,1,"iops",$null)
      }
  }
  

• How to get host ESX PowerCLI using network details (IP address)?

  Hello

  I'm using script below to get (generation Version, ESX host name, name of the Cluster, datacenter, IPaddress (Service & Vmkernel console))

  -

  ---

  SE connect-VIServer *-user *-password *.

  Get-vmhost (Hostname). Select name, Version, Build,

  @{N = "Cluster-Name"; E={@(($_ | {{(Get-cluster))}}.

  @{N = 'Center'; {E = {Get-Datacenter - VMhost $_}},

  @{N = 'Service Console'; E={@(($_ | {{(Get-vmhostnetworkadapter))}}

  -

  ---

  Output as follows:

  -

  ---

  Name               : *******

  Version: version 3.5.0

  Build: 207095

  The cluster name:

  Data Center: *.

  Service-Console: {vmnic1, vmnic0, vmnic6, vmnic7...}

  -

  ---

  Can some please help me how to change above script to include the IP address of the Console of Service & VMkernel... Thanks in advance...

  You can extend your script with the IP addresses of the VMKernel and Service Console like this:

  Get-vmhost (Hostname) | Select Name, Version, Build,
  @{N="Cluster-Name";E={@(($_ | Get-cluster))}},
  @{N="Datacenter";E={Get-Datacenter -VMhost $_}},
  @{N="Service Console";E={@(($_ | Get-vmhostnetworkadapter | Where-Object {$_.PortGroupName -eq "Service Console"}).IP)}},
  @{N="VMKernel";E={@(($_ | Get-vmhostnetworkadapter | Where-Object {$_.PortGroupName -eq "VMKernel"}).IP)}}
  

  Best regards, Robert

• Error when using Get-compliance in PowerCLI.

  Hi, I tried to use some PowerShell scripts on my VM to do some Manager Update update working, but when I run the command, for example, Get-compliance, error message is displayed.

  API version ' 2.52' for vCenter Server xxx is not supported. "

  + CategoryInfo: InvalidOperation: ( , NotSupportedException)

  + FullyQualifiedErrorId: Insufficient_VIM_API_Version, VMware.VumAutomation.Commands.GetCompliance

  Someone at - he lived the same error before? How to solve this problem? Thank you!

  The Release Notes say that you should be to Update Manager 4.0 Update 1.

  Judging from the message (API 2.52) you are using Virtual Center 2.5.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Get-connectionbroker not allowed for additional user PowerCLI

  Hi all

  We lack vSphere 5.1, 5.2 view Horizon with PowerCLI 5.5r2 on a victory 2k8R2 box and everything was rosey until we tried to run PowerCLI cmdlets as another user who has installed the program initially. We tried to run cmdlets (get-connectionbroker specifically) PowerCLI as another user, who was a member of the local Administrators group and received the error FAILED, error = not allowed.

  I can run get-VIServer and get - VM successfully in the same session from client, but not get-connectionbroker. If I run PowerCLI as long as user, I initially installed the program I can run all these commands without error. Am I missing a permission somewhere? The new user account is also a Director in vCenter to root. I'm trying to connect to our servers to view connection Horizon, but can't seem to. Any ideas?

  Thank you

  Thomas

  The solution was to grant the user new rights of administrator account in view administrator himself.

• How to calculate the CPU Ready on Cluster DRS via Powercli?

  Hi all!

  I have a DRS Vsphere cluster. I want to know what is the value of the loan of CPU I have in my group.

  For example, I get 20% of powercli value, it is normal for the cluster, but if I have 100% or more, I have a problem.

  How to achieve via Powercli? And how to calculate the percentage values correctly?

  I know, I can get all values of CPU Ready of VMs cluster, but IT is not the same thing, I need overall value of CPU Ready.

  Thanks in advance!

  As far as I know you can get the cpu.ready.summation for ESXi nodes or VMs.

  For a cluster, you will need to get the value of each node in the cluster ESXi and then take the average.

  The metric cpu.radey.summation is expressed in milliseconds.

  To get a percentage, you need to calculate the percentage of loan period during the interval during which it was measured.

  Something like this (this will give the loan current %)

  $clusterName = "mycluster.

  $stat = "cpu.ready.summation".

  $esx = get-Cluster-name $clusterName | Get-VMHost

  $stats = get-Stat-entity $esx - Stat $stat - Realtime - MaxSamples 1 - forum «»

  $readyAvg = $stats | Measure-object-property - average value. Select - ExpandProperty average

  $readyPerc = $readyAvg / ($stats [0].) IntervalSecs * 1000)

  Write-Output "Cluster $($clusterName) - CPU % loan $(' {0:p}'-f $readyPerc).

• Identify DIMM memory installed using PowerCLI

  Hi guys,.

  Does anyone know how identify the DIMM memory installed using PowerCLI?

  With the help of smboisDump, I get the following

  MEMORY: 25 #.

  Geographical area: "DIMM_A1.

  Bank: "CPU 1 CHANNEL 0 DIMM 1.

  Manufacturer: '0xCE00 '.

  Series: "35F3A656."

  Part number: "M393B1K70DH0-YH9".

  Matrix memory: #23

  Form factor: 0 x 09 (DIMM)

  Type: 0 x 18 (DDR3)

  Detail of type: 0 x 2000 (registered)

  Data width: 64-bit (bit ECC + 8)

  Size: 8 GB

  Speed: 1333 MHz

  I would like to be able to get this help PowerCLI, in particular the following information will be of interest

  • Location
  • Part number
  • Type
  • Size
  • Speed

  
  

  I need to perform upgrades memory for 50 5.5 ESXi hosts and prefer if I didn't have to read all the smboisDump files and manually copy and paste the information in Excel.

  I have looked at using get-esxcli and get-view but, do not know the correct attributes to select.

  
  

  Thank you

  
  

  OK, I seem to have bypassed the error.

  Although the CIM server on host Service showed the execution, I have restarted using the following

  CIMService = Get-VMHostService - VMHost $item | Where {$_.} Label - match "CIM Server"}

  Restart VMHostService - $CIMService HostService - confirm: $false

  
  

  After that, the previous code worked

  I found the following handy KB VMware http://kb.vmware.com/kb/1025757

  Another good blog for ESX material followed by using PowerShell is physical ESX followed with PowerShell - VMware PowerCLI Blog - Blogs from VMware

  and

  for the CIM of information https://www.vmware.com/support/developer/cim-sdk/smash/u3/ga/apirefdoc/

• PowerCLI 6.0R2 bug with Import-Module-prefix?

  Yesterday I installed a couple of nine Win2012R2 servers and of course installed PowerCLI 6.0R2.

  In order to avoid multiple commands with the same name, we use the--Prefix setting for the modules. It worked great in R1 but I am facing problems with R2.

  Load the modules with code below:

  $VMwareModules = 'VMware.VimAutomation.Core', 'VMware.VimAutomation.Vds'

  foreach ($Module in $VMwareModules) { }

  if (! (Get-Module | ? {$_. (({Name -eq $Module})) {}

  Try {

  Import-Module -Nom $Module -Prefix "VMW"

  }

  Catch {

  $ErrorMessage = $_ . Exception. Message

  breaking

  }

  }

  }

  
  

  When running Get-Module now the modules but show the Basic module shows all ExportedCommands (which he did in R1).

  Basic modules shows too, now that 'script' instead of 'manifesto', as in R1.

  Not sure if this has anything to do with this.

  
  

  If we compare the number of orders 'Raphael' in R1 and R2, missing 300 orders for the Basic module in R2.

  
  

  Is this a bug? Is there a solution?
  

  
  

  R2:

  PS C:\ > get-module

  Version of Moduleinfo name ExportedCommands

  ---------- -------    ----                                ----------------

  Script Initialize-VMware_VimAutomation_Vds 0.0

  Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Con...}

  Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, add-Type, Clear-Variable, Compare-Object...}

  VMware.VimAutomation.Core script 6.0.0.0

  Clear VMware.VimAutomation.Sdk 6.0.0.0

  6.0.0.0 binary VMware.VimAutomation.Vds {add-VDSwitchPhysicalNetworkAdapter, add-VDSwitchVMHost, E...

  PS C:\ > get-vitoolkitversion

  PowerCLI Version

  ----------------

  VMware vSphere PowerCLI 6.0 Release 2 build 3056836

  ---------------

  Component versions

  ---------------

  VMWare AutoDeploy PowerCLI component 6.0 build 2358282

  VMWare ImageBuilder PowerCLI component 6.0 build 2358282

  VMware vSphere PowerCLI component 6.0 build 3052101

  VDS's VMware PowerCLI component 6.0 build 3052101

  
  

  PS C:\ > (get-command * vmw *) .count

  33

  
  

  R1:

  PS C:\ > get-module

  Version of Moduleinfo name ExportedCommands

  ---------- -------    ----                                ----------------

  Script Initialize-VMware_VimAutomation_Vds 0.0

  Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Con...}

  Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, add-Type, Clear-Variable, Compare-Object...}

  VMware.VimAutomation.Core manifesto 6.0.0.0 {Add-PassthroughDevice, add VirtualSwitchPhysicalNetworkAd... }

  Clear VMware.VimAutomation.Sdk 6.0.0.0

  6.0.0.0 binary VMware.VimAutomation.Vds {add-VDSwitchPhysicalNetworkAdapter, add-VDSwitchVMHost, E...

  PS C:\ > get-vitoolkitversion

  PowerCLI Version

  ----------------

  VMware vSphere PowerCLI 6.0 Release 1 build 2548067

  ---------------

  Component versions

  ---------------

  VMWare AutoDeploy PowerCLI component 6.0 build 2358282

  VMWare ImageBuilder PowerCLI component 6.0 build 2358282

  License of VMware PowerCLI component 6.0 build 2315846

  VMware vSphere PowerCLI component 6.0 build 2548068

  VDS's VMware PowerCLI component 6.0 build 2548068

  PS C:\ > (get-command * vmw *) .count

  12 p

  Hello

  First of all, I must say that you are right. This is a regression introduced in 6.0 R2 caused by updates in the manifesto of the module which target to attack another bug. Let me give you more explanation in detail on the specifics of the module VMware.VimAutomation.Core.

  Binary VMware.VimAutomation.Core is always snap-in in 6.0 R1, 6.0R2 and 6.0 R3. Which is related to internal constraints that will be overcome in the next version and the binary file is converted to module as it should.

  As binary VMware.VimAutomation.Core is pluggable PowerCLI makes it look like a module declaring a manifest module which load the snap and load so its commands to load this module 'false '. The VMWare.VimAutomation.Core module so manifest module powershell that refer to a script that loads the binary VMWare.VimAutomation.Core snap. Script files, the manifesto and that loads the snap are in the module folder: '\Modules\VMware.VimAutomation.Core '.

  Now the problem you face is that, in 6.0R1, the script that loads the snap was referenced in NestedModules module manifest, which means that all orders imported as nested module are imported into the scope of the module session. This makes the component controls snap to consider as a command module and that's why your use case has worked with 6.0R1. The problem with this is that if someone calling Remove-Module command for this module it deletes the orders of the current session, and if Import-Module is called again in the same session, that it will fail with an error "The VMware.VimAutomation.Core is already added," so no commands are loaded once the module is removed from the current session. Because of this bug, we decided not to reference the script component snap load in NestedModules but in ModulesToProcess of the module manifest. When it is referenced in the ModulesToProcess that makes the script commands to be loaded in the scope of global session which means that these commands are removed from the session when Remove-Module is called and if Import-Module is called once again he will not fail because the module manifest try again to load the sanp-in. When the controls are respectively in the context that they are not affected by the specification of modules and that is why they cannot be imported with the desired prefix you want.

  To be honest we didn't know this side effect when we discussed the initial bug with Remove-Module. All these problems will be solved in the next PowerCLI release when binary VMware.VimAutomation.Core will become the module. Until then, I suggest you workaround with fixation of the VMWare.VimAutomation.Core manifest file. To do this you have need open and change of \Modules\VMware.VimAutomation.Core\VMware.VimAutomation.Core.psd1

  the following way:

  1. set ModuleToProcess on a string is empty

  2. put NestedModules to @('VMware.VimAutomation.Core.ps1')

  This will make the module to behave in the same way as 6.0R1

  Kind regards

  Dimitar Milov

• Userful info fromesxcfg-* by powercli

  I often asked by the network, info info team / vlan mac. I found myself running under cmd 3 to explain things to them. can we get this in powercli & xls?

  Mac vmhost, Nic, Nic, nic belongs to what vswitch / vmkernel ports & they IP...

  ~ # esxcfg - vmknic - l

  ~ # esxcfg - NICS - l

  ~ #

  ~ # esxcfg - vswitch - l

  Thank you

  You can do all this with the Get-EsxCLi cmdlet.

  Like this

  $esxcli = get-EsxCli - VMHost MyEsxi

  # esxcfg - vmknic - l

  {foreach ($vmk to {$esxcli.network.ip.interface.list ()})}

  $esxcli.network.ip.interface.ipv4.get($vmk.) Name) |

  Select Name,@{N='PortGroup'; E = {$vmk. The PortGroup}},@{N='IP family '; E = {'IPv4'}},

  @{N = 'IP address'; E={$_. IPv4Address}},

  @{N = 'Subnet mask'; E={$_. IPv4Netmask}},

  @{N = "Broadcast"; E={$_. IPv4Broadcast}},

  @{N = 'MAC'; E = {$vmk. MACAddress}},

  @{N = "MTU"; E = {$vmk. MTU}},

  @{N = "TSOMSS"; E = {$vmk. TSOMSS}},

  @{N = "enabled"; E = {$vmk. Activated}},

  @{N = ' Type'; E={$_. AddressType}}

  }

  # esxcfg - NICs - l

  $esxcli.network.nic.list () |

  where {$_.} Name - match "vmnic"} |

  Select Name,@{N='PCI'; E={$_. PCIDevice}},

  Driver, speed, Duplex, MACAddress, MTU, link, Description

  # esxcfg - vswitch - l

  {foreach ($vss to {$esxcli.network.vswitch.standard.list ()})}

  $vss | Select @{N = "Report name"; E={$_. Name}},

  NumPorts,UsedPorts,ConfiguredPorts,MTU,@{N='Uplinks'; E={$_. {{Links rising-join ","}}

  $esxcli.network.vswitch.standard.portgroup.list () |

  where {$_.} VirtualSwitch - eq $vss. Name} |

  Select @{N = 'Portgroup name'; E={$_. Name}},

  VLANID,@{N='Used Ports; E={$_. ActiveClients}},

  @{N = 'Links'; E = {}

  ($esxcli.network.vswitch.standard.portgroup.policy.failover.get ($_.)) Name) |

  Select ActiveAdapters - ExpandProperty) - join «,»

  }}

  }

  {foreach ($vds to {$esxcli.network.vswitch.dvs.vmware.list ()})}

  $vds | Select @{N = 'Name DVS'; E={$_. Name}},

  NumPorts,UsedPorts,ConfiguredPorts,MTU,@{N='Uplinks'; E={$_. {{Links rising-join ","}}

  $vds. DVPort |

  Select DVPortgroupID,InUse,@{N='Client'; E={$_. {{CLient-join ","}}

  }

• Data warehouses up-to-date for a pool of VMware using PowerCli

  Using this as a starting block.

  VMware View 5.2 Documentation Library

  I want to combine both functions and the variables to use ".txt files" with my new and old data warehouses listed.

  I edited a bit, combining both functions and variables for lists old and new creation, but I don't know about the context to provide variables for text files.  All PowerShell / PowerCli guru?

  # Function PowerShell to add new, then remove the old warehouses of data in an automatic pool.

  # UpdateDatastoresForAutomaticPool

  # Parameters

  # $Pool ID of the pool pool to update.

  # $OldDatastore full path to OldDatastore.txt to be removed.

  # $NewDatastore full path to NewDatastore.txt to add.

  $Pool = "C:\powercli\PersistentPools.txt".

  $OldDatastore = "C:\powercli\OldDatastore.txt".

  $NewDatastore = "C:\powercli\NewDatastore.txt".

  function RemoveDatastoreFromAutomaticPool

  {param ($Pool, $OldDatastore)

  $PoolSettings = (get-pool-pool_id, $Pool)

  $currentdatastores = $PoolSettings.datastorePaths

  $datastores = «»

  foreach ($path in $currentdatastores.split (";"))) {

  If (-not ($path - eq $OldDatastore)) {}

  $datastores = $datastores + "$path;"

  }

  }

  Update-LITERALLY-pool_id, $Pool - datastorePaths $datastores

  }

  function AddDatastoreToAutomaticPool

  {param ($Pool, $NewDatastore)

  $PoolSettings = (get-pool-pool_id, $Pool)

  $datastores = $PoolSettings.datastorePaths + "; $NewDatastore ".

  Update-LITERALLY-pool_id, $Pool - datastorePaths $datastores

  }

  Thank you

  -Matt

  You use literal strings instead of the content for the files. Assuming that the contents of the file is a list with one entry on each line, you need to change your code actually look at the data, for example:

  $oldstores = get-content "C:\powercli\OldDatastore.txt".

  foreach ($path in $currentdatastores.split (";"))) {

  If (-not ($oldstores - contains $path)) {}

  ...

  }

  }

• Get full names extended data warehouses

  Hello

  I used PowerCLI 5.1

  I am able to get the name of the data store + its first respective measure in this way:

  Get-Datastore. where {$_.type - eq "VMFS"} | % {write-host $_.} Name $(_.ExtensionData.Info.Vmfs.Extent[0])$. DiskName}

  
  

  But it simply returns a canonical name, not the full name as DGC fiber... . (< canonical name >) or Local disk from VMware (< canonical name >) which is seen in the graphical interface for a data store selected under scopes.

  It is possible to retrieve the full name of the first measure for all stores of data in a liner uses just cmdlet Get - data store ? So if there are 10 stores data only 10 datastore + extensions display names pairs will be returned similar to the highest of the output of the command.

  It is possible to get a similar output as in list of devices/paths get HBA with Powercli for peripheral column, but without having to use the cmdlets Get-VMHost, Get-VMHostHba and Get-ScsiLun because I just need 1 to 1 output to the data store and her first litter?
  

  Thank you

  Rindr

  Try like this

  Get-Datastore | where {$_.type -eq "VMFS"} |
  Select Name,
      @{N="CanonicalName";E={($_.ExtensionData.Info.Vmfs.Extent[0]).DiskName}},
      @{N="DisplayName";E={(Get-ScsiLun -CanonicalName ($_.ExtensionData.Info.Vmfs.Extent[0]).DiskName -VMHost (Get-VIObjectByVIView $_.ExtensionData.Host[0].Key)).ExtensionData.DisplayName}}