I was (un)installing Exchange rollup when (un)installation completed successfully , I noticed that it left all Exchange services disabled

.
As Exchange services needs to be started with automatic startup mode , I was going to do it one by one using Services snap-in . Just as I went to Start to open Services snap-in I noticed the Windows Power Shell shortcut pinned to my taskbar , so I decided to use it to achieve my goal and here is how I did that.
At an elevated Windows Power Shell I did the following :
- I used Get-Service cmdlet to check the status of Microsoft Exchange related services :
Get-Service | Where-Object { $_.DisplayName –ilike “Microsoft Exchange *” | ft Name,Status |
Get-Service | Where-Object { $_.DisplayName –ilike “Microsoft Exchange *” } | Set-Service –StartupType Automatic
|
Get-Service | Where-Object { $_.DisplayName –ilike “Microsoft Exchange *” } | Start-Service
|
By now all Exchange services are running with automatic startup mode, but unfortunately whenever I tried to use any of the management tools I got a connection failure as IIS services are still down . In order to fix this issue I executed the following commands
Get-Service | Where-Object { $_.DisplayName –eq “World Wide Web Publishing Service” } | Set-Service –StartupType Automatic
|
Get-Service | Where-Object { $_.DisplayName –eq “World Wide Web Publishing Service” } | Start-Service
|
Get-Service | Where-Object { $_.DisplayName –eq “IIS Admin Service” } | Set-Service –StartupType Automatic
|
Get-Service | Where-Object { $_.DisplayName –eq “IIS Admin Service” } | Start-Service
|
Just after that I was able to start my Exchange administrative tools and connect successfully to my Exchange server

No comments:
Post a Comment