diff --git a/windows/client-management/mdm/TOC.md b/windows/client-management/mdm/TOC.md
index 4ec8751db6..2777f01ddd 100644
--- a/windows/client-management/mdm/TOC.md
+++ b/windows/client-management/mdm/TOC.md
@@ -45,28 +45,6 @@
## [DMProcessConfigXMLFiltered](dmprocessconfigxmlfiltered.md)
## [Using PowerShell scripting with the WMI Bridge Provider](using-powershell-scripting-with-the-wmi-bridge-provider.md)
## [WMI providers supported in Windows 10](wmi-providers-supported-in-windows.md)
-## [Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-### [Design a custom configuration service provider](design-a-custom-windows-csp.md)
-### [IConfigServiceProvider2](iconfigserviceprovider2.md)
-#### [IConfigServiceProvider2::ConfigManagerNotification](iconfigserviceprovider2configmanagernotification.md)
-#### [IConfigServiceProvider2::GetNode](iconfigserviceprovider2getnode.md)
-### [ICSPNode](icspnode.md)
-#### [ICSPNode::Add](icspnodeadd.md)
-#### [ICSPNode::Clear](icspnodeclear.md)
-#### [ICSPNode::Copy](icspnodecopy.md)
-#### [ICSPNode::DeleteChild](icspnodedeletechild.md)
-#### [ICSPNode::DeleteProperty](icspnodedeleteproperty.md)
-#### [ICSPNode::Execute](icspnodeexecute.md)
-#### [ICSPNode::GetChildNodeNames](icspnodegetchildnodenames.md)
-#### [ICSPNode::GetProperty](icspnodegetproperty.md)
-#### [ICSPNode::GetPropertyIdentifiers](icspnodegetpropertyidentifiers.md)
-#### [ICSPNode::GetValue](icspnodegetvalue.md)
-#### [ICSPNode::Move](icspnodemove.md)
-#### [ICSPNode::SetProperty](icspnodesetproperty.md)
-#### [ICSPNode::SetValue](icspnodesetvalue.md)
-### [ICSPNodeTransactioning](icspnodetransactioning.md)
-### [ICSPValidate](icspvalidate.md)
-### [Samples for writing a custom configuration service provider](samples-for-writing-a-custom-configuration-service-provider.md)
## [Configuration service provider reference](configuration-service-provider-reference.md)
### [AccountManagement CSP](accountmanagement-csp.md)
#### [AccountManagement DDF file](accountmanagement-ddf.md)
diff --git a/windows/client-management/mdm/create-a-custom-configuration-service-provider.md b/windows/client-management/mdm/create-a-custom-configuration-service-provider.md
deleted file mode 100644
index cb8579e827..0000000000
--- a/windows/client-management/mdm/create-a-custom-configuration-service-provider.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Create a custom configuration service provider
-description: Create a custom configuration service provider
-ms.assetid: 0cb37f03-5bf2-4451-8276-23f4a1dee33f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# Create a custom configuration service provider
-
-Mobile device OEMs can create custom configuration service providers to manage their devices. A configuration service provider includes an interface for creating, editing, and deleting nodes, and the nodes themselves. Each node contains data for one registry value and can optionally support get, set, and delete operations.
-
-To design a custom configuration service provider, the OEM must perform the following steps:
-
-1. Establish node semantics
-2. Shape the configuration service provider's subtree
-3. Choose a transactioning scheme for each node
-4. Determine node operations
-
-For more information, see [Designing a custom configuration service provider](design-a-custom-windows-csp.md).
-
-To write a custom configuration service provider, the OEM must implement the following interfaces:
-
-- [IConfigServiceProvider2](iconfigserviceprovider2.md) (one per configuration service provider)
-
-- [ICSPNode](icspnode.md) (one per node)
-
-- [ICSPNodeTransactioning](icspnodetransactioning.md) (optional, for internally transactioned nodes only)
-
-- [ICSPValidate](icspvalidate.md) (optional, for UI only)
-
-This code must be compiled into a single .dll file and added to a package by using the instructions found in "Adding content to a package" in [Creating packages](https://msdn.microsoft.com/library/windows/hardware/dn756642). While writing this code, OEMs can store registry settings and files in the following locations.
-
-
-
-
-
-
-
-
-File location |
-%DataDrive%\SharedData\OEM\CSP</p> |
-
-
-Registry location |
-$(HKLM.SOFTWARE)\OEM\CSP</p> |
-
-
-
-
-
-For examples of how to perform common tasks such as adding a node, replacing a node's value, querying a node's value, or enumerating a node's children, see [Samples for writing a custom configuration service provider](samples-for-writing-a-custom-configuration-service-provider.md).
-
-To register the configuration service provider as a COM object, you must add the following registry setting to your package. This step is required. In the following sample, replace *uniqueCSPguid* with a new, unique CLSID generated for this purpose. Replace *dllName* with the name of the .dll file that contains the code for your configuration service provider.
-
-``` syntax
-
-
-
-
-
-```
-
-To register the configuration service provider with ConfigManager2, you must add the following registry setting to your package. This step is required. In the following sample, replace *dllName* with the name of the configuration service provider (the name of the root node). Replace *uniqueCSPguid* with the same *uniqueCSPguid* value as in the preceding example.
-
-``` syntax
-
-
-
-
-
-```
-
-To make the configuration service provider accessible from WAP XML, you must register it with the WAP data processing unit by setting the following registry key in your package. Replace *Name* with the name of the configuration service provider. Leave the GUID value exactly as written here.
-
-``` syntax
-
-
-
-
-
-```
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/design-a-custom-windows-csp.md b/windows/client-management/mdm/design-a-custom-windows-csp.md
deleted file mode 100644
index 583e098cdc..0000000000
--- a/windows/client-management/mdm/design-a-custom-windows-csp.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: Design a custom configuration service provider
-description: Design a custom configuration service provider
-MS-HAID:
-- 'p\_phDeviceMgmt.designing\_a\_custom\_configuration\_service\_provider'
-- 'p\_phDeviceMgmt.design\_a\_custom\_windows\_csp'
-ms.assetid: 0fff9516-a71a-4036-a57b-503ef1a81a37
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# Design a custom configuration service provider
-
-To design a custom configuration service provider, the OEM must perform the following steps:
-
-1. Establish node semantics
-2. Shape the configuration service provider's subtree
-3. Choose a transactioning scheme for each node
-4. Determine node operations
-
-For more information about the larger process of writing a new configuration service provider, see [Create a custom configuration service provider](create-a-custom-configuration-service-provider.md).
-
-## Establish node semantics
-
-First, determine the nodes you need based on the kind of data to be stored in the registry.
-
-Nodes can represent anything from abstract concepts or collections (such as email accounts or connection settings) to more concrete objects (such as registry keys and values, directories, and files).
-
-### Example
-
-For example, a hypothetical Email configuration service provider might have these nodes:
-
-- Account: The name of the email account (such as "Hotmail")
-
-- Username: The user name or email address ("exampleAccount@hotmail.com")
-
-- Password: The user's password
-
-- Server: The DNS address of the server ("mail-serv1-example.mail.hotmail.com")
-
-The `Account`, `Username`, and `Server` nodes would hold text-based information about the email account, the user's email address, and the server address associated with that account. The `Password` node, however, might hold a binary hash of the user's password.
-
-## Shape the configuration service provider's subtree
-
-After determining what the nodes represent, decide where each node fits in the settings hierarchy.
-
-The root node of a configuration service provider's subtree must be the name of the configuration service provider. In this example, the root node is `Email`.
-
-All of the nodes defined in the previous step must reside under the configuration service provider's root node. Leaf nodes should be used to store data, and interior nodes should be used to group the data into logical collections. Node URIs must be unique. In other words, no two nodes can have both the same parent and the same name.
-
-There are three typical scenarios for grouping and structuring the nodes:
-
-- If all of the data belongs to the same component and no further categorizing or grouping is required, you can build a flat tree in which all values are stored directly under the root node. For examples of this design, see [DevInfo configuration service provider](devinfo-csp.md), [HotSpot configuration service provider](hotspot-csp.md), and [w4 APPLICATION configuration service provider](w4-application-csp.md).
-
-- If the configuration service provider's nodes represent a preexisting set of entities whose structure is well-defined (such as directories and files), the configuration service provider's nodes can simply mirror the existing structure.
-
-- If the data must be grouped by type or component, a more complex structure is required. This is especially true when there can be multiple instances of the dataset on the device, and each set is indexed by an ID, account name, or account type. In this case, you must build a more complex tree structure. For examples, see [ActiveSync configuration service provider](activesync-csp.md), [CertificateStore configuration service provider](certificatestore-csp.md), and [CMPolicy configuration service provider](cmpolicy-csp.md).
-
-### Example
-
-The following image shows an incorrect way to structure the hypothetical `Email` configuration service provider. The interior `Account` nodes group the account data (server name, user name, and user password).
-
-
-
-However, the account nodes in this design are not unique. Even though the nodes are grouped sensibly, the path for each of the leaf nodes is ambiguous. There is no way to disambiguate the two `Username` nodes, for example, or to reliably access the same node by using the same path. This structure will not work. The easiest solution to this problem is usually to replace an interior node (the grouping node) by:
-
-1. Promoting a child node.
-
-2. Using the node value as the name of the new interior node.
-
-The following design conveys the same amount of information as the first design, but all nodes have a unique path, and therefore it will work.
-
-
-
-In this case, the `Server` nodes have been promoted up one level to replace the `Account` nodes, and their values are now used as the node names. For example, you could have two different email accounts on the phone, with server names "www.hotmail.com" and "exchange.microsoft.com", each of which stores a user name and a password.
-
-Note that the process of shaping the configuration service provider’s subtree influences the choice of transactioning schemes for each node. If possible, peer nodes should not have dependencies on each other. Internode dependencies other than parent/child relationships create mandatory groups of settings, which makes configuration service provider development more difficult.
-
-## Choose a transactioning scheme for each node
-
-For each node, decide whether to use *external transactioning* or *internal transactioning* to manage the transaction phases (rollback persistence, rollback, and commitment) for the node.
-
-External transactioning is the simplest option because it allows ConfigManager2 to automatically handle the node's transactioning.
-
-However, you must use internal transactioning for the following types of nodes:
-
-- A node that supports the **Execute** method.
-
-- A node that contains sensitive information (such as a password) that must not be saved in plain text in the ConfigManager2 rollback document.
-
-- A node that has a dependency on another node that is not a parent. For example, if a parent node has two children that are both required, the configuration service provider could use internal transactioning to defer provisioning the account until both values are set.
-
-You can choose to mix transactioning modes in your configuration service provider, using internal transactioning for some operations but external transactioning for others. For more information about writing an internally transactioned node, see the [ICSPNodeTransactioning](icspnodetransactioning.md) interface.
-
-## Determine node operations
-
-The operations available for each node can vary depending on the purpose of the configuration service provider. The configuration service provider will be easier to use if the operations are consistent. For more information about the supported operations, see the [ICSPNode](icspnode.md) interface.
-
-For externally transactioned nodes, an operation implementation must include the contrary operations shown in the following table to allow rollback of the operation.
-
-For internally transactioned nodes, the practice of implementing the contrary commands for each command is recommended, but not required.
-
-
-
-
-
-
-
-
-
-
-
-Add |
-Clear and DeleteChild |
-
-
-Copy |
-To copy to a new node: Clear and DeleteChild
-To copy to an existing node: Add and SetValue |
-
-
-Clear |
-To restore the state of the deleted node: SetValue and SetProperty |
-
-
-DeleteChild |
-To restore the old node: Add |
-
-
-DeleteProperty |
-To restore the deleted property: SetProperty |
-
-
-Execute |
-Externally transactioned nodes do not support the Execute command. |
-
-
-GetValue |
-None |
-
-
-Move |
-To restore a source node: Move
-To restore an overwritten target node: Add and SetValue |
-
-
-SetValue |
-To restore the previous value: SetValue |
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/iconfigserviceprovider2.md b/windows/client-management/mdm/iconfigserviceprovider2.md
deleted file mode 100644
index c73e0ce0b4..0000000000
--- a/windows/client-management/mdm/iconfigserviceprovider2.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: IConfigServiceProvider2
-description: IConfigServiceProvider2
-ms.assetid: 8deec0fb-59a6-4d08-8ddb-6d0d3d868a10
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# IConfigServiceProvider2
-
-
-OEMs are required to implement this interface once per configuration service provider. ConfigManager2 clients use this interface to instantiate the configuration service provider, to communicate general state information to the configuration service provider, and often to access or create nodes.
-
-The following table shows the methods defined by this interface that OEMs must implement.
-
-
-
-
-
-
-
-
-
-
-
-IConfigServiceProvider2::ConfigManagerNotification |
-Enables ConfigManager2 to send notifications to a configuration service provider of events such as when the configuration service provider is loaded or unloaded, when rollbacks are performed, and when actions are called on nodes. |
-
-
-IConfigServiceProvider2::GetNode |
-Returns a node from the configuration service provider based on the path relative to the root node. |
-
-
-
-
-
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md b/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md
deleted file mode 100644
index 67ed91ca36..0000000000
--- a/windows/client-management/mdm/iconfigserviceprovider2configmanagernotification.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: IConfigServiceProvider2 ConfigManagerNotification
-description: IConfigServiceProvider2 ConfigManagerNotification
-ms.assetid: b1f0fe0f-afbe-4b36-a75d-34239a86a75c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# IConfigServiceProvider2::ConfigManagerNotification
-
-
-This method enables ConfigManager2 to send notifications of events to a configuration service provider, such as when the configuration service provider is loaded or unloaded, when rollbacks are performed, and when actions are called on nodes.
-
-## Syntax
-
-
-``` syntax
-HRESULT ConfigManagerNotification([in] CFGMGR_NOTIFICATION cmnfyState,
- [in] LPARAM lpParam);
-```
-
-## Parameters
-
-
-*cmnfyState*
-
--
-The following events are supported by all configuration service providers.
-
-
-
-
-
-
-
-
-
-
-
-CFGMGR_NOTIFICATION_LOAD |
-First time the configuration service provider is loaded/instantiated. |
-
-
-CFGMGR_NOTIFICATION_BEGINCOMMANDPROCESSING |
-About to run the first command of a transaction. |
-
-
-CFGMGR_NOTIFICATION_ENDCOMMANDPROCESSING |
-Last command of transaction has executed. This event is always raised if BEGINCOMMANDPROCESSING was raised, even if the handling of BEGINCOMMANDPROCESSING failed. |
-
-
-CFGMGR_NOTIFICATION_BEGINCOMMIT |
-About to commit the first command of a transaction. |
-
-
-CFGMGR_NOTIFICATION_ENDCOMMIT |
-Last command of a transaction has been committed. This event is always raised if BEGINCOMMIT was raised, even if the handling of BEGINCOMMIT failed. |
-
-
-CFGMGR_NOTIFICATION_BEGINROLLBACK |
-About to roll back the first command of the transaction. |
-
-
-CFGMGR_NOTIFICATION_ENDROLLBACK |
-Last command of the transaction has been rolled back. This event is always raised if BEGINROLLBACK was raised, even if the handling of BEGINROLLBACK failed. |
-
-
-CFGMGR_NOTIFICATION_UNLOAD |
-The configuration service provider is about to be unloaded/deleted. |
-
-
-CFGMGR_NOTIFICATION_SETSESSIONOBJ |
-Session object is available for use; lpParam can be cast to an IConfigSession2 pointer. |
-
-
-CFGMGR_NOTIFICATION_BEGINTRANSACTIONING |
-Primarily used for compatibility with v1 configuration service providers. Signals the beginning of a transactioning sequence. |
-
-
-CFGMGR_NOTIFICATION_ENDTRANSACTIONING |
-Primarily used for compatibility with v1 configuration service providers. Signals the end of a transactioning sequence. |
-
-
-
-
-
-
-
-
-*lpParam*
-
--
-Normally NULL, but contains a pointer to an IConfigSession2 instance if cmnfState is CFGMGR_NOTIFICATION_SETSESSIONOBJ.
-
-
-
-
-## Return Value
-
-A value of S\_OK indicates success.
-
-## Remarks
-
-ConfigManager2 guarantees that if it raised one of the BEGIN events
-
-- CFGMGR\_NOTIFICATION\_BEGINCOMMANDPROCESSING
-- CFGMGR\_NOTIFICATION\_BEGINCOMMIT
-- CFGMGR\_NOTIFICATION\_BEGINROLLBACK
-
-then the corresponding END event will be raised, even if the handling of the BEGIN notification failed.
-For each transaction, the sequence of notifications is:
-
-1. BEGINCOMMANDPROCESSING
-
-2. BEGINTRANSACTIONING
-
-3. ENDTRANSACTIONING
-
-4. ENDCOMMANDPROCESSING
-
-5. Either BEGINCOMMIT or BEGINROLLBACK, depending on whether the transaction succeeded or failed.
-
-6. Either ENDCOMMIT or ENDROLLBACK, depending on whether the transaction succeeded or failed.
-
-Each configuration service provider will receive the relevant BEGIN/END notifications exactly once per each transaction that ConfigManager2 executes.
-
-## Requirements
-
-**Header:** None
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/iconfigserviceprovider2getnode.md b/windows/client-management/mdm/iconfigserviceprovider2getnode.md
deleted file mode 100644
index b1ed4618c7..0000000000
--- a/windows/client-management/mdm/iconfigserviceprovider2getnode.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: IConfigServiceProvider2 GetNode
-description: IConfigServiceProvider2 GetNode
-ms.assetid: 4dc10a59-f6a2-45c0-927c-d594afc9bb91
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# IConfigServiceProvider2::GetNode
-
-
-This method returns a node from the configuration service provider based on the path that was passed in. The returned node is a descendent of the root node.
-
-## Syntax
-
-
-``` syntax
-HRESULT GetNode([in] IConfigManager2URI* pURI,
- [out] ICSPNode** ppNode,
- [in, out] DWORD* pgrfNodeOptions);
-```
-
-## Parameters
-
-*pUri*
-
--
-URI of the child node, relative to the root node. For example, to access the "./Vendor/Contoso/SampleCSP/ContainerA/UserName" node, ConfigManager2 calls the configuration service provider's
GetNode method and passes in an IConfigManager2URI instance representing the URI “SampleCSP/ContainerA/UserName”.
-
-
-
-ppNode
-
--
-If the query is successful, this returns the ICSPNode instance at the pUri location in the configuration service provider's tree.
-
-
-
-pgrfNodeOptions
-
--
-Nodes support the following features.
-
-
-
-
-
-
-
-
-
-
-
-
-CSPNODE_OPTION_NATIVESECURITY
|
-0x01 |
-The native security option signifies that the node handles its own security checking, and that ConfigManager2 does not have to manage security for this node. |
-
-
-CSPNODE_OPTION_INTERNALTRANSACTION
|
-0x02 |
-The internal transactioning option tells ConfigManager2 that the configuration service provider handles the transactioning (rollback and commitment) for the node. To handle internal transactioning, the node must implement the ICSPNodeTransactioning. |
-
-
-CSPNODE_OPTION_HANDLEALLPROPERTIES
|
-0x04 |
-Unused. |
-
-
-CSPNODE_OPTION_SECRETDATA
|
-0x08 |
-Unused. |
-
-
-
-
-
-
-
-## Return Value
-
-This method returns an ICSPNode. If the function returns null, call GetLastError to get the error value.
-
-A value of S\_OK indicates that a node was successfully found. CFGMGR\_E\_NODENOTFOUND indicates that the node does not exist. Note that this may be normal, as in the case of optional nodes.
-
-## Requirements
-
-**Header:** None
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnode.md b/windows/client-management/mdm/icspnode.md
deleted file mode 100644
index bb66997ee8..0000000000
--- a/windows/client-management/mdm/icspnode.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: ICSPNode
-description: ICSPNode
-ms.assetid: 023466e6-a8ab-48ad-8548-291409686ac2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode
-
-This interface does most of the work in a configuration service provider. Each individual node in a configuration service provider tree is represented by a separate implementation of this interface. The actions of a ConfigManager2 client are typically translated into calls to an instance of an ICSPNode.
-
-These methods must be implemented so that, if they fail, the node's state at the end of the method matches the state before the method was called.
-
-Some nodes will not be able to perform certain actions, and can return CFGMGR\_E\_COMMANDNOTALLOWED for those methods. For each method that is implemented for externally–transactioned nodes, the contrary method must also be implemented, as defined by "Determine node operations" in [Designing a custom configuration service provider](design-a-custom-windows-csp.md).
-
-The following table shows the methods defined by this interface that OEMs must implement.
-
-
-
-
-
-
-
-
-
-
-
-ICSPNode::Add |
-Adds an immediate child to a configuration service provider node and returns a pointer to the new child node. |
-
-
-ICSPNode::Clear |
-Deletes the contents and children of the current configuration service provider node. Called before ICSPNode::DeleteChild. |
-
-
-ICSPNode::Copy |
-Makes a copy of the current node at the specified path within the configuration service provider. If the target node exists, it should be overwritten. |
-
-
-ICSPNode::DeleteChild |
-Deletes the specified child node from the configuration service provider node. |
-
-
-ICSPNode::DeleteProperty |
-Deletes a property from a configuration service provider node. |
-
-
-ICSPNode::Execute |
-Runs a task on an internally-transactioned configuration service provider node by passing in the specified user data and returning a result. |
-
-
-ICSPNode::GetChildNodeNames |
-Returns the list of children for a configuration service provider node. |
-
-
-ICSPNode::GetProperty |
-Returns a property value from a configuration service provider node. |
-
-
-ICSPNode::GetPropertyIdentifiers |
-Returns a list of non-standard properties supported by the node. The returned array must be allocated with CoTaskMemAlloc. |
-
-
-ICSPNode::GetValue |
-Gets the value and data type for the node. Interior (non-leaf) nodes may not have a value. |
-
-
-ICSPNode::Move |
-Moves this node to a new location within the configuration service provider. If the target node already exists, it should be overwritten. |
-
-
-ICSPNode::SetProperty |
-Sets a property value for a configuration service provider node. |
-
-
-ICSPNode::SetValue |
-Sets the value for the configuration service provider node. It is an error to attempt to set the value of an interior node. |
-
-
-
-
-
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodeadd.md b/windows/client-management/mdm/icspnodeadd.md
deleted file mode 100644
index 81f5b2cce5..0000000000
--- a/windows/client-management/mdm/icspnodeadd.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: ICSPNode Add
-description: ICSPNode Add
-ms.assetid: 5f03d350-c82b-4747-975f-385fd8b5b3a8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::Add
-
-This method adds an immediate child node to a configuration service provider node and returns a pointer to the new node.
-
-## Syntax
-
-``` syntax
-HRESULT Add([in] IConfigManager2URI* pChildName,
- [in] CFG_DATATYPE DataType,
- [in] VARIANT varValue,
- [in, out] ICSPNode** ppNewNode,
- [in, out] DWORD* pgrfNodeOptions);
-```
-
-## Parameters
-
-*pChildName*
- Name of child node to add.
-
-*DataType*
- Data type of the child node to add. Supported types include:
-- CFG\_DATATYPE\_NODE
-
-- CFG\_DATATYPE\_NULL
-
-- CFG\_DATATYPE\_BINARY
-
-- CFG\_DATATYPE\_INTEGER
-
-- CFG\_DATATYPE\_STRING
-
-- CFG\_DATATYPE\_MULTIPLE\_STRING
-
-*varValue*
- Value of the child node to add.
-
-*ppNewNode*
- New child node to return.
-
-*pgrfNodeOptions*
- Features supported on the new child node.
-
-
-
-
-
-
-
-
-
-
-
-CSPNODE_OPTION_NATIVESECURITY
|
-0x01 |
-The native security option signifies that the node handles its own security checking, and that ConfigManager2 does not have to manage security for this node. |
-
-
-CSPNODE_OPTION_INTERNALTRANSACTION
|
-0x02 |
-The internal transactioning option tells ConfigManager2 that the configuration service provider handles the transactioning (rollback and commitment) for the node. To handle internal transactioning, the node must implement the ICSPNodeTransactioning. |
-
-
-CSPNODE_OPTION_HANDLEALLPROPERTIES
|
-0x04 |
-Unused. |
-
-
-CSPNODE_OPTION_SECRETDATA
|
-0x08 |
-Unused. |
-
-
-
-
-
-## Return Value
-
-This method returns an ICSPNode and the feature options supported on that child node. If the method returns null, call GetLastError to get the error value.
-
-A value of S\_OK indicates that a node was successfully found. CMN\_E\_ALREADY\_EXISTS indicates that a child node with the same name already exists. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **Add** method.
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::Clear](icspnodeclear.md) and [ICSPNode::DeleteChild](icspnodedeletechild.md) must also be implemented or rollback will fail.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodeclear.md b/windows/client-management/mdm/icspnodeclear.md
deleted file mode 100644
index 89db169b0f..0000000000
--- a/windows/client-management/mdm/icspnodeclear.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: ICSPNode Clear
-description: ICSPNode Clear
-ms.assetid: b414498b-110a-472d-95c0-2d5b38cd78a6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-
-# ICSPNode::Clear
-
-This method deletes the contents and child nodes of the current configuration service provider node. This method is always called on the child node before [ICSPNode::DeleteChild](icspnodedeletechild.md) is called on the parent node.
-
-
-## Syntax
-
-``` syntax
-HRESULT Clear();
-```
-
-
-## Return Value
-
-A value of S\_OK indicates that the node was successfully cleared. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **Clear** method.
-
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::SetValue](icspnodesetvalue.md) and [ICSPNode::SetProperty](icspnodesetproperty.md) must also be implemented or rollback will fail.
-
-Before calling **Clear** on the target node, ConfigManager2 attempts to gather the current state of the node; the parent node does not have to preserve the state of its child nodes if they are externally-transactioned.
-
-## Requirements
-
-**Header:** None
-
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodecopy.md b/windows/client-management/mdm/icspnodecopy.md
deleted file mode 100644
index 1771aad0fa..0000000000
--- a/windows/client-management/mdm/icspnodecopy.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: ICSPNode Copy
-description: ICSPNode Copy
-ms.assetid: cd5ce0bc-a08b-4f82-802d-c7ff8701b41f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::Copy
-
-This method makes a copy of the current node at the specified path within the configuration service provider. If the target node exists, it should be overwritten.
-
-## Syntax
-
-``` syntax
-HRESULT Copy([in] IConfigManager2URI* puriDestination,
- [in, out] ICSPNode** ppNewNode,
- [in, out] DWORD* pgrfNodeOptions);
-```
-
-## Parameters
-
-*puriDestination*
- Path and name of new node's location, relative to the configuration service provider's root node.
-
-*ppNewNode*
- New node created by the copy operation.
-
-*pgrfNodeOptions*
- Features supported on the new node.
-
-
-
-
-
-
-
-
-
-
-
-
-CSPNODE_OPTION_NATIVESECURITY
|
-0x01 |
-The native security option signifies that the node handles its own security checking, and that ConfigManager2 does not have to manage security for this node. |
-
-
-CSPNODE_OPTION_INTERNALTRANSACTION
|
-0x02 |
-The internal transactioning option tells ConfigManager2 that the configuration service provider handles the transactioning (rollback and commitment) for the node. To handle internal transactioning, the node must implement the ICSPNodeTransactioning. |
-
-
-CSPNODE_OPTION_HANDLEALLPROPERTIES
|
-0x04 |
-Unused. |
-
-
-CSPNODE_OPTION_SECRETDATA
|
-0x08 |
-Unused. |
-
-
-
-
-
-## Return Value
-
-A value of S\_OK indicates that the node was successfully copied to the new location. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **Copy** method.
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::Add](icspnodeadd.md), [ICSPNode::SetValue](icspnodesetvalue.md), [ICSPNode::Clear](icspnodeclear.md), and [ICSPNode::DeleteChild](icspnodedeletechild.md) must also be implemented or rollback will fail.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodedeletechild.md b/windows/client-management/mdm/icspnodedeletechild.md
deleted file mode 100644
index e08d2b025d..0000000000
--- a/windows/client-management/mdm/icspnodedeletechild.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: ICSPNode DeleteChild
-description: ICSPNode DeleteChild
-ms.assetid: 8cf3663d-a4cf-4d11-b03a-f1d096ad7f9c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::DeleteChild
-
-Deletes the specified child node from the configuration service provider node. [ICSPNode::Clear](icspnodeclear.md) must always be called first on the child node that is to be deleted.
-
-## Syntax
-
-``` syntax
-HRESULT DeleteChild([in] IConfigManager2URI* puriChildToDelete);
-```
-
-## Parameters
-
-*puriChildToDelete*
- The name of the child node to delete.
-
-## Return Values
-
-| Return Value | Description |
-|------------------------------|--------------------------------------------------|
-| CFGMGR\_E\_NODENOTFOUND | The child node does not exist |
-| CFGMGR\_E\_COMMANDNOTALLOWED | The child node to be deleted is a read-only node |
-| S\_OK | Success. |
-
-
-A value of S\_OK indicates that a node was successfully deleted. CFGMGR\_E\_NODENOTFOUND indicates that the child node does not exist. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **ICSP::DeleteChild** method, or that the child node to be deleted is a read-only node.
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::Add](icspnodeadd.md) must also be implemented or rollback will fail.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodedeleteproperty.md b/windows/client-management/mdm/icspnodedeleteproperty.md
deleted file mode 100644
index 6bcd73cc62..0000000000
--- a/windows/client-management/mdm/icspnodedeleteproperty.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: ICSPNode DeleteProperty
-description: ICSPNode DeleteProperty
-ms.assetid: 7e21851f-d663-4558-b3e8-590d24b4f6c4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::DeleteProperty
-
-This method deletes a property from a configuration service provider node.
-
-## Syntax
-
-``` syntax
-HRESULT DeleteProperty([in] REFGUID guidProperty);
-```
-
-## Parameters
-
-*guidProperty*
- The GUID of the property to delete.
-
-## Return Value
-
-A value of S\_OK indicates that a node was successfully found. CFGMGR\_E\_PROPERTYNOTSUPPORTED indicates that this node does not manage or implement the property itself, but delegates it to ConfigManager2. E\_NOTIMPL indicates this method is not supported by this node.
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::SetProperty](icspnodesetproperty.md) must also be implemented or rollback will fail.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodeexecute.md b/windows/client-management/mdm/icspnodeexecute.md
deleted file mode 100644
index b5008f4972..0000000000
--- a/windows/client-management/mdm/icspnodeexecute.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: ICSPNode Execute
-description: ICSPNode Execute
-ms.assetid: 5916e7b7-256d-49fd-82b6-db0547a215ec
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-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
-
-*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)
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodegetchildnodenames.md b/windows/client-management/mdm/icspnodegetchildnodenames.md
deleted file mode 100644
index 176e294eb1..0000000000
--- a/windows/client-management/mdm/icspnodegetchildnodenames.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: ICSPNode GetChildNodeNames
-description: ICSPNode GetChildNodeNames
-ms.assetid: dc057f2b-282b-49ac-91c4-bb83bd3ca4dc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::GetChildNodeNames
-
-This method returns the list of child nodes for a configuration service provider node.
-
-## Syntax
-
-``` syntax
-HRESULT GetChildNodeNames([out] ULONG* pulCount,
- [out,size_is(,*pulCount)] BSTR** pbstrNodeNames);
-```
-
-## Parameters
-
-*pulCount*
-The number of child nodes to return.
-
-*pbstrNodeNames*
-The array of child node names. The returned array must be allocated with CoTaskMemAlloc. Each element of the array must be a valid, non-NULL BSTR, allocated by SysAllocString or SysAllocStringLen. The names returned must not be encoded in any way, including URI-encoding, for canonicalization reasons.
-
-## Return Value
-
-A value of S\_OK indicates that a node was successfully found. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this was called on a leaf node (no children will be returned).
-
-## Remarks
-
-For externally–transactioned nodes, no additional methods are required for successful rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodegetproperty.md b/windows/client-management/mdm/icspnodegetproperty.md
deleted file mode 100644
index e617650c97..0000000000
--- a/windows/client-management/mdm/icspnodegetproperty.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: ICSPNode GetProperty
-description: ICSPNode GetProperty
-ms.assetid: a2bdc158-72e0-4cdb-97ce-f5cf1a44b7db
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::GetProperty
-
-This method returns a property value from a configuration service provider node.
-
-## Syntax
-
-``` syntax
-HRESULT GetProperty([in] REFGUID guidProperty,
- [in,out] VARIANT* pvarValue);
-```
-
-## Parameters
-
-*guidProperty*
-GUID that specifies the property to return.
-
-*pvarValue*
-Value to return.
-
-## Return Value
-
-A value of S\_OK indicates that the value was successfully returned. CFGMGR\_E\_COMMANDNOTSUPPORTED indicates that the node does not implement the property itself, but delegates the management of the property to ConfigManager2.
-
-## Remarks
-
-Every node must handle the CFGMGR\_PROPERTY\_DATATYPE property.
-
-For externally–transactioned nodes, no additional methods are required for successful rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodegetpropertyidentifiers.md b/windows/client-management/mdm/icspnodegetpropertyidentifiers.md
deleted file mode 100644
index 479913e683..0000000000
--- a/windows/client-management/mdm/icspnodegetpropertyidentifiers.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: ICSPNode GetPropertyIdentifiers
-description: ICSPNode GetPropertyIdentifiers
-ms.assetid: 8a052cd3-d74c-40c4-845f-f804b920deb4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::GetPropertyIdentifiers
-
-This method returns a list of non-standard properties supported by the node. The returned array must be allocated with `CoTaskMemAlloc`.
-
-## Syntax
-
-``` syntax
-HRESULT GetPropertyIdentifiers([out] ULONG* pulCount,
- [out,size_is(,*pulCount)] GUID** pguidProperties);
-```
-
-## Parameters
-
-*pulCount*
-The number of non-standard properties to return.
-
-*pguidProperties*
-The array of property GUIDs to return. This array must be allocated with CoTaskMemAlloc.
-
-## Return Value
-
-A value of S\_OK indicates that the properties were successfully returned. E\_NOTIMPL indicates that this method is not supported by the node.
-
-## Remarks
-
-For externally–transactioned nodes, no additional methods are required for successful rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodegetvalue.md b/windows/client-management/mdm/icspnodegetvalue.md
deleted file mode 100644
index 0e8d591f35..0000000000
--- a/windows/client-management/mdm/icspnodegetvalue.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: ICSPNode GetValue
-description: ICSPNode GetValue
-ms.assetid: c684036d-98be-4659-8ce8-f72436a39b90
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::GetValue
-
-This method gets the value and data type for the node. Interior (non-leaf) nodes may not have a value.
-
-## Syntax
-
-``` syntax
-HRESULT GetValue([in,out] VARIANT* pvarValue);
-```
-
-## Parameters
-
-*pvarValue*
-Data value to return. A node containing a password value returns 16 asterisks (‘*’) for this method. A leaf node whose value has not been set returns a variant whose type is VT_NULL.
-
-
-## Return Value
-
-A value of S\_OK indicates that a node was successfully found. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **ICSP::GetValue** methods, or that this is an interior node.
-
-## Remarks
-
-For externally–transactioned nodes, this node is not required to implement any other methods for a successful rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodemove.md b/windows/client-management/mdm/icspnodemove.md
deleted file mode 100644
index 40d917ca2f..0000000000
--- a/windows/client-management/mdm/icspnodemove.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: ICSPNode Move
-description: ICSPNode Move
-ms.assetid: efb359c3-5c86-4975-bf6f-a1c33922442a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::Move
-
-This method moves the node to a new location within the configuration service provider. If the target node already exists, it should be overwritten.
-
-## Syntax
-
-``` syntax
-HRESULT Move([in] IConfigManager2URI* puriDestination);
-```
-
-## Parameters
-
-*puriDestination*
-Path and name of the node's new location, relative to the configuration service provider's root node.
-
-## Return Value
-
-A value of S\_OK indicates that the node was successfully moved. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **ICSP::Move** method.
-
-## Remarks
-
-For externally–transactioned nodes, if this method is implemented, then [ICSPNode::Add](icspnodeadd.md) and [ICSPNode::SetValue](icspnodesetvalue.md) must also be implemented or rollback will fail.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodesetproperty.md b/windows/client-management/mdm/icspnodesetproperty.md
deleted file mode 100644
index 8052bf2d5d..0000000000
--- a/windows/client-management/mdm/icspnodesetproperty.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: ICSPNode SetProperty
-description: ICSPNode SetProperty
-ms.assetid: e235c38f-ea04-4cd8-adec-3c6c0ce7172d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::SetProperty
-
-This method sets a property value for a configuration service provider node.
-
-## Syntax
-
-``` syntax
-HRESULT SetProperty([in] REFGUID guidProperty,
- [in] VARIANT varValue);
-```
-
-## Parameters
-
-*guidProperty*
-The GUID of the property.
-
-*varValue*
-The value to return.
-
-## Return Value
-
-A value of S\_OK indicates that a node was successfully found. CFGMGR\_E\_COMMANDNOTSUPPORTED indicates that this node delegates the management of the property to ConfigManager2.
-
-## Remarks
-
-Every node must properly handle the CFGMGR\_PROPERTY\_DATATYPE property.
-
-For externally–transactioned nodes, no additional methods are required for successful rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodesetvalue.md b/windows/client-management/mdm/icspnodesetvalue.md
deleted file mode 100644
index afcbc3b99d..0000000000
--- a/windows/client-management/mdm/icspnodesetvalue.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: ICSPNode SetValue
-description: ICSPNode SetValue
-ms.assetid: b218636d-fe8b-4a0f-b4e8-a621f65619d3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNode::SetValue
-
-This method sets the value for the configuration service provider node. It is an error to attempt to set the value of an interior node.
-
-## Syntax
-
-``` syntax
-HRESULT SetValue([in] VARIANT varValue);
-```
-
-## Parameters
-
-*varValue*
-Value to set. To clear a leaf node’s value, set varValue’s type to VT_NULL.
-
-## Return Value
-
-A value of S\_OK indicates that the value was set successfully. CFGMGR\_E\_COMMANDNOTALLOWED indicates that this node does not support the **ICSP::SetValue** method, or that it's an internal node.
-
-## Remarks
-
-For externally–transactioned nodes, no additional methods must be implemented to support rollback.
-
-## Requirements
-
-**Header:** None
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspnodetransactioning.md b/windows/client-management/mdm/icspnodetransactioning.md
deleted file mode 100644
index 93b4a35b7b..0000000000
--- a/windows/client-management/mdm/icspnodetransactioning.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: ICSPNodeTransactioning
-description: ICSPNodeTransactioning
-ms.assetid: 24dc518a-4a8d-41fe-9bc6-217bbbdf6a3f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPNodeTransactioning
-
-This is an optional interface that enables a configuration service provider to define its own transactioning scheme (internal transactioning) for an individual node. Transactioning supports the ability to roll back previous actions on a node. The majority of nodes use external transactioning, which is handled automatically, and do not need to implement this interface. For more information about internal and external transactioning, including how to handle the `RollbackAction` functions, see "Determine node operations" in [Designing a custom configuration service provider](design-a-custom-windows-csp.md).
-
-``` syntax
-interface ICSPNodeTransactioning : IUnknown
-{
- HRESULT PersistRollbackAddState([in] IConfigManager2URI* puriChild,
- [in] CFG_DATATYPE DataType,
- [in] VARIANT varValue,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackCopyState([in] IConfigManager2URI* puriDestination,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackDeleteChildState([in] IConfigManager2URI* puriChild,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackClearState([in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackExecuteState([in] VARIANT varUserData,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackMoveState([in] IConfigManager2URI* puriDestination,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackSetValueState([in] VARIANT varValue,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackSetPropertyState([in] REFGUID guidProperty,
- [in] VARIANT varValue,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT PersistRollbackDeletePropertyState([in] REFGUID guidProperty,
- [in] ISequentialStream* pRollbackStream,
- [in] ISequentialStream* pUninstallStream);
- HRESULT RollbackAdd([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackCopy([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackDeleteChild([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackClear([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackExecute([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackMove([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackSetValue([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackSetProperty([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
- HRESULT RollbackDeleteProperty([in] ISequentialStream* pUndoStream,
- [in] BOOL fRecoveryRollback);
-
- HRESULT Commit();
-};
-```
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/icspvalidate.md b/windows/client-management/mdm/icspvalidate.md
deleted file mode 100644
index 3d59448e68..0000000000
--- a/windows/client-management/mdm/icspvalidate.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: ICSPValidate
-description: ICSPValidate
-ms.assetid: b0993f2d-6269-412f-a329-af25fff34ca2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# ICSPValidate
-
-This interface is optional. It is called by ConfigManager2 as it batches commands before transactioning begins. This allows the configuration service provider to validate the node before performing specific actions. It is generally only used for configuration service providers that need to expose UI.
-
-``` syntax
-interface ICSPValidate : IUnknown
-{
- HRESULT ValidateAdd([in] IConfigNodeState* pNodeState,
- [in] IConfigManager2URI* puriChild,
- [in] CFG_DATATYPE DataType,
- [in] VARIANT varValue);
- HRESULT ValidateCopy([in] IConfigNodeState* pNodeState,
- [in] IConfigManager2URI* puriDestination);
- HRESULT ValidateDeleteChild([in] IConfigNodeState* pNodeState,
- [in] IConfigManager2URI* puriChild);
- HRESULT ValidateClear([in] IConfigNodeState* pNodeState);
- HRESULT ValidateExecute([in] IConfigNodeState* pNodeState,
- [in] VARIANT varUserData);
- HRESULT ValidateMove([in] IConfigNodeState* pNodeState,
- [in] IConfigManager2URI* puriDestination);
- HRESULT ValidateSetValue([in] IConfigNodeState* pNodeState,
- [in] VARIANT varValue);
- HRESULT ValidateSetProperty([in] IConfigNodeState* pNodeState,
- [in] REFGUID guidProperty,
- [in] VARIANT varValue);
- HRESULT ValidateDeleteProperty([in] IConfigNodeState* pNodeState,
- [in] REFGUID guidProperty);
-```
-
-## Related topics
-
-[Create a custom configuration service provider](create-a-custom-configuration-service-provider.md)
-
-
-
-
-
-
-
-
diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
index f224b4242c..3ca4486f3b 100644
--- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
+++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
@@ -12,7 +12,7 @@ ms.topic: article
ms.prod: w10
ms.technology: windows
author: manikadhiman
-ms.date: 05/15/2019
+ms.date: 07/01/2019
---
# What's new in mobile device enrollment and management
@@ -56,6 +56,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
- [What is dmwappushsvc?](#what-is-dmwappushsvc)
- **Change history in MDM documentation**
+ - [July 2019](#july-2019)
- [June 2019](#june-2019)
- [May 2019](#may-2019)
- [April 2019](#april-2019)
@@ -1880,6 +1881,13 @@ How do I turn if off? | The service can be stopped from the "Services" console o
## Change history in MDM documentation
+### July 2019
+
+|New or updated topic | Description|
+|--- | ---|
+|Create a custom configuration service provider|Deleted the following documents from the CSP reference because extensibility via CSPs is not currently supported:
Create a custom configuration service provider
Design a custom configuration service provider
IConfigServiceProvider2
IConfigServiceProvider2::ConfigManagerNotification
IConfigServiceProvider2::GetNode
ICSPNode
ICSPNode::Add
ICSPNode::Clear
ICSPNode::Copy
ICSPNode::DeleteChild
ICSPNode::DeleteProperty
ICSPNode::Execute
ICSPNode::GetChildNodeNames
ICSPNode::GetProperty
ICSPNode::GetPropertyIdentifiers
ICSPNode::GetValue
ICSPNode::Move
ICSPNode::SetProperty
ICSPNode::SetValue
ICSPNodeTransactioning
ICSPValidate
Samples for writing a custom configuration service provider|
+
+
### June 2019
|New or updated topic | Description|
diff --git a/windows/client-management/mdm/samples-for-writing-a-custom-configuration-service-provider.md b/windows/client-management/mdm/samples-for-writing-a-custom-configuration-service-provider.md
deleted file mode 100644
index 0ee7ef78f1..0000000000
--- a/windows/client-management/mdm/samples-for-writing-a-custom-configuration-service-provider.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Samples for writing a custom configuration service provider
-description: Samples for writing a custom configuration service provider
-ms.assetid: ccda4d62-7ce1-483b-912f-25d50c974270
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.prod: w10
-ms.technology: windows
-author: manikadhiman
-ms.date: 06/26/2017
----
-
-# Samples for writing a custom configuration service provider
-
-The following example shows how to retrieve Integrated Circuit Card Identifier (ICCID) and International Mobile Subscriber Identity (IMSI) for a dual SIM phone.
-
-## Retrieving ICCID and IMSI for a dual SIM phone
-
-The following sample is used in the [IConfigServiceProvider2::ConfigManagerNotification](iconfigserviceprovider2configmanagernotification.md) method implementation. It first retrieves the IConfigSession2 object, and then queries the ICCID with the IConfigSession2::GetSessionVariable method. To retrieve the IMSI, replace L”ICCID” with L”IMSI”.
-
-``` syntax
-case CFGMGR_NOTIFICATION_SETSESSIONOBJ:
- if (NULL != lpParam)
- {
- m_pSession = reinterpret_cast(lpParam);
- m_pSession->AddRef();
- }
-
- bstrContext = SysAllocString(L"ICCID");
- if (NULL == bstrContext)
- {
- hr = E_OUTOFMEMORY;
- goto Error;
- }
-
- hr = m_pSession->GetSessionVariable(bstrContext, &varValue);
- if (FAILED(hr))
- {
- goto Error;
- }
- break;
-```
-
-
-
-
-
-
-