I'm a relatively new coder to the VM PowerCli enviornment.
And I am trying to code for automation the creation of a desktop pool and incorporate it into a Global Desktop Entitlement.
The pool, will be created from a virtual machine hosted in vSphere, and has GRID enabled.
Now, I do know the key to enable renderer3D, and what the value should be.
But, my problem comes along when trying to add this pool to a Global Entitlement.
I'm getting error thrown out that there is a mismatch with the with the 3D rendering setting between the desktop pool and the global entitlement.
Up until now, I have been using the lmvutil command, which is very clunky to use and very limited.
I'm trying to find a way to do this through PowerCLI without having to invoke lmvutil.
I know that I can get the Global Entitlement ID with the Get-HVPool cmdlet, and what it returns is not practical to use.
So I was hoping there was something similar for global entitlements, but I'm not seeing anything.
Hoping someone can point me in the right direction.
OK, so I was testing a PowerShell script that creates a manual desktop pool from a virtual machine on our vCenter and creates a Global Desktop Entitlement, and assigns a user to that as well as the newly created desktop pool.
The virtual machine does have the NVIDIA GRID GPU enabled.
When I run my script, it throws the following error:
Exception calling "Desktop_Create" with "2" argument(s): "ExceptionType : VMware.Hv.InvalidArgument
ErrorMessage : Machine Machine/NzA2ZjhkYWQtYWU2NC00Yjk4LTkxOGEtZjA1ODg1NGY0NTNj/VW5hc3NpZ25lZFZpcnR1YWxNYWNoaW5l/M2VkYzk3NTctZDcwNS00MWViLWJhODEtN2FlNT
E3ZGYyMDRi/L0RDMSAoQ2xpZnRvbiwgTkopL3ZtL1dvcmtzdGF0aW9ucy9Vc2VyL0lTL05ldE9wcy9NT05HRUxMUDAxREMx/dm0tMjU1 requires GRID, but the desktop is not enabled to support it
ParameterName : manualDesktopSpec.machines"
At C:\Users\*********\Documents\WindowsPowerShell\Modules\VMware.Hv.Helper\VMware.HV.Helper.psm1:3403 char:5
+ CategoryInfo : NotSpecified: (:) , MethodInvocationException
+ FullyQualifiedErrorId : VimException
Now, I see that it is coming from the the New-HVPool cmdlet from the module.
And the reason, because it is not enabled on the desktop, but it is.
So I am not sure where it is looking to determine if GRID is enabled on the desktop.
Through the GUI, on the Horizon Connection server everything works fine.