Azure AD Connect on Server 2019 Core (no GUI)

Allan Ross 6 Reputation points
2019-11-29T05:48:12.797+00:00

I've just installed Azure AD Connect on my first domain controller and it installed and configured with no problems and is now syncing on-prem AD with Azure.

I tried to install in on the second DC, the only difference between the two machines is that this one did not have the GUI installed. No problem, ran the installer from the command line. Once the installer finishes and the configuration screens start, it crashes as soon as I click [Customize].

XamlParseExeption - Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception.

I've done some searching and found some comments that lead me to believe this is not supported on Server Core. That seems foolish. I can manage the server remotely for everything so going Core makes a lot of sense. Remote management with Powershell is the new hotness....right?

Do I really need the GUI to install this? Once it's running, can I uninstall the GUI? Seems even more foolish if true. Is there a Powershell method to install this product?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,508 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Trevor Seward 11,681 Reputation points
    2019-11-29T06:00:59.713+00:00

    This is outlined on Prerequisites for Azure AD Connect.

    Namely, it does not support Server Core. It is also not recommended to deploy on Domain Controller(s). Another thing to keep in mind is AAD Connect is not a highly available service; you technically don't need to install a second one if you're doing PHS/federation.

    2 people found this answer helpful.
    0 comments
  2. thgibard-MSFT 356 Reputation points
    2019-11-30T18:06:25.83+00:00

    As @Trevor Seward starts to explain - Azure AD Connect is not designed to work on Windows Server Core version - plus, this scenario will not be supported by Microsoft for production environment. As described on the following page : https://learn.microsoft.com/fr-fr/azure/active-directory/hybrid/how-to-connect-install-prerequisites.

    Concerning Azure AD Connect, it's also not supported to have several Azure AD Connect for 1 Tenant / Azure Active Directory. Azure AD Connect is not really a SPOF but if you want to setup high-availability for this component - you may deploy 1 production and working Azure AD Connect + 1 another Azure AD Connect that will be configured in Staging mode. More details on this link part Staging server.

    0 comments