locked
Installing Exchange 2016 on Server 2016 Error with GUI RRS feed

  • Question

  • I get this error message while trying to install Exchange 2016 Preview on Windows Server 2016 Technical Preview 4. I setup the sever with GUI from the very start and it isn't working.

    Error:
    The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange Setup can begin

    I tried to install this feature using ps using this command.

    Install-WindowsFeature Server-Gui-Mgmt-Infra –Restart

    But I get this error

    Install-WindowsFeature : ArgumentNotValid: The role, role service, or feature name is not valid:
    'Server-Gui-Mgmt-Infra'. The name was not found.
    At line:1 char:1
    + Install-WindowsFeature Server-Gui-Mgmt-Infra –Restart
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (Server-Gui-Mgmt-Infra:String) [Install-WindowsFeature], Exception
        + FullyQualifiedErrorId : NameDoesNotExist,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand

    Wednesday, January 13, 2016 1:51 AM

Answers

  • Looks like Windows Server 2016 is not supported as a domain controller yet with Exchange 2016:

    https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    he following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.

    Network and directory server requirements for Exchange 2016

     

    Component Requirement

    Domain controllers

    All domain controllers in the forest need to be running one of the following:

    • Windows Server 2012 R2 Standard or Datacenter

    • Windows Server 2012 Standard or Datacenter

    • Windows Server 2008 R2 Standard or Enterprise

    • Windows Server 2008 R2 Datacenter RTM or later

    • Windows Server 2008 Standard, Enterprise, or Datacenter

    Active Directory forest

    The Active Directory forest functionality level needs to be at Windows Server 2008 or higher.

    DNS namespace support

    Exchange 2016 supports the following domain name system (DNS) namespaces:

    • Contiguous

    • Noncontiguous

    • Single label domains

    • Disjoint

    For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces.

    IPv6 support

    In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013.

    Also, you should really be asking this question in the Windows Server Forum.  They will be better suited to help you with your issue installing the GUI the Server 2016.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

    • Proposed as answer by Niko.Cheng Sunday, January 24, 2016 7:47 AM
    • Marked as answer by Niko.Cheng Saturday, January 30, 2016 8:13 AM
    Wednesday, January 13, 2016 2:44 PM

All replies

  • Looks like Windows Server 2016 is not supported as a domain controller yet with Exchange 2016:

    https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    he following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.

    Network and directory server requirements for Exchange 2016

     

    Component Requirement

    Domain controllers

    All domain controllers in the forest need to be running one of the following:

    • Windows Server 2012 R2 Standard or Datacenter

    • Windows Server 2012 Standard or Datacenter

    • Windows Server 2008 R2 Standard or Enterprise

    • Windows Server 2008 R2 Datacenter RTM or later

    • Windows Server 2008 Standard, Enterprise, or Datacenter

    Active Directory forest

    The Active Directory forest functionality level needs to be at Windows Server 2008 or higher.

    DNS namespace support

    Exchange 2016 supports the following domain name system (DNS) namespaces:

    • Contiguous

    • Noncontiguous

    • Single label domains

    • Disjoint

    For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces.

    IPv6 support

    In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013.

    Also, you should really be asking this question in the Windows Server Forum.  They will be better suited to help you with your issue installing the GUI the Server 2016.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

    • Proposed as answer by Niko.Cheng Sunday, January 24, 2016 7:47 AM
    • Marked as answer by Niko.Cheng Saturday, January 30, 2016 8:13 AM
    Wednesday, January 13, 2016 2:44 PM
  • Hi,

    GUI features are removed from server 2016 and only exchange which will work on 2016 server is exchange 2016 CU3.Exchange 2016 native without any CU by default will not get installed on latest release of server 2016.

    Muhammad hammad Sikander

    Monday, October 10, 2016 2:35 PM
    • Proposed as answer by AerrowMVP Saturday, February 4, 2017 3:12 PM
    Wednesday, February 1, 2017 5:35 AM
  • After much trial and error, I went ahead and installed Exchange 2016 on my Server 2012 R2 without issues.

    Perhaps testing with CU 4 will do the trick, but it just isn't worth the hassle at the moment to spend more time on making it work with 2016.

    Server 2012 R2 and Exchange 2016 do get along well.


    Desclaimer: This is only for my test lab, so if you desperately need to use it on Server 2016 then I can see it being a necessity, otherwise use 2012.

    • Proposed as answer by Rufoolz Tuesday, February 6, 2018 3:54 PM
    • Unproposed as answer by Rufoolz Tuesday, February 6, 2018 3:54 PM
    Tuesday, July 25, 2017 4:37 AM
  • For all others that have this error you were probably pointed to the exchange download software by Microsoft which is just the RTM.

    Follow this link https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx  to get the latest version of Exchange 2016 the latest CU will be a full exchange iso install.


    • Proposed as answer by Rufoolz Tuesday, February 6, 2018 4:07 PM
    • Edited by Rufoolz Tuesday, February 6, 2018 4:08 PM
    Tuesday, February 6, 2018 4:06 PM
  • Just thought I would post this as I had the same problem.

    I was trying to install Exchange 2016 on Windows Server 2016 with the GUI installed and got the Server-Gui-Mgmt-Infra error. Very odd as I installed the GUI version of server not the core.

    Had a look round and found lots of people mentioning installing Cumulative Update 4 for Exchange Server 2016, all these post were quite old and CU4 is no longer available. A look in the MS download site though and I found Exchange 2016 CU7.

    https://support.microsoft.com/en-gb/help/3177106/cumulative-update-4-for-exchange-server-2016

    Downloaded this and hey presto everything works fine.

    So if you are having problems get the latest cumulative update for exchange and give it a go.

    Just as a note I was originally trying to install the latest exchange version from TechNet.

    Hope this helps


    Thursday, March 1, 2018 6:48 PM