mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
49 lines
1.3 KiB
Markdown
49 lines
1.3 KiB
Markdown
---
|
||
title: ICSPNode Execute
|
||
description: ICSPNode Execute
|
||
ms.assetid: 5916e7b7-256d-49fd-82b6-db0547a215ec
|
||
ms.author: maricia
|
||
ms.topic: article
|
||
ms.prod: w10
|
||
ms.technology: windows
|
||
author: MariciaAlforque
|
||
ms.date: 06/26/2017
|
||
---
|
||
|
||
# ICSPNode::Execute
|
||
|
||
This method runs a task on an internally-transactioned configuration service provider node by passing in the specified user data and returning a result. The exact meaning of **Execute** and whether it is even supported depends on the purpose of the node. For example, **Execute** called on a node that represents a file should probably **ShellExecute** the file, whereas calling **Execute** on a registry node generally does not make sense.
|
||
|
||
## Syntax
|
||
|
||
``` syntax
|
||
HRESULT Execute([in] VARIANT varUserData);
|
||
```
|
||
|
||
## Parameters
|
||
|
||
<a href="" id="varuserdata"></a>*varUserData*
|
||
Data to pass into the execution.
|
||
|
||
## Return Value
|
||
|
||
A value of S\_OK indicates that the operation was performed successfully on the node. E\_NOTIMPL should be returned if this method is not implemented.
|
||
|
||
## Remarks
|
||
|
||
Externally–transactioned nodes do not support this method.
|
||
|
||
## Requirements
|
||
|
||
**Header:** None
|
||
|
||
## Related topics
|
||
|
||
[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
|
||
|
||
|
||
|
||
|
||
|
||
|