I do something similar with some of my samples - I use Superior Drummer 2 in every project, so I actually used a symbolic link (like a junction point) to move those samples back over to my SSD, despite my sample directory being D:\Music samples.
 
Although it's worth noting that CCC seems to respect the old Cakewalk Content directory established by X3. At least, that worked for me. So, if you have X3, make sure you set that up pointing to the correct place before you upgrade.

I was wondering if using Junction Points would affect the various destination folders that are, (can be), set in 'Preferences'?  Some of those items are placed in the 'Cakewalk Content' folder during install.  Many of those I move to other drives.
 
Thanks.

Yes, the actual content of a directory must be moved prior to creating a junction, but this will work on whichever directory level you choose. Everything at the junction level and lower will actually reside in another physical location.

The full path needs to be in the mklink?
ie:
mklink /j "C:\Program Files\Cakewalk\Studio Instruments" "V:\Cakewalk\Studio Instruments"
Our lovely model Twiggy will demonstrate:

Do I have this right?
 
TIA
 
Tom
 

I'd like a further clarification on Tom's screenshot. Is that for 32 bit plugs, then? How about for 64 bit stuff?
 
Thanks. scook has recommended this but I've put it off and succeeded at installing my libraries elsewhere. I would however, like to understand this method and seeing Tom's pic has made it seem more approachable!
Michael

This is a great thread to bookmark. Very interesting.

Michael,
Please note the screenshot is from my office rig, its a 32 bit system.
I'm not sure the  "C;\Windows\system32" is supposed to be in there.
That's why I posted the screenshot, and to clarify if the full path needs to be listed.
I'm guessing yes on the full path, but will wait for a response before I actually run the command.
T

If you want a more in depth explanation, you can read here:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365006(v=vs.85).aspx
 
I was a little confused between junctions and symbolic links and found a good write up here:
http://superuser.com/questions/343074/directory-junction-vs-directory-symbolic-link
 
Having read through them, I plan to use junctions and start small.

Very good thread and very timely for me. Just last night, I changed the file path (within CCC) for the Cakewalk Content folder to be on my D: Drive (samples drive as well as where I deignated all my X3 content to be). I only installed a couple of the recent updates, but will do the rest tonight. 
 
I'm hoping this will be where the CCC is going to default for all future content (loops, samples etc...) or will I need to use junctions (so I'm sure it's done correctly)??  

scook
The assumption in my initial post is data already exists in the folder on the C drive but it does not matter. What does matter is prior to issuing the mklink command, the path on the C: drive must not exist and the path on the D: (or whatever drive is actually storing the data) must exist. This is why in the example above, the first step moves the "C:\Cakewalk Content" folder to the D: drive.
 
The process for a new install where "C:\Cakewalk Content" did not exist is
1) create "D:\Cakewalk Content"
2) Run cmd.exe as administrator and type:
mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content"
Then when installing, the installer will think it is writing to "C:\Cakewalk Content" but the OS actually writes everything to "D:\Cakewalk Content." When SONAR starts up it will use the "C:\Cakewalk Content" default setting but the OS actually reads the data from "D:\Cakewalk Content."
 

i think the bit I've put in bold is the most important part of using mklink.
 
It's no good just to copy (or cut) your files across, the path on the C: drive must not exist, so you have to delete it once you've moved your files.