An apparently common issue with Outlook for Mac 2011 is crazily highCPU usage, enough to spin up the fans on a desktop machine or drainthe battery on a laptop, when Outlook really shouldn’t be doinganything.
Exchange 2016 High CPU usage on a exchange 2016 after migration from exchange 2010. Hardware Setup: VM (Windows Server 2016), 2 virtuell sockets with 2 processors each, 32gb of ram running on a ProLiant DL360p gen8, all behind a firewall. (top 13 are mac users with office for mac). Configure Outlook Anywhere.
If you do some Googling, you’ll find a lot of people complaining andalmost as many recommended solutions. Updating to a version after14.2 is a typical suggestion, as is deleting and rebuilding your mailaccounts (ugh, no thanks).
Keeping Outlook up to date isn’t a bad idea, but the problem stillpersisted with the latest version as of today (14.4.3).
In my case, the high CPU usage had something to do with my GmailIMAP account, which is accessed from Outlook alongside my Exchangemailbox. Disabling the Gmail account stopped the stupid CPU usage,but that’s not really a solution.
What did work was using the Progress window to see what Outlook was upto whenever the CPU pegged. As it turned out, there was a particularIMAP folder — the ‘Starred’ folder, used by both Gmail and Outlookfor starred and flagged messages, respectively — which was beingconstantly refreshed by Outlook. It would upload all the messages inthe folder to Gmail, then quiesce for a second, then do it overagain. Over and over.
Outlook’s IMAP implementation is just generally bad, and this seemsto happen occasionally without warning. But the Outlook engineersseem to have anticipated it, because if you right-click on an IMAPfolder, there’s a helpful option called “Repair Folder”. If you useit on the offending folder, it will replace the contents of the localIMAP store with the server’s version, and break the infinite-refresh cycle.
Dynamsoft Webcam SDK provides JavaScript APIs that enable you to easily capture images and video streams from USB Video Class (UVC) compatible webcams from within a browser. With the browser-based Webcam library, you can capture a live video stream into a container and grab an image with a couple lines of code in your web application.Feature Highlights:. Webcam control for mac.
So, long story short; if you have high-CPU issues with Outlook Mac,try the following:
And, of course, lobby your friendly local IT department to usesomething that sucks less than Exchange.
0 Comments, 0 Trackbacks
[/technology] permalink
Can't believe Outlook Mac kept giving me issues. This is the 2nd major one in a week.An apparently common issue with Outlook for Mac 2011 is crazily highCPU usage, enough to spin up the fans on a desktop machine or drainthe battery on a laptop, when Outlook really shouldn’t be doinganything.
Exchange 2016 High CPU usage on a exchange 2016 after migration from exchange 2010. Hardware Setup: VM (Windows Server 2016), 2 virtuell sockets with 2 processors each, 32gb of ram running on a ProLiant DL360p gen8, all behind a firewall. (top 13 are mac users with office for mac). Configure Outlook Anywhere.
If you do some Googling, you’ll find a lot of people complaining andalmost as many recommended solutions. Updating to a version after14.2 is a typical suggestion, as is deleting and rebuilding your mailaccounts (ugh, no thanks).
Keeping Outlook up to date isn’t a bad idea, but the problem stillpersisted with the latest version as of today (14.4.3).
In my case, the high CPU usage had something to do with my GmailIMAP account, which is accessed from Outlook alongside my Exchangemailbox. Disabling the Gmail account stopped the stupid CPU usage,but that’s not really a solution.
What did work was using the Progress window to see what Outlook was upto whenever the CPU pegged. As it turned out, there was a particularIMAP folder — the ‘Starred’ folder, used by both Gmail and Outlookfor starred and flagged messages, respectively — which was beingconstantly refreshed by Outlook. It would upload all the messages inthe folder to Gmail, then quiesce for a second, then do it overagain. Over and over.
Outlook’s IMAP implementation is just generally bad, and this seemsto happen occasionally without warning. But the Outlook engineersseem to have anticipated it, because if you right-click on an IMAPfolder, there’s a helpful option called “Repair Folder”. If you useit on the offending folder, it will replace the contents of the localIMAP store with the server’s version, and break the infinite-refresh cycle.
Dynamsoft Webcam SDK provides JavaScript APIs that enable you to easily capture images and video streams from USB Video Class (UVC) compatible webcams from within a browser. With the browser-based Webcam library, you can capture a live video stream into a container and grab an image with a couple lines of code in your web application.Feature Highlights:. Webcam control for mac.
So, long story short; if you have high-CPU issues with Outlook Mac,try the following:
And, of course, lobby your friendly local IT department to usesomething that sucks less than Exchange.
0 Comments, 0 Trackbacks
[/technology] permalink
Can't believe Outlook Mac kept giving me issues. This is the 2nd major one in a week.