- Remove From My Forums
-
Вопрос
-
Добрый день, коллеги!
Объясните пожалуйста для чего служит служба MSExchangeNotificationsBroker, и почему она вечно не запускается, при этом никаких проблем в производстве не наблюдается, спасибо
Ответы
-
Привет,
на самом деле она запускается при старте сервера, а потом останавливается. By design для E2016.
Release notes for Exchange 2016
Раздел Mailbox:
-
Notifications Broker service stops after 30 seconds When you start your Exchange server, you might notice the
Notifications Broker service start and then stop after approximately 30 seconds. If you attempt to start the service manually, it will successfully start and then stop, again after approximately 30 seconds. No errors or warnings are included
in the Event log.This behavior is expected in on-premises deployments of Exchange 2016. The
Notifications Broker service performs a configuration check on each time the server starts. If there is nothing for the
Notifications Broker service to do, it stops automatically until the next time the server is restarted.
-
Помечено в качестве ответа
15 октября 2016 г. 5:32
-
Abstract: On a fresh new Windows 2012 R2 with Exchange 2016 you see the ‘Microsoft Exchange Notifications Broker’ as stopped and giving a red error in the dashboard. The fix is quite easy:
Solution:
Click on “Services” and deselect the “Microsoft Exchange Notification Broker”
According to the Microsoft Exchange 2016 release notes:
Notifications Broker service stops after 30 seconds When you start your Exchange server, you might notice the Notifications Broker service start and then stop after approximately 30 seconds. If you attempt to start the service manually, it will successfully start and then stop, again after approximately 30 seconds. No errors or warnings are included in the Event log.This behavior is expected in on-premises deployments of Exchange 2016. The Notifications Broker service performs a configuration check on each time the server starts. If there is nothing for the Notifications Broker service to do, it stops automatically until the next time the server is restarted.
It is quite normal that the service is showing as “stopped” so it should be safe to exclude it on the dashboard.
This is a per user setting, so if you have a team who manage exchange, then this setting must be implemented in each profile on each exchange server.
When you open the server manager on Windows 2012 R2 with Exchange 2016 installed you see an error stating that the Microsoft Exchange Notifications Broker has stopped.
This is by design with Exchange 2016 on-prem deployments. This is from the Exchange 2016 release notes.
Notifications Broker service stops after 30 seconds When you start your Exchange server, you might notice the Notifications Brokerservice start and then stop after approximately 30 seconds. If you attempt to start the service manually, it will successfully start and then stop, again after approximately 30 seconds. No errors or warnings are included in the Event log.
This behavior is expected in on-premises deployments of Exchange 2016. The Notifications Broker service performs a configuration check on each time the server starts. If there is nothing for the Notifications Broker service to do, it stops automatically until the next time the server is restarted.
As the error is very annoying and can look problematic this service check can be disabled in Server manager by selecting the drop down box next to ‘services’ find ‘Microsoft Exchange Notifications Broker’
На чтение 4 мин Опубликовано 26 апреля, 2021
Содержание
- Austin’s blog
- Tuesday, 27 September 2016
- [Resolved] Microsoft Exchange Notifications Broker stopped Exchange 2016
- 5 comments:
- the microsoft exchange transport service entered the stopped
Austin’s blog
Do you pause on an exhausted ring?
Tuesday, 27 September 2016
[Resolved] Microsoft Exchange Notifications Broker stopped Exchange 2016
I wanted to thank you for this great read!! I definitely enjoying every little bit of it I have you bookmarked to check out new stuff you post. south african brokers forex
Wow, cool post. I’d like to write like this too — taking time and real hard work to make a great article. but I put things off too much and never seem to get started. Thanks though. Pepperstone review nederlands
Bitcoin has proven to be by far the most profitable investment of the past decade, and the next ten years offer even more promise. The most successful BTC investors have followed a series of smart principles, which will be even more important for taking profits moving forward. Bitcoin investment.
Robo-advising has actually interrupted the possession monitoring sector by offering algorithm-driven suggestions and also a personalized profile monitoring which does not necessarily demand human guidance. Eyal Nachum is a fintech guru and a director at Bruc Bond. Eyal is the architect of the software that SMEs use to do cross-border payments.
who and what are the constituents and components of the international payment system? To start with, banks and financial institutions form the first layer of the international payment service wherein they hold accounts of other global banks who in turn hold accounts of the former. This enables the banks to send and receive payments from each other as they can simply debit their accounts and credit the other bank’s account with them and this in turn leads to payments flowing to the recipient bank that debit the sending bank and credit their account.
the microsoft exchange transport service entered the stopped
Все новые темы
| Автор | ||||
|---|---|---|---|---|
| tutsi2007 Старожил форума Зарегистрирован: 09.08.2006
|
|
|||
| Вернуться к началу |
|
|||
 |
||||
| Зарегистрируйтесь и реклама исчезнет!
|
||||
|
||||
| Freshtm Новичок Зарегистрирован: 05.02.2014 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| ADMINDM guru 
Зарегистрирован: 04.11.2007
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| tutsi2007 Старожил форума Зарегистрирован: 09.08.2006
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| ADMINDM guru
Зарегистрирован: 04.11.2007
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| tutsi2007 Старожил форума Зарегистрирован: 09.08.2006
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| ADMINDM guru
Зарегистрирован: 04.11.2007
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| tutsi2007 Старожил форума Зарегистрирован: 09.08.2006
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| ADMINDM guru
Зарегистрирован: 04.11.2007
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| tutsi2007 Старожил форума Зарегистрирован: 09.08.2006 Adblock |
If you are working with Microsoft Exchange 2016, On-Prem, you weill find a new service named, Microsoft Exchange Notifications Broker. The Notifications Broker service is set to start AUTOMATICALLY by default and if you start it manually you will notice it stops after 30 seconds.
What Is The Microsoft Exchange Notifications Broker Service?
The Microsoft Exchange Notifications Broker is was introduced in Exchange 2016 (and dropped from Exchange 2019) to:
Provide Exchange notifications to local and remote Exchange processes. SOURCE
It is a required service in Exchange 2016 and is dependent on both Microsoft Exchange Active Directory Topology Service and the Net.TCP Port Sharing Service.
Why Does the Microsoft Exchange Notifications Broker Service Stop Running?
The Exchange Notifications Broker service only runs for 30 seconds and then stops automatically by design because it is only checking the servers configuration at startup. To save resources it turns itself off after the checks are complete.
How To Disable Notification Broker Service Alerts in Server Manager?
If you are tired of seeing pointless service alerts about the Exchange Notification Broker Service in your Server Manager, just click the SERVICES dropdown and uncheck it.
- Updated on June 17, 2022
- Exchange, Powershell
Sometimes you need to restart the Exchange Server services. You have the option to restart the Exchange Server. Restarting will take more time and effort than restarting the Exchange services. It’s possible to restart the services through services.msc. It’s not as fast as restarting the services through PowerShell. In this article, you will learn how to restart Exchange Server services through PowerShell.
Table of contents
- Get a list of Exchange services
- Restart all Exchange running services
- Restart all Exchange services with startup type automatic
- Restart all Exchange services
- Conclusion
Get a list of Exchange services
Run Exchange Management Shell as administrator. Let’s first get a list of all the Exchange services on the server. This can be running and stopped services. We are going to use the Get-Service cmdlet.
[PS] C:>Get-Service | Where {$_.DisplayName -like "*Exchange*"} | Where {$_.DisplayName -notlike "*Hyper-V*"} | Format-Table DisplayName, Name, Status
DisplayName Name Status
----------- ---- ------
Microsoft Exchange Search Host Controller HostControllerService Running
Microsoft Exchange Compliance Audit MSComplianceAudit Running
Microsoft Exchange Active Directory Topology MSExchangeADTopology Running
Microsoft Exchange Anti-spam Update MSExchangeAntispamUpdate Running
Microsoft Exchange Compliance Service MSExchangeCompliance Running
Microsoft Exchange DAG Management MSExchangeDagMgmt Running
Microsoft Exchange Mailbox Transport Delivery MSExchangeDelivery Running
Microsoft Exchange Diagnostics MSExchangeDiagnostics Running
Microsoft Exchange EdgeSync MSExchangeEdgeSync Running
Microsoft Exchange Search MSExchangeFastSearch Running
Microsoft Exchange Frontend Transport MSExchangeFrontEndTransport Running
Microsoft Exchange Health Manager MSExchangeHM Running
Microsoft Exchange Health Manager Recovery MSExchangeHMRecovery Running
Microsoft Exchange IMAP4 MSExchangeImap4 Stopped
Microsoft Exchange IMAP4 Backend MSExchangeIMAP4BE Stopped
Microsoft Exchange Information Store MSExchangeIS Running
Microsoft Exchange Mailbox Assistants MSExchangeMailboxAssistants Running
Microsoft Exchange Mailbox Replication MSExchangeMailboxReplication Running
Microsoft Exchange Notifications Broker MSExchangeNotificationsBroker Stopped
Microsoft Exchange POP3 MSExchangePop3 Stopped
Microsoft Exchange POP3 Backend MSExchangePOP3BE Stopped
Microsoft Exchange Replication MSExchangeRepl Running
Microsoft Exchange RPC Client Access MSExchangeRPC Running
Microsoft Exchange Service Host MSExchangeServiceHost Running
Microsoft Exchange Mailbox Transport Submission MSExchangeSubmission Running
Microsoft Exchange Throttling MSExchangeThrottling Running
Microsoft Exchange Transport MSExchangeTransport Running
Microsoft Exchange Transport Log Search MSExchangeTransportLogSearch Running
Microsoft Exchange Unified Messaging MSExchangeUM Running
Microsoft Exchange Unified Messaging Call Router MSExchangeUMCR Running
Tracing Service for Search in Exchange SearchExchangeTracing Running
Microsoft Exchange Server Extension for Windows Server Backup wsbexchange StoppedRestart all Exchange running services
Only restart the Exchange running services.
[PS] C:>$services = Get-Service | ? { $_.name -like "MSExchange*" -and $_.Status -eq "Running"};foreach ($service in $services) {Restart-Service $service.name -Force}What if there are Exchange services not running? The above command will not restart these Exchange services.
Restart all Exchange services with startup type automatic
Restart all Exchange services with startup type automatic. If an Exchange service is stopped at the moment with startup type automatic, it will start after running the command.
[PS] C:>$services = get-wmiobject win32_service | ? {$_.name -like "MSExchange*" -and $_.StartMode -eq "Auto"};foreach ($service in $services) {Restart-Service $service.name -Force}The third and last command in the article will restart all the Exchange services.
[PS] C:>Get-Service *Exchange* | Where {$_.DisplayName -notlike "*Hyper-V*"} | Restart-Service -ForceConclusion
With the proper PowerShell command, you can restart all the Exchange services. Suppose you don’t want to use PowerShell; use Windows Services Manager (services.msc). But it’s faster to use the PowerShell commands.
Did you enjoy this article? You may also like Restart Exchange services with PowerShell script. Don’t forget to follow us and share this article.
ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Read more »
На чтение 6 мин. Просмотров 47 Опубликовано 17.04.2021
Использование Windows без периодически возникающих раздражающих сообщений и ошибок звучит как мечта. Однако похоже, что эта мечта все еще недостижима, даже с такой потрясающей версией ОС Windows, как Windows 10. Причина, по которой Windows так популярна сегодня на рынке, заключается в том, что она обещала своим пользователям отличную возможность модификации и совместима почти с каждое приложение на рынке.
Однако пользователи начали переходить на Mac OS X, потому что ее довольно легко понять и использовать, и она предлагает быстрый опыт с почти безошибочной производительностью. Давайте узнаем, как решить эту досадную проблему!
Содержание
- Как отключить «Exchange Active Sync Policies» Всплывающее окно управления учетными записями пользователей брокера
- Решение 1. Переключитесь на локальную учетную запись, а не на учетную запись Microsoft
- Решение 2. Переход на Outlook
- Решение 3. Переключение UAC на Se Уровень любопытства Ниже
- Решение 4. Реестр Tweak
Как отключить «Exchange Active Sync Policies» Всплывающее окно управления учетными записями пользователей брокера
Эта конкретная проблема обычно начинает появляться сразу после накопительного обновления, и она уже давно вызвала недовольство пользователей. Эта конкретная проблема возникает не одна, и обычно она вызывает пару дополнительных проблем, которые иногда бывает довольно сложно исправить.
Эта проблема заключается в том, что система контроля учетных записей пользователей (UAC) спрашивает:« Вы хотите разрешить этому приложению вносить изменения в ваш компьютер? » и ссылаясь на Exchange Active Sync Policies Broker как на приложение в вопросах. Давайте узнаем, как легко решить эту проблему!
Решение 1. Переключитесь на локальную учетную запись, а не на учетную запись Microsoft
Использование локальной учетной записи может решить проблему для вас, и эти запросы UAC будут обрабатываться автоматически UAC. Однако вы могли использовать свою учетную запись Microsoft с какой-либо целью и хотите продолжать использовать ее в обычном режиме. Если вы переключитесь на локальную учетную запись, вы все равно сможете использовать учетную запись Microsoft для приложений, которым она требуется.
- Перейдите к строке поиска в меню «Пуск» и введите следующее и нажмите на первый результат.
«Измените изображение вашей учетной записи или настройки профиля»
- В разделе “Учетные записи” должно открыться приложение “Настройки”.
- В подменю “Ваша учетная запись” нажмите Вместо этого войдите в локальную учетную запись. Если вы уже используете локальной учетной записи, появится другой вариант: «Вместо этого войдите в систему с учетной записью Microsoft».
- Чтобы изменить свою учетную запись на локальную, вам нужно будет повторно ввести текущий пароль для ваша учетная запись Microsoft.
- После того, как вы введете правильный пароль, вам нужно будет настроить локальную учетную запись, введя свое имя пользователя, пароль и подсказку для пароля.
- На последнем экране нажмите «Выйти и завершить».
Решение 2. Переход на Outlook
Это второй обходной путь, который вы можете попробовать, чтобы избавиться от этого раздражающего всплывающего окна UAC. сообщение вверх. Поскольку эта конкретная проблема связана с вашей учетной записью Exchange в почтовом приложении, удалите ее из приложения и переключитесь на Outlook или сторонний почтовый менеджер.
- Откройте приложение «Почта», выполнив поиск в строке поиска в меню «Пуск».
- Слева. в разделе “Почта”, найдите внизу значок шестеренки, который откроет “Настройки” на правой панели.
- Нажмите на первый вариант с названием “Управление учетными записями”.
- Нажмите в вашей учетной записи Exchange, чтобы управлять ее настройками.
- В открывшемся окне нажмите на опцию Удалить учетную запись, чтобы удалить эту учетную запись из почтового приложения.
- Нажмите кнопку «Сохранить» и перезагрузите компьютер.
- Убедитесь, что сообщение UAC по-прежнему отображается на вашем компьютере.
- Если это не так, не стесняйтесь. , чтобы переключиться на Outlook в почтовом менеджере по умолчанию.
Решение 3. Переключение UAC на Se Уровень любопытства Ниже
Работа с брокером активных политик синхронизации Exchange обычно разрешена UAC, и именно поэтому вы получаете запрос об этом, как только обновляете свой компьютер. Кажется, что каждое новое накопительное обновление сбрасывает ваши настройки UAC на самый высокий уровень безопасности, и именно поэтому вы не можете избавиться от сообщения об ошибке.
- Откройте панель управления с помощью ищите его в меню “Пуск”.
- Переключите параметр “Просмотр по” на панели управления на мелкие значки и найдите параметр “Учетные записи пользователей”.
- Откройте его и нажмите ” Измените настройки управления учетными записями пользователей ».
- Вы заметите, что есть несколько различных опций, которые вы можете выбрать на ползунке. Если ваш ползунок установлен на верхнем уровне, вы определенно получите больше всплывающих сообщений, чем обычно.
- Попробуйте уменьшить это значение на единицу, если оно находится на верхнем уровне, и проверьте, не это помогло.
- Мы рекомендуем вам не отключать его полностью, потому что он не будет уведомлять вас, когда приложения пытаются внести изменения в ваш компьютер и когда вы вносите изменения в настройки Windows.
Решение 4. Реестр Tweak
Если ваш уровень безопасности контроля учетных записей не был установлен на максимум, вы могли бы исправить это с помощью простого исправления реестра, которое позволит нам повысить уровень политик Exchange ActiveSync. Брокер в список автоутверждения COM UAC, что означает, что вам не нужно будет нажимать «Да» каждый раз, когда он хочет внести изменения в ваш компьютер.
- Откройте редактор реестра, выполнив поиск для «regedit» или набрав «regedit» в диалоговом окне «Выполнить», которое можно открыть с помощью Ctrl + Комбинация клавиш R.
- Проверьте, есть ли запись реестра REG_DWORD под названием {C39FF590-56A6-4253-B66B-4119656D91B4} с данными 1 в следующем месте:
HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion UAC COMAutoApprovalList
- Если он не существует, убедитесь, что вы создаете его в указанном выше месте, щелкнув правой кнопкой мыши папку COMAutoApprovalList и выбрав New >> DWORD (32-bit) Value.
- Назовите его {C39FF590-56A6-4253-B66B-4119656D91B4} и установите для него значение 1.
- После того, как мы убедились, что включили в список брокер активных политик синхронизации Exchange, давайте проверим, повышены ли права инструмента. Убедитесь, что существует следующий ключ:
HKEY_LOCAL_MACHINE SOFTWARE Classes CLSID {C39FF590-56A6-4253-B66B-4119656D91B4} Elevation
- Если он не создает его, щелкнув правой кнопкой мыши кнопку {C39FF590-56A6-4253-B66B-4119656D91B4} и выбрав Новый >> Ключ. Назовите его Elevation.
- Убедитесь, что в ключе Elevation есть DWORD с именем Enabled и убедитесь, что для него установлено значение 1.
- Проблема должна быть решена. теперь, как только вы перезагрузите компьютер.
- Если эта конкретная проблема все еще возникает, вернитесь в редактор реестра и удалите следующий ключ, если он существует в этом месте:
HKEY_CURRENT_USER SOFTWARE Classes CLSID {C39FF590-56A6-4253-B66B-4119656D91B4}
Posted by Jays99 2019-07-10T13:00:41Z
Good day all
We recently upgraded our Exchange 2016 to CU 10 and all went well without any issues, then after the reboot I noticed that the transport service was stuck on stopping.
Everything else seems to be fine, the database is mounted, there is sufficient disk space etc.
Any ideas?
Regards
17 Replies
-
habanero
Microsoft Exchange Expert
-
check
302
Best Answers -
thumb_up
526
Helpful Votes
It will probably fail to start at some point in time. What errors are in the corresponding event log?
Was this post helpful?
thumb_up
thumb_down
-
check
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
Nothing out of the ordinary,
MessageTrackingLogs: Failed to create the log directory: M:logs because of the error: Could not find a part of the path ‘M:’.. Logs will not be generated until the problem is corrected — This location has never existed
Watson report about to be sent for process id: 18080, with parameters: E12IIS, c-RTL-AMD64, 15.01.1531.003, MSExchangeSubmission, M.E.Transport.Logging, M.E.T.L.M.MessageTrackingLogWriterProvider.CreateLogWriter, System.NullReferenceException, 884d-dumptidset, 15.01.1531.003.
ErrorReportingEnabled: FalseCmdlet failed. Cmdlet Get-Notification, parameters -Summary «True».
The description for Event ID 16024 from source MSExchangeSubmission cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
The problem is I recently took over the Exchange responsibilities and currently trying to back track how everything was done and installed, but without any documentation it it proving to be difficult.
Regards
Was this post helpful?
thumb_up
thumb_down
-
Is it stuck on stopping after the server came back online or the server won’t shut down for the reboot? If it’s not shutting down because of it just kill the process and it should be healthy when the server boots again. If it’s having trouble on startup I would set the service to delayed start, reboot, and see if that resolves it.
Was this post helpful?
thumb_up
thumb_down
-
Nothing out of the ordinary,
MessageTrackingLogs: Failed to create the log directory: M:logs because of the error: Could not find a part of the path ‘M:’.. Logs will not be generated until the problem is corrected — This location has never existed
Watson report about to be sent for process id: 18080, with parameters: E12IIS, c-RTL-AMD64, 15.01.1531.003, MSExchangeSubmission, M.E.Transport.Logging, M.E.T.L.M.MessageTrackingLogWriterProvider.CreateLogWriter, System.NullReferenceException, 884d-dumptidset, 15.01.1531.003.
ErrorReportingEnabled: FalseCmdlet failed. Cmdlet Get-Notification, parameters -Summary «True».
The description for Event ID 16024 from source MSExchangeSubmission cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
The problem is I recently took over the Exchange responsibilities and currently trying to back track how everything was done and installed, but without any documentation it it proving to be difficult.
Regards
I assume the M: drive set up for your logs. Is that filling up, and does exchange have the correct path for saving logs? Are you taking regular backups using built-in or a third party solution? Are you logged in on the exchange admin account?
1 found this helpful
thumb_up
thumb_down
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
So I have set the service startup as disabled, manual, automatic and delayed and still the same issue is being experienced.
I have checked the V15 folder now in this case there is one on the C: drive and the D; Drive the one on the C: drive is an old one as i have puzzled together there was an old Exchange server or this could have been moved:
Now the C: drive has Program Files> Microsoft > Exchange & Exchange server > Exchange server > V15 > Logging monitoring
The D: drive has: Program Files > Microsoft > Exchange Server > V15 > Then here is the normal bin, client access etc
It is writing logs to this location, exchange management shell connects, yes I have a third party backup solution in place which took a backup yesterday but would like to get this working as we urgently need to upgrade the CU as it was extremely out dated. and then Yes I am logged in as admin
I found this in event viewer:
The worker process crashes continuously on startup: D:Program FilesMicrosoftExchange ServerV15Binedgetransport.exe. The service will be stopped.
But besides t his nothing else I can see
Was this post helpful?
thumb_up
thumb_down
-
You said «D:» drive, the error is looking for «M:» did that drive letter change? You’ll need to either change the drive letter or the location of the log storage.
Edit: Is it possible the «M» drive was a third drive connected to that server and it no longer connected for some reason? I think that because it’s strange you aren’t seeing a log folder anywhere.
1 found this helpful
thumb_up
thumb_down
-
Is circular logging currently enabled? Run this command in powershell and let me know if ‘True’ shows up under enabled.
Powershell
Get-MailboxDatabase | select name, circularloggingenabled | sort circularloggingenabled -desc | ft -AutoSize
Was this post helpful?
thumb_up
thumb_down
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
Yes circular logging is enabled:
Get-MailboxDatabase | select name, circularloggingenabled | sort circularloggingenabled -desc |
ft -AutoSizeName CircularLoggingEnabled
—- ———————-
Mailbox Database True
Was this post helpful?
thumb_up
thumb_down
-
Jays99 wrote:
Yes circular logging is enabled:
Get-MailboxDatabase | select name, circularloggingenabled | sort circularloggingenabled -desc |
ft -AutoSizeName CircularLoggingEnabled
—- ———————-
Mailbox Database Truehmm…if your backups are working properly, you shouldn’t need to have circularlogging enabled. Typically people will enable it when backups aren’t working properly and they don’t want the logs to fill up disk space.
I’m confused and a little concerned about exchange existing on both C and D drives.Run this in powershell and paste the output.
Powershell
Test-ServiceHealth
1 found this helpful
thumb_up
thumb_down
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
I am extremely concerned about a bunch of things which I am still trying to sort out (Just never enough time in a day to do it all)
For example in the management console if you go to servers, there are two servers listed one of which was the old Exchange server (Which no longer has Exchange installed on it)
[PS] C:Windowssystem32>Test-ServiceHealth
Role : Mailbox Server Role
RequiredServicesRunning : False
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeIS, MSExchangeMailboxAssistants, MSExchangeRepl,
MSExchangeRPC, MSExchangeServiceHost, MSExchangeSubmission, MSExchangeThrottling,
MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {MSExchangeDelivery}Role : Client Access Server Role
RequiredServicesRunning : False
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC,
MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning : {MSExchangeIMAP4, MSExchangePOP3}Role : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning : {}Role : Hub Transport Server Role
RequiredServicesRunning : False
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {MSExchangeTransport}
Was this post helpful?
thumb_up
thumb_down
-
The old Exchange server wasn’t uninstalled properly by whoever left this for you, you’ll need to do a manual cleanup with ADSIEdit to fix that one, plenty of docs, just take backups first before modifying.
Transport service stuck stopping is usually a bad transport agent in my experience, get-transportagent and see what is listed, do they all still exist? If not remove any that are now defunct, then any that are genuine check with the vendors for updates, such as in-line antivirus tools needing a patch for the CU you’re running.
Also are the AV scanner excludes set via your management console? Double check both the main OS ones are and those specific to Exchange, they can be scanning on access and slowing down Exchange.
2 found this helpful
thumb_up
thumb_down
-
The old exchange install wasn’t decommissioned properly. You need to resolve that before continuing. You can use ADSIedit to resolve.
example
Go to Primary Domain Controller
2. Open ADSIEDIT
3. Right Click on ADSIEdit and Click Connect to
4. Connect to “Default Naming Context”
5. Navigate to the following objects and Delete them.
DC=Domain,DC=Com -> OU=Microsoft Exchange Security Groups
DC=Domain,DC=Com -> CN=Microsoft Exchange System Objects
6. Right Click on ADSIEdit and Click Connect to
7. Connect to “Configuration”
8. Navigate to the following objects and Delete them.
CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange
CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange Autodiscover
9. Force the Active directory Replication.
Make sure you have good backups before doing this.
Edit: This guide is actually to remove the last exchange server from an environment. I’ll try to find the correct process for removing a tombstoned installation.
1 found this helpful
thumb_up
thumb_down
-
If you aren’t comfortable doing this on your own, I highly recommend opening a case with Microsoft for guidance. Recovering a damaged exchange server can be extremely difficult, time consuming, and everyone at your company will be mad at you.
1 found this helpful
thumb_up
thumb_down
-
chipotle
Microsoft Exchange Expert
-
check
39
Best Answers -
thumb_up
80
Helpful Votes
If you need to remove the Exchange server with ADSIEdit you can refer to this article and follow the steps:
REMOVE EXCHANGE SERVER USING ADSI EDIT Opens a new window Opens a new window
However that is not supported by Microsoft, and as mentioned above, for security reasons, you’d better contact Microsoft for further guidance.
1 found this helpful
thumb_up
thumb_down
-
check
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
Hi all,
After an extremely long night I managed to get it sorted out. There were more issues than what Spiceworks allows to type out in caracters. LOL
Thanks for all of the responses and ideas.
Cheers
Was this post helpful?
thumb_up
thumb_down
-
Congrats! that’s not an easy problem to tackle. Did you end up using adsiedit?
Was this post helpful?
thumb_up
thumb_down
-
OP
Jays99
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.poblano
No not yet, that has actually been scheduled for tomorrow (As I only finished at 7 AM this morning) to basically remove all entries from the old Exchange server and old Domain Controller as well as build a new secondary domain controller as well as a secondary Exchange server to act as a replication server (This will be done using our backup solution and doing a stand by copy of the server in VMware and add another database as well as to sort out a few other issues to get the server to a point where you would say it is following best practice
Oh yes and I will be disabling Circular Logging as this is not needed (Thanks for reminding me of this)
Was this post helpful?
thumb_up
thumb_down
Read these next…
Merging two domains with the same name?
Windows
It seems that a possible company merger is coming down the pipeline, but as luck would have it, the active directory domains have the same name (ie, domain.local)The domain I maintain is running server 2019 at a 2016/2019 functional level.The other domain…
How can I track changes to network adapter configuration
Windows
Ok, so we have a site where most of the users have local admin and they have a small group of users who «know about computers». The site runs pretty smoothly but we’re seeing a bunch of users who are able to function on the wired network but aren’t able …
Snap! — Cooling in Antarctica, Back to the Moon, Biological Clothing, AI Sci-Fi
Spiceworks Originals
Your daily dose of tech news, in brief.
Welcome to the Snap!
Flashback: February 3, 1986: The term “vaporware” is first used by Philip Elmer-DeWitt in a TIME magazine article (Read more HERE.)
Bonus Flashback: February 3, 1966: Luna 9 Lan…
Safety Glasses with Glasses
Networking
I’m going to be pulling some new wire soon through some dirty drop ceilings, and without fail, at some point I always get a piece of something in my eye at some point during the job.I’d like to avoid that this time.I have struggled to find safety glasses …
AD on-premise courses
IT & Tech Careers
Hello!We have a predominantly on-prem AD environment. Whilst we will be moving to M365 that will be in a while.We have a number of junior staff that need basic instruction in Active Directory and file/folder permissions. I recall many years ago the MC…
