Tag Archives: e-mail

How to Improve Microsoft Outlook Performance

Confirm that your Microsoft Outlook client is up to date Office Account > Update Options > Update Now

Consider disabling “Show Apps in Outlook” in Outlook Options >  AdvancedConsider disabling Message arrival notifications, these include “Play a sound”, “Briefly change the mouse pointer”, “Show and envelope icon in the taskbar”, and “Display a Desktop Alert” in Outlook Options > Mail

Consider disabling “Use animations when expanding conversations and groups” in Outlook Options >AdvancedConsider disabling “Show Weather on the calendar” in Outlook Options > Calendar

Microsoft Outlook for Android will require Android 9.0 or above starting 10th July 2023

Beginning 10th July 2023, Outlook for Android will no longer support Android 8.x or below.  Users will need to upgrade their Android operating system to Android 9.0 or newer.  If this is not possible then the Android device will need to be replaced with a device that is able to run Android 9.0 or newer.

If users are using Outlook for Android on phones running an older version of Android, they will no longer be able to update to newer versions of Outlook for Android when Microsoft  implement this change.

It should be possible to use the “Get-MobileDevice” powershell command to export a list of devices that are using ActiveSync.  Using this report it should then be possible to review which Android devices are still running an OS that is too old.

Get-MobileDevice | Export-Csv -Path “c:\getmobiledevice\devices.csv”

When using the powershell command above please make sure that the output folder exists.  In this case I created a folder called “getmobiledevice” on the root of C:\

Update Rollup 3 for Windows Small Business Server 2011 (SBS 2011) has been Released

Update Rollup 3 for Windows Small Business Server 2011 (SBS 2011) brings support for deploying Windows 8 in your SBS 2011 environment using the SBS 2011 connect computer wizard

This update rollup contains all the updates that were included in the previous update rollup. Additionally, this update fixes the following issues

Issue 1 You receive a warning message when you try to deploy a client computer that is running Windows 8 in Windows Small Business Server 2011 Standard. Note This issue occurs because Windows Small Business Server 2011 Standard does not support client computers that are running Windows 8. However, after you apply this update, you do not receive a warning message.

Issue 2 After you run client deployment tools in Windows Small Business Server 2011 Standard, Windows Store apps do not work on client computers that are running Windows 8

Note The update described in this article adds support for user profile migration

Issue 3 You cannot remotely connect to a Windows 8 client computer from the Remote Web Access webpage

Issue 4 After you install the Microsoft .NET Framework 4.5 and then install the .NET Framework 4, you do not receive email notifications

Issue 5 You cannot download a file or a folder whose path contains non-ASCII characters on the Remote Web Access webpage

Issue 6 Assume that the name of a user, group, or organization unit (OU) contains a slash (/). When the user, group, or OU is a member of a group that is traversed during the Remote Web Access logon process, the user, group, or OU cannot log on to the Remote Web Access webpage.

Issue 7 When Windows Small Business Server uses the default configuration, Windows Server Update Services (WSUS) cannot synchronize Best Practices Analyzer (BPA) with Windows Small Business Server.  Additionally, new updates for BPA are displayed only in the optional updates menu.

Note After you install the update that is described in this article, the following changes occur in BPA and WSUS:

• Update rollups for BPA are auto-approved as update rollups for Windows Small Business Server

• The “tools” category is added to WSUS

• The BPA installation is approved and is displayed in the “Updates with Microsoft Software License Terms that are pending approval” group

Mqqm.dll – Pre Service Pack 2 Revision History for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Small Business Server 2011 (SBS 2011)

Mqqm.dll – Pre Service Pack 2 Revision History for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Small Business Server 2011 (SBS 2011)

01-Oct-2013 – 6.1.7601.22469 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2824770 – Delayed delivery when you send many messages on a Windows 7, Windows Server 2008 R2, Windows 8 or Windows Server 2012-based Message Queuing server

04-May-2013 – 6.1.7601.22317 – Mqqm.dll – x64 – http://support.microsoft.com/kb/2829589 – Message Queuing service freezes when queue size increases in Windows Server 2008 SP2 or Windows Server 2008 R2

08-Mar-2012 – 6.1.7601.21938 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2656875 – Delay when you send messages to Message Queuing clients by using a Direct=TCP format in Windows 7 or in Windows Server 2008 R2

14-Jan-2012 – 6.1.7601.21898 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2665875 – An update is available that enables you to receive messages by using a mismatched DNS CNAME alias in Windows 7 or in Windows Server 2008 R2

08-Jul-2011 – 6.1.7601.21766 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2554746 – MSMQ service might not send or receive messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008

02-Jul-2011 – 6.1.7601.21762 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2566230 – High memory usage by the Message Queuing service when you perform a remote transactional read on a Message Queuing 5.0 queue in Windows 7 or in Windows Server 2008 R2

15-Jan-2011 – 6.1.7601.21642 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2495655 – The contents of some Message Queuing messages may become corrupted when you enable message encryption in Windows 7 or in Windows Server 2008 R2

14-Jan-2011 – 6.1.7601.21641 – Mqqm.dll – x86/x64 – http://support.microsoft.com/kb/2491890 – Message Queuing may become unresponsive when you enable message encryption in Windows 7 or in Windows Server 2008 R2