The OS is also supposed to clean them up, but sometimes cannot when a process on the server (such as a virus scanner or similar) has a read lock on the folder. They are used as temporary containers for doing atomic file data swaps. Unfortunately, those folders are created by macOS, not by Excel.
#Os x microsoft office autoupdate location mac
This only occurs on the Mac if I'm using WinExcel in a VM, I never have a problem accessing from the same server, also over an SMB connection. Sometimes I'll get this constantly, other times I'll be able to go weeks without the problem. I think it is some kind of interaction between Mac sandboxing and SMB file access, but it isn't totally consistent. They know about the problem, people have posted about it on their forums and I've sent feedback to that effect. This has been going on for the last couple of years and I'm kind of pissed that Microsoft doesn't bother to address this. I won't be able to save it, even in a different location. The latter is a bad sign, since I'll frequently then get an error message from Excel stating there is a problem accessing the file. Other times, I'll see a folder created like filename-f58dk-f7dk2-l07ku. Sometimes when the file opens, I see a temporary file name like ~filename. I'm opening Excel files (xlsx, xlsm) stored on a Mac file server, accessed with SMB. We’re aware of the Keychain alerts that pop up when converting to MAS distribution and are exploring some possible ways to mitigate or eliminate them.
There are no other differences- in fact, the bits we distribute are literally the same bits we deliver to Apple for them to distribute via the MAS. The only functional differences are that the MAS apps only support subscription licenses, and the MAS is responsible for installing updates. The Office apps obtained from Microsoft are identical to the apps obtained through the Mac App Store.
Anyone else have any experiences-especially any negative ones-moving from standalone to MAS? I've been tempted to replace with the MAS version also, just to get out from under the Microsoft AudoUpdate process-but have been worried that something would break due to sandboxing, minor differences in capabilities between the two versions, etc. I'm currently running the standalone version (University O365 license). Moep, thanks for sharing your experiences.
0 kommentar(er)
