Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a brand new windows 2012 standard server, with the gui installed and I have mounted three volumes from a storage array onto the C drive under another folder. So I have folder "A" setup on the server, and three junctions inside that called "B", "C" and "D", each of which is linked to a 3TB set of discs. I used the File and Storage services gui to setup these junctions, and they appear to function perfectly within the server itself. The drives appear as reparse points within the explorer interface(So the drive icon with the arrow).

Now the issue comes when these are used on client machines, and the same goes for XP, 7 and 8, but not osx. The junctions appear as a shortcut(So a folder icon with an arrow), and can be clicked on but when you come back into folder "A" to look at the links the junction you just entered is gone. The same goes for all three junctions, and is only fixed by closing and re-opening explorer after a seemingly random amount of time.

After some fiddling I discovered that the link icon is disapearing and being replaced with a folder that is marked in file explorer as being either hidden or system(Although checking in a command prompt says no such thing, the folders are clearly marked as Reparse points and are not hidden or system). This makes it even more confusing when turning on "view hidden, system...etc" in windows explorer makes those folder appear in their slightly faded form(As if they are system or hidden). Closing and re-opening explorer returns these folders back to their original state temporarily.

I've fixed it in the sort-term by turning on the show hidden option in explorer, but this is not a long-term solution as it is causing lots of issues for users who are having to deal with thumbs.db issues and similar things. Has anyone come across this?

share|improve this question
    
Having searched Google high and low for a solution to this, it turns out I was just struggling from not using the correct terminology to hit the MSDN explanation. The link below explains in detail the problem and possible solutions. blogs.technet.com/b/asiasupp/archive/2010/11/03/… –  Tony Cheetham May 2 '13 at 15:03

1 Answer 1

Your comment on your answer makes reference to a problem in the Windows 7 SMBv2 client. Disabling SMBv2, as described in the document you reference, is a major step backwards in performance for your clients. Disabling the directory cache on your clients may increase your servers' workload, too. Mounting a directory under the volume, rather than the volume itself, is a possible workaround but, personally, I'd strongly consider changing up the architecture of these folders to move away from the junction points.

You can use DFS namespaces to "graft" together disparate shares into a single namespace w/o using junction points and you'll get to keep SMBv2 on. This gives you the advantage that you can split these volumes out onto physically separate servers later, if you should ever need that, with great ease.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.