VMware Cloud Community
ramoj
Contributor
Contributor
Jump to solution

GET-DesktopVM command does not work throws no object found in vmware.view.broker

Hello,

get-desktopvm cmdlet does not work and throws the error as no object found.

Other cmdlets work except get-desktopvm.

I have checked the other cmdlets they are working except the get-desktopvm, please help me.

IS there any possibility that we can unregister and re-register the vmware.view.broker snappin.

Get-DesktopVM

Get-DesktopVM : No output object

At line:1 char:1

+ Get-DesktopVM

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

    + CategoryInfo          : ObjectNotFound: (vmware.view.pow...ts.GetDesktopVM:GetDesktopVM) [Get-DesktopVM], Exception

    + FullyQualifiedErrorId : No object,vmware.view.powershell.cmdlets.GetDesktopVM

Thanks in advance.

Regards,

Naveen. S

Reply
0 Kudos
1 Solution

Accepted Solutions
ramoj
Contributor
Contributor
Jump to solution

Hi

After some research found that the communication between connection server + vcenter (included composer server) is not established and that's the reason the get-desktopVM cmdlet was unable to fetch the vm's from the vcenter and throwing the error message.

There was no issue with the module vmware.view.broker or the powershell.cmdlets.

Thanks for suggestions..

Now issue got fixed.. Smiley Happy

View solution in original post

Reply
0 Kudos
10 Replies
LucD
Leadership
Leadership
Jump to solution

Which PowerCLI version and which View version are you using?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ramoj
Contributor
Contributor
Jump to solution

Powercli 6.5.0 & VMware view 7.0.2

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Upgrade to at least 6.5R1 (better is 6.5.2), then you will have the module VMware.VimAutomation.HorizonView for working with Horizon View 7.*.

See Automating VMware Horizon 7 with VMware PowerCLI 6.5


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ramoj
Contributor
Contributor
Jump to solution

Thanks for suggestion, I am using 6.5R1 powercli verison.

But can't we get the vmware.view.broker module fixed and fix get-desktopvm cmdlet working?

Coz most of my scripts are configured with this module and cmdlets..

Thanks

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Did you already try restarting the Connection server where you run the script?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ramoj
Contributor
Contributor
Jump to solution

Yes, I have restarted the connection server.

scripts are running in connection server itself.

The other cmdlets are working fine except the get-desktopVM Smiley Sad

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

And do you get the VMs in the Admin page in a browser when logging on with the same credentials?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ramoj
Contributor
Contributor
Jump to solution

Yes, I do get the list of VM's in the view admin page and the pools.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

I'm out of ideas I'm afraid.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ramoj
Contributor
Contributor
Jump to solution

Hi

After some research found that the communication between connection server + vcenter (included composer server) is not established and that's the reason the get-desktopVM cmdlet was unable to fetch the vm's from the vcenter and throwing the error message.

There was no issue with the module vmware.view.broker or the powershell.cmdlets.

Thanks for suggestions..

Now issue got fixed.. Smiley Happy

Reply
0 Kudos