Skip to content

Slack feedback: problems with SMBHOME

Hey all, I've configured a couple of departmental shares for our org and they map correctly. However, whatever is defined for SMBHOME isn't automatically mapped. Where should I be looking specifically? Trying v3.1.8

my response:

Thank you very much for your feedback. Indeed, this was one of the first features that NSM had, and for this reason, it has not received much attention anymore. Most installations work with a home server to which %USERNAME% is mapped—we do the same. For example, smb://my.homefiler.company.com/%USERNAME%. A Therefore, SMBHOME has fallen into oblivion. I have checked: the code is still there but is only started once when initializing the app, that is, before authentication. If there is no network at this point or if the network connection has changed, SMBHOME will not be (re)set. TL;DR There is work here for us. The function is important, albeit clearly seldom used, and we will work on making it function correctly again. However, due to a current lack of resources, it will take some time. Until then, the aforementioned method of setting the home via home-filer and %USERNAME% could be a temporary workaround. Thank you once again for your precious feedback!

The handling of SMBHOME occurs within the init process of Mounter.swift. However, this should be done with every network change or ticket renewal/AD reading.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information