We found out that this is clearly AD credentials issue. When we create local user@vsphere.local and give him the same privelegies it works like a charm in both Web and Classic client.
↧
Channel:
VMware Communities: Message List
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: VMware Communities: Message List
- Channel Number: 20038825
- Language: English
- Registered On: June 30, 2013, 8:21 am
- Number of Articles: 231085
- Latest Snapshot: November 6, 2020, 7:52 am
- RSS URL: http://communities.vmware.com/community/feeds/messages?rssusername=allb18c
- Publisher: https://communities.vmware.com/?view=discussions
- Description: Most recent forum messages
- Catalog: //vmware1620.rssing.com/catalog.php?indx=20038825
© 2025 //www.rssing.com