Outlook cannot attach files larger than about 1MB

JasGot

Recent migration to on-prem Exchange 2019.

SOME users, using different versions of Outlook, are getting an attachment size error.
So far it is Outlook 2010 and Outlook 2016

The Exchange server connectors are set for 50MB send and receive.
MS Outlook 2010 and above default to 20MB
I have tried the Registry setting of:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences\MaximumAttachmentSize

I have read that when Exchange is in use, Outlook doesn't use the default size limit of 20MB OR the Registry setting above.

I'm stumped.
Is there any other place attachment size restrictions can be set?

I have some users NOT having any problems.

The same troubled users CAN log in via OWA and attach the file without any issues.

So I'm sure it is a workstation specific issue.

Any thoughts?

syko24

@jasgot - What value do you have set for MaximumAttachmentSize? Value is set in KB so make sure you have the appropriate number. If that looks good then possibly try a reboot after modifiying the value.

JasGot

@syko24 said in Outlook cannot attach files larger than about 1MB:

@jasgot - What value do you have set for MaximumAttachmentSize? Value is set in KB so make sure you have the appropriate number. If that looks good then possibly try a reboot after modifiying the value.

51200
We'll reboot and check.

JasGot

JasGot

@jasgot said in Outlook cannot attach files larger than about 1MB:

Interesting

51200.

Breaks the display here.

dbeato

@jasgot Does this happen on any user profile? if not I would try a new user profile and test. Or does it work on another computer?

JasGot

@syko24 said in Outlook cannot attach files larger than about 1MB:

@jasgot - What value do you have set for MaximumAttachmentSize? Value is set in KB so make sure you have the appropriate number. If that looks good then possibly try a reboot after modifiying the value.

Can attach up to 10MB after reboot.

JasGot

I'm going to make sure that registry setting is applied correctly on a few PCs and then restart them. I'll report my findings on Monday.