I'm setting up a Server 2012 R2 with Hyper-V role in a typically SMB environment (virtualized DC and Exchange on one single Host). Before, in the SBS times, there usually was one physical server, a handful of PCs and one subnet. Now, with virtualized systems, it seems to be useful to have more than one subnet, see here.
Please advice whether this environment would be a feasible one:
a) Put Users and DC/file/print server (VM1) on one subnet.
b) Give Exchange (VM2), because it has an open port 443 for incoming mail and activesync, an own subnet and allow traffic to/from local users to mail server only as needed via firewall rules.
c) Give host it's own subnet, determine one of the users PCs as admin PC and create rules and routes to grant access to the host subnet only for this PC.
Would that be ok?
The server is a Two-NIC-Proliant (ML150 Gen9). I plan to team these NICs and have one vSwitch. So all the traffic, i.e. the three subnets, would coexist on the one and only vSwitch and would be balanced through the teamed NICs.
Is that reasonable?
Thanks in advance, Stefano