LMSCRIPT.PIF and the SMSLS logon script

• Microsoft Systems Management Server versions 1.0 and 1.1

SYMPTOMS

The SMSLS logon script stop responding (hangs) when used with some Windows 3.1 and Windows for Workgroups 3.1 or 3.11 configurations.

CAUSE

When a Windows system logs on to a network, LMSCRIPT.EXE is run on the client to parse and run the logon script. Under some Windows configurations, applications run from the logon script can cause LMSCRIPT.EXE to hang. This problem usually occurs due to a timing problem with the background and foreground processes.

Since LMSCRIPT.EXE is an MS-DOS-based program, a LMSCRIPT.PIF file is used to describe it's required environment. Other drivers or processes running under Windows can take processor cycles away from LMSCRIPT.EXE. This can hang the LMSCRIPT process or cause applications that are running within the logon script to fail.

RESOLUTION

You may be able to reduce or eliminate this problem by modifying the \WINDOWS\SYSTEM\LMSCRIPT.PIF file or by creating a batch file:

Modifying LMSCRIPT.PIF

1. Run PIF Editor (PIFEDIT.EXE) and open \WINDOWS\SYSTEM\LMSCRIPT.PIF.

2. Ensure the Execution Background check box is selected. It should be by default.

3. Select the Execution Exclusive check box.

4. Save your changes and quit PIF editor.

1. Run PIF Editor (PIFEDIT.EXE) and open \WINDOWS\SYSTEM\LMSCRIPT.PIF.

2. Choose Advanced, and then increase the Background Priority and Foreground Priority values.

3. Save your changes and quit PIF editor.

Creating Batch File

Create a batch file called NTLOGON.BAT with the following entries:

   Net Time
   Net Use <network drive>: \\<ServerName>\<SMS Share>
   <network drive>:
   SMSLS.BAT  (SMSLS logon script)
   <local drive C>: