[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1920
  • Last Modified:

Mailbox users using 79% of the MAPI CPU on my Exchange server

I have an Exchange server 2010 running with Servicepack 2, with rollup 2. After we migrated the users from MDeamon to Exchange 2010, I get very high network traffic and tons of logfiles is written on one specific mailbox database.

I see there is 6 users, causing this. I tried to setup their Outlook client again, but still I see very high network load on the server during a workday. If they shut down their computers, everything goes to normal.

I tried to use Exmon to see which users are causing this, and I found three so far. But I can hardly see the other three which the performance troubleshooter under toolbox shows on my Exchange server. It says:The top 6 users account for 79% of the MAPI CPU usage on the server.

What can be the cause of this? The problem seems to be only in the main workhours, could it be some calenders thats causing this? Because when migration from Outlook Connector on MDeamon, we also imported all calendars and contacts.

Would be great with some tips and how I can narrow down these six users causing this heavily load on my exchange server.

Thanks in advance.
0
Mr Woober
Asked:
Mr Woober
  • 4
  • 3
1 Solution
 
Ess KayEntrapenuerCommented:
perhaps they have a virus sending out mail unknowingly




Try to log them in when they are away and see if problem continues
0
 
AmitIT ArchitectCommented:
What is the outlook version and rollup level on exchange server. RU4 is latest. If you know the user which is causing this issue, switch them to different machine and check if that helps to resolve this issue.
0
 
Mr WooberAuthor Commented:
The users has an updated anti-virus, and they all run Outlook 2007 with Servicepack 3. I'm updating the Exchange server with rollup 4 now, only had rollup 2. Dont know if that might help with this issue or not.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
AmitIT ArchitectCommented:
I would say before upgrading to Exchange 2010 to RU4. Switch these user to different machine, and then check the result. If issue still persist, move forward to upgrade RU4 and then verify again.
0
 
Mr WooberAuthor Commented:
Thanks for the tip amit. I just sat up Outlook 2010 for one of the users that was causing these issues, and I see no stress on the server so far. So it looks like it could be the Outlook client of the user or something on his machine.
0
 
Mr WooberAuthor Commented:
I found the problem, was using Outlook Connector and some registry settings that was still there, causing the Outlook to go in a loop. Uninstalling Outlook Connector and clearing the registry fixed the problem.
0
 
AmitIT ArchitectCommented:
Where you removed this key, i guess on client side.
0
 
Mr WooberAuthor Commented:
Problem solved by myself.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now