MS Logon script which also Handles Shares Offered from Novell Netware Servers
Keywords: MS Logon script Novell
Here's a Microsoft Net Logon script, which also handles shares offered from Novell Netware servers.
- This fix is specific to MS net logon, for both 95 and NT boxes:
- Create a subdirectory of \netlogon, called SUPDLL. Move the WinBatch DLLs
into \netlogon\SUPDLL.
- Create a .BAT file that looks like:
@echo off
@if "%OS%"=="Windows_NT" set NTLOGSW=/HIGH
@path=%PATH%;%0\..\SUPDLL
@start /w /max %NTLOGSW% %0\..\tstlogon.exe
- The %0 in 95 returns the path to the netlogon share. The %0 in NT is the UNC path of the computer followed
by the netlogon share, followed by the name of the logon script! Something like:
\\computer\netlogonshare\loginscript.bat
- The START /w eliminates the illegal operation, so long as you are only doing RunWaits (not waiting for a WinBatch program to finish will cause the problem again).
- In NT you need to explicitly connect \netlogon to LASTDRIVE-1 and do any runs from that drive.
(The drawback is that the drive is connected through the whole session.)
To do this in NT (95 automatically maps the Z: drive to the netlogon share),
you'll need to get the netlogon directory utilizing the netlogon variable, with something like:
nt_logon_ser = Environment("LOGONSERVER")
nt_logon_ser = strcat(nt_logon_ser, "\netlogon")
and then map that to the Z: drive yourself.
- The %NTLOGSW% helps a little bit with execution time on NT.
The SUPDLL in the path lets you take the .DLLs out of the \netlogon subdir, and then you can put them locally (you'll want a refresh routine in your script though).
The idea is that \supdll protects you from missing DLLs letting you get WinBatch up (so you can replace them).
This means that the .DLLs are not in \netlogon, so they will be found on \system(32) if present,
or in SUPDLL if not (the path is the last in the search order). Since you are modifying the path
inside a DOSBOX, it disappears after the box is closed.
- Handle the update of the files in \system(32) within the executable itself.
This kink changes the RAS execution time of the 100k executable from 7 min average
down to 75 sec. There is no appreciable change to LAN connected logons
(which are already blindingly fast).
- By the way, starting with /HIGH priority also makes a 20% difference.
Article ID: W13511
Filename: MS Logon Script Handles Netware Shares.txt
File Created: 2000:02:08:11:32:24
Last Updated: 2000:02:08:11:32:24