Benches macOS

14

Finder data not being written to .DS_Stor…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

The symptom of the problem I am experiencing is that the position of icons on my desktop (as well as icons in other folders in my home directory, as well as Finder window settings for folder in my home directory) are lost every time I log out. On a subsequent login, all of the icons "reflow" starting from the top right corner of the screen, just below the boot volume icon. I have been able to determine that this has to do with the .DS_Store file(s) in the Desktop folder and other folders of my home directory. If a .DS_Store file exists, the timestamp does not change when I change the icon layout and logout. If I delete the .DS_Store file, it is not re-created.

In my case, my home directory (and the child Desktop folder) is being mounted off an SMB share on a Windows 2003 server. My Mac is using AD authentication to the same Windows 2003 server, which is the domain controller. I'm logging in with my AD credentials, and my home directory mapping is picked up from the home directory field in AD.

Now, Googling this problem, I found a lot of people complaining about wanting to suppress the use/creation of the .DS_Store files on Windows network volumes. This led to an Apple KB article (
http://support.apple.com/kb/HT1629) on how to modify a default to prevent the creation of .DS_Store files on network volumes--essentially the very behavior I am experiencing. The upshot of the KB article is to us the following command in terminal:

*defaults write com.apple.desktopservices DSDontWriteNetworkStores true*

I did a 'defaults read' to confirm this default isn't set on my install of Mac OS X 10.5.6--and it isn't. I then tried using the following variation in the hope I could force the behavior I wanted:

*defaults write com.apple.desktopservices DSDontWriteNetworkStores false*

Predictably, this had to effect.

The upshot is, NONE of the Finder data for files and folders in my home directory (icon positions, Finder view window defaults, etc.) is preserved between logons. And this is driving me nuts! I've spent several hours over the past two evening trying to troubleshoot this, and I've had no luck.

As a footnote, I'll mention that if I drag a folder from my home directory onto the local hard disk, the .DS_Store file is created/updated and things behave as expected (icon position and Finder window defaults are preserved). But, if I then drag the folder back over to my home directory, the values in the .DS_Store file become "frozen" and don't change.

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    biovizier

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    ..."
    Unlike 10.4, 10.5 does not create DS_Store files on MSDOS volumes. However resource forks are still created when appropriate."...

    Thanks for that information.

    I was not aware that this behaviour had changed in 10.5, but can confirm that my 10.5.6 system behaves as you describe - new .DS_Store files are not created on FAT formatted volumes, and existing ones are not updated under circumstances where that would be expected.

    It seems Apple cares more about Windows users whining about .DS_Store files being created on their flash drives after using them on a Mac than it does about Mac users forced to use FAT formatted flash drives for interoperability with computers at work, school, etc.

    Another example of the erosion of the Mac experience. Sad.

  2. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, after a couple of days with no suggestions from anyone, I broke down and called Apple support. My call was quickly escalated from the front-line tech to a product specialist, who referred my problem to the server guys.

    Unfortunately, the answer I received was, "Windows doesn't support .DS_Store files." This answer makes it pretty clear that someone didn't understand the questions. Finder doesn't need the SMB server to "support" .DS_Store files any more than Pages or Numbers needs the SMB server to "support" their document files.

    So, I've rephrased my e-mail in a question to be escalated to the product engineers. I was told it could take several days. I'll post the result, but I'm not hopeful. If anyone else has any ideas, I'd be only too happy to hear them. One post at a third-party app developer's website seemed to imply that there was some kind of change in OS 10.5, and that perhaps .DS_Store files are not longer used on network volumes (or that the default behavior is to not use them). In any case, I'm still stuck.

  3. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Curiouser and curiouser...

    While continuing to Google this PITA question, I came across a product called BlueHarvest (
    http://www.zeroonetwenty.com/blueharvest/) that actually bills itself as a utility that "allows you to keep your disks and servers free of Mac 'trails' by automatically removing DS_Store files..." among other things. In the FAQ for this product is the following question:

    +Does Mac OS X 10.5 create DS_Store files on MSDOS volumes?+

    With the following answer:

    +No. Unlike 10.4, 10.5 does not create DS_Store files on MSDOS volumes. However resource forks are still created when appropriate.+

    This confirms the exact same behavior I'm experiencing! I sent these guys an e-mail asking them if they could at least tell me how they know this is the case (or more specifically, where this behavior is documented by Apple). If I can find this out, I could at least send it along to Apple tech support in support of the notion that their "Windows doesn't support .DS_Store files" answer is incorrect.

    How disappointing and frustrating this first experience with Macintosh technical support is proving to be. 😟

  4. 0

    biovizier

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    ..."
    Unlike 10.4, 10.5 does not create DS_Store files on MSDOS volumes. However resource forks are still created when appropriate."...

    Thanks for that information.

    I was not aware that this behaviour had changed in 10.5, but can confirm that my 10.5.6 system behaves as you describe - new .DS_Store files are not created on FAT formatted volumes, and existing ones are not updated under circumstances where that would be expected.

    It seems Apple cares more about Windows users whining about .DS_Store files being created on their flash drives after using them on a Mac than it does about Mac users forced to use FAT formatted flash drives for interoperability with computers at work, school, etc.

    Another example of the erosion of the Mac experience. Sad.

  5. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    As further proof that Windows has nothing to do with this problem, I've been able to reproduce the problem (existing .DS_Store not being updated and missing .DS_Store not being created) on a remote volume mapped from an SMB (Samba) share on an OpenStep 4.2 server, as well as from an NFS share on the same server. In all cases, Finder is not creating/using these files on remote volumes. This behavior is different than the default behavior documented in KB article HT1629 under Mac OS 10.4.

    C'mon Apple... what gives here? Did you change the default on 10.5 and, if so, how do I change it back?

  6. 0

    biovizier

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hey, try this:

    1.

    Put a file in a folder on your Desktop.

    Edit: not your Desktop, but rather a typical local home on an HFS+ volume ~/Desktop

    2.

    Use "Get Info" to add a "Comment".

    The comment can be up to somewhere between 700 and 800 characters.

    3.

    Copy the folder to a FAT formatted flash drive, SMB share, etc.

    4.

    Create a new folder on the flash drive.

    5.

    Move the file from the first folder to the second folder.

    Confirm that the "Finder" shows the comment to be there.

    6.

    Quit the "Finder" - in 10.4 and earlier, this action would ensure that all .DS_Store files get updated, including transfer of comments. I.e. don't "relaunch" or "kill", etc. Enable and user the "Quit" menu, or use:<pre>

    osascript -e 'tell application "Finder" to quit</pre>

    7.

    Now where's the comment?

    In step 2, you could also have just created a file on the non-HFS volume and wasted your time typing in a 700 character comment.

    In step 6, a more real-world scenario is ejecting the drive or logging out, but deliberately quitting the "Finder" is the most conservative way to ensure that changes get written to .DS_Store files and comments survive. In 10.5.6, even under these conditions, comments are lost.

    Icon positions and view preferences are one thing, but with comments - that's real user-inputted data that Apple is playing fast and loose with. And if they no longer support comments on non-HFS volumes, the "Finder" shouldn't be showing you the comments when you double-check them in step 5, or allow them to be added in the alternate version of step 2.

    ..."
    C'mon Apple... what gives here?"...

    Unfortunately, this "Discussions" site is not frequented by Apple devs. Have you considered filing a bug report? I wonder what they would tell you, eg. if the treatment of .DS_Store files actually does turn out to be a bug or is intentional as it suspiciously seems...

    http://developer.apple.com/bugreporter/index.html

  7. 0

    Francine Schwieder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I found this all very interesting, and conducted a few experiments with the KEYDRIVE I have formatted at FAT32. Sure enough there are no .DS_Store files, and the Spotlight Comment gets irrevocably lost. I've never used that much because I knew the comments weren't part of the file and had an unfortunate tendency to get lost in translation, even before this new behavior in Leopard. Now instead of a tendency to get lost, there is a guarantee that they absolutely WILL disappear. You don't even have to move 'em to another folder: put a file with a comment on the drive, Finder shows the comment in GetInfo. Dismount the drive. Remount the drive. No more comment.

    I did note that whatever arrangement you had in terms of the window (List or Icon or Column View) when you dismount the drive is the arrangement it will have when remounted. However, any custom arrangement is lost. Thus if it is in Icon view and you manually rearrange to have all the folders together, when you dismount/remount it comes back in Icon view, but everything is in alphanumeric order.

    The resource forks are indeed preserved, so the drive does have things like ._foo.png files accompanying the foo.png files. The .Trashes and .Spotlight-V100 folders and .fseventsd files are also present. Just the .DS_Store files are gone. Not sure how that will make Windows users happier since, if they have the dot files visiblity turned on they'll see all the other dot files.... So they still won't be thrilled, and Mac users lose some functionality, and potentially lose some data. I've seen folks who have lost many many hours of work when the Spotlight Comments all disappeared. They get upset.

    Francine

    User uploaded file

    Francine
    Schwieder

  8. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you, biovizier and Francine. Your comments have helped reinforce my suspicion that that root cause of my problem--the failure to preserve the layout of the icons on my Desktop--are the direct result of my home directory being mounted from a remote volume, and of that being due to Mac OS 10.5 not using .DS_Store files on remote volumes (including, apparently, thumb drives).

    As I mentioned, I have opened a support incident with Apple on this, and am still waiting on a response from them. I'll post results here as events warrant.

  9. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Darn.

    It seems that the behavior experienced by both biovizier and Francine are attributable to the fact that they are interacting with remote filesystems that are either FAT or FAT32. I have just learned that remote volumes (regardless of whether they are USB thumb/travel/key drives or SMB/AFP/NFS remote mounts) that use the FAT or FAT32 filesystem +will not use .DS_Store files+. To wit:

    Russ Tulloch of ZeroOneTwenty was kind enough to respond to my e-mail inquiry asking him how he knows that 10.5 does NOT create .DS_Store files, as opposed to 10.4 which does (see previous post this thread). I specifically asked him if he had run across something to this effect documented by Apple. Russ responded:

    Hi Jeff,

    When I was preparing BlueHarvest 2.0 I did lots of testing under 10.5 (both pre-release dev builds and the release build). I could NEVER get 10.5 to create DS_Store files on MSDOS (FAT) volumes. As far as I know this isn't documented anywhere.

    Just to be clear however: 10.5 still creates DS_Store files on SMB-shares, just not on MSDOS (FAT) physical "disks". It certainly should be creating DS_Store files all over your SMB shares!

    I just re-tested this under 10.5.6 and yes, it creates DS_Store files on SMB-shares and not on MSDOS (FAT) disks.

    Unfortunately, in my case, the remote file system I am accessing is NTFS. So, unlike biovizier and Francine, I should not be experiencing this. Quite the contrary: according to Russ, on 10.5.6, I absolutely
    should be seeing the creation and modification of .DS_Store files.

    Looks like I'm back to square one. No choice but to press this issue with Apple support.

  10. 0

    biovizier

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the follow up - very informative.

    ..."
    I absolutely should be seeing the creation and modification of .DS_Store files."...

    Are you in control of the SMB server? If not, perhaps the admin has done something.

    I don't know much about it, but it is apparently possible to configure an SMB server to arbitrarily "veto" the creation of files matching certain patterns, something that could potentially be applied to ".DS_Store" files...

  11. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you in control of the SMB server? If not, perhaps the admin has done something.

    Yep, it's my server. I own it, I set it up. There's nothing expressly or explicitly configured on the server that would be responsible for this. In my 15+ years as a Windows Server sysadmin, I've never seen any precedent for a Windows server preventing or otherwise interfereing with the creation of a specific type of file.

    I don't know much about it, but it is apparently possible to configure an SMB server to arbitrarily "veto" the creation of files matching certain patterns, something that could potentially be applied to ".DS_Store" files...

    Eh... yes and no. Servers providing SMB shares via Samba can include the 'veto files' option in the smb.conf file. However, since this is a Windows server, there is no smb.conf file. Windows Server 2003 R2 and later can create a file group with a file screen to block certain types of files, but I'm using Windows Server 2003 "R1", which doesn't support such functionality, and in any case I wouldn't have configured it.

  12. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This evening, I repeated and expanded my testing. The client was an iMac running Mac OS 10.5.6. The three servers were UNIX (OpenStep 4.2 with Samba), NTFS (Windows Server 2003 with Services for Macintosh), and a MacBook (Mac OS 10.5.6). Here are the results of determining where the Finder was able to create a .DS_Store file and retain both icon-in-window positions and Spotlight Comments:

    SMB on UNIX: no

    NFS on UNIX: no

    SMB on NTFS: no

    AFP on NTFS: YES

    SMB on Mac: no

    AFP on Mac: YES

    So, bottom line is, on my iMac, I can't seem to use .DS_Store files with any file sharing protocol other than AFP. If anyone else is experiencing behavior to the contrary, please post steps you follow that cause creation of a .DS_Store file on a remote NTFS volume connected with SMB file sharing.

    Side note: I checked, and my support incident ticket has been marked CLOSED since I opened it earlier this week ⚠ so I've been waiting for contact from Apple that was never going to come. With my latest test results, it looks like it's time to go get unpleasant with Apple.

  13. 0

    jlanter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, I still haven't contacted Apple again, yet, because until last night I didn't think I had enough new information to get Apple pointed in the right direction. However, last night I brought my new work MacBook home from work, and tried in on my network. It
    did create a .DS_Store file, and worked perfectly.

    From this I was able to determine what's going on: if I log on to my iMac using a local account, then map a network volume using SMB, Finder will create and use a .DS_Store file on the network volume. However, if I log on to my iMac using an Active Directory account, then map a network volume using SMB, Finder will NOT create and use a .DS_Store file on the network volume.

    This just keeps getting more and more interesting....

  14. 0

    David Moyle

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've just read this topic and thought I would add what I have discovered here at work recently pertaining to a similar issue.

    Server 2003 AD, 10.5.5/5.6 clients. Active Directory authentication and login. Mounts smb home folder.

    For all of our new students we have discovered an issue were students were able to read and write into their home directory but it would disappear from the folder view. Confirmed that all files and folders created were on the server. We investigated many options and were certain that it related to lack of read/view permission of the folder.

    One week later realised that .DS_Store files were not being created for our new students. How this is different from last year I'm still unsure unless it carried over from when they mounted their home directory 8+ months ago.

    If I copy a generic .DS_Store into their home directory they are now able to view their folder as expected. As this is only a new thing I'm pointing to either:

    10.5.5

    10.5.6(Seems to be irrelevant in testing)

    Stacks

    Any more thoughts would be appreciated, this issue isn't as serious any more but I would still technically like to know..