Sep 23 2022 01:29 AM - edited Sep 23 2022 01:37 AM
Sep 23 2022 01:29 AM - edited Sep 23 2022 01:37 AM
Can anyone tell when Windows Server 2022 will be supported for Azure AD Connect 2.0?
According to learn.microsoft.com/docs Windows Server 2019 remains the last fully supported OS for now, since WS 2016 is already in extended support and as such should be unfeasible in a quite dynamic cloud connectivity scenario.
Also, the docs mention this:
source: Azure AD Connect: Prerequisites and hardware - Microsoft Entra | Microsoft Learn
fyi @EldenChristensen
Thank you very much for your time and investigations in advance!
Feb 21 2023 02:57 PM
@Deleted This a good question. We are currently looking at upgrading our environment and I'd like to consider Server 2022 instances. However, if a key functionality like Azure AD Connect is not yet supported, then I'll have to select 2019 instead. However, if I knew that 2022 would be supported in x-months or something like that, I might hold off to avoid a mixed environment of 2022 and 2019 servers. I understand there have been those with a successful implementation of Azure AD Connect on Server 2022, but until it's officially supported, I don't think I will. Has anyone heard/read anything official regarding 2022 support?
Feb 22 2023 05:26 PM
@Deleted
Yes, you are correct, not yet supported by Windows 2022 unfortunately
Jun 22 2023 01:31 AM - edited Jun 22 2023 01:32 AM
Jun 22 2023 01:31 AM - edited Jun 22 2023 01:32 AM
SolutionSeems this one is done. on a sidenote
"We recommend the usage of domain joined Windows Server 2022." 👏
source: Azure AD Connect: Prerequisites and hardware - Microsoft Entra | Microsoft Learn
see also: Azure AD Connect 2.0 - to support Windows Server Core - Microsoft Community Hub
Oct 01 2023 05:10 PM
We've just installed AD Connect V2 on a Server 2022 box and it syncs fine. We do however get strange messages form the portal.
Something like this:
/****** begin strange message *********/
The latest Synchronization Errors report for your Azure AD Connect is not available. For getting the latest Synchronization Errors report you must meet the following requirements.
Please follow the steps in the troubleshooting documentation to fix the issue.
/****** end strange message *********/
We've most certainly done confirmed the aforementioned suggestions. All is syncing. It's slightly confusing to see but it works. Any thoughts?
-Cheers
@Deleted
Oct 02 2023 03:51 AM
@AntohnyLariscy I am afraid that is out of my scope. Please contact your support via portal.azure.com or admin.microsoft.com. They need to be aware about that quirk, as it seems to be one.
Jul 18 2024 05:05 PM
Jul 18 2024 05:06 PM
You don't have permission to access "http://account.godaddy.com/" on this server.
Reference #18.c8e9c717.1721345356.13c92e13
https://errors.edgesuite.net/18.c8e9c717.1721345356.13c92e13
why is this happening to me, I am unable to sign into GoDaddy today and this is the correct messages I keep receiving.
Jun 22 2023 01:31 AM - edited Jun 22 2023 01:32 AM
Jun 22 2023 01:31 AM - edited Jun 22 2023 01:32 AM
SolutionSeems this one is done. on a sidenote
"We recommend the usage of domain joined Windows Server 2022." 👏
source: Azure AD Connect: Prerequisites and hardware - Microsoft Entra | Microsoft Learn
see also: Azure AD Connect 2.0 - to support Windows Server Core - Microsoft Community Hub