mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
fix some warnings
This commit is contained in:
parent
3767924db5
commit
313a2f0bcd
@ -5,7 +5,6 @@ ms.assetid: 0895606e-96c0-491e-8b1c-52e56b00365d
|
|||||||
author: mattzmsft
|
author: mattzmsft
|
||||||
ms.author: mazeller
|
ms.author: mazeller
|
||||||
keywords: HoloLens, wifi, wireless, internet, ip, ip address
|
keywords: HoloLens, wifi, wireless, internet, ip, ip address
|
||||||
ms.date: 08/30/19
|
|
||||||
ms.prod: hololens
|
ms.prod: hololens
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
|
@ -7,7 +7,6 @@ ms.sitesec: library
|
|||||||
author: dansimp
|
author: dansimp
|
||||||
ms.author: dansimp
|
ms.author: dansimp
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.date: 06/11/2019
|
|
||||||
ms.reviewer: cottmca
|
ms.reviewer: cottmca
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
@ -34,7 +33,8 @@ Before you run the diagnostic tool, make sure you have the latest Windows update
|
|||||||
2. Select Run and follow the on-screen instructions. For full details, refer to [Deploy Surface Diagnostic Toolkit for Business](https://docs.microsoft.com/surface/surface-diagnostic-toolkit-business).
|
2. Select Run and follow the on-screen instructions. For full details, refer to [Deploy Surface Diagnostic Toolkit for Business](https://docs.microsoft.com/surface/surface-diagnostic-toolkit-business).
|
||||||
|
|
||||||
The diagnosis and repair time averages 15 minutes but could take an hour or longer, depending on internet connection speed and the number of updates or repairs required.
|
The diagnosis and repair time averages 15 minutes but could take an hour or longer, depending on internet connection speed and the number of updates or repairs required.
|
||||||
# If you still need help
|
|
||||||
|
## If you still need help
|
||||||
|
|
||||||
If the Surface Diagnostic Toolkit for Business didn’t fix the problem, you can also:
|
If the Surface Diagnostic Toolkit for Business didn’t fix the problem, you can also:
|
||||||
|
|
||||||
|
@ -16,12 +16,10 @@ ms.date: 08/30/2016
|
|||||||
|
|
||||||
# About MBAM 2.0 SP1
|
# About MBAM 2.0 SP1
|
||||||
|
|
||||||
|
|
||||||
This topic describes the changes in Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 Service Pack 1 (SP1). For a general description of MBAM, see [Getting Started with MBAM 2.0](getting-started-with-mbam-20-mbam-2.md).
|
This topic describes the changes in Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 Service Pack 1 (SP1). For a general description of MBAM, see [Getting Started with MBAM 2.0](getting-started-with-mbam-20-mbam-2.md).
|
||||||
|
|
||||||
## <a href="" id="what-s-new-in-mbam-2-0-sp1"></a>What’s new in MBAM 2.0 SP1
|
## <a href="" id="what-s-new-in-mbam-2-0-sp1"></a>What’s new in MBAM 2.0 SP1
|
||||||
|
|
||||||
|
|
||||||
This version of MBAM provides the following new features and functionality.
|
This version of MBAM provides the following new features and functionality.
|
||||||
|
|
||||||
### Support for Windows 8.1, Windows Server 2012 R2, and System Center 2012 R2 Configuration Manager
|
### Support for Windows 8.1, Windows Server 2012 R2, and System Center 2012 R2 Configuration Manager
|
||||||
@ -257,8 +255,9 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
// Microsoft BitLocker Administration and Monitoring
|
// Microsoft BitLocker Administration and Monitoring
|
||||||
//===================================================
|
//===================================================
|
||||||
|
|
||||||
# pragma namespace ("\\\\.\\root\\cimv2")
|
# pragma namespace ("\\\\.\\root\\cimv2")
|
||||||
# pragma deleteclass("Win32_BitLockerEncryptionDetails", NOFAIL)
|
# pragma deleteclass("Win32_BitLockerEncryptionDetails", NOFAIL)
|
||||||
|
|
||||||
[Union, ViewSources{"select DeviceId, BitlockerPersistentVolumeId, BitLockerManagementPersistentVolumeId, BitLockerManagementVolumeType, DriveLetter, Compliant, ReasonsForNonCompliance, KeyProtectorTypes, EncryptionMethod, ConversionStatus, ProtectionStatus, IsAutoUnlockEnabled from Mbam_Volume"}, ViewSpaces{"\\\\.\\root\\microsoft\\mbam"}, dynamic, Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
[Union, ViewSources{"select DeviceId, BitlockerPersistentVolumeId, BitLockerManagementPersistentVolumeId, BitLockerManagementVolumeType, DriveLetter, Compliant, ReasonsForNonCompliance, KeyProtectorTypes, EncryptionMethod, ConversionStatus, ProtectionStatus, IsAutoUnlockEnabled from Mbam_Volume"}, ViewSpaces{"\\\\.\\root\\microsoft\\mbam"}, dynamic, Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
||||||
class Win32_BitLockerEncryptionDetails
|
class Win32_BitLockerEncryptionDetails
|
||||||
{
|
{
|
||||||
@ -290,8 +289,8 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
Boolean IsAutoUnlockEnabled;
|
Boolean IsAutoUnlockEnabled;
|
||||||
};
|
};
|
||||||
|
|
||||||
# pragma namespace ("\\\\.\\root\\cimv2")
|
# pragma namespace ("\\\\.\\root\\cimv2")
|
||||||
# pragma deleteclass("Win32Reg_MBAMPolicy", NOFAIL)
|
# pragma deleteclass("Win32Reg_MBAMPolicy", NOFAIL)
|
||||||
[DYNPROPS]
|
[DYNPROPS]
|
||||||
Class Win32Reg_MBAMPolicy
|
Class Win32Reg_MBAMPolicy
|
||||||
{
|
{
|
||||||
@ -352,8 +351,8 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
EncodedComputerName;
|
EncodedComputerName;
|
||||||
};
|
};
|
||||||
|
|
||||||
# pragma namespace ("\\\\.\\root\\cimv2")
|
# pragma namespace ("\\\\.\\root\\cimv2")
|
||||||
# pragma deleteclass("Win32Reg_MBAMPolicy_64", NOFAIL)
|
# pragma deleteclass("Win32Reg_MBAMPolicy_64", NOFAIL)
|
||||||
[DYNPROPS]
|
[DYNPROPS]
|
||||||
Class Win32Reg_MBAMPolicy_64
|
Class Win32Reg_MBAMPolicy_64
|
||||||
{
|
{
|
||||||
@ -414,8 +413,8 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
EncodedComputerName;
|
EncodedComputerName;
|
||||||
};
|
};
|
||||||
|
|
||||||
# pragma namespace ("\\\\.\\root\\cimv2")
|
# pragma namespace ("\\\\.\\root\\cimv2")
|
||||||
# pragma deleteclass("CCM_OperatingSystemExtended", NOFAIL)
|
# pragma deleteclass("CCM_OperatingSystemExtended", NOFAIL)
|
||||||
[Union, ViewSources{"select Name,OperatingSystemSKU from Win32_OperatingSystem"}, ViewSpaces{"\\\\.\\root\\cimv2"},
|
[Union, ViewSources{"select Name,OperatingSystemSKU from Win32_OperatingSystem"}, ViewSpaces{"\\\\.\\root\\cimv2"},
|
||||||
dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
||||||
class CCM_OperatingSystemExtended
|
class CCM_OperatingSystemExtended
|
||||||
@ -426,8 +425,8 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
uint32 SKU;
|
uint32 SKU;
|
||||||
};
|
};
|
||||||
|
|
||||||
# pragma namespace ("\\\\.\\root\\cimv2")
|
# pragma namespace ("\\\\.\\root\\cimv2")
|
||||||
# pragma deleteclass("CCM_ComputerSystemExtended", NOFAIL)
|
# pragma deleteclass("CCM_ComputerSystemExtended", NOFAIL)
|
||||||
[Union, ViewSources{"select Name,PCSystemType from Win32_ComputerSystem"}, ViewSpaces{"\\\\.\\root\\cimv2"},
|
[Union, ViewSources{"select Name,PCSystemType from Win32_ComputerSystem"}, ViewSpaces{"\\\\.\\root\\cimv2"},
|
||||||
dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
|
||||||
class CCM_ComputerSystemExtended
|
class CCM_ComputerSystemExtended
|
||||||
@ -449,35 +448,23 @@ If you are upgrading to MBAM 2.0 SP1 and you are using MBAM with Configuration M
|
|||||||
MBAM 2.0 SP1 is now available in the following languages:
|
MBAM 2.0 SP1 is now available in the following languages:
|
||||||
|
|
||||||
- English (United States) en-US
|
- English (United States) en-US
|
||||||
|
|
||||||
- French (France) fr-FR
|
- French (France) fr-FR
|
||||||
|
|
||||||
- Italian (Italy) it-IT
|
- Italian (Italy) it-IT
|
||||||
|
|
||||||
- German (Germany) de-DE
|
- German (Germany) de-DE
|
||||||
|
|
||||||
- Spanish, International Sort (Spain) es-ES
|
- Spanish, International Sort (Spain) es-ES
|
||||||
|
|
||||||
- Korean (Korea) ko-KR
|
- Korean (Korea) ko-KR
|
||||||
|
|
||||||
- Japanese (Japan) ja-JP
|
- Japanese (Japan) ja-JP
|
||||||
|
|
||||||
- Portuguese (Brazil) pt-BR
|
- Portuguese (Brazil) pt-BR
|
||||||
|
|
||||||
- Russian (Russia) ru-RU
|
- Russian (Russia) ru-RU
|
||||||
|
|
||||||
- Chinese Traditional zh-TW
|
- Chinese Traditional zh-TW
|
||||||
|
|
||||||
- Chinese Simplified zh-CN
|
- Chinese Simplified zh-CN
|
||||||
|
|
||||||
## How to Get MDOP Technologies
|
## How to Get MDOP Technologies
|
||||||
|
|
||||||
|
|
||||||
MBAM 2.0 SP1 is a part of the Microsoft Desktop Optimization Pack (MDOP). MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see [How Do I Get MDOP](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
|
MBAM 2.0 SP1 is a part of the Microsoft Desktop Optimization Pack (MDOP). MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see [How Do I Get MDOP](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
[Release Notes for MBAM 2.0 SP1](release-notes-for-mbam-20-sp1.md)
|
[Release Notes for MBAM 2.0 SP1](release-notes-for-mbam-20-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
@ -7,7 +7,6 @@ ms.sitesec: library
|
|||||||
ms.author: dansimp
|
ms.author: dansimp
|
||||||
author: dansimp
|
author: dansimp
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 12/03/18
|
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
ms.topic: troubleshooting
|
ms.topic: troubleshooting
|
||||||
@ -34,8 +33,6 @@ When troubleshooting basic Start issues (and for the most part, all other Window
|
|||||||
- Powershell:[System.Environment]::OSVersion.Version
|
- Powershell:[System.Environment]::OSVersion.Version
|
||||||
- WinVer from CMD.exe
|
- WinVer from CMD.exe
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Check if Start is installed
|
### Check if Start is installed
|
||||||
|
|
||||||
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
||||||
@ -66,7 +63,6 @@ If it is installed but not running, test booting into safe mode or use MSCONFIG
|
|||||||
- If that file does not exist, the system is a clean install.
|
- If that file does not exist, the system is a clean install.
|
||||||
- Upgrade issues can be found by running `test-path "$env:windir\panther\miglog.xml"`
|
- Upgrade issues can be found by running `test-path "$env:windir\panther\miglog.xml"`
|
||||||
|
|
||||||
|
|
||||||
### Check if Start is registered or activated
|
### Check if Start is registered or activated
|
||||||
|
|
||||||
- Export the following Event log to CSV and do a keyword search in a text editor or spreadsheet:
|
- Export the following Event log to CSV and do a keyword search in a text editor or spreadsheet:
|
||||||
|
@ -1,15 +1,15 @@
|
|||||||
# Deploy Windows 10 with Configuration Manager
|
# Deploy Windows 10 with Configuration Manager
|
||||||
## [Configuration Manager components](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md)
|
## [Configuration Manager components](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md)
|
||||||
### [Integrate Configuration Manager with MDT](deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
### [Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||||
### [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
### [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||||
### [Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
### [Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||||
### [Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
### [Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||||
### [Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
### [Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||||
### [Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
### [Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||||
### [Create a task sequence with Configuration Manager and MDT](deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
### [Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||||
### [Finalize the operating system configuration for Windows 10 deployment with Configuration Manager](finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md)
|
### [Finalize the operating system configuration for Windows 10 deployment with Configuration Manager](finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md)
|
||||||
### [Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
### [Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||||
### [Monitor the Windows 10 deployment with Configuration Manager](monitor-windows-10-deployment-with-configuration-manager.md)
|
### [Monitor the Windows 10 deployment with Configuration Manager](monitor-windows-10-deployment-with-configuration-manager.md)
|
||||||
### [Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
### [Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||||
### [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
### [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||||
### [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager.md)
|
### [Perform an in-place upgrade to Windows 10 using Configuration Manager](../upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager.md)
|
@ -445,7 +445,7 @@ If you have already completed steps in [Deploy Windows 10 in a test lab using Mi
|
|||||||
- Summary: click **Next**
|
- Summary: click **Next**
|
||||||
- Confirmation: click **Finish**
|
- Confirmation: click **Finish**
|
||||||
|
|
||||||
9. For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the [Add applications](deploy-windows-mdt/create-a-windows-10-reference-image.md#sec03) section of the [Create a Windows 10 reference image](deploy-windows-mdt/create-a-windows-10-reference-image.md) topic in the TechNet library.
|
9. For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the [Add applications](deploy-windows-mdt/create-a-windows-10-reference-image.md#add-applications) section of the [Create a Windows 10 reference image](deploy-windows-mdt/create-a-windows-10-reference-image.md) topic in the TechNet library.
|
||||||
|
|
||||||
10. The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the **Task Sequences** node under **MDT Build Lab** and then click **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
10. The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the **Task Sequences** node under **MDT Build Lab** and then click **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
||||||
- Task sequence ID: **REFW10X64-001**<br>
|
- Task sequence ID: **REFW10X64-001**<br>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user