Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Best Approach for Login Scripts
Message
 
 
À
23/08/2001 18:36:12
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00548374
Message ID:
00548599
Vues:
21
All you have to do is launch Netware Admin utility and go to the details of the container object where all the users exist. Create your login script. If you need a search map, the syntax is:

MAP INS S1:=servername/volume:dir_path

This will insert the search path at the beginning of the path environment variable. Otherwise:

MAP S16:=servername/volume:dir_path

will place it at the end. The number will be bumped up to the next available number.

FWIS, I prefere not to use Login scripts for drive mappings. I do all this viw Windows Explorer and just make the connection persistent. You can also look in the registry to see where this info is recorded, and just add a registry entry via the VFP Registry class.

If you go with the login script, you have to enable the Execute Login Script option in whatever Client you are using.


>We are running VFP 5.0 on about 40 clients connected to a Novell server. Client OS include Win 95, 98, NT, and 2000. We are getting ready to move the database to a Win 2000 server and would like to implement login scripts on all of the clients to map a server directory among other things.
>
>I am a little wary of running WSH on all of the clients because I think it opens the door to viruses and worms. That said I would like to hear suggestions on the best approach to a standardized login script for all clients.
>
>For instance:
>
>1) DOS commands. Can we accomplish what we need on all machines?
>
>2) WSH.
>
>3) KiXtart. Does this run on Win 95/98?
>
>4) Perl (possibly using Perl2Exe).
>
>5) Other ?
>
>TIA for all suggestions.
>
>Peter Robinson
Mark McCasland
Midlothian, TX USA
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform