MKLINK – Create and Use Links in Windows

Hi,

Is there a way to create a link (or something that works the same way) that will be accessible through the network neighbourhood. Basically - on one computer I've created a link that links to a folder inside this computer. When I access this computer through the network and I need to be able to click this link and go where it should take me. Instead when I click it I got an error message that it links to a place that is unaccessible (even though it is accessible, and its also shared, so there shouldn't be any problems accessing it this way). Any ideas?

!>

I hope to be able to help a little bit, but I'm really hoping someone more familiar with networks than I in general will reply ; it's something of a weak area for me in terms of knowledge.

But if I were to try it I would first give the folder on the remote system the correct sharing permissions, which I understand you have done … only because of my lack of experience in this regard I can't tell you "but check this" or "make sure of that" with that first step. Like I don't know if the sharing permission has to be all the way up to the parent folder, which it might.

Then when setting up the symbolic link ( see post prior to yours for syntax  ) I would use full path designations that specify the names of both systems, like …

  \\[server_name]\[drive]:\[folder_path]

… and I would expect that's all there is to it, but I'm probably forgetting something.

For what it's worth, I accomplish what you want to do all the time but with Dropbox. The sharing permissions are set up in the Dropbox executable itself, and it pretty much takes care of the rest. So in your case you'd have a Dropbox folder at both locations, and all you would need to do to make a file ( or folder ) visible at both spots is drag it into the Dropbox folder, same as you would if you were copying it into any other folder. Dropbox takes care of the rest—when you access the other computer you'll see it in that system's Dropbox folder. I have 50  GB but you can open a 2  GB acct for free to start. Only problem with the free accts is there's a max size limitation on individual files ( don't know what it is ), a limitation which is removed in pay accts.

Hey,

Thanks for reply, but this doesn't want to work for me either Does it work on your computer? One question though - in the path should I specify the drive letter, or the share name? For example my computer network name is "office" and I'm sharing disk d: as "library", so should it be \\office\d\[folder_path] or \\office\library\[folder_path]?

As for Dropbox - I really don't want to install any additional software, and I'm already using Google Drive, so I want to try to do it 'normal' way first

Thanks!
!>

> . . . this doesn't want to work for me
> either*Does it work on your computer?

I can't tell you … as of the night before last, my desktop has been out of commission with an electrical h/w problem of some sort and I only have my phone right now, otherwise I likely would've experimented a bit. Nothing like the smell of burning wires while you're typing away, trying to get shit done.


> in the path should I specify the drive letter
> or the share name? . . . . . . should it be
> \\office\d\[folder_path] or
> \\office\library\[folder_path]?

Same answer as above. I'm thinking also there might be a permissions issue with accessing your office computer from home even if your syntax is right. Your network admin can answer that, and could also be a good source to help resolve your problem altogether.


> As for Dropbox . . . . . . I'm already using
> Google Drive, so I want to try to do it
> 'normal' way first

Didn't know you already had something like Dropbox … I take it you already know you can do the same thing with Google Drive? The specifics might be a bit different, but its purpose is the same.

xxxmichaelking said:

> in the path should I specify the drive letter
> or the share name? . . . . . . should it be
> \\office\d\[folder_path] or
> \\office\library\[folder_path]?

Same answer as above. I'm thinking also there might be a permissions issue with accessing your office computer from home even if your syntax is right. Your network admin can answer that, and could also be a good source to help resolve your problem altogether.

Well, I'm my network admin, its just a home network with 3 computers, nothing fancy Anyone else could take a look on this?

xxxmichaelking said:

> As for Dropbox . . . . . . I'm already using
> Google Drive, so I want to try to do it
> 'normal' way first

Didn't know you already had something like Dropbox … I take it you already know you can do the same thing with Google Drive? The specifics might be a bit different, but its purpose is the same.

Well, not exactly. I don't want data to be copied anywhere, I just want a link:)

!>

Kari said:

I have no issues in creating a symlink with a network share.

This not what I want to accomplish. What I need to do, is to create a normal symlink between two folders on my computer, and this part works ok. Than, when I access this computer through my LAN network, I want to be able to click this link and follow where it leads me, but it doesn't work. Both the target and the source folders of the link are shared and accessible normally through LAN (actually - all disks on this computer are shared), but when I click the link I've got an error message. So this is a problem.

I am not certain that this post strictly belongs in this thread but, since creating a hard link is an important step in my process, I post it here.

By the way, the tutorial on creating a link is fantastic and by far the best I have seen after having read several.

I am in the process of adding a SSD to my computer and using it as the system drive (Win7x64). In order to reduce the space needed on the SSD when migrating my system files I decided to copy (backup) the C:\Users folder and all subfolders (to an external drive), then delete the \Users folder on the C:\ drive prior to cloning the system files to the SSD.

After booting the system from the SSD I would wipe the C:\ partition on the old system HDD, rename that partition, and create a \Users folder. I would then transfer the backed-up Users folder to that drive.

The next step would be to create a Users folder on the SSD as a link and make the Users folder on the HDD as the target.

Before I actually start the process, I will much appreciate any comments on what I have described.

However my first step did not go as desired. When attempting to backup the C:\Users folder the backup software (SyncBack) reported that it was not able to copy several files because "The process cannot access the file because it is being used by another process." I tried several workarounds to solve this problem, but no joy. I list the files here:

\mrb\AppData\Local\Microsoft\Windows\UsrClass.dat
\mrb\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG1
\mrb\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG2
\mrb\AppData\Local\Microsoft\Windows\WebCacheLock.dat
\mrb\AppData\Local\Microsoft\Windows\WebCache\V01.log
\mrb\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat
\mrb\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.tmp
\mrb\ntuser.dat
\mrb\ntuser.dat.LOG1
\mrb\ntuser.dat.LOG2

So my question is: How much trouble am I inviting by simply ignoring the fact that these files will not be available in the transferred Users folder? Is it possible that windows will create these files later, as needed?
　

Kari-
Many thanks for your reply. I am a bit confused:

On the first page of your tutorial you WARN: "Notice that a repair install is also an upgrade install, so if you have ever done a repair install (= in-place upgrade to same edition), you cannot sysprep." I have at one time done such a repair.

In post #22 (for those of us who have already installed Seven) the process clearly requires use of sysprep. So where does that leave me?

Meanwhile I would very much appreciate your comments on my basic question concerning the listed User files that could not be backed-up or copied. Can these be ignored?