Configure AD VM on Hyper-V to provide AD services on user network (on one NIC) and logging on management network (separate NIC)

active-directory hyper-v

As the topic suggests, I want to have the AD VM on Hyper-V connect to two different VLANs (100 and 200) which are different physical networks. One physical network (VLAN 100) is where all the user desktops lie (Need AD for user authentication) and one physical network is (VLAN 200) where I will forward the Event logs (Application, Security Events on the AD VM to.

These are two separate VLAN networks which require different physical NICs, in order to address a requirement to have logging on a separate segment.

How should I connect the AD VM to one Virtual Switch for user desktop segment and to another Virtual Switch for logging segment? Any pointers will be most appreciated!


Solution 1:

How should I connect the AD VM to one Virtual Switch for user desktop segment and to another Virtual Switch for logging segment?

Connect each virtual NIC to each respective virtual switch and assign each virtual NIC a valid ip address in each respective network.

Related

How to limit root disk space for pod
Accessing Ubuntu 20.04 from Mac OS Catalina: which client to use?
Configuring Parse-Server with HTTPS in Express
I have created one vpc with three different subnets and I am facing issue while doing ssh from instances. getting check public key error
Clarification on understanding Linux disk usage with df and how tmpfs should be assessed
NTFS permissions inheriting incorrectly as "this folder only"
Stash and Unstash in jenkins declarative pipeline
AWS - Can a Private Subnet reach the Internet only with NAT without Internet Gateway
Need a simple High Availability file share
Access to historical Dialogflow data
How to use UNIX domain sockets behind Apache / mod_proxy_uwsgi?
Changing or updating the passphrase in gcp lamp vm