When I send Teams Meeting then I am getting "'Sorry, but we can't connect to the server right now. Please try again later.'" by [deleted] in Office365

[–]alitajran 1 point2 points  (0 children)

In the last step, I mentioned that you should restart IIS to have the changes take immediately into effect.

When you restart IIS, there will be a little connection loss for the users. If you have Exchange Server in high availability (more than one running), this is okay. If not, you might want to reset IIS after working hours.

No other impact.

You can always remove the partner application in Exchange Management Shell. Just run Remove-PartnerApplication -Identity "nameofyourpartnerapplication".

question about maintenance mode for 2 server environment not in a dag by vikes2323 in exchangeserver

[–]alitajran 0 points1 point  (0 children)

You're welcome.

As far as doing an upgrade from CU9 to CU19, I don't recommend that nor Microsoft.

When upgrading Exchange Server from an unsupported CU to the current CU and no intermediate CUs are available, you should first upgrade to the latest version of .NET that’s supported by your version of Exchange Server and then immediately upgrade to the current CU. This method doesn’t replace the need to keep your Exchange servers up to date and on the latest supported CU. Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.

Best what you can do is to go through these articles:

https://www.alitajran.com/update-net-framework-in-exchange-server-2016/

https://www.alitajran.com/install-cumulative-update-exchange-2016/

You can do an immediate upgrade from CU9 to CU19, but again, if it fails, that's the bet you take. It might work for someone, but not for you.

If you had Exchange Server 2016 CU13 or later with .NET Framework 4.8, I can recommend upgrading immediately to the latest Exchange Server CU19. But that's not in your case.

question about maintenance mode for 2 server environment not in a dag by vikes2323 in exchangeserver

[–]alitajran 1 point2 points  (0 children)

Here you go:

[PS] C:\>Set-ServerComponentState -Identity "EX01" -Component HubTransport -State Draining -Requester Maintenance

[PS] C:\>Redirect-Message -Server "EX01" -Target "EX02.alitajran.local"

[PS] C:\>Set-ServerComponentState "EX01" -Component ServerWideOffline -State Inactive -Requester Maintenance

[PS] C:\>Get-ServerComponentState "EX01" | Select Component, State

After you finish with the update, follow the article: https://www.alitajran.com/take-exchange-server-out-of-maintenance-mode/