Microsoft KB Archive/253648
Article ID: 253648
Article Last Modified on 10/27/2006
- Microsoft Systems Management Server 2.0 Standard Edition
- Microsoft Systems Management Server 2.0 Service Pack 1
- Microsoft Systems Management Server 2.0 Service Pack 2
- Microsoft Systems Management Server 2.0 Service Pack 3
This article was previously published under Q253648
You are unable to successfully install the Systems Management Server (SMS) client on a Windows NT 4.0-based computer by using the Smsls.bat file, but you do not receive any error messages.
You may see entries similar to the following one in the WN_Logon.log file:
If you attempt to run Snboot.exe, or Smsboot1.exe on the client, you may receive the following error message:
The dosonly command is enabled in the Config.nt file.
Disable the dosonly option by remarking (REM) it out of the Config.nt file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Windows NT Help DOSONLY notes:
Normally when you exit an MS-DOS-based application, Windows NT returns to the Windows NT command interpreter (CMD.EXE). However, by default, when you run a TSR or temporarily suspend an MS-DOS-based application to return to the command prompt Windows NT runs COMMAND.COM, the command interpreter for the MS-DOS environment. This preserves the MS-DOS environment allowing you to use the TSR immediately.
Because starting and running other types of applications from the COMMAND.COM prompt can disrupt a TSR or suspended MS-DOS-based applications, Windows NT provides the DOSONLY command. The DOSONLY command allows only MS-DOS-based applications to be started from the COMMAND.COM prompt. You can include the DOSONLY command in your CONFIG.NT file or the equivalent custom startup file in an application’s PIF.
Additional query words: prodsms Smsls bat CONFIG NT REM WN_Logon log Snboot Smsboot1 SMS cmd exe command com
Keywords: kbbug kbclient kbconfig kbinterop kbnofix kbprb kbsetup kbsmsutil kbupgrade KB253648