Exchange EWS Url

-->Help please, tried installing CU22 on to Exchange 2016 but failed.  
Did you complete the installation?

No, it crashed any the very start stating the user wasn't a member of the organisation group even though it was,.

You have to complete the installation/update to have it fully functional.

Ok I can't because it crashes at the first step, states that you must be a member of the organization management role or a member of enterprise admin which the account is a member of?

Further down on the list it States that the active directory doesn't exist or can't be contacted?

Exchange installation might have removed some files.
Please try the installation and complete it. Else you will have issues again.

If you broke your exchange server you can try a repair install..
You basically set up a new windows install with the databases copied or moved to the exact same drive letters and reinstall exchange.
https://practical365.com/recovering-a-failed-exchange-server-2016-server/

How did you try installing it?

Did you download it and then start the CU install from an elevated cmd.exe prompt?

Cumulative installers are full Exchange installers and they actually uninstall Exchange. So if it crashed or you forced it to quit part of the way through, you need to reinstall.

1. Make sure the user you are logged in as, is a member of the Organization Management group. (You need to do this even if the user is a Domain Admin).

2. Mount the CU ISO, then open a command prompt as Administrator. (You need to Run As Administrator even if you are logged in as a user who is a member of the Administrators group)

3. E:\Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /Mode:Upgrade  (where E is your ISO drive letter)

Note: this command runs the upgrade in unattended mode but it gives you feedback all during the install. You just sit and watch it. If you have a deployment where Exchange is running on multiple VMs then there are additional steps. The command above is for an Exchange server that runs on one VM.

ou must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to
continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

You must use an account that's a member of the Organization Management role group to install the first Client Access
server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

You must use an account that's a member of the Organization Management role group to install the first Client Access
server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The
supplied credential for '***\administrator' is invalid. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx


The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.

Nobody have any other ideas as have tried all the above and still the same?

Seems like you have issue with your DC.
Please make sure your DC is healthy first.
And make sure DNS IPs are correct in your Exchange server

Hi MAS, DNS is correct, points to 127.0.0.1, is there a tool to check the DC or Active Directory?

-->Hi MAS, DNS is correct, points to 127.0.0.1, is there a tool to check the DC or Active Directory?
Is your Exchange is installed in DC?

Yes

Then this is expected when you have DC and Exchange in one OS.

Sorted this by changing the administrator password and creating another account with all the required permissions.