Scenario: A user wants to get rid of the Clutter functionality for their Mailbox, but does not see the Clutter settings within their Outlook client or Outlook on the Web (aka OWA or whichever name you want to refer to it as since its been rebranded so many times). Typically there are clutter options available to the end user within their client. However Clutter settings will only appear when:
If user currently has Clutter enabled:
-Clutter settings appear
If user currently has Focused Inbox enabled:
-Clutter settings will not appear
If neither Clutter or Focused Inbox is enabled:
-Both Clutter and Focused Inbox appear as options in the user’s Mail Settings
Solution: If disabling the Focused Inbox doesnt allow it to appear, feel free to disable Clutter from the backend by running commands similar to this:
set-clutter -identity steve -enable $False (Or $true to turn it back on)
get-clutter -identity steve | Select IsEnabled
Category: Outlook 2016
Determine if “Delay Delivery” was used for a message sent
Scenario: You want to determine if a message that you received was sent using “Delay delivery”
Indicators: Below are some indicators to determine if the message was sent using Delay Delivery:
Message Header: (located on any message received by the sender)
–Deferred-Delivery – Check for t his property in the Message Header similar to Deferred-Delivery: Mon, 4 Jan 2021 15:36:00 +0000
Email Item Properties: (located only on the sender’s email item located in the sent items)
–Outlook Column View: Defer Until, Received, and Sent
–
–MFCMAPI: PR_Message_Delivery_Time, PR_Deferred_Delievery_Time, PR_Deferred_Send_Time
Note: The properties of the test message above show that the message was created at 10:34am EST but delayed delivery until 10:36am EST.
Remove an orphaned MSExchDelegateListBL (autodiscover) entry
Scenario: A user no longer has fullaccess to a shared mailbox BUT the shared mailbox still attempts to reconnect via Autodiscover in the Outlook profile.
Solution: The following scriptlets will detect the autodiscover links associated with the problem mailbox and attempt to remove them. Note, you can remove all backlinks, or specific backlinks.
$u = "Steve"
$u_DN = Get-ADUser $u | select -ExpandProperty DistinguishedName
$d = Get-ADUser $u -Properties msExchDelegateListBL | select msExchDelegateListBL
#To remove all backLinks
$d.msexchdelegatelistBL | %{Set-ADUser $_ -Remove @{msExchDelegateListLink = "$u_dn"}}
#To Remove specific BackLinks
$SharedMailboxToRemove
$d | Where msexchdelegatelistBL -like "*$SharedMailboxToRemove*" | Select -ExpandProperty msexchdelegatelistBL | %{Set-ADUser $_ -Remove @{msExchDelegateListLink = "$u_dn"}}
Scenario: When adding a new mail profile, it automatically completes and does not display the Add Mail wizard for a different account
Scenario: You want to add a new mail profile for a different account in Outlook. When adding the new mail profile (via Control Panel OR via “Choose Profile” when opening Outlook), the new profile automatically completes and adds YOUR email account, and it doesn’t display the “Add Account” wizard where you can enter in a different email account.
Cause: This is by design in Outlook 2016 through the use of ZeroConfigExchange.
Workarounds:
If you wish to disable this feature all together:
Navigate to one of the follow keys: HKey_Current_usersoftwareMicrosoftOffice16.0outlookautodiscover or HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice16.0OutlookAutoDiscover Disable the ZeroConfigExchange DWORD by setting the value to 0
If you wish to keep this feature enabled but allow the wizard to pop up for additional accounts, you can leave the ZeroConfigExchange DWORD enabled (meaning it has a value of 1) and you can add the DWORD ZeroConfigExchangeOnce
Navigate to: HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice16.0OutlookAutoDiscover Add ZeroConfigExchangeOnce and set the value to 1
Cannot View Free/Busy information of user after Outlook 2016 client upgrade
Scenario: After a Outlook client upgrade to 2016, you notice that you cannot view/alter the calendar of someone you have delegated permissions for in the Outlook client. OWA works fine and you can still view/alter the calendar through a Outlook 2013 client.
Resolution: We found that the WindowsEmailAddress is:
- Different than the PrimarySMTPAddress
- not a email alias for the mailbox (The WindowsEmailAddress shows a alias that is not in the proxy addresses/Emailaddresses).
Change the WindowsEmailAddress to an address that matches the PrimarySMTPAddress (which is a alias/proxyaddress for the mailbox)
Set-Mailbox jdoe1 -windowsemailaddress <whatever the primarysmtpaddress is>
Outlook’s Autodiscover Redirect Limit – Hybrid Autodiscover Breaking for Exchange Online Mailboxes / Remote On-Premises Mailboxes
Scenario: After introducing additional Exchange On-Premises servers, we noticed that Autodiscover stopped working for our Exchange Online Hybrid mailboxes that were on computers internal to the domain. Using the ‘Test E-mail AutoConfiguration’ feature in Outlook, it would fail after the SCP/DNS autodiscover lookup.
Reason: Outlook has an Autodiscover Redirect limit of 8-10 responses. Being we had more than 10 servers in our Exchange Infrastructure, once it hit the response limit from each SCP lookup for each server, it would then fail all redirects thereafter. You do not need 100 SCP Failures if its going to fail after the first 10 servers.
Solution: You can reduce the number of SCP lookup’s by performing any of the following.
- Set the AutoDiscoverSiteScope value on each Exchange server so it only serves requests for each AD Site via the following command: Set-ClientAccessServer ExSrv1 -autodiscoversitescope NewYork (Or a combination NewYork,Baltimore,Tampa)
- Set the AutoDiscoverSiteScope to $null so it does not participate in SCP lookups via the following command: Set-ClientAccessServer ExSrv1 -AutodiscoverSiteScope $null
- Set the AutoDiscoverServiceInternalURI to $null so it does not participate in SCP lookups via the following command: Set-ClientAccessServer ExSrv1 -AutodiscoverServiceInternalURI $null
Ex-Shell 