Either one will create a symbolic link between local directories. The difference between them is the mklink /d uses a soft link while mklink /j uses a hard link. A few restrictions for hard links is that both links must be on the same file system and remote sharing is not supported. Soft links allow access across remote storage shares but there is increased disk I/O overhead as a consequence. If you plan to use symbolic links to offer access to an application, the mklink /J link is preferable in your situation.
, thanks for responding, I appreciate it and you do 'rule
I do understand these difference between Directory Symbolic Link and Junction as far and as in depth as your recitation goes, it's pretty much the same info I was able to glean from Microsoft's documentation on TechNet. What I don't understand is your reasoning for saying a Junction would be better in the application described, where none of the differences I've been able to glean between a Directory Symbolic Link and Junction really matter in this instance? Please say more!
Just reread your post; is the increse in disk i/o why you'd recommend going with Junctions in this example? I'd think the disk i/o difference would be neglagable, but don't have any experince here...
My experience with this command line parameter is limited as well but I've seem to grasp and understand at the basic level like you have. A soft link is in essence a shortcut to the original file. If you delete the original file, the soft link is useless. A hard link is like a clone, if you delete the original file the file will not be deleted because the hard link is still pointing to the same bit of information of the hard drive. The information does not get deleted until both hard links and originals are gone. I think the website i got the research from has to be wrong. If the mklink /J was truly a "hard link" parameter then deleting the original file would still allow me to see it in the hard link. This is not the case. The test file gets deleted from both ends, which means the /J and /D parameters are both soft links!
In this case they both use the same disk I/O usage, behave the same, so the only difference is their features. I would recommend using /D switch hence you have support across different partitions (C:,D:,E:,etc) remote shares, etc.
Sorry for the inaccurate information.