Vista - Hyper V on a domain controller??

Hi everyone,

Im having a issue with running HYPER V on a 2008 domain controller, and was
hoping someone could help me.

Basically we have a 2008 standard, domain controller, running exchange 2007.
It is also running DHCP and DNS service. We have setup HYPER V to run a
standard 2003 server on the same machine.

The first NIC on the server is for the 2008 machine, and the second NIC is
attached to the 2003 virtual machine.

For a while everything was working great, but I then noticed that the hyper
v nic picked up an ip address from DHCP, and the name of the 2008 server
resolves to that ip instead of its main ip!

I apologize if I have confused everyone with my explanation, but is there a
way to resolve this issue?

thank you,

Steve S

This is really not the way you should run. Using A DC and Hyper-V and
Exchange all on the same physical server along with DNS and DHCP is bound to
cause problems. In fact, this is why SBS 2008 specifically excludes support
for running on a hyper-v parent (but does support running as a Hyper-V
child.)

A better solution would be to run Hyper-V as the only role on the parent
physical computer, and virtualize your DC and other workloads. If you run
Hyper-V as the sole role on a Parent partition, you end up with the same
licensing as if you ran all your workloads on the parent. If this is
Standard, you have "1+1", if Enterprise you have "1+4" licenses. That first
"1" is the license to run a Hyper-V parent. But ONLY if you use it soley for
the Hyper-V parent, with no additional roles.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"SStavreski" <SStavreski@xxxxxx> wrote in message
news:22D3CA1F-E26A-4D5B-92F8-14C864B8BCAD@xxxxxx

thanks for that Charlie,

I understand it will cause issues, but i may not have a choice now.

no other work arounds? can i tell DHCP not to give out IP address to certain
network cards?

thanks,

Steve

"Charlie Russel - MVP" wrote:

You can bind DHCP to a specific card, yes. Open the DHCP manager highlight
IPv4 click advanced, and click Bindings. Same for IPv6. That won't be the
only issue, I'm sure. I sincerely think you're going down a bad road that
will cause support issues and headaches over time. You have an investment
now, I know, but it won't get better over time.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"SStavreski" <SStavreski@xxxxxx> wrote in message
news:62269200-EEDB-4B36-9A6F-3B0909CF616C@xxxxxx

That is always a problem with a multihomed DC.

How did the NIC used by the vms get an IP on the host machine? It
should not have any connection to the host OS at all. Go into the TCP/IP
settings on the host and clear all of the check boxes for the parent
partition. The vms will still be able to use the NIC.

This article from Ben's blog might make it clearer.

http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx

"SStavreski" <SStavreski@xxxxxx> wrote in message
news:62269200-EEDB-4B36-9A6F-3B0909CF616C@xxxxxx