OK, I have a volume on a dynamic disk that has a drive letter, but I am trying to get it to mount to a folder on another drive. I have done this before on this same server and it worked fine. When I do it now via "Disk Managment" I get the error: "The path cannot be used for creating a drive path likely because the folder does not exist or is already a drive path to some other volume" The folder is not used in another junction. I have tried creating a new folder and mounting it there, same error. I have tried mounting a different volume, same error. Yes the destination and source drives are NTFS. Yes I have admisitrator rights. I have even tried reformatting the source drive. I have no idea what is wrong. I was able to find a KB article that mentioned the error, but it did not help: http://support.microsoft.com/kb/883100 Server 2003 Standard x86 SP2 __________________

You don't create junction points in Disk Management. You create junction points using LinkD http://support.microsoft.com/kb/205524 Example of Oxymoron: Person who is pro life and anti sex education. Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.

Yes...Disk Managment can be used to create junctions I tried to sue the linkd command, it just response saying that it could not create the junction The junction tool of sysinternals also does not work

How do you create a junction point in Disk Management? What was the syntax when you executed the linkd command? Example of Oxymoron: Person who is pro life and anti sex education. Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.

Open Disk Managment: right click a formatted volume click "Change drive letter and paths". Click add, select "Mount in the following empty NTFS folder", Select browse, select your folder, click ok. Tada, you created a junction within Disk Managment. You can use the dir command to verify this. Here is the syntax I used with linkd: F:\Storage>linkd folder \\?\Volume{d912359f-3c05-4445-a311-26ee89e83a76} Could not open: folder Yes the folder exists. I tried reversing source and destination sections just in case I misunderstood which was which, but that failed as well. I was able to mount that drive (using the GUID as I did here) to a directory I created within my profile, after creating the folder using md, but when I tried to get into that folder, I got the error "The parameter is incorrect". After finding the Microsoft document below, I was able to use the mountvol command to mount the drives correctly. Do you know if these junctions are permanent? What I mean is, will I have to run the mountvol command again after a reboot as I do with Linux' mount command? http://support.microsoft.com/kb/205524