Outlook 2016 - Save Multiple Attachments not saving to Network Drives

Hi Jonathon,

So, you have tried on others computers, different network environment, different file types and even test in a new fresh installation, same result. May I know for the Mapped Network folder, if all the network folders cannot save multiple attachments? Or just specific one folder?

Please check if you can download or save multiple attachments in related mail web app, if you are using office 365 accounts, you can sign in to Outlook Web App (https://outlook.office.com/owa/) to check if you can download all to the mapped network folders.

Thanks,

Iry

Hi Jason, happy holidays and thank you for taking this on.

Jonathon has pretty much answered all your questions and I can confirm the behaviour he described. But here are my answeres;

>>1. May I know whether you are saying right-click the attachment and choose “ Save All Attachments” button to save them to a Network folder?

I've tried all options but once in the select folder dialog selecting [OK] just doesn't respond when trying to save to a network folder. 

>>2. When you mention the network folder is hosted on a local server, do you mean it’s an IP address? 

Mapped drives (e.g. N:\path ) as well as UNC paths (e.g. \server\share\path) have the same effect. We do not use IP addresses for network shares. The network shares are hosted by local servers or NAS. The WDC NAS of the customer runs on Windows Storage Server 2008 R2 and the servers are Windows Server 2012R2 VMs on Hyper-V.

>>And does the network drive is a RAID (redundant array of independent disks) on your internal network?

This should never be relevant. However the NAS has 2 disks in RAID1. The Server2012R2 virtual machines run on Hyper-V on core Server 2012R2 with RAID1 and Storage Spaces (in RAiD5) config.

Since SMBv1 has been disabled on most of our servers and NAS devices at our customers I tested if might be a cause for this behaviour. But it does not matter if SMBv1 is disabled or enabled on the server hosting the share.

>>3. Are you configured your mail account with Exchange, IMAP or POP?

In both situations Outlook is connected to Exchange in Office 365 E3 plan (hosted exchange). Like Jonathan said his means configuration through autodiscover. This is an ActiveSync connection with server outlook.office365.com as far as I can tell. We don't have POP or IMAP accounts.

We have been using Outlook 2016 / Office365 for several years and never had any problems. It is only since a recent update that this occurs. But unfortunately I don't know exactly since when...

m.vr.gr,

René

Apologies for the delay, I've been out of the office through the Holiday.

1. May I know whether you are saying right-click the attachment and choose “ Save All Attachments” button to save them to a Network folder?

I have attempted the save through multiple options, first through the dropdown offered in the usual "Save Attachment" option as well as from the "Save All Attachments" option in the Ribbon.

2. When you mention the network folder is hosted on a local server, do you mean it’s an IP address? And does the network drive is a RAID (redundant array of independent disks) on your internal network?

As Rene mentioned above, it does not seem to matter if the Drive is a permanently mapped letter drive, UNC or IP navigation. I have tested multiple scenarios, it just seems to have to do with it not being a physically connected drive. In one of my environments, there is a SAN RAID in place. However, in two of my other environments there is no RAID. One of the environments is Linux, the other is wholly Windows Servers, while the third is a hybrid environment.

3. Are you configured your mail account with Exchange, IMAP or POP?

I have tested through multiple accounts, most were Exchange Autodiscover, but I have also tested with a couple of IMAP accounts. Again, behavior is the same across all samples.

Also, just as a confirmation, I am running the latest version of Office in all cases, and in multiple test cases, the installation was a fresh installation, one test case, the only installed software was a fully updated version of Windows 10 and a fully updated version of Office 2016 to be sure there wasn't any software conflict happening.

In regards to the attachments, I have tested with a multitude of file types, to make sure it wasn't a file type issue. I have tested Office files such as Word documents and Excel Spreadsheets, PDFs, images of various formats, and again, the exact same results are experienced.

As mentioned in my first post, the user that initially brought this up to me was previously on Outlook 2010 and had no issues with this functionality. The only thing that changed in that environment was the upgrade from 2010 to 2016. It was after I recieved that ticket that I began investigating other environments and determined that it did not matter.