SMSLSFIX.ZIP contains modified versions of the SMS 1.2 SMSLS.BAT and RUNSMS.BAT.
The modifications are intended to work around the problem described in the below
KB article.

This workaround has not been fully regression-tested and should be applied only 
to systems experiencing this specific problem. Unless you are severely impacted 
by this specific problem, Microsoft recommends that you wait for the next 
Service Pack that contains this fix. Contact Microsoft Product Support Services 
for more information.

++++++++++++++++++++++++++++++++++++

TCP/IP Inventory is not collected on SMS 1.2 WFW 3.11 Clients


--------------------------------------------------------------------------
The information in this article applies to:

- Systems Management Server 1.2
--------------------------------------------------------------------------

SYMPTOMS
========
When a WFW 3.11 client is inventoried by running either RUNSMS.BAT or SMSLS.BAT, 
no TCP/IP information is collected.  The absence of TCP/IP inventory will also 
cause Remote Control using IP sockets to fail. The following message is displayed 
during inventory, if it is run in verbose mode by setting SMSLS=1 prior to 
execution.

..
.
Looking for TCP/IP stack
Looking for Wolverine stack
Performing TCP/IP detection
C:\MS\SMS\BIN\IPCONFIG.EXE > C:\MS\SMS\TEMP\IPCONFIG.SMS
"IP address information not found in output file"


CAUSE
=====
Invdos.exe does not detect TCP/IP inventory whilst the SMS_P environment variable is present.  SMS_P is a temporary variable set in RUNSMS.BAT / SMSLS.BAT and is used for storage of path details, during client setup execution.  The variable is then re-set during termination of the respective batch file.


RESOLUTION
==========

To work around this problem the following changes need to be made to the runsms.bat 
which resides in ..\SMS\SITE.SRV\MAINCFG.BOX\CLIENT.SRC\ and smsls.bat which is 
found at ..\SMS\SITE.SRV\MAINCFG.BOX\

Add an additional variable e.g. SMS_P2 to the :START section i.e.

	:START

	REM Check to see if we can save path and reserve the necessary environment
	REM space before continuing.
	set SMS_P=%PATH%
	set SMS_P2=%PATH%
	set SMS_TEMP=123456789012345678901234567890123456789012345
	if "%SMS_TEMP%"=="123456789012345678901234567890123456789012345" goto FIND_OS
	goto LOW_ENV


Reset the SMS_P variable prior to execution of invdos.exe in the :RUN_DOS section 
i.e.

	:RUN_DOS
	if not exist %0\..\%SMS_BIN%\setls%SMS_OS%.exe goto NOPATHARG0

	setls%SMS_OS% -m:E -i -p:%SMS_BIN%\CLI_DOS.EXE -pa:/p:%%SMS_UNC%%\ -pa:%SMS_VERBOSE% %SMS_VERBOSE%
	set SMS_P=
	setls%SMS_OS% -m:E -i -p:%SMS_BIN%\INVDOS.EXE  -pa:/l:%%SMS_UNC%%\ -pa:/i -pa:%SMS_VERBOSE% %SMS_VERBOSE%
	goto RESTORE

Restore the path from the new variable (SMS_P2) by changing the path line in the 
:RESTORE section i.e. 

	:RESTORE
	REM Restore the previous path setting.
	PATH=%SMS_P2%
	goto END

And finally reset the new variable, instead of SMS_P  in the :END section i.e.

	:END
	set SMS_P2=
	set SMS_OS=

	set SMS_BIN=
	set SMS_VERBOSE=

STATUS
======

Microsoft has confirmed this to be a problem in Systems Management Server version 
1.20. A supported fix is now available, but has not been fully regression-tested 
and should be applied only to systems experiencing this specific problem. Unless 
you are severely impacted by this specific problem, Microsoft recommends that you 
wait for the next Service Pack that contains this fix. Contact Microsoft Product 
Support Services for more information.