I’ve tried this on many different machines. It isn’t working. I’ve attempted to split assignments to different blades, I originally tried doing link aggregation;
(for folks following along at home - http://www.pcgamer.com/how-to-set-up-nic-teaming-link-aggregation/)
but thinking that might be causing the problem, I got off my high-horse and tried just single pipes back and forth. Nada. I’m giving up on this until I can get some legit hand-holding because I’m convinced this isn’t working in the public beta release. Starting the domain-server from the cmd line is working (sort of) but no assignment client fires. Even using the -n7 on the specific domain-server box when done from the cmd line results in zero ac and therefore empty domain shown. Regardless if the assignment is locally executed or from a remote node. It just doesn’t matter. Here check it out:
For the sake of this experiment, please assume I have physical access to each machine, switch, and router participating in the test. Including 2 isolated stand-alone interface.exe clients if need be. I did read port teaming is not possible in Win10Enterprise, (but that doesn’t explain why doing single NIC failed to work… perhaps change the Link Agg Group on the smart-switch?) Learning as I go, and I know just enough to be dangerous.
Blades parked until you can help me sort it all out…
Thanks @b. Happy Holidays.