diff --git a/devices/surface-hub/surface-hub-authenticator-app.md b/devices/surface-hub/surface-hub-authenticator-app.md index c00bb03bbb..b303d0354c 100644 --- a/devices/surface-hub/surface-hub-authenticator-app.md +++ b/devices/surface-hub/surface-hub-authenticator-app.md @@ -34,7 +34,7 @@ To let people in your organization sign in to Surface Hub with their phones and - Surface Hub is set up with either a local or domain-joined account. -Currently, you cannot use Microsoft Authenticator to sign in to Surface Hubs that are joined to an Active Directory domain or to Azure AD. +Currently, you cannot use Microsoft Authenticator to sign in to Surface Hubs that are joined to Azure AD. ## Individual prerequisites diff --git a/windows/client-management/mdm/bitlocker-csp.md b/windows/client-management/mdm/bitlocker-csp.md index c432bac103..556cb49468 100644 --- a/windows/client-management/mdm/bitlocker-csp.md +++ b/windows/client-management/mdm/bitlocker-csp.md @@ -798,7 +798,7 @@ The following diagram shows the BitLocker configuration service provider in tree
Allows the Admin to disable the warning prompt for other disk encryption on the user machines.
> [!Important] -> Starting in Windows 10, next major update, the value 0 can only be set for Azure Active Directory joined devices. Windows will attempt to silently enable [BitLocker](https://docs.microsoft.com/en-us/windows/device-security/bitlocker/bitlocker-overview) for value 0. +> Starting in Windows 10, version 1803, the value 0 can only be set for Azure Active Directory joined devices. Windows will attempt to silently enable [BitLocker](https://docs.microsoft.com/en-us/windows/device-security/bitlocker/bitlocker-overview) for value 0. > [!Warning] > When you enable BitLocker on a device with third party encryption, it may render the device unusable and will require reinstallation of Windows. @@ -826,7 +826,7 @@ The following diagram shows the BitLocker configuration service provider in treeThe following list shows the supported values:
-- 0 – Disables the warning prompt. Starting in Windows 10, next major update, the value 0 can only be set for Azure Active Directory joined devices. Windows will attempt to silently enable BitLocker for value 0. +- 0 – Disables the warning prompt. Starting in Windows 10, version 1803, the value 0 can only be set for Azure Active Directory joined devices. Windows will attempt to silently enable BitLocker for value 0. - 1 (default) – Warning prompt allowed. ``` syntax diff --git a/windows/client-management/mdm/cm-cellularentries-csp.md b/windows/client-management/mdm/cm-cellularentries-csp.md index e81ff53e92..22bb311265 100644 --- a/windows/client-management/mdm/cm-cellularentries-csp.md +++ b/windows/client-management/mdm/cm-cellularentries-csp.md @@ -14,9 +14,6 @@ ms.date: 08/02/2017 The CM\_CellularEntries configuration service provider is used to configure the General Packet Radio Service (GPRS) entries on the device. It defines each GSM data access point. -> [!Note] -> Starting in the next major update to Windows 10, the CM\_CellularEntries CSP is supported in Windows 10 Home, Pro, Enterprise, and Education editions. - This configuration service provider requires the ID\_CAP\_NETWORKING\_ADMIN capability to be accessed from a network configuration application. The following diagram shows the CM\_CellularEntries configuration service provider management object in tree format as used by Open Mobile Alliance Client Provisioning (OMA CP). The OMA DM protocol is not supported with this configuration service provider. diff --git a/windows/client-management/mdm/configuration-service-provider-reference.md b/windows/client-management/mdm/configuration-service-provider-reference.md index 5a601e0ca8..16f80bc1f1 100644 --- a/windows/client-management/mdm/configuration-service-provider-reference.md +++ b/windows/client-management/mdm/configuration-service-provider-reference.md @@ -2453,7 +2453,7 @@ Footnotes: Footnotes: - 1 - Added in Windows 10, version 1607 - 2 - Added in Windows 10, version 1703 -- 3 - Added in the next major update to Windows 10 +- 3 - Added in Windows 10, version 1803 ## CSP DDF files download diff --git a/windows/client-management/mdm/defender-csp.md b/windows/client-management/mdm/defender-csp.md index bcab5ce598..b2c82ca8e5 100644 --- a/windows/client-management/mdm/defender-csp.md +++ b/windows/client-management/mdm/defender-csp.md @@ -314,7 +314,7 @@ Node that can be used to perform signature updates for Windows Defender. Supported operations are Get and Execute. **OfflineScan** -Added in Windows 10, next major update. OfflineScan action starts a Windows Defender offline scan on the computer where you run the command. This command causes the computer reboot and start in Windows Defender offline mode to begin the scan. +Added in Windows 10, version 1803. OfflineScan action starts a Windows Defender offline scan on the computer where you run the command. This command causes the computer reboot and start in Windows Defender offline mode to begin the scan. Supported operations are Get and Execute. diff --git a/windows/client-management/mdm/developersetup-csp.md b/windows/client-management/mdm/developersetup-csp.md index 4057384f64..de3145a84f 100644 --- a/windows/client-management/mdm/developersetup-csp.md +++ b/windows/client-management/mdm/developersetup-csp.md @@ -1,6 +1,6 @@ --- title: DeveloperSetup CSP -description: The DeveloperSetup configuration service provider (CSP) is used to configure developer mode on the device. This CSP was added in the next major update of Windows 10. +description: The DeveloperSetup configuration service provider (CSP) is used to configure developer mode on the device. This CSP was added in the Windows 10, version 1703. ms.assetid: ms.author: maricia ms.topic: article diff --git a/windows/client-management/mdm/dmclient-csp.md b/windows/client-management/mdm/dmclient-csp.md index e69e71e093..4de7bc9cc1 100644 --- a/windows/client-management/mdm/dmclient-csp.md +++ b/windows/client-management/mdm/dmclient-csp.md @@ -261,7 +261,7 @@ Optional. Number of days after last sucessful sync to unenroll. Supported operations are Add, Delete, Get, and Replace. Value type is integer. **Provider/*ProviderID*/AADSendDeviceToken** -Device. Added in Windows 10 next major update. For AZure AD backed enrollments, this will cause the client to send a Device Token if the User Token can not be obtained. +Device. Added in Windows 10 version 1803. For AZure AD backed enrollments, this will cause the client to send a Device Token if the User Token can not be obtained. Supported operations are Add, Delete, Get, and Replace. Value type is bool. @@ -713,27 +713,27 @@ Required. Added in Windows 10, version 1709. Integer node determining if a devic Supported operations are Get and Replace. Value type is integer. **Provider/*ProviderID*/FirstSyncStatus/BlockInStatusPage** -Required. Device Only. Added in Windows 10, next major update. This node determines whether or not the MDM progress page is blocking in the Azure AD joined or DJ++ case, as well as which remediation options are available. +Required. Device Only. Added in Windows 10, version 1803. This node determines whether or not the MDM progress page is blocking in the Azure AD joined or DJ++ case, as well as which remediation options are available. Supported operations are Get and Replace. Value type is integer. **Provider/*ProviderID*/FirstSyncStatus/AllowCollectLogsButton** -Required. Added in Windows 10, next major update. This node decides whether or not the MDM progress page displays the Collect Logs button. +Required. Added in Windows 10, version 1803. This node decides whether or not the MDM progress page displays the Collect Logs button. Supported operations are Get and Replace. Value type is bool. **Provider/*ProviderID*/FirstSyncStatus/CustomErrorText** -Required. Added in Windows 10, next major update. This node allows the MDM to set custom error text, detailing what the user needs to do in case of error. +Required. Added in Windows 10, version 1803. This node allows the MDM to set custom error text, detailing what the user needs to do in case of error. Supported operations are Add, Get, Delete, and Replace. Value type is string. **Provider/*ProviderID*/FirstSyncStatus/SkipDeviceStatusPage** -Required. Device only. Added in Windows 10, next major update. This node decides wheter or not the MDM device progress page skips after Azure AD joined or Hybrid Azure AD joined in OOBE. +Required. Device only. Added in Windows 10, version 1803. This node decides wheter or not the MDM device progress page skips after Azure AD joined or Hybrid Azure AD joined in OOBE. Supported operations are Get and Replace. Value type is bool. **Provider/*ProviderID*/FirstSyncStatus/SkipUserStatusPage** -Required. Device only. Added in Windows 10, next major update. This node decides wheter or not the MDM user progress page skips after Azure AD joined or DJ++ after user login. +Required. Device only. Added in Windows 10, version 1803. This node decides wheter or not the MDM user progress page skips after Azure AD joined or DJ++ after user login. Supported operations are Get and Replace. Value type is bool. diff --git a/windows/client-management/mdm/dmclient-ddf-file.md b/windows/client-management/mdm/dmclient-ddf-file.md index 51a46a8897..fda5ae3f82 100644 --- a/windows/client-management/mdm/dmclient-ddf-file.md +++ b/windows/client-management/mdm/dmclient-ddf-file.md @@ -20,7 +20,7 @@ This topic shows the OMA DM device description framework (DDF) for the **DMClien Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download). -The XML below is for Windows 10, next major update. +The XML below is for Windows 10, version 1803. ``` syntax diff --git a/windows/client-management/mdm/images/Provisioning_CSP_DMClient_TH2.png b/windows/client-management/mdm/images/Provisioning_CSP_DMClient_TH2.png new file mode 100644 index 0000000000..28ae086ef7 Binary files /dev/null and b/windows/client-management/mdm/images/Provisioning_CSP_DMClient_TH2.png differ diff --git a/windows/client-management/mdm/images/Provisioning_CSP_Defender.png b/windows/client-management/mdm/images/Provisioning_CSP_Defender.png new file mode 100644 index 0000000000..6ee31a8f16 Binary files /dev/null and b/windows/client-management/mdm/images/Provisioning_CSP_Defender.png differ diff --git a/windows/client-management/mdm/images/Provisioning_CSP_RemoteWipe_DMandCP.png b/windows/client-management/mdm/images/Provisioning_CSP_RemoteWipe_DMandCP.png new file mode 100644 index 0000000000..f7d21f0a94 Binary files /dev/null and b/windows/client-management/mdm/images/Provisioning_CSP_RemoteWipe_DMandCP.png differ diff --git a/windows/client-management/mdm/images/provisioning-csp-assignedaccess.png b/windows/client-management/mdm/images/provisioning-csp-assignedaccess.png index b1ebee57d9..663f449910 100644 Binary files a/windows/client-management/mdm/images/provisioning-csp-assignedaccess.png and b/windows/client-management/mdm/images/provisioning-csp-assignedaccess.png differ diff --git a/windows/client-management/mdm/images/provisioning-csp-defender.png b/windows/client-management/mdm/images/provisioning-csp-defender.png index 8d34e77eb9..4d90f1b6f2 100644 Binary files a/windows/client-management/mdm/images/provisioning-csp-defender.png and b/windows/client-management/mdm/images/provisioning-csp-defender.png differ diff --git a/windows/client-management/mdm/images/provisioning-csp-dmclient-th2.png b/windows/client-management/mdm/images/provisioning-csp-dmclient-th2.png index 486779f038..28ae086ef7 100644 Binary files a/windows/client-management/mdm/images/provisioning-csp-dmclient-th2.png and b/windows/client-management/mdm/images/provisioning-csp-dmclient-th2.png differ diff --git a/windows/client-management/mdm/images/provisioning-csp-remotewipe-dmandcp.png b/windows/client-management/mdm/images/provisioning-csp-remotewipe-dmandcp.png index c6e1215e4d..8a01ad0dff 100644 Binary files a/windows/client-management/mdm/images/provisioning-csp-remotewipe-dmandcp.png and b/windows/client-management/mdm/images/provisioning-csp-remotewipe-dmandcp.png differ 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 6c82e08937..17ab0d9a6c 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 @@ -1405,7 +1405,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardwareAdded the following new policies for Windows 10, next major update:
+Added the following new policies for Windows 10, version 1803:
Supported operation is Get. **FailedUpdates/*Failed Update Guid*/RevisionNumber** -
Added in the next major update of Windows 10. The revision number for the update that must be passed in server to server sync to get the metadata for the update. +
Added in the Windows 10, version 1803. The revision number for the update that must be passed in server to server sync to get the metadata for the update.
Supported operation is Get. @@ -91,7 +91,7 @@ The following diagram shows the Update configuration service provider in tree fo
Supported operation is Get. **InstalledUpdates/*Installed Update Guid*/RevisionNumber** -
Added in the next major update of Windows 10. The revision number for the update that must be passed in server to server sync to get the metadata for the update. +
Added in Windows 10, version 1803. The revision number for the update that must be passed in server to server sync to get the metadata for the update.
Supported operation is Get. @@ -135,7 +135,7 @@ The following diagram shows the Update configuration service provider in tree fo
Supported operation is Get. **PendingRebootUpdates/*Pending Reboot Update Guid*/RevisionNumber** -
Added in the next major update of Windows 10. The revision number for the update that must be passed in server to server sync to get the metadata for the update. +
Added in Windows 10, version 1803. The revision number for the update that must be passed in server to server sync to get the metadata for the update.
Supported operation is Get. diff --git a/windows/security/threat-protection/windows-defender-atp/troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md index 1e32ef16a7..d6dbef14e6 100644 --- a/windows/security/threat-protection/windows-defender-atp/troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md @@ -10,7 +10,7 @@ ms.pagetype: security ms.author: macapara author: mjcaparas ms.localizationpriority: high -ms.date: 10/16/2017 +ms.date: 02/26/2018 --- # Troubleshoot custom threat intelligence issues @@ -33,15 +33,15 @@ This page provides detailed steps to troubleshoot issues you might encounter whi ## Learn how to get a new client secret If your client secret expires or if you've misplaced the copy provided when you were enabling the custom threat intelligence application, you'll need to get a new secret. -1. Login to the [Azure management portal](https://ms.portal.azure.com). +1. Login to the [Azure management portal](https://portal.azure.com). 2. Select **Active Directory**. 3. Select your tenant. -4. Click **Application**, then select your custom threat intelligence application. The application name is **WindowsDefenderATPThreatIntelAPI** (formerly known as **WindowsDefenderATPCustomerTiConnector**). +4. Click **App registrations** > **All apps**. Then select the application name **WindowsDefenderATPThreatIntelAPI** (formerly known as **WindowsDefenderATPCustomerTiConnector**). -5. Select **Keys** section, then provide a key description and specify the key validity duration. +5. Under **Settings**, select **Keys**, then provide a key description and specify the key validity duration. 6. Click **Save**. The key value is displayed. diff --git a/windows/security/threat-protection/windows-defender-atp/troubleshoot-siem-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/troubleshoot-siem-windows-defender-advanced-threat-protection.md index c384aeaa9e..4d77042ae0 100644 --- a/windows/security/threat-protection/windows-defender-atp/troubleshoot-siem-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/troubleshoot-siem-windows-defender-advanced-threat-protection.md @@ -34,13 +34,13 @@ This page provides detailed steps to troubleshoot issues you might encounter. ## Learn how to get a new client secret If your client secret expires or if you've misplaced the copy provided when you were enabling the SIEM tool application, you'll need to get a new secret. -1. Login to the [Azure management portal](https://ms.portal.azure.com). +1. Login to the [Azure management portal](https://portal.azure.com). 2. Select **Azure Active Directory**. 3. Select your tenant. -4. Click **Application**, then select your SIEM tool application. The application name is `https://windowsdefenderatpsiemconnector`. +4. Click **App registrations** > **All apps**, then select your SIEM tool application. The application name is `https://windowsdefenderatpsiemconnector`. 5. Select **Keys** section, then provide a key description and specify the key validity duration. @@ -48,6 +48,7 @@ If your client secret expires or if you've misplaced the copy provided when you 7. Copy the value and save it in a safe place. + ## Error when getting a refresh access token If you encounter an error when trying to get a refresh token when using the threat intelligence API or SIEM tools, you'll need to add reply URL for relevant application in Azure Active Directory.