You can also create a hard link. A hard link is an item in file store whereby more than one path references a file in the same volume.
To create these links, you could do the following:
# Create Test FolderOnce you run this (suitably amended for your environment possibly), you would see some thing like this in Explorer and within a PowerShell V5 window (nb: I am running V5 on a Server 2012R2 system with the RTM version of WMF 5).
# Now a subfolder
# And a real doc
1..10 | Out-File c:\Foo\SlTest\Real\foo.txt
# Now create a symbolic link
New-Item -ItemType SymbolicLink -Name .\virtual -Target .\real
# And a symlink for a file
New-Item -ItemType SymbolicLink -Name .\SYMfoo.txt -Target .\real\foo.txt
# You can also create a hard link
New-Item -ItemType HardLink -Name .\hard.txt -Target .\real\foo.txt
I find symlinks particularly useful in my training. For my PowerShell courses, I create a 4-VM 'farm', and use differencing disks to reduce the overlap in contents (Saves around 20 GB!). I create a symbolic link for the differencing disk (ie where it should be) that points to the one copy of that file I DO copy. Up to now, my setup instructions require the setup tech to run a batch file using Command.com. Once PowerShell V5 is commonly available, I'll get rid of that and make the setup all PowerShell.