This post is also available in: Slovenian
Some users complained about Otlook abnormally slowly opens or. applying on the Exchange server. For some it takes 10 min, for some 1 hour to open Outlook and to be connected to Exchange server. After that sending and reciving emails was ok. Many users however did not have any problems connecting. What to do?
Problems at the workstation
First you look if the Outlook client is configured to run in chached mode or not. In this case, tick of cached mode because an error may occur if user have a large mailbox or a bunch of additional mailboxes and connections to others calendars. All this can slow down the app. Sometimes it helps to erase the profile and re-create it.
Often happens problems with the outlook credentials in the Credential Manager, so you wipe all outlook certificates. When you restart Outlook, it certificate i recovered. If you are ussing Outlook anywhere with RPC/HTTP, you temporally suspend it.
Problems on the Exchange server
After upgrading to a newer CU is ofthe the case to re-register Performance Counters using PowerShell. But first check if the registry key was added TCP Keep Alive Time.
TCP Keep alive Time
This parameter determines how often TCP attempts to verify whether the connection is still valid and if not, is suspended. If you receive a response to the transmitted packet is after the time that we set, again checking whether the connection is still valid or not. With TCPMaxDataRetransmissions will be determined by how many packets are sent without a response before the connection is lost.
Default setting in Exchange server is 2 hours.
How to check if a server have default or reccommended settings Keep Alive time?
Josh Jerdon is author of powwershell script to verify the status of all Exchange servers: TCP Keep Alive Time Report Script
Performance Counters ERRORS
Error ID 106 about Performance counter. solutions on the internet most often mentioned GlsPerformancecounters.xml missing and after installing the new CU it happens ofthen that file is no longer in default folder for Exchange 2013 c:\Program Files\Microsoft\Exchange server\v15\setup\perf\ . After GLSPerformancecounters usually get another error about other coutner missing, so it’s best to re-register all coutners – all 158 Exchange Performance Counters.
Author Jeff Guillet; Fix for Performance Counter Updating Error (Event 106) on Exchange Servers
$files = Get-ChildItem $exinstall\setup\perf\*.xml
Write-Host "Registering the perfmon counters"
$count = 0;
foreach ($i in $files)
$f = $i.directory, "\", $i.name -join ""
Write-Host $count $f -BackgroundColor red
New-PerfCounters -DefinitionFileName $f