diff --git a/devices/surface-hub/index.md b/devices/surface-hub/index.md index 03268e3bb2..8c84d59605 100644 --- a/devices/surface-hub/index.md +++ b/devices/surface-hub/index.md @@ -36,14 +36,3 @@ Documents related to the Microsoft Surface Hub. - -  - -  - -  - - - - - diff --git a/mdop/mbam-v25/release-notes-for-mbam-25-sp1.md b/mdop/mbam-v25/release-notes-for-mbam-25-sp1.md index d8e92abf32..b52e59331b 100644 --- a/mdop/mbam-v25/release-notes-for-mbam-25-sp1.md +++ b/mdop/mbam-v25/release-notes-for-mbam-25-sp1.md @@ -119,7 +119,16 @@ If Internet Explorer Enhanced Security Configuration (ESC) is turned on, an "Acc **Workaround:** If the "Access Denied" error message appears when you try to view reports on the MBAM Server, you can set a Group Policy Object or change the default manually in your image to disable Enhanced Security Configuration. You can also alternatively view the reports from another computer on which ESC is not enabled. ### Support for Bitlocker XTS-AES encryption algorithm -Bitlocker added support for the XTS-AES encryption algorithm in Windows 10, version 1511. As of HF02, MBAM now supports this Bitlocker option. +Bitlocker added support for the XTS-AES encryption algorithm in Windows 10, version 1511. +As of HF02, MBAM now supports this Bitlocker option and is a client-only update. +However, there are two known limitations: + +* MBAM will correctly report compliance status but the **Cipher Strength** field in MBAM reports will be empty. +MBAM pre-built reports and compliance charts won’t break but the **Cipher Strength** column will be empty for XTS machines. +Also, if a customer has a custom report that uses this particular field, they may have to make adjustments to accommodate this update. + +* Customers must use the same encryption strength for OS and data volumes on the same machine. +If different encryption strengths are used, MBAM will report the machine as **non-compliant**. ### Self-Service Portal automatically adds "-" on Key ID entry As of HF02, the MBAM Self-Service Portal automatically adds the '-' on Key ID entry. diff --git a/windows/manage/waas-wufb-intune.md b/windows/manage/waas-wufb-intune.md index 91e628629f..b22418aedb 100644 --- a/windows/manage/waas-wufb-intune.md +++ b/windows/manage/waas-wufb-intune.md @@ -146,7 +146,7 @@ In this example, you use three security groups from Table 1 in [Build deployment 8. Because the **Ring 2 Pilot Business Users** deployment ring receives the CB feature updates after 14 days, in the **OMA-URI Settings** section, click **Add** to add another OMA-URI setting. 8. In **Setting name**, type **Defer feature updates for 14 days**, and then select **Integer** from the **Data type** list. -10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatePeriodInDays**. +10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays**. 11. In the **Value** box, type **14**, and then click **OK**. ![Settings for this policy](images/waas-wufb-intune-step11a.png) @@ -186,7 +186,7 @@ You have now configured the **Ring 2 Pilot Business Users** deployment ring to e 8. In **Setting name**, type **Defer feature updates for 0 days**, and then select **Integer** from the **Data type** list. -10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatePeriodInDays**. +10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays**. 11. In the **Value** box, type **0**, and then click **OK**. @@ -228,7 +228,7 @@ You have now configured the **Ring 3 Broad IT** deployment ring to receive CBB f 8. In **Setting name**, type **Defer quality updates for 7 days**, and then select **Integer** from the **Data type** list. -10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferQualityUpdatePeriodInDays**. +10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferQualityUpdatesPeriodInDays**. 11. In the **Value** box, type **7**, and then click **OK**. @@ -236,7 +236,7 @@ You have now configured the **Ring 3 Broad IT** deployment ring to receive CBB f 8. In **Setting name**, type **Defer feature updates for 30 days**, and then select **Integer** from the **Data type** list. -10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatePeriodInDays**. +10. In the **OMA-URI** box, type **.Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays**. 11. In the **Value** box, type **30**, and then click **OK**.