> Hi,
>
> I was wondering whether there are any best practice guidelines for the
> initial setup of the current Hyper-V RC? My main question is regarding
> network connectivity - can the Hyper-V parent partition be connected to the
> internal network and be a domain member (for management and VM backup
> purposes), even if the child partitions it hosts were connected to a
> less-secure network such as a DMZ? I'm assuming this is not a recommended
> configuration unless the VMs can be configured to have no access whatsoever
> to the parent partition?
>
> Thanks!

> Hi,
>
> I was wondering whether there are any best practice guidelines for the
> initial setup of the current Hyper-V RC? My main question is regarding
> network connectivity - can the Hyper-V parent partition be connected to
> the
> internal network and be a domain member (for management and VM backup
> purposes), even if the child partitions it hosts were connected to a
> less-secure network such as a DMZ? I'm assuming this is not a recommended
> configuration unless the VMs can be configured to have no access
> whatsoever
> to the parent partition?
>
> Thanks!

> Hi Bill,
>
> Many thanks for the speedy response - I wasn't planning on running
> anything
> apart from the Management Consoles for Hyper-V plus some agents for VM
> backup
> and parent partition OS monitoring purposes (nothing too resource
> intensive).
>
> "NJC1" wrote:
>
>> Hi,
>>
>> I was wondering whether there are any best practice guidelines for the
>> initial setup of the current Hyper-V RC? My main question is regarding
>> network connectivity - can the Hyper-V parent partition be connected to
>> the
>> internal network and be a domain member (for management and VM backup
>> purposes), even if the child partitions it hosts were connected to a
>> less-secure network such as a DMZ? I'm assuming this is not a recommended
>> configuration unless the VMs can be configured to have no access
>> whatsoever
>> to the parent partition?
>>
>> Thanks!

> Questions about DMZ operations can get tricky. The real point is that a
> vm can only access a physical network through a physical NIC on the host.
> If you have a vm connected to a DMZ you must have a NIC in the host
> connected to that DMZ somehow. If you also have another NIC in the host
> connected to some other network there is always a possibility of a leak
> from one network to the other, no matter how slight the risk may be.
>
> "NJC1" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hi Bill,
>>
>> Many thanks for the speedy response - I wasn't planning on running
>> anything
>> apart from the Management Consoles for Hyper-V plus some agents for VM
>> backup
>> and parent partition OS monitoring purposes (nothing too resource
>> intensive).
>>
>> "NJC1" wrote:
>>
>>> Hi,
>>>
>>> I was wondering whether there are any best practice guidelines for the
>>> initial setup of the current Hyper-V RC? My main question is regarding
>>> network connectivity - can the Hyper-V parent partition be connected to
>>> the
>>> internal network and be a domain member (for management and VM backup
>>> purposes), even if the child partitions it hosts were connected to a
>>> less-secure network such as a DMZ? I'm assuming this is not a
>>> recommended
>>> configuration unless the VMs can be configured to have no access
>>> whatsoever
>>> to the parent partition?
>>>
>>> Thanks!
>

> NJC1,
>
> If you have _any_ device with two NICs with one connected to each zone
> (such as a firewall), then there is also a possibility of a leak from one
> network to the other, no matter how slight the risk may be.
>
> So in your case, if TCP/IP is not actually bound to the host adaptor, then
> your risk is fairly small.
>
> --
> Dave Harry
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
>> Questions about DMZ operations can get tricky. The real point is that
>> a vm can only access a physical network through a physical NIC on the
>> host. If you have a vm connected to a DMZ you must have a NIC in the host
>> connected to that DMZ somehow. If you also have another NIC in the host
>> connected to some other network there is always a possibility of a leak
>> from one network to the other, no matter how slight the risk may be.
>>
>> "NJC1" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hi Bill,
>>>
>>> Many thanks for the speedy response - I wasn't planning on running
>>> anything
>>> apart from the Management Consoles for Hyper-V plus some agents for VM
>>> backup
>>> and parent partition OS monitoring purposes (nothing too resource
>>> intensive).
>>>
>>> "NJC1" wrote:
>>>
>>>> Hi,
>>>>
>>>> I was wondering whether there are any best practice guidelines for the
>>>> initial setup of the current Hyper-V RC? My main question is regarding
>>>> network connectivity - can the Hyper-V parent partition be connected to
>>>> the
>>>> internal network and be a domain member (for management and VM backup
>>>> purposes), even if the child partitions it hosts were connected to a
>>>> less-secure network such as a DMZ? I'm assuming this is not a
>>>> recommended
>>>> configuration unless the VMs can be configured to have no access
>>>> whatsoever
>>>> to the parent partition?
>>>>
>>>> Thanks!
>>
>