As you might have noticed, it is not possible to remove an Endpoint in Advanced Services, the only option offered is to edit an existing endpoint. There is a little trick however you can use to circumvent this:
- To remove an ASD Endpoint, go to Administration, Advanced Services, Server Configuration and change the VCO to external when using internal or vice versa. You will see a pop up stating that this will destroy all configured ASD endpoints (don’t worry, it will not remove your standard endpoints).
- Click OK and after that set the VCO back to its original setting. When using an external VCO for production, the configuration entries are still in the cache, you only might need to retype the password when using ‘Basic” as user type.
- Finally go to Endpoint and add a new Endpoint: AD, HTTP REST, SOAP or vCenter Server.
Final tip: before you remove your endpoints, describe how they are configured. Write down all specifics and make a snapshot of your vCAC appliance so if need be, you can revert to your previous state.
Last night, while watching the weird football match between Brazil and Germany (final result 1-7!), I received a tweet from @vExpert saying that the vExpert 2014 Q2 announcement was available online. (See https://t.co/KxFGL0qJ17 )
I didn’t receive any e-mail messages from VMware regarding this subject yet, so I assumed that the title had evaded me, that I had not done enough to prove myself worthy.
First a bit more about the vExpert program:
vExpert is an yearly award given by VMware to IT professionals that contribute to the VMware community by sharing information with colleagues, customers, partners using blogs, presentations and other forms of communication. Or, as VMware states it herself, “A vExpert, in the simplest of terms, is an active member of the VMware community who imparts his/her advanced knowledge on others. VMware is exceptional at developing community; it’s really the industry standard in this regard. The vExpert program is a way of recognizing people who participate in the community and increase awareness of VMware products and uses. It’s quite genius really; it encourages people to market VMware and grow its ecosystems.“
Anyway, I clicked the link in the tweet and searched for my name and… Wow! That’s awesome! So, I’m very happy and proud that I can tell you that I’m a vExpert for 2014
I want to congratulate all new and returning vExperts from both Q1 and Q2 2014 and would like to encourage everyone to help improve the community by sharing knowledge! Write blogs, tweet about your knowledge and experience (unless covered by NDA) and apply for the vExpert programm. Enrollment for Q3 is still open: http://bit.ly/LMJqB5
We’ve been working very hard with VMware Support Engineers and Developpers over the last two weeks and they did a great job fixing our vCAC environment together with us. It is very hard to detect what was causing the problem exactly. most likely it was a combination of small p.e.b.k.a.c. errors and bugs in the software we stumbled upon in our particular implementation. VMware Tech Support requested some hot fixes and we are waiting for those, or vCAC 6.1, which ever comes first.
But here are just acouple of tips that might prevent you from running into similar problems:
- when changing certificates, do not use an intermediate CA;
- when changing certificates follow the VMware documentation meticulously, do not change the order in which you deploy the certs;
- using vCenter Orchestrator in stead of the VCO appliance is a bit more of a challenge, so you might be better of using the VCO appliance or the built-in VCO;
- using a supported edition of vCenter SSO is more challenging compared to the vCAC SSO appliance.
All in all, although we had very defiant problems, vCAC remains a stable environment. Just never forget to think in chains, it’s not a single product, rather a multi-tiered application, even in a single install. In the coming months we’ll be building a distributed setup of vCAC 6.0 or 6.1. When we’re done I´ll write a blog about that and any issues we might have encountered.
PS: p.e.b.k.a.c. = problem exists between keyboard and chair