Dears,
recently I met a strange problem when using Horizon PowerCLI with VSAN environment.
I created a automatic linked clone pool with VSAN environment and required a daily scheduled task to disable/enable this pool.
The solution I found is via Horizon PowerCLI - update-automaticlinkedclonepool.
Although I tried the PowerCLI quite fine in my lab, I had no luck when deploying the script to the production.
The scripts (or the command) are almost the same between lab and production, just like following:
Update-AutomaticLinkedCLonePool -Pool_id {POOL_ID} -disabled $true
And the error messages:
Update-AutomaticLinkedClonePool : PowershellService::UpdateAutomaticLinkedClonePool FAILED, error=Virtual SAN functionality is not supported:Virtual SAN is not available because no Virtual SAN datastores are configured.
位於 行:1 字元:32
+ Update-AutomaticLinkedClonePool <<<< -Pool_id {POOL_ID} -disabled $true
+ CategoryInfo : InvalidResult: (vmware.view.pow...LinkedClonePoo
l:UpdateAutomaticLinkedClonePool) [Update-AutomaticLinkedClonePool], Excep
tion
+ FullyQualifiedErrorId : PowershellService::UpdateAutomaticLinkedClonePoo
l FAILED,vmware.view.powershell.cmdlets.UpdateAutomaticLinkedClonePool
If I changed the pool setting with using not VSAN and the desktops still stayed in VSAN, the script ran normally as expected.
Once the setting change back to use VSAN, it failed again with the same error messages.
There is no such issue in my lab (the same horizon version 6.0.2 / ESXi 5.5 update 2).
Desktop pools in VSAN are still workable with the enable/disable script.
Could anyone give me some hints to do with this issue?
I would appreciate a lot!
Regards,
Joe