Security Update For Exchange Server 2016 CU6 (KB4045655) didnt apply - now Exchange disabled

We have a new Windosw 2016 server with Exchange 2016.
This was working fine until we installed the latest updates.

Specifically "Security Update For Exchange Server 2016 CU6 (KB4045655)".
This tried to run but then displays "Failed to install 29/12/2017"

The problem is that all the Exchange services are disabled and isn't working
HowdythereAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Muhammad AsifSenior Solutions ArchitectCommented:
Can you please let us know what services are not running?  Are you getting the issue with Microsoft Exchange Front-end Transport, Transport, Replication and Information Store server?

Moreover, are you also getting the issue while opening PowerShell and ECP on that server. If yes then please let me the error which you are getting.
0
Valentina PerezExchange ServersCommented:
Hi,

Are you able to enable again all the exchange services?

Check with the folloing command the services: Test-ServiceHealth

Regards
Valentina
0
8046586Commented:
If the update passed partially and failed, you should try reinstalling it. Stop the antivirus, close all management consols and all windows while the update is running. Run the update as administrator. If it fails again try downloading it from scratch and repeat the procedure. You can try running the update in safe mode too (if do not require some running services)
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

RoninCommented:
Set the services back to Automatic and start them.
Also review installation log file for errors and post them.
0
HowdythereAuthor Commented:
All the Services seemed to be set to disabled. Following suggestions elsewhere, I set all Disabled Services to Automatic.
Changed UAC to low level.
Downloaded the Exchange 2016 CU6 KB4045655 update manually and ran from an elevated Command window.
This did not help.

We are running Sophos Endpoint Security. I clicked to stop On Access scanning etc.
So I tried to manually start some of the services, but they seem to fail with the messages similar to:-
Windows could not start the Microsoft Exchange Active Directory Topology Service on Local Computer.
Error 1068: The dependency service or group failed to start.

I checked the dependency list and they seem to be started "Net TCP Port Sharing Service" and  "Netlogin"

Should I try Exchange Server 2016 CU7 install?
0
8046586Commented:
I don't want to say that you are in deep s..., but do not put your self in further trouble with improvisation. Do not jump on to next update before you fix this issue. Exchange updates are sometimes very complex, and you have to fulfil the prerequisites. Otherwise, services will stop operating.
Going back to your failed update. Is any reason you run this update, but you didn't go to CU8? Did you reed the CU6 prerequisites?
Do not follow blindly our suggestions because we might be missing some details (we do not have access to your server and we do not have the history).
Why the services become disabled? After the failed update or you disabled them manually? Do you know which service was starting automatically and which one was manual before the update?
0
Muhammad AsifSenior Solutions ArchitectCommented:
We had face few days ago similar kind of an issue. The services were not starting and we were also not able to open PowerSehll and ECP on affected Exchange server.  We had found the solution and it is described in the given below link.  Please look into it as it might help you.

https://solutionsorbit.com/2017/12/20/exchange-services-information-store-frontend-service-transport-are-not-starting-exchange-management-shell-and-virtual-directories-are-not-opening-exchange-version-exchange-2016-2013-windows/
0
Muhammad AsifSenior Solutions ArchitectCommented:
Any Update?  Have you managed to resolved this case?   If issue still persists then can you please share the errors with us which you are getting in event viewer.
0
Todd NelsonSystems EngineerCommented:
A similar issue has been documented on several sites. Take a look at this reference. Hopefully it will guide you to a resolution.

https://oddytee.wordpress.com/2017/11/09/cannot-start-service-msexchangeservicehost-on-computer-during-exchange-cu-update/
0
HowdythereAuthor Commented:
Thanks for everyones help on this.
Looks like its an issue with KB4045655 (17/12/2017) that reflects a similar issue that occurred a few months back.
Tried most suggestions, but couldn't get Exchange Services to start. It may be rpc registry setting, but couldn't find it to remove.

So, did a restore in the end.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Howdythere (https:#a42420132)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer
0
Shawn (Rosco) HaysCreative Branding and Marketing ManagerCommented:
0
HowdythereAuthor Commented:
Thanks Rosco - I resolved the issue by restoring a backup from a day earlier - but your solution looks like it may have worked !!
1
Muhammad AsifSenior Solutions ArchitectCommented:
Hi Howdythere,

Can you please guide me about backup recovery of Exchange, if we have two Exchange 2016 servers in DAG and one of it goes down or have some problem as just like you were facing. So in this case, what we need to do?

Should we need to restore the whole Exchange system along with drives and everything or just we need to restore the system state?  if we restore the system then is there would be any inconsistancy?

Can you please explain the best way which you are following?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Updates

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.