Symlinks let you define soft/hard links to files/directories placed in different locations. Essentially, they are like windows shortcuts (a.k.a. soft symlinks) and the other type is something in-between the two: shortcuts and Original Files/directories. You can use HardLinks as an original file/folder, transparently.
Linux/Unix has inbuilt feature of creating symlinks using “ln” command. On older Windows versions, there is no inbuilt utility that does that. However, on Windows Vista, Windows 7 you can use a command line utility called “mklink”. But not everyone likes the command line that’s why there is a GUI-based tool for this: Symlinker.
There are several Use cases for employing Hard symlinks. e.g. when you are running out of diskspace on your c:\ drive and certain programs still force you to install new software in c:\ drive (most microsoft, Google products do that) you can create a directory symlink and point it to another drive, save the buck. Another reason would be to move the caches, libraries (media player, iTunes songs lib), indexes (picasa photocache, search indexes, google desktop indexes) which take a large amount of disk space on your C:\drive.
There could be n number of other reasons, and this tool always comes handy.
To use this properly, here is some background on types of SymLinks:
A soft link is essentially a shortcut to a file or folder –it won’t pretend its part of the filesystem. You can still directly reference or open a file with the symlinked path, and it mostly works.
A hard link directly points to the file, and acts to the operating system as if it is the file itself. You’ll want to use this option the majority of the time if you are trying to fake an application’s directory just like the case described earlier.
Using Symlinks for a Network Share
There’s nothing special you need to do here. Just delete the symlink file like you do.