Merge remote-tracking branch 'refs/remotes/origin/master' into rs1
@ -14,4 +14,6 @@
|
||||
## [Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)
|
||||
## [Surface Dock Updater](surface-dock-updater.md)
|
||||
## [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
||||
### [Enroll and configure Surface devices with SEMM](enroll-and-configure-surface-devices-with-semm.md)
|
||||
### [Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
|
||||
|
||||
|
@ -0,0 +1,135 @@
|
||||
---
|
||||
title: Enroll and configure Surface devices with SEMM (Surface)
|
||||
description: Learn how to create a Surface UEFI configuration package to control the settings of Surface UEFI, as well as enroll a Surface device in SEMM.
|
||||
keywords: surface enterprise management
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
---
|
||||
|
||||
# Enroll and configure Surface devices with SEMM
|
||||
|
||||
With Microsoft Surface Enterprise Management Mode (SEMM), you can securely configure the settings of Surface UEFI on a Surface device and manage those settings on Surface devices in your organization. When a Surface device is managed by SEMM, that device is considered to be *enrolled* (sometimes referred to as activated). This article shows you how to create a Surface UEFI configuration package that will not only control the settings of Surface UEFI, but will also enroll a Surface device in SEMM.
|
||||
|
||||
For a more high-level overview of SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
#### Download and install Microsoft Surface UEFI Configurator
|
||||
The tool used to create SEMM packages is Microsoft Surface UEFI Configurator. You can download Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/en-us/download/details.aspx?id=46703) page in the Microsoft Download Center.
|
||||
Run the Microsoft Surface UEFI Configurator Windows Installer (.msi) file to start the installation of the tool. When the installer completes, find Microsoft Surface UEFI Configurator in the All Apps section of your Start menu.
|
||||
|
||||
>**Note**: Microsoft Surface UEFI Configurator is supported only on Windows 10.
|
||||
|
||||
## Create a Surface UEFI configuration package
|
||||
|
||||
The Surface UEFI configuration package performs both the role of applying a new configuration of Surface UEFI settings to a Surface device managed with SEMM and the role of enrolling Surface devices in SEMM. The creation of a configuration package requires you to have a signing certificate to be used with SEMM to secure the configuration of UEFI settings on each Surface device. For more information about the requirements for the SEMM certificate, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
To create a Surface UEFI configuration package, follow these steps:
|
||||
|
||||
1. Open Microsoft Surface UEFI Configurator from the Start menu.
|
||||
2. Click **Start**.
|
||||
3. Click **Configuration Package**, as shown in Figure 1.
|
||||
|
||||

|
||||
|
||||
*Figure 1. Select Configuration Package to create a package for SEMM enrollment and configuration*
|
||||
|
||||
4. Click **Certificate Protection** to add your exported certificate file with private key (.pfx), as shown in Figure 2. Browse to the location of your certificate file, select the file, and then click **OK**.
|
||||
|
||||

|
||||
|
||||
*Figure 2. Add the SEMM certificate and Surface UEFI password to a Surface UEFI configuration package*
|
||||
|
||||
5. When you are prompted to confirm the certificate password, enter and confirm the password for your certificate file, and then click **OK**.
|
||||
6. Click **Password Protection** to add a password to Surface UEFI. This password will be required whenever you boot to UEFI. If this password is not entered, only the **PC information**, **About**, **Enterprise management**, and **Exit** pages will be displayed. This step is optional.
|
||||
7. When you are prompted, enter and confirm your chosen password for Surface UEFI, and then click **OK**. If you want to clear an existing Surface UEFI password, leave the password field blank.
|
||||
8. If you do not want the Surface UEFI package to apply to a particular device, on the **Choose which Surface type you want to target** page, click the slider beneath the corresponding Surface Book or Surface Pro 4 image so that it is in the **Off** position. (As shown in Figure 3.)
|
||||
|
||||

|
||||
|
||||
*Figure 3. Choose the devices for package compatibility*
|
||||
|
||||
9. Click **Next**.
|
||||
10. If you want to deactivate a component on managed Surface devices, on the **Choose which components you want to activate or deactivate** page, click the slider next to any device or group of devices you want to deactivate so that the slider is in the **Off** position. (Shown in Figure 4.) The default configuration for each device is **On**. Click the **Reset** button if you want to return all sliders to the default position.
|
||||
|
||||

|
||||
|
||||
*Figure 4. Disable or enable individual Surface components*
|
||||
|
||||
11. Click **Next**.
|
||||
12. To enable or disable advanced options in Surface UEFI or the display of Surface UEFI pages, on the **Choose the advanced settings for your devices** page, click the slider beside the desired setting to configure that option to **On** or **Off** (shown in Figure 5). In the **UEFI Front Page** section, you can use the sliders for **Security**, **Devices**, and **Boot** to control what pages are available to users who boot into Surface UEFI. (For more information about Surface UEFI settings, see [Manage Surface UEFI settings](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-uefi-settings).) Click **Build** when you have finished selecting options to generate and save the package.
|
||||
|
||||

|
||||
|
||||
*Figure 5. Control advanced Surface UEFI settings and Surface UEFI pages with SEMM*
|
||||
|
||||
13. In the **Save As** dialog box, specify a name for the Surface UEFI configuration package, browse to the location where you would like to save the file, and then click **Save**.
|
||||
14. When the package is created and saved, the **Successful** page is displayed.
|
||||
|
||||
>**Note**: Record the certificate thumbprint characters that are displayed on this page, as shown in Figure 6. You will need these characters to confirm enrollment of new Surface devices in SEMM. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
|
||||
|
||||

|
||||
|
||||
*Figure 6. The last two characters of the certificate thumbprint are displayed on the Successful page*
|
||||
|
||||
Now that you have created your Surface UEFI configuration package, you can enroll or configure Surface devices.
|
||||
|
||||
>**Note**: When a Surface UEFI configuration package is created, a log file is created on the desktop with details of the configuration package settings and options.
|
||||
|
||||
## Enroll a Surface device in SEMM
|
||||
When the Surface UEFI configuration package is executed, the SEMM certificate and Surface UEFI configuration files are staged in the firmware storage of the Surface device. When the Surface device reboots, Surface UEFI processes these files and begins the process of applying the Surface UEFI configuration or enrolling the Surface device in SEMM, as shown in Figure 7.
|
||||
|
||||

|
||||
|
||||
*Figure 7. The SEMM process for configuration of Surface UEFI or enrollment of a Surface device*
|
||||
|
||||
Before you begin the process to enroll a Surface device in SEMM, ensure that you have the last two characters of the certificate thumbprint on hand. You will need these characters to confirm the device’s enrollment (see Figure 6).
|
||||
|
||||
To enroll a Surface device in SEMM with a Surface UEFI configuration package, follow these steps:
|
||||
|
||||
1. Run the Surface UEFI configuration package .msi file on the Surface device you want to enroll in SEMM. This will provision the Surface UEFI configuration file in the device’s firmware.
|
||||
2. Select the **I accept the terms in the License Agreement** check box to accept the End User License Agreement (EULA), and then click **Install** to begin the installation process.
|
||||
3. Click **Finish** to complete the Surface UEFI configuration package installation and restart the Surface device when you are prompted to do so.
|
||||
4. Surface UEFI will load the configuration file and determine that SEMM is not enabled on the device. Surface UEFI will then begin the SEMM enrollment process, as follows:
|
||||
* Surface UEFI will verify that the SEMM configuration file contains a SEMM certificate.
|
||||
* Surface UEFI will prompt you to enter to enter the last two characters of the certificate thumbprint to confirm enrollment of the Surface device in SEMM, as shown in Figure 8.
|
||||
|
||||

|
||||
|
||||
*Figure 8. Enrollment in SEMM requires the last two characters of the certificate thumbprint*
|
||||
|
||||
* Surface UEFI will store the SEMM certificate in firmware and apply the configuration settings that are specified in the Surface UEFI configuration file.
|
||||
|
||||
5. The Surface device is now enrolled in SEMM and will boot to Windows.
|
||||
|
||||
You can verify that a Surface device has been successfully enrolled in SEMM by looking for **Microsoft Surface Configuration Package** in **Programs and Features** (as shown in Figure 9), or in the events stored in the **Microsoft Surface UEFI Configurator** log, found under **Applications and Services Logs** in Event Viewer (as shown in Figure 10).
|
||||
|
||||

|
||||
|
||||
*Figure 9. Verify the enrollment of a Surface device in SEMM in Programs and Features*
|
||||
|
||||

|
||||
|
||||
*Figure 10. Verify the enrollment of a Surface device in SEMM in Event Viewer*
|
||||
|
||||
You can also verify that the device is enrolled in SEMM in Surface UEFI – while the device is enrolled, Surface UEFI will contain the **Enterprise management** page (as shown in Figure 11).
|
||||
|
||||

|
||||
|
||||
*Figure 11. The Surface UEFI Enterprise management page*
|
||||
|
||||
|
||||
## Configure Surface UEFI settings with SEMM
|
||||
|
||||
After a device is enrolled in SEMM, you can run Surface UEFI configuration packages signed with the same SEMM certificate to apply new Surface UEFI settings. These settings are applied automatically the next time the device boots, without any interaction from the user. You can use application deployment solutions like System Center Configuration Manager to deploy Surface UEFI configuration packages to Surface devices to change or manage the settings in Surface UEFI.
|
||||
|
||||
For more information about how to deploy Windows Installer (.msi) files with Configuration Manager, see [Deploy and manage applications with System Center Configuration Manager](https://technet.microsoft.com/library/mt627959).
|
||||
|
||||
If you have secured Surface UEFI with a password, users without the password who attempt to boot to Surface UEFI will only have the **PC information**, **About**, **Enterprise management**, and **Exit** pages displayed to them.
|
||||
|
||||
If you have not secured Surface UEFI with a password or a user enters the password correctly, settings that are configured with SEMM will be dimmed (unavailable) and the text Some settings are managed by your organization will be displayed at the top of the page, as shown in Figure 12.
|
||||
|
||||

|
||||
|
||||
*Figure 12. Settings managed by SEMM will be disabled in Surface UEFI*
|
BIN
devices/surface/images/surface-enroll-semm-fig1.png
Normal file
After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig1.png
Normal file
After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig10.png
Normal file
After Width: | Height: | Size: 128 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig11.png
Normal file
After Width: | Height: | Size: 108 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig12.png
Normal file
After Width: | Height: | Size: 65 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig3.png
Normal file
After Width: | Height: | Size: 126 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig4.png
Normal file
After Width: | Height: | Size: 113 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig5.png
Normal file
After Width: | Height: | Size: 110 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig6.png
Normal file
After Width: | Height: | Size: 112 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig7.png
Normal file
After Width: | Height: | Size: 94 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig8.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig9.png
Normal file
After Width: | Height: | Size: 66 KiB |
BIN
devices/surface/images/surface-semm-enrollment-fig2.png
Normal file
After Width: | Height: | Size: 112 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig1.png
Normal file
After Width: | Height: | Size: 74 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig10.png
Normal file
After Width: | Height: | Size: 87 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig11.png
Normal file
After Width: | Height: | Size: 45 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig12.png
Normal file
After Width: | Height: | Size: 170 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig13.png
Normal file
After Width: | Height: | Size: 122 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig14.png
Normal file
After Width: | Height: | Size: 60 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig2.png
Normal file
After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig3.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig4.png
Normal file
After Width: | Height: | Size: 52 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig5.png
Normal file
After Width: | Height: | Size: 66 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig6.png
Normal file
After Width: | Height: | Size: 108 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig7.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig8.png
Normal file
After Width: | Height: | Size: 276 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig9.png
Normal file
After Width: | Height: | Size: 133 KiB |
148
devices/surface/unenroll-surface-devices-from-semm.md
Normal file
@ -0,0 +1,148 @@
|
||||
---
|
||||
title: Unenroll Surface devices from SEMM (Surface)
|
||||
description: Learn how to unenroll a device from SEMM by using a Surface UEFI reset package or the Recovery Request option.
|
||||
keywords: surface enterprise management
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
---
|
||||
|
||||
# Unenroll Surface devices from SEMM (Surface)
|
||||
|
||||
When a Surface device is enrolled in Surface Enterprise Management Mode (SEMM), a certificate is stored in the firmware of that device. The presence of that certificate and the enrollment in SEMM prevent any unauthorized changes to Surface UEFI settings or options while the device is enrolled in SEMM. To restore control of Surface UEFI settings to the user, the Surface device must be unenrolled from SEMM, a process sometimes described as reset or recovery. There are two methods you can use to unenroll a device from SEMM—a Surface UEFI reset package and a Recovery Request.
|
||||
|
||||
>**Warning:** To unenroll a device from SEMM and restore user control of Surface UEFI settings, you must have the SEMM certificate that was used to enroll the device in SEMM. If this certificate becomes lost or corrupted, it is not possible to unenroll from SEMM. Back up and protect your SEMM certificate accordingly.
|
||||
|
||||
For more information about SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
## Unenroll a Surface device from SEMM with a Surface UEFI reset package
|
||||
|
||||
The Surface UEFI reset package is the primary method you use to unenroll a Surface device from SEMM. Like a Surface UEFI configuration package, the reset package is a Windows Installer (.msi) file that configures SEMM on the device. Unlike the configuration package, the reset package will reset the Surface UEFI configuration on a Surface device to its default settings, remove the SEMM certificate, and unenroll the device from SEMM.
|
||||
|
||||
Reset packages are created specifically for an individual Surface device. To begin the process of creating a reset package, you will need the serial number of the device you want to unenroll, as well as the SEMM certificate used to enroll the device. You can find the serial number of your Surface device on the **PC information** page of Surface UEFI, as shown in Figure 1. This page is displayed even if Surface UEFI is password protected and the incorrect password is entered.
|
||||
|
||||

|
||||
|
||||
*Figure 1. The serial number of the Surface device is displayed on the Surface UEFI PC information page*
|
||||
|
||||
>**Note:** To boot to Surface UEFI, press **Volume Up** and **Power** simultaneously while the device is off. Hold **Volume Up** until the Surface logo is displayed and the device begins to boot.
|
||||
|
||||
To create a Surface UEFI reset package, follow these steps:
|
||||
|
||||
1. Open Microsoft Surface UEFI Configurator from the Start menu.
|
||||
2. Click **Start**.
|
||||
3. Click **Reset Package**, as shown in Figure 2.
|
||||
|
||||

|
||||
|
||||
*Figure 2. Click Reset Package to create a package to unenroll a Surface device from SEMM*
|
||||
|
||||
4. Click **Certificate Protection** to add your SEMM certificate file with private key (.pfx), as shown in Figure 3. Browse to the location of your certificate file, select the file, and then click **OK**.
|
||||
|
||||

|
||||
|
||||
*Figure 3. Add the SEMM certificate to a Surface UEFI reset package*
|
||||
|
||||
5. Click **Next**.
|
||||
6. Type the serial number of the device you want to unenroll from SEMM (as shown in Figure 4), and then click **Build** to generate the Surface UEFI reset package.
|
||||
|
||||

|
||||
|
||||
*Figure 4. Use the serial number of your Surface device to create a Surface UEFI reset package*
|
||||
|
||||
7. In the **Save As** dialog box, specify a name for the Surface UEFI reset package, browse to the location where you would like to save the file, and then click **Save**.
|
||||
8. When the package generation has completed, the **Successful** page is displayed. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
|
||||
|
||||
Run the Surface UEFI reset package Windows Installer (.msi) file on the Surface device to unenroll the device from SEMM. The reset package will require a reboot to perform the unenroll operation. After the device has been unenrolled, you can verify the successful removal by ensuring that the **Microsoft Surface Configuration Package** item in **Programs and Features** (shown in Figure 5) is no longer present.
|
||||
|
||||

|
||||
|
||||
*Figure 5. The presence of the Microsoft Surface Configuration Package item in Programs and Features indicates that the device is enrolled in SEMM*
|
||||
|
||||
## Unenroll a Surface device from SEMM with a Recovery Request
|
||||
|
||||
In some scenarios, a Surface UEFI reset package may not be a viable option to unenroll a Surface device from SEMM (for example, where Windows has become unusable). In these scenarios you can unenroll the device by using a Recovery Request generated from within Surface UEFI. The Recovery Request process can be initiated even on devices where you do not have the Surface UEFI password.
|
||||
|
||||
The Recovery Request process is initiated from Surface UEFI on the Surface device, approved with Microsoft Surface UEFI Configurator on another computer, and then completed in Surface UEFI. Like the reset package, approving a Recovery Request with Microsoft Surface UEFI Configurator requires access to the SEMM certificate that was used to enroll the Surface device.
|
||||
|
||||
To initiate a Recovery Request, follow these steps:
|
||||
|
||||
1. Boot the Surface device that is to be unenrolled from SEMM to Surface UEFI.
|
||||
2. Type the Surface UEFI password if you are prompted to do so.
|
||||
3. Click the **Enterprise management** page, as shown in Figure 6.
|
||||
|
||||

|
||||
|
||||
*Figure 6. The Enterprise management page is displayed in Surface UEFI on devices enrolled in SEMM*
|
||||
|
||||
4. Click or press **Get Started**.
|
||||
5. Click or press **Next** to begin the Recovery Request process.
|
||||
>**Note:** A Recovery Request expires two hours after it is created. If a Recovery Request is not completed in this time, you will have to restart the Recovery Request process.
|
||||
6. Select **SEMM Certificate** from the list of certificates displayed on the **Choose a SEMM reset key** page (shown in Figure 7), and then click or press **Next**.
|
||||
|
||||

|
||||
|
||||
*Figure 7. Choose SEMM Certificate for your Recovery Request (Reset Request)*
|
||||
|
||||
7. On the **Enter SEMM reset verification code** page you can click the **QR Code** or **Text** buttons to display your Recovery Request (Reset Request) as shown in Figure 8, or the **USB** button to save your Recovery Request (Reset Request) as a file to a USB drive, as shown in Figure 9.
|
||||
|
||||

|
||||
|
||||
*Figure 8. A Recovery Request (Reset Request) displayed as a QR Code*
|
||||
|
||||

|
||||
|
||||
*Figure 9. Save a Recovery Request (Reset Request) to a USB drive*
|
||||
|
||||
* To use a QR Code Recovery Request (Reset Request), use a QR reader app on a mobile device to read the code. The QR reader app will translate the QR code into an alphanumeric string. You can then email or message that string to the administrator that will produce the reset verification code with Microsoft Surface UEFI Configurator.
|
||||
* To use a Recovery Request (Reset Request) saved to a USB drive as a file, use the USB drive to transfer the file to the computer where Microsoft Surface UEFI Configurator will be used to produce the Reset Verification Code. The file can also be copied from the USB drive on another device to be emailed or transferred over the network.
|
||||
* To use the Recovery Request (Reset Request) as text, simply type the text directly into Microsoft Surface UEFI Configurator.
|
||||
|
||||
8. Open Microsoft Surface UEFI Configurator from the Start menu on another computer.
|
||||
>**Note:** Microsoft Surface UEFI Configurator must run in an environment that is able to authenticate the certificate chain for the SEMM certificate.
|
||||
9. Click **Start**.
|
||||
10. Click **Recovery Request**, as shown in Figure 10.
|
||||
|
||||

|
||||
|
||||
*Figure 10. Click Recovery Request to begin the process to approve a Recovery Request*
|
||||
|
||||
11. Click **Certificate Protection** to authenticate the Recovery Request with the SEMM certificate.
|
||||
12. Browse to and select your SEMM certificate file, and then click **OK**.
|
||||
13. When you are prompted to enter the certificate password as shown in Figure 11, type and confirm the password for the certificate file, and then click **OK**.
|
||||
|
||||

|
||||
|
||||
*Figure 11. Type the password for the SEMM certificate*
|
||||
|
||||
14. Click **Next**.
|
||||
15. Enter the Recovery Request (Reset Request), and then click **Generate** to create a reset verification code (as shown in Figure 12).
|
||||
|
||||

|
||||
|
||||
*Figure 12. Enter the Recovery Request (Reset Request)*
|
||||
|
||||
* If you displayed the Recovery Request (Reset Request) as text on the Surface device being reset, use the keyboard to type the Recovery Request (Reset Request) in the provided field.
|
||||
* If you displayed the Recovery Request (Reset Request) as a QR Code and then used a messaging or email application to send the code to the computer with Microsoft Surface UEFI Configurator, copy and paste the code into the provided field.
|
||||
* If you saved the Recovery Request (Reset Request) as a file to a USB drive, click the **Import** button, browse to and select the Recovery Request (Reset Request) file, and then click **OK**.
|
||||
|
||||
16. The reset verification code is displayed in Microsoft Surface UEFI Configurator, as shown in Figure 13.
|
||||
|
||||

|
||||
|
||||
*Figure 13. The reset verification code displayed in Microsoft Surface UEFI Configurator*
|
||||
|
||||
* Click the **Share** button to send the reset verification code by email.
|
||||
|
||||
17. Enter the reset verification code in the provided field on the Surface device (shown in Figure 8), and then click or press **Verify** to reset the device and unenroll the device from SEMM.
|
||||
18. Click or press **Restart now** on the **SEMM reset successful** page to complete the unenrollment from SEMM, as shown in Figure 14.
|
||||
|
||||

|
||||
|
||||
*Figure 14. Successful unenrollment from SEMM*
|
||||
|
||||
19. Click **End** in Microsoft Surface UEFI Configurator to complete the Recovery Request (Reset Request) process and close Microsoft Surface UEFI Configurator.
|
||||
|
||||
|
@ -57,7 +57,7 @@ AppLocker and Device Guard should run side-by-side in your organization, which o
|
||||
|
||||
**Device Guard with Credential Guard**
|
||||
|
||||
Although Credential Guard is not a feature within Device Guard, many organizations will likely deploy Credential Guard alongside Device Guard for additional protection against credential theft. Similar to virtualization-based protection of kernel mode code integrity, Credential Guard leverages hypervisor technology to protect domain credentials. This mitigation is targeted at resisting the use of pass-the-hash and pass-the-ticket techniques. By employing multifactor authentication with Credential Guard, organizations can gain additional protection against such threats. For information about how to deploy Credential Guard to your Windows 10 Enterprise clients, see the [Enable Credential Guard](#enable-cg) section. In addition to the client-side enablement of Credential Guard, organizations can deploy mitigations at both the CA and domain controller level to help prevent credential theft. Microsoft will be releasing details about these additional mitigations in the future.
|
||||
Although Credential Guard is not a feature within Device Guard, many organizations will likely deploy Credential Guard alongside Device Guard for additional protection against credential theft. Similar to virtualization-based protection of kernel mode code integrity, Credential Guard leverages hypervisor technology to protect domain credentials. This mitigation is targeted at resisting the use of pass-the-hash and pass-the-ticket techniques. By employing multifactor authentication with Credential Guard, organizations can gain additional protection against such threats. For information about how to deploy Credential Guard to your Windows 10 Enterprise clients, see the [Enable Credential Guard](#enable-cg) section. In addition to the client-side enablement of Credential Guard, organizations can deploy mitigations at both the CA and domain controller level to help prevent credential theft. Refer to the [Credential Guard](credential-guard.md) documentation for guidance on these additional mitigations.
|
||||
|
||||
**Unified manageability**
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create an enterprise data protection (EDP) policy (Windows 10)
|
||||
description: Microsoft Intune and System Center Configuration Manager (version 1606 or later) helps you create and deploy your enterprise data protection (EDP) policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network.
|
||||
description: Microsoft Intune and System Center Configuration Manager (version 1605 Technical Preview or later) helps you create and deploy your enterprise data protection (EDP) policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network.
|
||||
ms.assetid: d2059e74-94bd-4e54-ab59-1a7b9b52bdc6
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
@ -17,13 +17,13 @@ author: eross-msft
|
||||
|
||||
<span style="color:#ED1C24;">[Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.]</span>
|
||||
|
||||
Microsoft Intune and System Center Configuration Manager (version 1606 or later) helps you create and deploy your enterprise data protection (EDP) policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network.
|
||||
Microsoft Intune and System Center Configuration Manager (version 1605 Technical Preview or later) helps you create and deploy your enterprise data protection (EDP) policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network.
|
||||
|
||||
## In this section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Create an enterprise data protection (EDP) policy using Microsoft Intune](create-edp-policy-using-intune.md) |Intune helps you create and deploy your EDP policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network. |
|
||||
|[Create and deploy an enterprise data protection (EDP) policy using System Center Configuration Manager](create-edp-policy-using-sccm.md) |Configuration Manager (version 1606 or later) helps you create and deploy your EDP policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network. |
|
||||
|[Create and deploy an enterprise data protection (EDP) policy using System Center Configuration Manager](create-edp-policy-using-sccm.md) |Configuration Manager (version 1605 Technical Preview or later) helps you create and deploy your EDP policy, including letting you choose your protected apps, your EDP-protection level, and how to find enterprise data on the network. |
|
||||
|
||||
|
||||
|
||||
|
@ -38,7 +38,6 @@ To help faster deployments and increase the ease of managing Windows, Microsoft
|
||||
- Ensure that user and device configuration settings are compliant with the baseline.
|
||||
- Set configuration settings. For example, you can use Group Policy, System Center Configuration Manager, or Microsoft Intune to configure a device with the setting values specified in the baseline.
|
||||
|
||||
|
||||
## Where can I get the security baselines?
|
||||
|
||||
Here's a list of security baselines that are currently available.
|
||||
@ -50,7 +49,12 @@ To help faster deployments and increase the ease of managing Windows, Microsoft
|
||||
- [Windows 10, Version 1511 security baseline](http://go.microsoft.com/fwlink/p/?LinkID=799381)
|
||||
- [Windows 10, Version 1507 security baseline](http://go.microsoft.com/fwlink/p/?LinkID=799380)
|
||||
|
||||
|
||||
### Windows Server security baselines
|
||||
|
||||
- [Windows Server 2012 R2 security baseline](http://go.microsoft.com/fwlink/p/?LinkID=799382)
|
||||
|
||||
## How can I monitor the security baseline deployment on my servers?
|
||||
|
||||
Microsoft’s Operation Management Services (OMS) helps you monitor security baseline deployments across your servers. To find out more, check out [Operations Management Suite](https://aka.ms/omssecscm).
|
||||
|