Using batch files in sharing packages
Article ID: 130898
Article Last Modified on 2/25/2007
APPLIES TO
- Microsoft Systems Management Server 1.0 Standard Edition
- Microsoft Systems Management Server 1.1 Standard Edition
- Microsoft Systems Management Server 1.2 Standard Edition
- Microsoft Systems Management Server 2.0 Standard Edition
- Microsoft Systems Management Server 2003
This article was previously published under Q130898
SUMMARY
When using a batch file as the command line executable for a sharing
package in Microsoft System Management Server, the "Requires Drive Letter"
option should be used. If "Runs with UNC Name" is used, the program
item gives the following error upon execution:
Could not start application with command line 'batch filename'.
File not found."
MORE INFORMATION
Windows 3.x clients do not process batch files when they are executed
through a Universal Naming Convention (UNC) connection. When the batch file
is executed, an MS-DOS virtual machine is opened to process the batch file.
However, the virtual machine does not support running batch files through
UNC connections and is unable to continue.
If instead, the package is defined to use a drive letter, the client will
assign a drive letter to the package share which will be available to the
virtual machine for processing the batch file.
Additional query words: sms share prodsms
Keywords: kbenv kbnetwork KB130898