Posts Tagged ‘Outlook 2016’

https://techcommunity.microsoft.com/t5/outlook-global-customer-service/how-outlook-2016-utilizes-exchange-server-2016-fast-search/ba-p/381195#

Secondary mailboxes

When Outlook 2016 released, the plan was to only support FAST search on your primary mailbox. However, starting in the Fall of 2017, you should see that any Exchange email account added through File | Account Settings (also known as MultiEx or multiple Exchange accounts) now fully supports FAST search.

 

If you are limited to using an older build of Outlook 2016 and search in a MultiEx mailbox, the FAST query may be submitted in the context of the logged on user (you). This causes the search results to be pulled from your own mailbox, not the secondary mailbox that currently has the focus in your Outlook client. If you are unable to upgrade your Outlook 2016 client to the November 2017 Monthly Channel Build, you can temporarily work around this limitation by using one of the following options:

  • Change the search scope to All Outlook Items, Subfolders, or All Mailboxes
  • Disable Outlook 2016’s use of FAST search via policy or local user registry setting (see the next section)

Note Other types of secondary stores, such as those added via Open these additional mailboxes or those that are automatically configured via AutoMapping, are still limited to WDS.

 

HOWEVER

 

I’ve found users report searching still sucks in their shared and/or secconday mbxs. So per document set the below DWORD key to 1 if a user reports this – though I’m still waiting to hear if there are negative connotations to this change

 

 

Disable Server Assisted Search

Group Policy registry path:
HKEY_CURRENT_USER\software\policies\Microsoft\office\16.0\outlook\search
DWORD: DisableServerAssistedSearch

Disables Outlook from requesting and using Search results from Exchange for cached and non-cached mailbox items. Instead, it will use search results from W

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

A company who had recently upgraded its Client PC’s to Outlook 2016 from Outlook 2010 and were using Exchange 2016 were starting to get

Out Of Office not working and also Free and Busy

After the removal of Microsoft Exchange Web Services Managed API 2.2  on Exchange 2016 server the problem with Out of Office was fixed an the EventID 5011 warnings in the eventvwr are gone

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

outlook-security-popup

 

You will need to run the below as Administrator , if the use doesn’t have local admin you will need to change them to one then remove after  ;

  • Right-click on the Outlook shortcut holding the SHIFT key and choose Run as administrator
  • Go to File > Options > Trust Center > Programmatic Access
  • Set the programmatic access to Never warn me about suspicious activity (not recommended)

outlook-programmatic-access

 

IMPORTANT NOTE: If these option are greyed out, it usually means that you didn’t run Outlook with administrative rights.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Outlook\Security
DWORD: ObjectModelGuard
Value: 2

As an alternative way, you can achieve the same result by altering your registry file in the following way:

  • Navigate through   (create the key if it doesn’t exist)
  • Add the following DWORD item:
    •  , with a value of 1.
    •  , with a value of 3.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
  • Navigate through   (create the key if it doesn’t exist)
  • Add the following DWORD items:
    •  , with a value of 1.
    •  , with a value of 3.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
    •  , with a value of 2.
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 with a new Office 365 account receive the above error during downloading new email. Testing the connection it looks like the Wireless connection she was connecting to the internet with was intermittently slow.

Changing the Wifi to a hotspot or cable connection resolved this

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 trying to add your email account to Outlook 2016 you get the follow error

an encrypted connection to your mail server is not available

365 is obviously  encrypted which means there must be something wrong with Autodiscover

  1. Check Autodiscover

Should be a CNAME to autodiscover.outlook.com. ( Put full stop on the end )

2. Make sure you have finished setting up the domain in 365 or it won’t listen for the domain

Test Autodiscover via : https://testconnectivity.microsoft.com/

Try logging in to powershell on your 365 Tenant and disabling OAuth2 (2fa ) 

Set-OrganizationConfig -OAuth2ClientProfileEnabled:$true
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 client with Office 365 trying to Cache a Shared Mailbox. Outlook brought up a load of Sync Errors

Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing.

If the server is self hosted you can remove the restriction via  : http://henrysluiman.blogspot.com.au/2013/02/how-to-increase-number-of-open-items.html

Microsoft fix for this is removed the Cache! https://support.microsoft.com/en-us/help/3115602/performance-problems-when-you-try-to-access-folders-in-a-secondary-mai

After rebuilding the OST and Profile and still no luck I started Outlook in Safemode which enabled the downloading of the emails

Once downloaded I could start Outlook Normally and all worked fine

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