[Sorry if this is too off-topic for even the OFFTOPIC
list but this is driving me crazy]

I have a situation where users on NT workstations need
to access resources on an NT network.  (surprise!)

Currently these resources are identified by UNC names
i.e.  \\box\sharename\path\...  etc    and users with
roaming profiles have shortcuts and registry entries
(and probably MSExcel links and who knows what else)
pointing to stuff using these names.

THE GOAL:  is to make the names they use independent
of the physical box the resource is on or the box
they are logged onto - so that we can move stuff 
around without rocking users out of the boat.     
Granted they'll have to change their shortcut 
references this one time - but then that's the end 
of it.

One way is to set drive mappings in logon scripts 
and have users change their shortcut and link references
to use the mapped drives.  This is acceptable but 
less than ideal because not all drive letters are 
available to all users (or all workstations) and if 
we move something we still have to fix up all the logon 
scripts in a user-dependent way.

NOW FINALLY THE QUESTION:   What I tried and thought
should work (but doesn't) is the following:

in each users's logon script use SETX to set startup
environment variables associating a name with each
UNC resource, like this:
      
        SETX ACCTNG \\boxZ\FINANCE\ACCOUNTING

then change all the references and shortcuts to reference
the resources like this:

        %ACCTNG%\mysheet.xls

No messy drive mappings - no running out of drive letters
and all the logon scripts change the same way and 
in fact can all just invoke some common script to set
these names.

In effect unix style symbolic links 

**BUT**  it doesn't work.    For example - desktop
shortcuts to a folder named this way won't open in one 
click - you have to click once, then click "open target".
And it's strange - not ALL of the shortcuts fail
this way - some actually do open in one click.   I haven't
been able to isolate what makes the difference.


Any ideas either about why this fails, or of some other
way to solve the original problem?

thx

-ns


---------------------------------------------------------------------------
  New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz

Reply via email to