Posts Tagged ‘Outlook’

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

Azure

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

Next Single Sign-On

Sign on URL : https://au-api.mimecast.com/login/saml

Identifier : https://au-api.mimecast.com/sso/%Customer ID% per Mimecase User Guide

Reply URL : https://au-api.mimecast.com/login/saml

User Identifier : user.mail

Azure AD Properterties : User assignment  required No 

Mimecast

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 : https://sts.windows.net/434324324342343242323442/ which you have copied from Azure portal.

e. In Login URL textbox, paste the value of Azure AD Single Sign-On Service URL : https://login.microsoftonline.com/434324324342343242323442/saml2 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

Issues

reply address ‘https://au-api.mimecast.com/login/saml’ does not match the reply addresses configured for the application: ‘https://au-api.mimecast.com/sso/’.

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: 0.0/10 (0 votes 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 https://support.microsoft.com/nl-nl/help/2212902/unexpected-autodiscover-behavior-when-you-have-registry-settings-under

 

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

When adding an Exchange account to a Send and Recieve Group you could get Sync Errors occuring

published calendar 0x80004005

To check which Published Calendar the error was talking about , go into  Account settings and go to the following tab below

You can remove these if you don’t need/want them

Image result for published calendar

 

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

There is a logon script that runs the following (Replace the server with whatever your imanage server is)

“C:\Program Files (x86)\Interwoven\WorkSite\addiman.exe” %IMANAGESERVER%

The details can also be added via Registry in the Group Policy : 

Key : HKCU\Software\Interwoven\WorkSite\8.0\Common\Login\RegisteredServers\%IMANAGESERVER%\

Value : Autologin
Type : REG_SZ
Value Data : Y

Value : DATABASES
Type : REG_MULTI_SZ
Value Data : %DATABASE%

Value : Local
Type : REG_SZ
Value Data : N

Value : Password
Type : REG_SZ
Value Data : 

Value : ServerName
Type : REG_SZ
Value Data : %SERVERNAME%

Value : TrustedLogin
Type : REG_SZ
Value Data : Y

Value : UserID
Type : REG_SZ
Value Data : 

 

 

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

Upon enabling two-factor authentication, when trying to open Outlook  you get the following error

Invalid Request: The request Tokens do not match the user context.

This is due to your existing password conflicting.

If you close down outlook

Open up command prompt and enter :   control /name Microsoft.CredentialManager

Clear out MicrosoftOfficeXX_Data:ADL and  MicrosoftOfficeXX_Data:ordid password

Start Outlook again

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

outlook_message_2007Recently we had an Outlook issue , where an Outlook Addin’s tab in the ribbon would not show in a users outlook , however on the same Windows profile and different Outlook profile the tab would show.

We checked to make sure the plugin with enabled in the Registry and Outlook and also reset all the custom tabs however only the Addin’s Status would show up in the Add In’s Tab instead of it’s own.

Speaking to the provider of the Addin , proved the add-in was actually licensed by email Domain name! We got the users Domain name added to the license file and voila , came straight away!

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