有没有办法将 UNC 路径映射到 Windows 2003 上的本地文件夹？

发布于 2024-10-06 02:29:18 字数 154 浏览 1 评论 0原文

我知道我可以将 UNC 路径映射到本地驱动器号。但是，我想知道是否有办法将 UNC 路径映射到本地文件夹。我有一个程序，其中硬编码到程序中的特定文件夹，我想尝试创建一个映射到 UNC 路径的同名文件夹，以便可以从网络共享访问数据。这可行吗？具体来说，这是在 Windows 2003 服务器上。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

自此以后，行同陌路 2024-10-13 02:29:18

是的，有一种方法可以将 UNC 路径映射到本地文件夹：

C:\>mklink /D Develop \\obsidian\Develop
symbolic link created for Develop <<===>> \\obsidian\Develop

这是因为我希望 build 服务器使用我自己 PC 的 Develop 文件夹作为其 Develop 文件夹：

10/20/2012  11:01 AM    <SYMLINKD>     Develop [\\obsidian\Develop]

这就是它。

MKLINK [[/D] | [/H] | [/J]] Link Target

        /D      Creates a directory symbolic link.  Default is a file
                symbolic link.
        /H      Creates a hard link instead of a symbolic link.
        /J      Creates a Directory Junction.
        Link    specifies the new symbolic link name.
        Target  specifies the path (relative or absolute) that the new link
                refers to.

注意：在我的实际情况中，我需要另一个级别的重定向，因为我正在使用的程序意识到Develop是一个符号链接，指向到远程机器，并拒绝遵守。我告诉程序关闭并通过给它一个指向本地资源的连接来执行它所指示的操作。

10/20/2012  11:06 AM    <JUNCTION>     Develop [C:\Develop2\]
10/20/2012  11:01 AM    <SYMLINKD>     Develop2 [\\obsidian\Develop]

Yes, there is a way to map a UNC path to a local folder:

C:\>mklink /D Develop \\obsidian\Develop
symbolic link created for Develop <<===>> \\obsidian\Develop

This is because i want a build server to use my own PC's Develop folder as its Develop folder:

10/20/2012  11:01 AM    <SYMLINKD>     Develop [\\obsidian\Develop]

And there you have it.

MKLINK [[/D] | [/H] | [/J]] Link Target

        /D      Creates a directory symbolic link.  Default is a file
                symbolic link.
        /H      Creates a hard link instead of a symbolic link.
        /J      Creates a Directory Junction.
        Link    specifies the new symbolic link name.
        Target  specifies the path (relative or absolute) that the new link
                refers to.

Note: In my actual situation i needed another level of redirection, because the program i'm using realized that Develop was a symbolic link, pointing to a remote machine, and refused to comply. i told the program to shut up and do what it's told by giving it a junction that points to a local resource.

10/20/2012  11:06 AM    <JUNCTION>     Develop [C:\Develop2\]
10/20/2012  11:01 AM    <SYMLINKD>     Develop2 [\\obsidian\Develop]

回复收藏 0 原文

凹づ凸ル 2024-10-13 02:29:18

这完全符合OP的要求——映射到网络共享的Windows 2003的符号链接。经过几个小时的观察和测试其他组件后，我发现这是唯一可以与网络共享一起使用的组件。

Windows XP 的符号链接驱动程序

此实用程序适用于 XP 和 2003 映射到网络共享并创建符号链接：http://schinagl.priv.at/nt/ln/ln.html#symboliclinksforwindowsxp

现在将其放入路径上的目录中，您就可以使用 senable 创建符号链接。 exe（带有symlink.sys）和ln.exe（您还需要从上述站点获取它以及它对 Visual C++ 运行时 DLL 的依赖项）。

添加的奖励：伪造 MkLink

将这两个附加文件放入具有 senable.exe 的同一目录中，并确保它们全部位于路径中。

mklink.cmd:

@echo off

SET DIR=%~dp0%
@powershell -NoProfile -ExecutionPolicy unrestricted -Command "& '%DIR%Symlink.ps1' %*"

pushd "%DIR%"
"%DIR%senable.exe" start
popd

Symlink.ps1:

param (
 [string]$symlinktype,
 [string]$link,
 [string]$target
)

$scriptpath = $MyInvocation.MyCommand.Path
$ScriptDir = Split-Path $scriptpath

$senable = Join-Path "$ScriptDir" senable.exe
$ln = Join-Path "$ScriptDir" ln.exe

pushd "$ScriptDir"
& cmd /c "$senable" install
popd
& cmd /c "$ln" -s "$target" "$link"

注意：

您需要在 Windows 2003 上安装以下其他项目（非 R2，我还不确定 R2 需要什么）：

Microsoft .NET Framework 2.0 Service Pack 1
Windows 成像组件
Windows Server 2003 Service Pack 2
Windows Management Framework Core（这带来了 PowerShell 2）

Chocolatey 包

我创建了一个 Chocolatey 包，它将为您完成所有这些操作：http://chocolatey.org/packages/win2003-mklink

重要提示

与常规符号链接不同，您不能简单地删除文件夹来删除符号链接文件夹。如果这样做，它将删除它指向的真实文件夹。因此使用时要格外小心。

This meets exactly what the OP asked for - a symbolic link for Windows 2003 that maps to a network share. After many hours looking at others and testing them, this is the only component I found that will work with network shares.

Symbolic Link Driver for Windows XP

This utility will work for both XP and 2003 mapping to a network share and creating a symlink: http://schinagl.priv.at/nt/ln/ln.html#symboliclinksforwindowsxp

Now put this in a directory that you put on the path and you have the ability to create symlinks using senable.exe (with symlink.sys) and ln.exe (you will need that from the above site as well along with its dependency on the Visual C++ runtime DLLs).

Added Bonus: Fake out MkLink

Put these additional two files into the same directory where you have senable.exe and make sure this is all on the path.

mklink.cmd:

@echo off

SET DIR=%~dp0%
@powershell -NoProfile -ExecutionPolicy unrestricted -Command "& '%DIR%Symlink.ps1' %*"

pushd "%DIR%"
"%DIR%senable.exe" start
popd

Symlink.ps1:

param (
 [string]$symlinktype,
 [string]$link,
 [string]$target
)

$scriptpath = $MyInvocation.MyCommand.Path
$ScriptDir = Split-Path $scriptpath

$senable = Join-Path "$ScriptDir" senable.exe
$ln = Join-Path "$ScriptDir" ln.exe

pushd "$ScriptDir"
& cmd /c "$senable" install
popd
& cmd /c "$ln" -s "$target" "$link"

Note:

You need the following other items installed on Windows 2003 (non-R2, I'm not fully sure what you need for R2 yet):

Microsoft .NET Framework 2.0 Service Pack 1
Windows Imaging Component
Windows Server 2003 Service Pack 2
Windows Management Framework Core (this brings PowerShell 2)

Chocolatey Package

I created a chocolatey package that will do all of this for you: http://chocolatey.org/packages/win2003-mklink

Important Note

Unlike regular symlinks, you can not simply delete the folder to remove the symbolic link folder. If you do that, it will delete the real folder it it pointing to. So use with extreme care.

回复收藏 0 原文