3 . Select Live Trace for the data source.
4 . In the Live Trace tab, change the host from Localhost to the remote Hyper-V server
by clicking the Edit button.
5 . Enter the name of the host. Additionally, separate credentials for the remote host
can be configured. Click OK.
6 . The next step is to apply a scenario. Click the Select Scenario drop-down list, and
select Remote Network Interfaces.
7 . Click the Configure link next to the capture configuration, as shown in Figure 3.49.
This allows the configuration of the exact traffic to be captured. Note that it shows
the actual virtual machines that are connected to the switch. In this case, I have
selected only to capture data from my VM4 virtual machine. Notice also that filters
can be applied to the type of traffic to be captured (or a filter can be applied on the
viewing of data post capture, but if you capture everything, then the capture file
will be substantially larger). Click OK.
8 . Now click the Start button to start the capture and view the packets.
9 . After the capture is finished, click the Stop button.Figure 3.49 Configuring the remote traffic to capture by using Message Analyzer
Figure 3.50 shows an example of my captured output from the virtual machine I
selected. The ability to remotely monitor specific network adapters, specific virtual
switches, and even specific virtual machines with no configuration on the source host
is a huge benefit and really completes and emphasizes the capabilities available with
Windows Server 2016 networking.