Unable to join a 2008 vm to the domain in esxi 4.1

Posted on 2011-02-21
Last Modified: 2012-05-11
In our enviorment we are running a cluster with esxi 4.1. I have a number of templates configured with xp, 2003, 2008, win7. All these templates will depoly a vm and add it automacticly to our domain using a custom specs. Except for the 2008 servers. These will not join the domain. Everything is set just like the other custom specs.
Am I missing something? Is there something special I need to do for 2008?
thanks for any help
Question by:rdefino
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 5

Author Comment

ID: 34944745
Also, Once the vm is up, I can add it to the doamin just fine. No errors.
LVL 121
ID: 34944796
Do you have Sysprep installed correctly.

Do you have VMware Tools installed, and are you using the VMXNET3 driver?

Author Comment

ID: 34944830
sysprep files are needed for 2008. they are built in.

Vmtools is installed  and I am using vmxnet3 driver.

The custom spec does everything else to the vm, but adding it to the domain.
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

LVL 121
ID: 34944889
When you watch the console of the VM, do you see Guest Customization run?
LVL 121
ID: 34944917
Check the Guest Customisation Log, also are you sure the account used, as correct access to join domain, and password is correct.

Often admins, forget to specifiy the Domain Credentials, and the Domain, both are required, otherwise it will try to join the domain with a local account. not domain\username

Author Comment

ID: 34945074
I definitely see the the customization run.

Where do I find the custom logs?

Also the password I'm using is my account which has full domain rights. It's the one I use to manually push it in.
LVL 121
ID: 34945205
have check the domain account is specified correctly with DOMAIN specified. Not just username and password.

try c:\temp or c:\windows\temp

Accepted Solution

rdefino earned 0 total points
ID: 34945681
I found the problem. In the custom spec, you can't just have the domain name there. you need the
LVL 121
ID: 34945760
Glad you got it working.

Author Closing Comment

ID: 34986535
I figured it out.

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question