Hi, In our case, we added the AD as a LDAP Identity source as the vCenter doesn't belong to the domain. The identity source works when we add the entry below: ldap://our_domain.org:389 B...
See more...
Hi, In our case, we added the AD as a LDAP Identity source as the vCenter doesn't belong to the domain. The identity source works when we add the entry below: ldap://our_domain.org:389 But that's not the case when the traffic goes throguh ldaps and 636 port ldaps://our_domain.org:636 This only works when we add a domain controllert: ldaps://our_DC.org:636 Thank you.
It seems that the log just holds the last update comitted to the ESXi What about the previous updagrades/updates? In my case, I get the information fromt the last patch applied, not the upg...
See more...
It seems that the log just holds the last update comitted to the ESXi What about the previous updagrades/updates? In my case, I get the information fromt the last patch applied, not the upgrade from 5 to 5.5 Thank you.
Hi, Two Virtual Center with 5.1 version. Just migrated a Custom Attribute to Tag for VC1. The migration looks fine but the Tag/Category shows in the other VC, VC2, and none of the VM manage...
See more...
Hi, Two Virtual Center with 5.1 version. Just migrated a Custom Attribute to Tag for VC1. The migration looks fine but the Tag/Category shows in the other VC, VC2, and none of the VM managed by the VC1 have assigned with the migrated tag. When I try to create a Tag or Category through the vsphere web client, whatever the VC I choose from the selector from the Tags Menu, the tag always is assigned to VC2 and never to the VC1. Thank you.