This message was deleted.
# microsoft-365s
Slackbot
04/11/2023, 9:13 PMThis message was deleted.
s
Scott Knights
04/11/2023, 11:35 PMMaybe disable hardware acceleration if your hosts don't have acceleration hardware. Setting for this & a few other things I set:
Scott Knights
04/11/2023, 11:35 PMI also usually disable the pointless root domain autodiscovery check in Outlook.
Microsoft Outlook 2016/Account Settings/Exchange
Exclude the root domain query based on your primary SMTP address Enabled
Scott Knights
04/11/2023, 11:36 PMHave had too many certificate issues with websites on the root domain. Or even worse, misconfigured CPanel sites that return an autodiscover response.
b
Balint Oberrauch
04/12/2023, 8:49 AMMaybe reconsider the Exchange Cache Mode. 3 Months usually is enough.
☝️ 1
🙌 1
n
newbie1998
04/12/2023, 10:50 AM@Scott Knights - can you clarify what you mean on root domain query based on your primary smtp enabled...?
newbie1998
04/12/2023, 11:08 AMok, here is an updated one
m
Matt Nation
04/12/2023, 2:18 PMNot really performance related, but i keep 'user' and 'computer' settings in their own GPOs and disable processing for the other
💯 2
n
newbie1998
04/12/2023, 2:49 PMthanks'
s
Scott Knights
04/13/2023, 12:45 AM@newbie1998 It is one of the autodiscover methods Outlook uses. Assume your domain is domain.com. Outlook checks for autodiscover information at domain.com before it checks autodiscover.domain.com. This can cause issues if the website returns its own autodiscover information (CPanel is terrible for this if it is misconfigured), so I usually disable this check as it is pointless in O365 environments.
See this article on autodiscover. Root domain check is step 6. It also used to cause certificate issues (which was one of the main reasons I disable it) but looking at the documentation now, it looks like recent versions of Outlook suppress certificate warnings.
https://support.microsoft.com/en-us/topic/outlook-2016-implementation-of-autodiscover-0d7b2709-958a-7249-1c87-434d257b9087
Scott Knights
04/13/2023, 12:54 AM@Matt Nation I usually do the same & prefix policy names with U or C so I know their settings scope. Having said that, having multiple settings in a smaller number of policies can speed up policy processing. Makes management harder though, so trading off GPO performance against manageability. @James Rankin has a great article that discusses this. Look for the 'Group Policy structuring' section.
https://james-rankin.com/articles/how-to-get-the-fastest-possible-citrix-logon-times/