Error Invalid Active Directory Domain
Contents |
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESXi 5 > Discussions Please enter a title. You can not post a blank
Error Invalid Active Directory Domain Vcenter Appliance
message. Please type your message and try again. 1 vc_cfg_result=302 Reply Latest reply: Oct 6, 2014 6:10 PM by Richardson Porto VCSA 5.5.0 the name reference is invalid active directory U2a - Error: Invalid Active Directory domain ThugsBunny Oct 6, 2014 2:44 AM I can't join the host (VCSA 5.5.0 U2a)
The Format Of The Specified Computer Name Is Invalid Vcenter 6
to domain. I get the message: Failed to execute 'usr/sbin/vpxd_servicecfg 'ad' 'test' 'administrator' CENSORED 'domain.local' ': VC_CFG_RESULT=301(Error: Invalid Active Directory domain.)Networt is configured with static IP, hostname is set as hostname.domain.local, my domain is based on Server 2012 R2.What can I try? 2219Views Tags:
Vcenter The Format Of The Specified Computer Name Is Invalid
none (add) vcsaContent tagged with vcsa, vcenter_server_applianceContent tagged with vcenter_server_appliance, 301Content tagged with 301 This content has been marked as final. Show 1 reply 1. Re: VCSA 5.5.0 U2a - Error: Invalid Active Directory domain Richardson Porto Oct 6, 2014 6:10 PM (in response to ThugsBunny) Take a look at this blog post: vCenter Server Appliance (VSA) 5.1 – Error: Invalid Active Directory Name/Enabling Active Directory Failed | V… --- If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points. Richardson Porto Senior Infrastructure Specialist LinkedIn: http://linkedin.com/in/richardsonporto Like Show 0 Likes (0) Actions Actions Remove from profile Feature on your profile More Like This Retrieving data ... Share This Page Legend Correct Answers - 10 points
View Search vCenter Server Appliance (VSA) 5.1 - Error: Invalid Active Directory Name/Enabling Active DirectoryFailed Posted on 11 November 201214 December 2012 by Craig Today, I decided to change my vCenter from being Windows based to the vCenter Server Appliance the format of the specified computer name is invalid vmware (VSA) 5.1.0a and when I tried to enter the LDAP details for Active Directory Authentication,
Error: Srv Records Are Not Being Served.
I received various error messages: Error: Invalid Active Directory domain Error: Enabling Active Directory failed Error: Invalid SRV Records The first thing vcsa 6 active directory to always check is your DNS settings to make sure you have forward and reverse look up records set up correctly, check these are all OK. Next, I did a basic ping test to VMF-VSA01 which is https://communities.vmware.com/thread/491730?start=0&tstart=0 the name of my VSA, again all working. Ah, I thought, perhaps I have entered in something wrong on the VSA network settings, so I double checked these, again all looked good. Then I remembered, that I should be using FQDN's (Fully Qualified Domain Names) for my VSA, so rather than using VMF-VSA01 I should use VMF-VSA01.vmfocus.local Another try at authenticating, and it still failed with ‘Error: Invalid Active Directory domain'. One more try, this https://vmfocus.com/2012/11/11/vcenter-server-appliance-5-1-error-invalid-active-directory-nameenabling-active-directory-failed/ time I changed the domain to vmfocus.local and boom, we have success! So to summarise: Make sure you use a FQDN for your vCenter Server Appliance Make sure you have forward and reverse look up record for your vCenter Server Appliance Make sure your domain is entered as a FQDN Share this:Click to email (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to share on Twitter (Opens in new window)Like this:Like Loading... Related Posted in vCenter, vSphereTagged vCenter, vSphere13 Comments Post navigation ← vCenter 5.1 UpgradeMy First UKVMUG → 13 thoughts on “vCenter Server Appliance (VSA) 5.1 - Error: Invalid Active Directory Name/Enabling Active DirectoryFailed” real says: 20 February 2013 at 07:18 Thanks very much. Solved my problem. Reply Andy says: 27 February 2013 at 03:33 Reverse DNS, i cant believe it. Thankyou so much, Ive spent two hours pulling my hair out Reply Pingback: vCenter Server Appliance - Active Directory Integration Issue | vNook Kevin says: 14 May 2013 at 22:24 Hi Craig, I just had the same DOH moment. Just thought I should let you know that you're not the only one.🙂 Reply Mauricio says: 23 May 2013 at 07:17 Thank you very much, It saved my life🙂 Reply Nate jones says: 28 May 2013 at 17:03 Thanks man! Feeling DOHish too! Reply Jon says: 16
Active Directory and therefore authentication/single sign-on would no longer work. Initially I tried to remove it from the domain by un-ticking the "Active Directory Enabled" checkbox http://nokitel.im/index.php/2015/01/12/vmware-vcenter-5-5-active-directory-joindisjoin/ in VMware vCenter Server Appliance Web Console but I would always get the "Enabling Active Directory failed" error: After some time searching, I tried the following commands to join the domain but without any luck: # /opt/likewise/bin/domainjoin-cli join labdomain.local # /usr/sbin/vpxd_servicecfg ad write PASSWORD labdomain.local A quick look at vpxd_cfg.log (cat /var/log/vmware/vpx/vpxd_cfg.log) revealed the issue and this time a not so active directory vague error message: 2015-01-12 10:31:46 3565: START locking... /usr/sbin/vpxd_servicecfg ad write 2015-01-12 10:31:46 3568: [3565]BEGIN execution of: /usr/sbin/vpxd_servicecfg 'ad' 'write' '' CENSORED 'labdomain.local' 2015-01-12 10:31:46 3568: Testing domain (labdomain.local) 2015-01-12 10:31:46 3568: Enabling active directory: 'labdomain.local' '' 2015-01-12 10:31:47 3568: ERROR: Enabling active directory failed: Joining to AD Domain: labdomain.local With Computer DNS Name: vCentervAPP01.labdomain.local Error: ERROR_MEMBER_NOT_IN_GROUP 2015-01-12 10:31:48 3568: VC_CFG_RESULT=302 invalid active directory 2015-01-12 10:31:48 3568: END execution I did not want to rebuild vCenter as I configured on it vCOps and Update Manager so I thought I would try one last time to force join: Create the missing vCenter computer object in AD Logon to vSphere Web Client Go to Home > Configuration >Identity Sources tab Remove any current domain identity sources that exist Click the green cross Select as Identity source type Active Directory as a LDAP Server Complete the relevant fields with the required information Related Posts Transferring a Virtual Machine Between vSphere ESXi Hosts August 17, 2016 Deploy & Configure vSphere HTML5 Web Client March 30, 2016 Nested Windows Hyper-V Server 2012 R2 on VMware vSphere ESXi 6 March 21, 2016 One Comment Andrew December 30, 2015 at 1:05 am · Edit Thank you for your post, this lead me to a major issue and resolution for adding VCSA 5.5 to a Windows 2012R2 domain. When adding VCSA 5.5 to the domain it fails if the AD server doesn't reply with SMBv1 (SRV.sys). By default that is disabled