Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

If No DHCP Server Is Available When a Windows Virtual Machine Is Customized, the Virtual Machine Might Not Be Able to Join a Domain (2262)

Details

After I've customized a virtual machine, why is the virtual machine not able to join a domain?

Solution

When you customize a virtual machine with a static IP address, the customization process assigns the IP to the network card during the final boot of the virtual machine. Joining a domain occurs before that, during the second boot. If no DHCP server is available during this second boot, the network card does not get a temporary IP address, and the virtual machine is not able to join a domain. During the third and final boot, the static IP addresses get assigned, but the "domain join" step is not performed again. The result is a virtual machine that is not part of the domain.

To solve this problem, make a DHCP server available so that the customized virtual machine gets a temporary IP address and joins the domain before a static IP is assigned.

Keywords

2262

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

1 2 3 4 5
0 Ratings

1 2 3 4 5
0 Ratings

Actions

Bookmark Document

KB:

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)