Posts Tagged ‘Outlook’

For a new deployment we needed for Outlook to show the Task’s ToDo List on the Outlook Home Screen







I couldn’t find this documented anywhere so I have to monitor the Outlook.exe during the change to find out what Registry Key it changed



Item : PinMail

Type : Dword

Value : 4

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

With the increase attack on 365 subscriptions without two factor enabled its good to check when a rule actually got added. This cannot be done with powershell you will need to perform with MFCMAPI

Download the latest MFCMAPI of 32bit or 64bit ( depending on your Office/Outlook version ) release here

You can do this on the User’s computer who should already have Outlook installed or you can create an Outlook profile as the user you would like to check the rule for on another PC. You can also create an Outlook Profile as an Administrator and give yourself full access to the User’s Maibox

Open MFCMAPI , Open the Profile , then go to Session and Logon

Double click on the account

Open the Root Folder and Navigate to here and right click on Inbox and Choose Open Associated Contents Table

The rule will look something like this , Message Class : IPM.Rule.Verson2.Message

Double click on this

Then find the following Name and check the value to confirm its the right Rule

Then Use this Rule to find the Date Created
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

So you are fully up-t0-date with Outlook however you are having issues with performance

  1. The first thing Microsoft 365 support will do it recreate your profile, and also recreate your OST , so make sure you have done this

  2. Next they will get you to run this :  Microsoft Support and Recovery Assistant for Office 365 (also known as ‘SaRA’). If will give you a list of problems you can work towards resolving

  3. Make sure you upgrade to 64bit Version of Office

Outlook display issues only affect 32-bit versions of Office. Normally, 32-bit applications can only access 2 GB of memory that all 32-bit apps share. Outlook appears to handle this limit poorly, making it unusable once available memory dips below what Outlook requires to run smoothly.

To see how much memory is available for Outlook, try the VMMap Sysinternals tool, which shows the private bytes or memory distributed for a process that cannot be shared. VMMap shows the bit version of Outlook, as well. For 32-bit Outlook, a number at 250,000 K or less is bad.

Use the following registry setting to prevent add-ins from using the extra memory available from LAA mode. Change the xx to 15 for Outlook 2013 or 16 for Outlook 2016:
HKEY_CURRENT_USER\Software\Microsoft\Office\xx.0\Outlook\ReserveHighAddressRange DWORD Value ‘1’

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a user not be able to delete items from another Users exchange Mailbox ( 2010 )  apart from having full permissions to the Mailbox 

Exchange 2010 Mailbox has a 30GB limit of the Recoverable Items Folder

To find this current quota run : 

Get-MailboxFolderStatistics -Identity %username% -FolderScope RecoverableItems | Format-List

To delete them , run : 

Search-mailbox -identity %username% -SearchDumpsterOnly -DeleteContent

If you can’t find Search-Mailbox , you need to assign the below role to the user and restart exchange shell

New-ManagementRoleAssignment –Role "Mailbox Import Export" –user "administrator"


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a user who’s accepted meeting requests were going straight to their Deleted items instead of being displayed in their Inbox

  • Checked in Mail and Calendars settings in Outlook which all were the default
  • Checked Delegate Permissions for the user
  • Check the Rules inside of Outlook Nothing there

Closing all Outlook windows and trying this again , the accepted meeting request still went the deleted items in Webmail which showed this was server side not Outlook/Client Side.  

Turns out there was a specific Webmail Server side Inbox rule/filter doing this which was not displayed in the Outlook Client. Disabling this resolved the issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Mimecast Guide

Azure Microsoft Guide

Create a Distribution Group in Office 365, this will be to Add the users to you want enable SSO on , add Users 

Make sure Mimecast is Synced with Office365 AD – Services -> Directory Synchronization ( Connect to 365 ) 

Perform manual sync in Mimecast to download user and group


On Azure – Got o Azure Active Directory, All Application find:  Mimecast Personal Portal

Next Single Sign-On

Sign on URL :

Identifier : ID% per Mimecase User Guide

Reply URL :

User Identifier : user.mail

Azure AD Properterties : User assignment  required No 


Configuring Mimecast-Personal-Portal for single sign-on

1.In a different web browser window, log into your Mimecast Personal Portal as an administrator.

2.Go to Services > Applications.

3.Click Authentication Profiles.

4.Click New Authentication Profile.

5.In the Authentication Profile section, perform the following steps:

a. In the Description textbox, type a name for your configuration.

b. Select Enforce SAML Authentication for Mimecast Personal

c. As Provider, select Azure Active Directory.

d. In Issuer URL textbox, paste the value of Azure AD SAML Entity ID : which you have copied from Azure portal.

e. In Login URL textbox, paste the value of Azure AD Single Sign-On Service URL : which you have copied from Azure portal.

f. In Logout URL textbox, paste the value of Sign-Out URL which you have copied from Azure portal.

g. Open your Downloaded Azure AD Signing Certificate (Base64 encoded) in notepad downloaded from Azure portal, copy the content of it into your clipboard, and then paste it to the Identity Provider Certificate (Metadata) textbox.

h. Select Allow Single Sign On.

i. Click Save.

Now Add a New Application Settings to Application and Link the Group you created in the first step to use this New Authentication Profile


reply address ‘’ does not match the reply addresses configured for the application: ‘’.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

On setting up a new surface for a user , which was enabled for modern authentication MFA 2fa in 365 , when asked in Outlook for Need Password the login prompt would come up blank and disappear.

  • Signing out and back in to Outlook did not fix this
  • Proxy Configuration was checked

**** Update ***** Make sure you have the following Reg Keys

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\DisableADALatopWAMOverride] – REG_DWORD “1”

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL] – REG_DWORD “1”

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a user who was sending emails with the following displayed in Outlook

I thought this issue and error was displaying when a user emailed back his email , however later I found out this was actually the error that showed when he created a new message using the signature

The issue was the email signature was referencing a server share and the PC was not on the domain

To fix this if you manually copy the images to the local machine you can edit the .htm file in the signature folder then find the HTML which references the incorrect image location and reference the new location where you saved the images to

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

It is possible to disable certain autodiscover steps by creating DWORD entries in the HKEY_CURRENT_USER\Software\Microsoft\Office\<version>\Outlook\AutoDiscover registry key.

Note. <version> can be 16.0 for Outlook 2016, 15.0 for Outlook 2013 and 14.0 for Outlook 2010.

The following DWORD entries can be created:

  • ExcludeHttpRedirect
  • ExcludeHttpsAutoDiscoverDomain
  • ExcludeHttpsRootDomain
  • ExcludeScpLookup
  • ExcludeSrvRecord
  • ExcludeLastKnownGoodURL (Outlook 2010 version 14.0.7140.5001 and later)
  • ExcludeExplicitO365Endpoint (Outlook 2016 version 16.0.6741.2017 and later)

Add the DWord of 1 to any of the above to skip the check

Per here


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)