You can install HTTP Watch or Fiddler on your workstation. Open IE and start a capture. Both programs will log Outlook's HTTP(s) activity. That will give you a better idea on what Outlook is doing when it hangs.
Any particular reason why you aren't doing cached exchange mode? I would be curious if the issues occur in cached mode. It might be worth testing with.
You can use resource monitor on your exchange server to check the server performance. Click on the "Disk" tab and note what your disk queue lengths are. Anything over 5 for extended periods of time is not good.
I will try the HTTP Watch, but i tested it without the Exchange HTTPS Configuration. Currently outlook have to use mapi, because no https proxy is configured in outlook.
Cache Mode: There are several problems with cache mode. First, There are Local files, which are in some cases are not wanted to have. And as well on our terminalservers, we can't activate exchange cache mode, otherwise the profile folders would explode.
So far i tested quite a few of the counteres and i am more than happy to say, that i am always under the optimal number.
Edit: Did the other counters now and all looks fine. Someone got any idea, how can i figure out, what outlook is trying to query with the call. In the screenshort you see outlook sending a packet to the server and the server recieves it. Then it takes up
to 20 seconds until the server is sending the information back to outlook. Now i need to some how figure out, what the server is searching for in this time.
For now i only now, does not show up in outlook save mode and does not show up on all users. Further more, i checked the mailbox databases und migrated mailboxes without results on the problem. The Counters look fine.
Whats next ? Any idea ?
-
Edited by
xaszy
17 hours 0 minutes ago