Hi I'm late to the "I know VFM is end of life" party but I just inherited sole responsibility (as opposed to just managing the links via the GUI). Needless to say we're still using it. Our national drive is on a filer with 1400 or so links under the main share which in the back-end are two different shares on different volumes. We probably don't use most functionality it was designed for. We do migrate data based off of past usage from one of those shares to another, but that's not as frequent of a need those are just one-offs typically (and, I could get around that writing my own tool if need be).
What do people manage DFS links with now? Can we manage these links with PowerShell, and if so is that still outside of NetApp or is there something NetApp specific involved or needed in their Posh toolkit? Is this all controlled by MSFT tools now? Is NetApp over this, and on to something better?
Also, somewhat unrelated, what is the "Timeout" setting for DFS links intended for? What is the timeout event happening here, when a client can't connect or resolve the link's location? I am trying to solve some issues related to extremely slow Mac loading times for our DFS folder. It's always been problematic because of the technology... but I'm curious how this setting ever comes into play and if it is of any concern. If I have a DFS link to folder "foo" but the back-end is gone, will the client wait for a timeout to do something as simple as loading the directory, for instance? I'm thinking we probably have at least a few stale directories (I think that's what I'm seeing as blue folders) that need to be cleaned up, wondering if any of that will help that though. On a Mac it's taking 10 minutes+ to just connect the drive as it seems to mount each link. I'm wondering if this timeout could be lowered to have any change. We're finding 3rd party software is still better than the built-in stuff Apple has now included.