:::: MENU ::::

Windows Junctions

In Unix and Linux creating links is something you do all the time, maybe you have a version number in that new apache catalog but you want to continue to just use \opt\apache or something, in Windows it’s not used much, well at least not according to my experience.

The other day I was upgrading SQL Server, the original media was on a catalog on C: (c:\nt) but there was not enough space on C: to hold both the original media and the new, what to do?

I moved the original media to my shiny large X: disk but the setup program was looking for the original on C:\NT, again what to do….?

You create a junction on C:\NT that points to X:, the program will not notice it, it thinks the media is still on C:\NT

Exemple:

Start CMD with admin rights.

C:\>cd nt

C:\NT>mklink /J c:\NT\Server_Developer_Edtn_2012_X64_SP1 x:\Server_Developer_Edtn_2012_X64_SP1

Junction created for c:\NT\Server_Developer_Edtn_2012_X64_SP1 <<===>> x:\Server_Developer_Edtn_2012_X64_SP1

 Now you have a link c:\NT\Server_Developer_Edtn_2012_X64_SP1 that points to x:\Server_Developer_Edtn_2012_X64_SP1

//R


So, what do you think ?