Re: NET USE vs. SUBST

  • Thread starter Thread starter Jetro
  • Start date Start date
J

Jetro

Enable and configure Off-line files on the Home directories.
*subst* has a deal with the local paths, *net use* applies to the network
shares.
You rename/label any drive via Windows Explorer the same way as you rename a
file.
 
Enable and configure Off-line files on the Home directories.

Sorry, but I can't do that. Because we shifting the computers, and
using roaming profiles. If I used cached Home directories, the hard disks
would be full in a moment.
*subst* has a deal with the local paths, *net use* applies to the network
shares.

But it _IS_ possible to subst a network drive! subst q: \\sdfsdf\\dsmfs$
You rename/label any drive via Windows Explorer the same way as you rename a
file.

Yes, but I don't want to instruct the users to do that. I want to use
loginscripts
instead. So I thought if there is a "secret" parameter for subst, or there
is a vbscript
function for that...

Thx for the answers,

Satu
 
If the users don't have a permanent working place you can delete either
locally cached profile or local copy of user's offline files at logoff or
both. Look in ComputerConfiguration/AdmTemplates/Network/OfflineFiles.
*subst* exists since MS-DOS when Microsoft didn't know anything about the
networks. If you *subst* the UNC path, you get *Disconnected network drive*
label in Windows Explorer. Even though the drive icon contains a red "X",
you are still able to access the drive. This behavior occurs because Windows
does not display the drive status correctly. To work around this behavior,
use the NET USE command to connect to network resources instead of the SUBST
command.

http://support.microsoft.com/?kbid=269163
Drives Created with the Subst Command Are Not Connected

http://support.microsoft.com/kb/218740/EN-US/
Cannot Use Subst.exe with UNC Path
 
Back
Top