PowerCLI

 View Only

What's New

  • New PowerCLI Community

    Welcome back to the new PowerCLI Community.   We are working hard with the developers to fix the code insert issue many of you reported.   This formatted code on the previous platform but did not convert well so we are working patching all posts.   I appreciate your patience.   @Jason McClellan, Platform Admin

Search Community

Latest Discussions

  • What exactly is in the variable $vCenterServers ? Same for $tagname . When you launch a cmdlet against multiple vCenters, the cmdlet will be executed on each of these vCenters. If that Tag doesn't exist on one of the vCenters, you will get a similar ...

  • This is how to do it really fast Get-View -ViewType VirtualMachine -Server $vCenter -Property Name, Snapshot | ?{$_.Snapshot} | Sort Name | Get-VIObjectByVIView | Get-Snapshot | Select VM, Name, Description, Created, SizeMB, SizeGB, @{Name="Cluster"; ...



Latest Q&A List

  • bwadbethke's profile image

    RE: How to manually sync Content Library via power ...

    u/Teh_Fonz gave me a lead on how to fix. I changed "-Sync" to "-AutomaticSync" and now it doesn't error anymore That should ...

  • Ayman Mahmoud's profile image

    RE: Mounting Datastore and keeping signature {No Formating ...

    i am sure that both ESXi their LUNs are available in the storage devices of the esxi vcenter client, the attachment all shows ...

Recent Shared Files List Add

  • Posted in: PowerCLI

  • Posted in: PowerCLI

  • Posted in: PowerCLI

  • Posted in: PowerCLI

  • Posted in: PowerCLI

Unanswered Threads

  • Posted in: PowerCLI

    Hi Folks, I've created a script to apply the json configuration from a "Golden Master" cluster to a bunch of other clusters. Using Import-LcmClusterDesiredState on a cluster for the first seems to be fine but once a newer json is available and I ...

  • Posted in: PowerCLI

    I need to get the vVOL folder name of a VM that I am creating. I cant assume that it is the VM name because a folder could have already existing leading to the new VM's folder being VM_1. Unfortunately, because the VM is on a vVOL I cant figure out ...