Julian Easterling's questions

I use Symlinks extensively on my file server to prevent duplication of directories and files. I've enabled remote evaluation of Symlinks by using fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1. However, now I'm getting a "The device is not ready" error when I browse the network share from a remote system.

The particular share I'm accessing is hosted on the D: drive and the Symlink on the host points to a directory created on the E: drive using mklink /D D:\Directory\Link E:\Directory since Junctions do not work across drives.

Is there anyway to "hide" the symlink completely to the client so that I don't have to configure every client accessing this share to follow symlinks? On the server, I have no problems navigating between folders/links.

A vendor is attempting to map and preserve a network drive using nt authority/system; so it stays persistent when the interactive session of the server is lost. They were able to do this on one server (Windows 2008 R2) but not a second computer (also Windows 2008 R2).

D:\PsExec.exe -s cmd.exe

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. all rights reserved.

C:\Windows\system32>whoami
nt authority\system

C:\Windows\system32>net use
New connections will be remembered.

Status        Local   Remote               Network
--------------------------------------------------------------------
OK            X:      \\netapp1\share1     Microsoft Windows Network
The command completed successfully.

C:\Windows\system32>net use q: \\netapp1\share1
System error 1808 has occurred.

The account used is a computer account. Use your global user account
or local user account to access this server.

C:\Windows\system32>

I am unsure on how to set up a "machine account mapping" which will preserve the drive letter of the Netapp path being mapped, so that the service account running a Windows service can continue to access the share after interactive logon has expired on the server. Since they were able to do this on one server but not another, I'm not sure how to troubleshoot the problem? Any suggestions?