Are you having issues editing Excel files that contain Macros and are stored on a network location?

We have been experiencing these issues too. For most of our stations we could just add the Network locationas a trusted path. But this has started to fail at least on some workstations.

We also tried adding the location under “Internet Options” which worked on some stations until recently. It now requires an https:// address which will not work for a share that just has an IP.

After losts of trial and error we decided to create Symbolic links on those stations to bypass the warning.

What Are Symbolic Links?

Symbolic links are basically advanced shortcuts. Create a symbolic link to an individual file or folder, and that link will appear to be the same as the file or folder to Windows — even though it’s just a link pointing at the file or folder.

So you can have a pointer lets say:
C:\Users\Alberto\Desktop\ExcelFiles

That points to a network location:
\\server1\Share1\ExcelFiles

The folder will look like a regular shortcut:

All its doing is pointing to the location on the server/nas.

When you open a file from this location. Excel “thinks” its a local file and you will not get the dreaded red warning:

Example with syntax

Let say you’re trying to access files on; “\\server1\Share1\ExcelFiles” we can create a link on your desktop that will be named “ExcelFiles”.

Start a command window with Administrator privileges type the following command but edit the paths to match your environment:

Thats it! now you can open any file from that link without the limmiting macro issue.

This will probably be disabled at some point. Microsoft has been trying to disable macros for a while now. But at least this can buy us some time until we move away from using them.

 Let us know if this has helped you.

Are you having issues with slow syncs when updating OneDrive shares? Is your OneDrive client taking massive amounts of memory?

We had this very issue. When we checked-in with Microsoft Support they really didn’t have much of an answer, or helpful response / fix.
After checking all our OneDrive clients we noticed that they were using lots of RAM.

As you can see our Windows stations were using around 2.1GB and out Macs around the same. Some users that had more shares on OneDrive were using 2.7GB!!!

After testing different versions of the client. We checked the amount of files on our shares and found that we had over 400k. These were mostly small java or other code that we kept for each of our projects. We always try to keep backups of the old client projects/environments. This was never an issue when we had on-premise network shares. But when we migrated to the cloud issues started to appear. Usually slow syncs, or crashing of office files used in collaboration such as Excel files.

While trouble shooting the issue we removed one of the shares. This brought down the amount of files being synced. It took the office about a day for OneDrive to re-sync. But after that it started to use around ~600MB of RAM. Which is still a lot. But we felt the performance improve.

We hope this helps other folks having similar problems.