I'd like to use VPC 2007 to emulate a simple Active Directory on a virtual
network--in particular, one domain controller, one member server, and one
Windows XP workstation. I have plenty of RAM and drive space on my host. This
is a stand-alone host on my home network.
I set up two W2K3 SP2 VMs. I added the domain controller role to the first
VM, but it failed during the DNS setup. I manually set up DNS, but I'm not
sure it's working properly; I don't seem to be able to add the second VM to
the domain as a member server.
Before I spend too much longer trying to figure this out, is there a simple
'best practices' guide for setting up such a network? You know, things like
the VPC console settings for suggested amount of RAM, networking settings,
etc. Also, the VM settings for networking, etc.? Tips on creating the Active
Directory domain in such an environment would be helpful, too.
Chris - 27 Oct 2007 23:56 GMT
Some of the details of both VMs...
- Networking set to the Ethernet port.
- Each VM is set to DHCP and is obtaining a 192.168.1.x address.
- The VMs can ping one another by computer name.
Bo Berglund - 28 Oct 2007 08:09 GMT
>Some of the details of both VMs...
>
>- Networking set to the Ethernet port.
>- Each VM is set to DHCP and is obtaining a 192.168.1.x address.
>- The VMs can ping one another by computer name.
By what I have understood you should NOT have a domain controller get
its IP via DHCP. Servers are supposed to be rock stable and never
change their addresses, hence you should set a fixed address (in the
same subnet of course).
Bo Berglund
Bill Grant - 30 Oct 2007 05:45 GMT
I agree with Bo. If you want to use DHCP, set it up on your DC for your
other domain machines.
Put the server which you want to be the DC in Local Only and give it a
static IP in its own IP subnet. Now you can run dcpromo to create the AD
files and set up DNS. If you want to use DHCP, set it up on the DC and
authorise it in AD.
Set your other server to obtain its network config automatically and set
it also to Local Only. When you boot it up it should get its config from
DHCP on the DC. You should now be able to join it to the domain. Do the same
for the client OS.
>>Some of the details of both VMs...
>>
[quoted text clipped - 8 lines]
>
> Bo Berglund