Executes a script that does not require rollback. Used by
Microsoft Provisioning Framework (MPF).
An example of a script that is appropriate for this procedure
would be a parser program. The script can take the form of a file
or an inline script block (like the <script> tag of an HTML
This procedure creates an intrinsic object that is available to
the script, ProviderXML. ProviderXML exposes the
IXMLDOMNode interface passed to the provider by a provisioning engine. The
XML contains the executeData node,
which contains all data passed to the provider. The script uses
this object to get and return data.
REM Return "<hello>World".
set ed = ProviderXML.selectSingleNode( "executeData" )
set newElement = ed.ownerDocument.createElement( "hello" )
newElement.text = "World"
sf.appendChild( newElement )
For inline scripts, it is important to avoid conflicts with XML.
If the script contains characters such as "<" and ">", embed
the script in a CDATA node.
Optional. Boolean that indicates whether the body of this node
is a file ("1"). If this attribute is set to any other value or not
specified, the script is assumed to be inline.
Required. ProgId of the script engine to load and use to run
the specified script. The script engine must be a COM object that
has the OLEScript registry key and implements the script
The following code fragment shows the format for sending data to
this procedure. For inline scripts, embed the script block in the
executeData node. For more information on individual
elements and attributes, see the Elements and Attributes table.
Example XML Response
ExecuteScript does not return data. However, the called
script may add output elements.