TechShizz | All posts tagged 'Outlook 2016'

Microsoft Outlook can’t start Microsoft InfoPath

Problem

When launching outlook you receive a popup saying "Microsoft Outlook can’t start Microsoft InfoPath"

Cause

Unknown

Solution

 Run Regedit & go to HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options\Mail

If the "Mail" kay doesnt exisit, create it.

Create a new DWORD called “DisableInfopathForms” & set the value to 1

Reference, Links and Imges

 http://www.cottenhamcomputers.co.uk/microsoft-outlook-cant-start-microsoft-infopath/ 

Disable ADAL for Outlook 2016

Problem

Various authentication issues including:

  • O365 profiles sets up instead of on prem mailbox
  • Outlook wont authenticate on Office 365
  • Outlook wont authenticate on Office 365 with SSO
Cause

ADAL is the new authentication method for azure cloud solutions. It over-rides the standard kerberos, basic and NTLM protocols.

Solution

ADAL can be disabled by registry key:

To disable modern authentication on a device, set the following registry keys:

Registry key

    Type

       Value

HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL

    REG_DWORD

        0


Reference, Links and Imges

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook/modern-authentication-on-outlook-2016-keeps-on/98a263f4-ab9c-4d6f-b5eb-2728a8e77412 

Read Receipts showing wrong time or time zone for Office 365 mailbox

If you get read receipts that state the time it was read was the previous day, or the time is just wrong this could be to do with the time settings on the mailbox.

Microsoft have a poor guide on this explaining WHY it happens, but does not say how to resolve it. 

https://support.microsoft.com/en-gb/help/2800633/read-receipt-from-an-office-365-recipient-displays-incorrect-time-zone-information

Here is the solution:

We can check this by first connecting to Office 365 via Azure PowerShell, and then running the follwing command. 

Get-MailboxRegionalConfiguration -Identity rtownsend@domain.co.uk | fl

If the TimeZone is wrong, it will be obvious. You will need to change it to your users local time zone. To see a list of time zones run this command in PowerShell.

$TimeZone = Get-ChildItem "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Time zones" | foreach {Get-ItemProperty $_.PSPath}; $TimeZone | sort Display | Format-Table -Auto PSChildname,Display

Once you know your time zone, run the following (replacing your correct time zone). 

Set-MailboxRegionalConfiguration -Identity rtownsend@domain.co.uk -TimeZone "GMT Standard Time"

https://technet.microsoft.com/en-us/library/dd351103(v=exchg.160).aspx

 

Error: "The security certificate has expired or is not valid" in Outlook

After migrating companies from on-premises exchange to Office 365, user may see the following error. 

"The security certificate has expired or is not yet valid"

This is because the local exchange server, although switched off still runs the IIS portion of exchange. The OWA is pointing users Outlook to look the the previous certificate that was used, not Microsoft's servers.

To fix this we need to amend the AutoDiscoverServiceInternalUrl value. 

1. Log on to the old on-premeises exchange and start the Exchange Power Shell

2. Check current value by running:

Get-ClientAccessServer -Identity "[SERVERNAME]" | Format-List

I would recommend screen taking a screen shot of this in case you need to revert back. Next, ping your office 365 autodiscover record and verify it's correct. E.g.

Ping autodiscover.domain.com

If all is OK you need to update as follows:

Set-ClientAccessServer -Identity "MBX-01" -AutoDiscoverServiceInternalUri "https://mbx01.contoso.com/autodiscover/autodiscover.xml"

Once this is done, clear the DNS server cache and restart the DNS service. Then on the client machines flush dns:

ipconfig /flushdns

This should resovle the error

Ref: https://technet.microsoft.com/en-us/library/bb125157(v=exchg.160).aspx