ENVIRONMENT: Windows NT/2000/XP without a client
This is pretty simple and is not ideal for all situations — for example, if the mapping is required before the user desktop has finished loading.
- Create a blank Application object.
- Go to Run Options/Launch Scripts.
- Enter the required mappings in the Run before Launching box. You need to use the windows format and syntax
net use S: \\ServerName\Share\Path /persistent:no
The /persistent:no removes the mapping on logout. This prevents problems when the command is rerun.
You can add as many mappings as you want.
- In the script engine location enter %*WINSYSDIR%\CMD.EXE /C
This runs the command.com on NT/2000/XP. The /C on the end ensures the script completes and doesn’t hang.
- On the Identification/Icon tab untick the Show Progress box. This just prevents the little “application is starting” box from showing.
- Finally go to the Associations and add the OUs, groups and users as required and set to Force Run.
Now when NAL starts up the script will run and the Windows mappings will connect.
Remember that any Windows command line stuff can be run this way, so go ahead and get creative.