Mapping %RootDrive% with SUBST vs. NET USE

[Jon]

What are the differences, if any, between using SUBST with a UNC vs. NET
USE?

We run TSE + MetaFrame with load balancing. We need user data stored to
a common place vs. on each server so users pick up where they left off no
matter what server they get.

In UsrLogon.Cmd, we are mapping %RootDrive% using SUBST with a UNC.
ServerA holds the user data and has a share called Users. So on ServerB,
what is the difference between

NET USE T: \\ServerA\Users
SUBST %RootDrive% T:\%UserName%

and

SUBST \\ServerA\Users\%UserName%

We prefer the second because it doesn't waste a drive letter. However,
we are experiencing intermittent application errors related to cannot
find drive/file type issues, but only for users logged onto ServerB. Is
SUBST with a UNC flakier than doing a NET USE or should I look elsehwere
for the problem?

-Jon

[Jon]

Aw, shucks...
In the second option, I meant:
SUBST %RootDrive% \\ServerA\Users\%UserName%

-Jon

In article <MPG.113fcf2a6...@news2.one.net>, an...@anon.net
says...

[Howie Erickson]

Jon,
I would look at the fact that you are not using a drive letter in the
Subst \\ServerA\Users\%username%. The correct syntax whether using a Net
use or a subst is to use a drive letter. What you are saying in the latter
subst is sustitute \\serverA\users\%ussername% for nothing (null). if you
provide it with %Rootdrive% or a given drive letter, then it should be much
more stable. Using that syntax, there should be little difference between
the subst and the net use.

Hope this helps,
Howie Erickson, MCP