locked
Windows Server 2016 Network Controller RRS feed

  • Question

  • Hi,

    I just installed Server 2016 Tech Preview 5 and wanted to see what the Network controller was all about. I installed the Role and it shows it there but there are no options on additional configuration. I've looked for articles but the area is still pretty vague. Can anyone point me in the way of documentation on what else to do ? I've read https://technet.microsoft.com/library/mt691521.aspx.

    Friday, June 3, 2016 4:33 AM

Answers

All replies

  • Hi NathanMagna,

    Have you read the following articles about Network controller? It provides more detailed information:

    Network Controller:

    https://technet.microsoft.com/en-sg/library/dn859239.aspx#bkmk_features

    Besides, since it's a new technology, I think there may be more information and official article for it later.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Friday, June 3, 2016 7:41 AM
  • Yes, I have thank you. I was looking to use a feature I seen to map the physical topology of the network. When I installed the role I was expecting something new in the Tools or a setting in Server Manager. 
    Friday, June 17, 2016 9:27 PM
  • There won't be. NC is entirely managed by powershell, as far as I know. For an inexperienced in poweshell (like me :P), VMM is a must, and a great tool! Its a tough installation. I managed to get NC installed with VMM after two weeks. I followed these procedures:

    https://blogs.technet.microsoft.com/larryexchange/2016/05/30/step-be-step-for-deploying-a-sdnv2-using-vmm-tp5-part-2/

    https://technet.microsoft.com/en-us/library/mt729074(v=sc.16).aspx

    Here are some tips I'd wish I had before installing it:

    • Before deploying the service, go enter the product key in the open designer.
    • Ensure that your vm is the same name as the certificate you created (if you deploy the standalone template)
    • For the connection string, use the FQDN, not only the cn name, even if you can reach the nc with that name alone.

    These are the ones that come to mind, but be sure to ask for more if you encounter issue. I hope I'll be able to help!


    Monday, June 20, 2016 5:23 PM