Exchange 2010 Initialization Failed.

The time is fine on the SBS.
In Network & Sharing centre i am connected to Nework 5 not my domain.local.

Did you make any changes in IIS?
If yes please revert it.

No changes to anything just ran the updates. The problem seems to be kb4539601, i am uninstalling it at the moment.
Other updates were for defender & malicious software removal tool.

If that didnt help. Please try EMTShooter
https://practical365.com/blog/fixing-exchange-2010-management-tools-winrm-errors/

Uninstalled the update & restarted but still the same.

When i try to check DNS i get "The server could not be contacted. Error was Access was denied. Would you like to add it anyway? If i do DNS is blank & says Configure a DNS Server. DNS Server & Client services are running.

Am i looking at restoring from a backup here?

Please run the EMTShooter and see how it is fixing or no.

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command ". 'C:\EMTshooter\EMT
shooter.ps1'"

Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to server.domain.local


[server.domain.local] Connecting to remote server failed with the following error message : Access is denied.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

server.domain.local

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

After each error is resolved, close this window and re-run the tool to check for additional problems.

[EMTS] C:\Windows\system32>

I can't get DNS up & running again.
"The server could not be contacted. Error was Access was denied. Would you like to add it anyway?"
 If i do DNS is blank & says Configure a DNS Server. Configure DNS Server is greyed out.

 DNS Server & Client services are running.

This link explained the same problem i'm having here so i followed the instructions & ran the command then restarted the server.

netdom resetpwd /server:DC.domain.local /userd:Domain\domain_admin /passwordd:*

Select allOpen in new window

Now when i log in i just get a blank desktop no icons or taskbar.
I tried endng & restarting explorer.exe in Task Manager but it makes no difference.

If DNS is not working Exchange will not work.
Please make sure DNS is working.

That’s the problem, i can’t get DNS up & running again

-->That’s the problem, i can’t get DNS up & running again
How many DCs you have ?

It's just the 1 SBS 2011

Then you have to fix your SBS.

At the moment i can't even get to the desktop, when i login i see the SBS Console but no desktop or taskbar, i tried endng & restarting explorer.exe in Task Manager but it makes no difference.
I logged into Safe mode & i can get to the desktop no problem.
I disabled startup items & non microsoft services in msconfig & restarted but same problem.
I created a new Network Admin account in safe mode & restarted, logged in to it & same problem.                    

I think i'll have to go to the office & restore from a backup.     

Ouch, sorry

So, after restoring from a backup, DNS is back working & all pcs are now connected to the server & internet again but unfortunately there is no email. EMC says "Initialization Failed" "The attempt to connect to http://xxxx.xxx.com/PowersShell using "Kerberos" authentication failed: Connecting to the remote server failed with the following error message: The WinRM client received an HTTP server error status (500) but the remote server did not include any other information about the cause of the failure."              

Was there a .NET update in there?

It was -      

January 31, 2020—KB4539601 (Preview of Monthly Rollup)

   

Did you try to restore from backup?

Yep, restored from backup & everything is working except Exchange -
"   So, after restoring from a backup, DNS is back working & all pcs are now connected to the server & internet again but unfortunately there is no email. EMC says "Initialization Failed" "The attempt to connect to http://xxxx.xxx.com/PowersShell using "Kerberos" authentication failed: Connecting to the remote server failed with the following error message: The WinRM client received an HTTP server error status (500) but the remote server did not include any other information about the cause of the failure."            

Run the three wizards I indicated above please.

"Run the Getting Started Tasks Wizards:
 * Connect to the Internet
 * Internet Address

No settings need to change, but the wizards should reseat things.

Also, the Fix My Network wizard on that tab is an important step."

CTIW - Detects router & server ips then ends with "Windows SBS did not properly configure your e-mail. To corrrect this re-run the wizard." Ran 3 times same outcome.
Internet ddress - "Internet Address Management.   In order to register a domain name you must first run the Connect to Internet wizard"
Fix My Network -
The ipv6 protocol is not disabled correctly - Skipped
The DNS server is not listening to the ip address of the primary network adapter - Fixed
DNS is using a DNS forwarder - Skipped
Self-issued certificate is expired - Errors

Please make sure all services are started.
If services are started please run the EMTShooter again.

All services are started..

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> C:\EMTshooter\EMTshooter.ps1

Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to SBS-SERVER2011.McPeakes.local


[sbs-server2011.mcpeakes.local] Connecting to remote server failed with the following error message : The WinRM client r
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

SBS-SERVER2011.McPeakes.local

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

After each error is resolved, close this window and re-run the tool to check for additional problems.

PS C:\Windows\system32>

Please run this command from an elevated EMS.

Add-PSsnapin Microsoft.Exchange.Management.PowerShell.E2010

Select allOpen in new window

I've just finished restoring from backup for a second time & everything is working again.

Thanks to everyone for all the help. It's time to upgrade this server to Essentials 2019 & migrate the email to Exchange online, have been pushing them to do this since late last year but think they are finally ready to do it now.

Thanks again.

Glad to know you sorted out.
Cheers

Closing this question, sorry for the delay. the restore from backup did the job. appreciate all of your help. 😉

Thanks for the help guys, much appreciated. 😉