Get "specified VMs is not found" when using Add-ManualPool in view PowerCLI

Add-ManualPool-pool_id MyPoolName displayName - MyDisplayName - powerPolicy AlwaysOn - autoLogoffTime immediately - isUserResetAllowed 1 - allowMultipleSessions 1 - vc_id ' % IDREMOVED % ' defaultProtocol - PCOIP - allowProtocolOverride 1 - id ' VirtualMachine-VM-75557 "»

This is the command I am trying to use.  I am just running directly in with the cmdlet view loaded PowerCLI powershell command window.  The Virtual Machine name (-id) is obtained using the command Get-DesktopVM, so I know it's good.  I tried with a couple of virtual machines.  The query Get-DesktopVM also States that isInPool = false so that can't be buggered me upward.

Here is my result when you use the command above.

Add-ManualPool: PowershellService::AddManualPool FAILED, error = one or more of the specified virtual machines is not found. Continued lack of VM-75557
On line: 1 char: 15
+ Add ManualPool < < < < - pool_id MyPoolName displayName - MyDisplayName-AlwaysOn - autoLogoffTime immediately - isUserResetAllowed power politics 1 - allowMultipleSessions 1 - vc_id ' % IDREMOVED % ' defaultProtocol - PCOIP - allowProtocolOverride 1 - id ' VirtualMachine-VM-75557 "»
+ CategoryInfo: InvalidResult: (vmware.view.pow... s.AddManualPool:AddManualPool) [Add ManualPool], Exception
+ FullyQualifiedErrorId: PowershellService::AddManualPool FAILED, vmware.view.powershell.cmdlets.AddManualPool

Thanks in advance for any guidance.  It seems that everything simply, it does not find the virtual machine... but the name is correct, and various data collection 'get' commands work with this ID. VM unfortunately, not much good information out there on view PowerCLI and diddly for Add-ManualPool examples.

Just tried this and I think that the field id is case-sensitive - you must use a virtual machine in tiny i.e. VirtualMachine-vm-75557

Mike

Tags: VMware

Similar Questions

Maybe you are looking for