Spaces in LDAP

With one of our deployments of VMware View we had problems with the linked clones. Adding the computer accounts to Active Directory failed everytime. Even after recreating the pool it failed. Computer accounts weren’t created in Active Directory.

After a lot of troubleshooting, logfile reading and consulting with VMware Support a colleague said: Why are you entering spaces in the LDAP path?

OMG, you’re kidding. Did I enter spaces in the LDAP path? NO WAY. Stupid, stupid me.

I know, I know, you’re not supposed to use spaces in LDAP. We checked everything, from server to configuration, but never, not once, I suspected spaces in my LDAP path. One of the good things of this search for errors though was that we triple checked the configuration and found nothing out of the ordinary (except of those pesky spaces).

So VMware, please add a browse window for the location in AD to prevent my stupid mistakes

Guest customization in VirtualCenter 2.5 fails

Tags: View

This entry was posted on Monday, May 18th, 2009 at 09:34 and is filed under VMware. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

About Anne Jan Elsinga

Anne Jan Elsinga is a Consultant for Imtech ICT in the Netherlands. He spends his working hours with a lot of virtualization stuff, from feasibility to implementation for server virtualization/consolidation and desktop virtualization. In 2009, 2010 and 2011 he was awarded with the VMware vExpert status. In the night time he dances latin, ballroom and salsa and he also discovered the pleasure of diving.

http://www.nikemaxsale.com air max shoes

Well , the view of the passage is totally correct ,your details is really reasonable and you guy give us valuable informative post, I totally agree the standpoint of upstairs. I often surfing on this forum when I m free and I find there are so much good information we can learn in this forum!