mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Updated_10ASCIIimages
This commit is contained in:
nimishasatapathy
parent
1bd6cf7441
commit
8020accca2
@ -25,10 +25,41 @@ The CM\_ProxyEntries configuration service provider is used to configure proxy c
|
||||
|
||||
|
||||
|
||||
The following diagram shows the CM\_ProxyEntries configuration service provider management object in tree format as used by Open Mobile Alliance Client Provisioning (OMA CP) and OMA Device Management(OMA DM). Support for OMA DM was added in Windows 10, version 1607.
|
||||
The following shows the CM\_ProxyEntries configuration service provider management object in tree format as used by Open Mobile Alliance Client Provisioning (OMA CP) and OMA Device Management(OMA DM). Support for OMA DM was added in Windows 10, version 1607.
|
||||
|
||||
|
||||
```
|
||||
./Vendor/MSFT
|
||||
CM_ProxyEntries
|
||||
----Entry
|
||||
--------ConnectionName
|
||||
--------BypassLocal
|
||||
--------Enable
|
||||
--------Exception
|
||||
--------Password
|
||||
--------Port
|
||||
--------Server
|
||||
--------Type
|
||||
--------Username
|
||||
|
||||
|
||||
./Device/Vendor/MSFT
|
||||
Root
|
||||
|
||||
|
||||
./Vendor/MSFT
|
||||
./Device/Vendor/MSFT
|
||||
CM_ProxyEntries
|
||||
----Entry
|
||||
--------ConnectionName
|
||||
--------BypassLocal
|
||||
--------Enable
|
||||
--------Exception
|
||||
--------Password
|
||||
--------Port
|
||||
--------Server
|
||||
--------Type
|
||||
--------Username
|
||||
```
|
||||
<a href="" id="entryname"></a>**entryname**
|
||||
Defines the name of the connection proxy.
|
||||
|
||||
|
||||
@ -28,10 +28,21 @@ Each policy entry identifies one or more applications in combination with a host
|
||||
|
||||
**Default Policies**: Policies are applied in order of their scope with the most specific policies considered before the more general policies. The phone’s default behavior applies to all applications and all domains and is only used when no other, more specific policy is available. The default policy is to use any available Wi-Fi network first and then any available APN.
|
||||
|
||||
The following diagram shows the CMPolicy configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||
|
||||
|
||||
The following shows the CMPolicy configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||
|
||||
```
|
||||
./Vendor/MSFT
|
||||
CMPolicy
|
||||
----PolicyName
|
||||
--------SID
|
||||
--------ClientType
|
||||
--------Host
|
||||
--------OrderedConnections
|
||||
--------Connections
|
||||
------------ConnXXX
|
||||
----------------ConnectionID
|
||||
----------------Type
|
||||
```
|
||||
<a href="" id="policyname"></a>***policyName***
|
||||
Defines the name of the policy.
|
||||
|
||||
|
||||
@ -28,10 +28,20 @@ Each policy entry identifies one or more applications in combination with a host
|
||||
|
||||
**Default Policies**: Policies are applied in order of their scope with the most specific policies considered before the more general policies. The phone’s default behavior applies to all applications and all domains and is only used when no other, more specific policy is available. The default policy is to use any available Wi-Fi network first and then any available APN.
|
||||
|
||||
The following diagram shows the CMPolicyEnterprise configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||
|
||||
|
||||
|
||||
The following shows the CMPolicyEnterprise configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||
```
|
||||
./Vendor/MSFT
|
||||
CMPolicy
|
||||
----PolicyName
|
||||
--------SID
|
||||
--------ClientType
|
||||
--------Host
|
||||
--------OrderedConnections
|
||||
--------Connections
|
||||
------------ConnXXX
|
||||
----------------ConnectionID
|
||||
----------------Type
|
||||
```
|
||||
<a href="" id="policyname"></a>***policyName***
|
||||
Defines the name of the policy.
|
||||
|
||||
|
||||
@ -15,12 +15,16 @@ ms.date: 06/26/2017
|
||||
# CustomDeviceUI CSP
|
||||
|
||||
The CustomDeviceUI configuration service provider allows OEMs to implement their custom foreground application, as well as the background tasks to run on an IoT device running IoT Core. Only one foreground application is supported per device. Multiple background tasks are supported.
|
||||
The following diagram shows the CustomDeviceUI configuration service provider in tree format as used by both the Open Mobile Alliance (OMA) Device Management (DM) and OMA Client Provisioning.
|
||||
The following shows the CustomDeviceUI configuration service provider in tree format as used by both the Open Mobile Alliance (OMA) Device Management (DM) and OMA Client Provisioning.
|
||||
|
||||
> **Note** This configuration service provider only applies to Windows 10 IoT Core (IoT Core).
|
||||
|
||||
|
||||
|
||||
```
|
||||
./Vendor/MSFT
|
||||
CustomDeviceUI
|
||||
----StartupAppID
|
||||
----BackgroundTasksToLaunch
|
||||
--------BackgroundTaskPackageName
|
||||
```
|
||||
<a href="" id="./Vendor/MSFT/CustomDeviceUI"></a>**./Vendor/MSFT/CustomDeviceUI**
|
||||
The root node for the CustomDeviceUI configuration service provider. The supported operation is Get.
|
||||
|
||||
|
||||
@ -20,10 +20,41 @@ ms.date: 08/11/2020
|
||||
|
||||
The Windows Defender configuration service provider is used to configure various Windows Defender actions across the enterprise.
|
||||
|
||||
The following image shows the Windows Defender configuration service provider in tree format.
|
||||
|
||||
|
||||
|
||||
The following shows the Windows Defender configuration service provider in tree format.
|
||||
```
|
||||
./Vendor/MSFT
|
||||
Defender
|
||||
----Detections
|
||||
--------ThreatId
|
||||
------------Name
|
||||
------------URL
|
||||
------------Severity
|
||||
------------Category
|
||||
------------CurrentStatus
|
||||
------------ExecutionStatus
|
||||
------------InitialDetectionTime
|
||||
------------LastThreatStatusChangeTime
|
||||
------------NumberOfDetections
|
||||
----Health
|
||||
--------ComputerState
|
||||
--------DefenderEnabled
|
||||
--------RtpEnabled
|
||||
--------NisEnabled
|
||||
--------QuickScanOverdue
|
||||
--------FullScanOverdue
|
||||
--------SignatureOutOfDate
|
||||
--------RebootRequired
|
||||
--------FullScanRequired
|
||||
--------EngineVersion
|
||||
--------SignatureVersion
|
||||
--------DefenderVersion
|
||||
--------QuickScanTime
|
||||
--------FullScanTime
|
||||
--------QuickScanSigVersion
|
||||
--------FullScanSigVersion
|
||||
----Scan
|
||||
----UpdateSignature
|
||||
```
|
||||
<a href="" id="detections"></a>**Detections**
|
||||
An interior node to group all threats detected by Windows Defender.
|
||||
|
||||
|
||||
@ -21,10 +21,40 @@ The DevDetail configuration service provider handles the management object which
|
||||
|
||||
For the DevDetail CSP, you cannot use the Replace command unless the node already exists.
|
||||
|
||||
The following diagram shows the DevDetail configuration service provider management object in tree format as used by OMA Device Management. The OMA Client Provisioning protocol is not supported for this configuration service provider.
|
||||
|
||||
|
||||
|
||||
The following shows the DevDetail configuration service provider management object in tree format as used by OMA Device Management. The OMA Client Provisioning protocol is not supported for this configuration service provider.
|
||||
```
|
||||
.
|
||||
DevDetail
|
||||
----URI
|
||||
--------MaxDepth
|
||||
--------MaxTotLen
|
||||
--------MaxSegLen
|
||||
----DevTyp
|
||||
----OEM
|
||||
----FwV
|
||||
----SwV
|
||||
----HwV
|
||||
----LrgObj
|
||||
----Ext
|
||||
--------Microsoft
|
||||
------------MobileID
|
||||
------------RadioSwV
|
||||
------------Resolution
|
||||
------------CommercializationOperator
|
||||
------------ProcessorArchitecture
|
||||
------------ProcessorType
|
||||
------------OSPlatform
|
||||
------------LocalTime
|
||||
------------DeviceName
|
||||
------------TotalStorage
|
||||
------------TotalRAM
|
||||
--------WLANMACAddress
|
||||
--------VoLTEServiceSetting
|
||||
--------WlanIPv4Address
|
||||
--------WlanIPv6Address
|
||||
--------WlanDnsSuffix
|
||||
--------WlanSubnetMask
|
||||
```
|
||||
<a href="" id="devtyp"></a>**DevTyp**
|
||||
Required. Returns the device model name /SystemProductName as a string.
|
||||
|
||||
|
||||
@ -19,10 +19,21 @@ The DeveloperSetup configuration service provider (CSP) is used to configure Dev
|
||||
> [!NOTE]
|
||||
> The DeveloperSetup configuration service provider (CSP) is only supported in Windows 10 Holographic Enterprise edition and with runtime provisioning via provisioning packages. It is not supported in MDM.
|
||||
|
||||
The following diagram shows the DeveloperSetup configuration service provider in tree format.
|
||||
|
||||
|
||||
|
||||
The following shows the DeveloperSetup configuration service provider in tree format.
|
||||
```
|
||||
./Device/Vendor/MSFT
|
||||
DeveloperSetup
|
||||
----EnableDeveloperMode
|
||||
----DevicePortal
|
||||
--------Authentication
|
||||
------------Mode
|
||||
------------BasicAuth
|
||||
----------------Username
|
||||
----------------Password
|
||||
--------Connection
|
||||
------------HttpPort
|
||||
------------HttpsPort
|
||||
```
|
||||
<a href="" id="developersetup"></a>**DeveloperSetup**
|
||||
<p style="margin-left: 20px">The root node for the DeveloperSetup configuration service provider.
|
||||
|
||||
|
||||
@ -19,10 +19,17 @@ The DeviceManageability configuration service provider (CSP) is used retrieve th
|
||||
|
||||
For performance reasons DeviceManageability CSP directly reads the CSP version from the registry. Specifically, the value csp\_version is used to determine each of the CSP versions. The csp\_version is a value under each of the CSP registration keys. To have consistency on the CSP version, the CSP GetProperty implementation for CFGMGR\_PROPERTY\_SEMANTICTYPE has to be updated to read from the registry as well, so that the both paths return the same information.
|
||||
|
||||
The following diagram shows the DeviceManageability configuration service provider in a tree format.
|
||||
|
||||
|
||||
|
||||
The following shows the DeviceManageability configuration service provider in a tree format.
|
||||
```
|
||||
./Device/Vendor/MSFT
|
||||
DeviceManageability
|
||||
----Capabilities
|
||||
--------CSPVersions
|
||||
----Provider
|
||||
--------ProviderID
|
||||
------------ConfigInfo
|
||||
------------EnrollmentInfo
|
||||
```
|
||||
<a href="" id="--device-vendor-msft-devicemanageability"></a>**./Device/Vendor/MSFT/DeviceManageability**
|
||||
Root node to group information about runtime MDM configuration capability on the target device.
|
||||
|
||||
|
||||
@ -17,10 +17,52 @@ ms.date: 04/30/2019
|
||||
|
||||
The DeviceStatus configuration service provider is used by the enterprise to keep track of device inventory and query the state of compliance of these devices with their enterprise policies.
|
||||
|
||||
The following image shows the DeviceStatus configuration service provider in tree format.
|
||||
|
||||
|
||||
|
||||
The following shows the DeviceStatus configuration service provider in tree format.
|
||||
```
|
||||
./Vendor/MSFT
|
||||
DeviceStatus
|
||||
----SecureBootState
|
||||
----CellularIdentities
|
||||
--------IMEI
|
||||
------------IMSI
|
||||
------------ICCID
|
||||
------------PhoneNumber
|
||||
------------CommercializationOperator
|
||||
------------RoamingStatus
|
||||
------------RoamingCompliance
|
||||
----NetworkIdentifiers
|
||||
--------MacAddress
|
||||
------------IPAddressV4
|
||||
------------IPAddressV6
|
||||
------------IsConnected
|
||||
------------Type
|
||||
----Compliance
|
||||
--------EncryptionCompliance
|
||||
----TPM
|
||||
--------SpecificationVersion
|
||||
----OS
|
||||
--------Edition
|
||||
--------Mode
|
||||
----Antivirus
|
||||
--------SignatureStatus
|
||||
--------Status
|
||||
----Antispyware
|
||||
--------SignatureStatus
|
||||
--------Status
|
||||
----Firewall
|
||||
--------Status
|
||||
----UAC
|
||||
--------Status
|
||||
----Battery
|
||||
--------Status
|
||||
--------EstimatedChargeRemaining
|
||||
--------EstimatedRuntime
|
||||
----DomainName
|
||||
----DeviceGuard
|
||||
--------VirtualizationBasedSecurityHwReq
|
||||
--------VirtualizationBasedSecurityStatus
|
||||
--------LsaCfgCredGuardStatus
|
||||
```
|
||||
<a href="" id="devicestatus"></a>**DeviceStatus**
|
||||
The root node for the DeviceStatus configuration service provider.
|
||||
|
||||
|
||||
@ -23,10 +23,16 @@ The DevInfo configuration service provider handles the managed object which prov
|
||||
|
||||
For the DevInfo CSP, you cannot use the Replace command unless the node already exists.
|
||||
|
||||
The following diagram shows the DevInfo configuration service provider management object in tree format as used by OMA Device Management. The OMA Client provisioning protocol is not supported by this configuration service provider.
|
||||
|
||||
|
||||
|
||||
The following shows the DevInfo configuration service provider management object in tree format as used by OMA Device Management. The OMA Client provisioning protocol is not supported by this configuration service provider.
|
||||
```
|
||||
.
|
||||
DevInfo
|
||||
----DevId
|
||||
----Man
|
||||
----Mod
|
||||
----DmV
|
||||
----Lang
|
||||
```
|
||||
<a href="" id="devid"></a>**DevId**
|
||||
Required. Returns an application-specific global unique device identifier by default.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user