mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 12:53:38 +00:00
Merge branch 'master' into siosulli-privacy-dpsw
This commit is contained in:
Sinead O'Sullivan
@ -2551,7 +2551,7 @@ The following list shows the CSPs supported in HoloLens devices:
|
||||
[PassportForWork CSP](passportforwork-csp.md) |  |  |  |
|
||||
| [Policy CSP](policy-configuration-service-provider.md) |  |  |  |
|
||||
| [RemoteFind CSP](remotefind-csp.md) |  |  <sup>4</sup> |  |
|
||||
| [RemoteWipe CSP](remotewipe-csp.md) |  |  <sup>4</sup> |  |
|
||||
| [RemoteWipe CSP](remotewipe-csp.md) (**doWipe** and **doWipePersistProvisionedData** nodes only) |  |  <sup>4</sup> |  |
|
||||
| [RootCATrustedCertificates CSP](rootcacertificates-csp.md) |  |  |  |
|
||||
| [TenantLockdown CSP](tenantlockdown-csp.md) |  |  |  <sup>10</sup> |
|
||||
| [Update CSP](update-csp.md) |  |  |  |
|
||||
@ -2635,3 +2635,4 @@ The following list shows the CSPs supported in HoloLens devices:
|
||||
- 8 - Added in Windows 10, version 2004.
|
||||
- 9 - Added in Windows 10 Team 2020 Update.
|
||||
- 10 - Added in [Windows Holographic, version 20H2](/hololens/hololens-release-notes#windows-holographic-version-20h2).
|
||||
|
||||
|
||||
@ -128,7 +128,7 @@ Requirements:
|
||||
> In Windows 10, version 1903, the MDM.admx file was updated to include an option to select which credential is used to enroll the device. **Device Credential** is a new option that will only have an effect on clients that have installed Windows 10, version 1903 or later.
|
||||
>
|
||||
> The default behavior for older releases is to revert to **User Credential**.
|
||||
> **Device Credential** is not supported for enrollment type when you have a ConfigMgr Agent on your device.
|
||||
> **Device Credential** is only supported for Microsoft Intune enrollment in scenarios with Co-management or Azure Virtual Desktop.
|
||||
|
||||
When a group policy refresh occurs on the client, a task is created and scheduled to run every 5 minutes for the duration of one day. The task is called " Schedule created by enrollment client for automatically enrolling in MDM from AAD."
|
||||
|
||||
|
||||
@ -20,6 +20,7 @@ The EnterpriseDesktopAppManagement configuration service provider is used to han
|
||||
Application installations can take some time to complete, hence they are done asynchronously. When the Exec command is completed, the client can send a generic alert to the management server with a status, whether it's a failure or success. For a SyncML example, see [Alert example](#alert-example).
|
||||
|
||||
The following shows the EnterpriseDesktopAppManagement CSP in tree format.
|
||||
|
||||
```
|
||||
./Device/Vendor/MSFT
|
||||
EnterpriseDesktopAppManagement
|
||||
@ -37,6 +38,7 @@ EnterpriseDesktopAppManagement
|
||||
--------UpgradeCode
|
||||
------------Guid
|
||||
```
|
||||
|
||||
<a href="" id="--vendor-msft-enterprisedesktopappmanagement"></a>**./Device/Vendor/MSFT/EnterpriseDesktopAppManagement**
|
||||
The root node for the EnterpriseDesktopAppManagement configuration service provider.
|
||||
|
||||
@ -194,15 +196,15 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
The following table describes the fields in the previous sample:
|
||||
|
||||
| Name | Description |
|
||||
|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Get | Operation being performed. The Get operation is a request to report the status of the specified MSI installed application. |
|
||||
| CmdID | Input value used to reference the request. Responses will include this value which can be used to match request and response. |
|
||||
| Name | Description |
|
||||
|--------|-----------------------|
|
||||
| Get | Operation being performed. The Get operation is a request to report the status of the specified MSI installed application.|
|
||||
| CmdID | Input value used to reference the request. Responses will include this value which can be used to match request and response. |
|
||||
| LocURI | Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting. |
|
||||
|
||||
|
||||
|
||||
**SyncML to perform MSI install operations for an application targeted to a specific user on the device. The Add command is required to preceed the Exec command.**
|
||||
**SyncML to perform MSI install operations for an application targeted to a specific user on the device. The Add command is required to precede the Exec command.**
|
||||
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
@ -292,7 +294,8 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
|
||||
|
||||
> **Note** Information status on the MSI job will be reported using standard OMA-DM notification mechanism. The status reported is represented using standard MSIEXEC return codes as HRESULT as defined in the MSIEXEC topic on Microsoft TechNet at <https://technet.microsoft.com/library/cc759262(v=ws.10).aspx>.
|
||||
> [!Note]
|
||||
> Information status on the MSI job will be reported using standard OMA-DM notification mechanism. The status reported is represented using standard MSIEXEC return codes as HRESULT as defined in the MSIEXEC topic on Microsoft TechNet at [Msiexec (command-line options)](https://technet.microsoft.com/library/cc759262%28v=ws.10%29.aspx).
|
||||
|
||||
|
||||
|
||||
@ -401,7 +404,7 @@ The following table MsiInstallJob describes the schema elements.
|
||||
<td>Command-line options to be used when calling MSIEXEC.exe</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td>Timeout</td>
|
||||
<td>TimeOut</td>
|
||||
<td>Amount of time, in minutes that the installation process can run before the installer considers the installation may have failed and no longer monitors the installation operation.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -550,21 +553,18 @@ Here's a list of references:
|
||||
|
||||
```xml
|
||||
<Alert>
|
||||
<CmdID>4</CmdID>
|
||||
<Data>1224</Data>
|
||||
<Item>
|
||||
<Source>
|
||||
<LocURI>./Device/Vendor/MSFT/EnterpriseDesktopAppManagement/MSI/{AF9257BA-6BBD-4624-AA9B-0182D50292C3}/DownloadInstall</LocURI>
|
||||
</Source>
|
||||
<Meta>
|
||||
<Type xmlns="syncml:metinf">Reversed-Domain-Name:com.microsoft.mdm.win32csp_install</Type>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
<Mark xmlns="syncml:metinf">informational</Mark>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
<CmdID>4</CmdID>
|
||||
<Data>1224</Data>
|
||||
<Item>
|
||||
<Source>
|
||||
<LocURI>./Device/Vendor/MSFT/EnterpriseDesktopAppManagement/MSI/{AF9257BA-6BBD-4624-AA9B-0182D50292C3}/DownloadInstall</LocURI>
|
||||
</Source>
|
||||
<Meta>
|
||||
<Type xmlns="syncml:metinf">Reversed-Domain-Name:com.microsoft.mdm.win32csp_install</Type>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
<Mark xmlns="syncml:metinf">informational</Mark>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
</Alert>
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
@ -719,7 +719,7 @@ ADMX Info:
|
||||
<!--/SupportedValues-->
|
||||
<!--Example-->
|
||||
Example for setting the device custom OMA-URI setting to enable this policy:
|
||||
To deny write access to removable storage within Intune’s custom profile, set OMA-URI to ```.\[device|user]\vendor\msft\policy\[config|result]\Storage/RemovableDiskDenyWriteAccess```, Data type to Integer, and Value to 1.
|
||||
To deny write access to removable storage within Intune’s custom profile, set OMA-URI to ```./Device/Vendor/MSFT/Policy/Config/Storage/RemovableDiskDenyWriteAccess```, Data type to Integer, and Value to 1.
|
||||
|
||||
See [Use custom settings for Windows 10 devices in Intune](/intune/custom-settings-windows-10) for information on how to create custom profiles.
|
||||
<!--/Example-->
|
||||
@ -740,4 +740,4 @@ Footnotes:
|
||||
- 7 - Available in Windows 10, version 1909.
|
||||
- 8 - Available in Windows 10, version 2004.
|
||||
|
||||
<!--/Policies-->
|
||||
<!--/Policies-->
|
||||
|
||||
@ -17,7 +17,7 @@ ms.date: 02/23/2018
|
||||
The Update configuration service provider enables IT administrators to manage and control the rollout of new updates.
|
||||
|
||||
> [!NOTE]
|
||||
> The Update CSP functionality of 'AprrovedUpdates' is not recommended for managing desktop devices. To manage updates to desktop devices from Windows Update, see the [Policy CSP - Updates](policy-csp-update.md) documentation for the recommended policies.
|
||||
> The Update CSP functionality of 'ApprovedUpdates' is not recommended for managing desktop devices. To manage updates to desktop devices from Windows Update, see the [Policy CSP - Updates](policy-csp-update.md) documentation for the recommended policies.
|
||||
|
||||
The following shows the Update configuration service provider in tree format.
|
||||
|
||||
|
||||
@ -390,6 +390,9 @@ Optional node. Name Resolution Policy Table (NRPT) rules for the VPN profile.
|
||||
|
||||
The Name Resolution Policy Table (NRPT) is a table of namespaces and corresponding settings stored in the Windows registry that determines the DNS client behavior when issuing queries and processing responses. Each row in the NRPT represents a rule for a portion of the namespace for which the DNS client issues queries. Before issuing name resolution queries, the DNS client consults the NRPT to determine if any additional flags must be set in the query. After receiving the response, the client again consults the NRPT to check for any special processing or policy requirements. In the absence of the NRPT, the client operates based on the DNS servers and suffixes set on the interface.
|
||||
|
||||
> [!NOTE]
|
||||
> Only applications using the [Windows DNS API](/windows/win32/dns/dns-reference) can make use of the NRPT and therefore all settings configured within the DomainNameInformationList section. Applications using their own DNS implementation bypass the Windows DNS API. One example of applications not using the Windows DNS API is nslookup, so always use the PowerShell CmdLet [Resolve-DNSName](/powershell/module/dnsclient/resolve-dnsname) to check the functionality of the NRPT.
|
||||
|
||||
<a href="" id="vpnv2-profilename-domainnameinformationlist-dnirowid"></a>**VPNv2/**<em>ProfileName</em>**/DomainNameInformationList/**<em>dniRowId</em>
|
||||
A sequential integer identifier for the Domain Name information. Sequencing must start at 0.
|
||||
|
||||
@ -419,8 +422,8 @@ Value type is chr. Supported operations include Get, Add, Replace, and Delete.
|
||||
<a href="" id="vpnv2-profilename-domainnameinformationlist-dnirowid-webproxyservers"></a>**VPNv2/**<em>ProfileName</em>**/DomainNameInformationList/**<em>dniRowId</em>**/WebProxyServers**
|
||||
Optional. Web Proxy Server IP address if you are redirecting traffic through your intranet.
|
||||
|
||||
> [!NOTE]
|
||||
> Currently only one web proxy server is supported.
|
||||
> [!NOTE]
|
||||
> Currently only one web proxy server is supported.
|
||||
|
||||
Value type is chr. Supported operations include Get, Add, Replace, and Delete.
|
||||
|
||||
@ -1600,4 +1603,3 @@ Servers
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user