Available in current versions of Windows, this command line tool allows you to create structures similar to the links you get in MacOS X and Linux.
Type mklink at a command prompt outputs the following:
mklink Creates a symbolic link. MKLINK [[/D] | [/H] | [/J]] Link Target /D Creates a directory symbolic link. Default is a file symbolic link. /H Creates a hard link instead of a symbolic link. /J Creates a Directory Junction. Link specifies the new symbolic link name. Target specifies the path (relative or absolute) that the new link refers to.
Very handy for abstracting a file system to make it do what you want. These junctions allow disparate parts of the local file system to be consolidated and structured to support specific application requirements.
For example. The following shows the creation of a pair of junctions linking a secured shared area of a file server to anonymous FTP upload points.
Note that the junctions appear as a special sort of folder -a bit like a shortcut. Opening one of these shows how the operating sees the junction as part of the file system, rather than a pointer or redirect.
Some clients do not see changes made in linked folders when they happen, but rather have to reenumerate the listing.
Earlier versions of MacOS X 10.9 had issues with junctions, but these appear to have been fixed. The work around was to use cifs://server/share rather than smb://server/share (similar to DFS behaviour).
As with links in the *nix style operating systems, these links and junctions can be confusing when you look at access controls.