diff --git a/devices/hololens/TOC.md b/devices/hololens/TOC.md index 9ee05419db..87ef48bb20 100644 --- a/devices/hololens/TOC.md +++ b/devices/hololens/TOC.md @@ -6,4 +6,5 @@ ## [Set up HoloLens in kiosk mode](hololens-kiosk.md) ## [Configure HoloLens using a provisioning package](hololens-provisioning.md) ## [Install apps on HoloLens](hololens-install-apps.md) +## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) ## [Change history for Microsoft HoloLens documentation](change-history-hololens.md) \ No newline at end of file diff --git a/devices/hololens/change-history-hololens.md b/devices/hololens/change-history-hololens.md index 0e8d411280..6b4a3479c5 100644 --- a/devices/hololens/change-history-hololens.md +++ b/devices/hololens/change-history-hololens.md @@ -8,13 +8,19 @@ ms.sitesec: library ms.pagetype: surfacehub author: jdeckerms ms.localizationpriority: medium -ms.date: 07/27/2017 +ms.date: 12/20/2017 --- # Change history for Microsoft HoloLens documentation This topic lists new and updated topics in the [Microsoft HoloLens documentation](index.md). +## December 2017 + +New or changed topic | Description +--- | --- +[Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | New + ## May 2017 | New or changed topic | Description | diff --git a/devices/hololens/hololens-encryption.md b/devices/hololens/hololens-encryption.md new file mode 100644 index 0000000000..aef7ea7f69 --- /dev/null +++ b/devices/hololens/hololens-encryption.md @@ -0,0 +1,123 @@ +--- +title: Enable Bitlocker encryption for HoloLens (HoloLens) +description: Enable Bitlocker device encryption to protect files stored on the HoloLens +ms.prod: w10 +ms.mktglfcycl: manage +ms.pagetype: hololens, devices +ms.sitesec: library +author: jdeckerms +ms.localizationpriority: medium +ms.date: 12/20/2017 +--- + +# Enable encryption for HoloLens + +You can enable [Bitlocker device encryption](https://docs.microsoft.com/windows/device-security/bitlocker/bitlocker-overview) to protect files and information stored on the HoloLens. Device encryption helps protect your data by encrypting it using AES-CBC 128 encryption method, which is equivalent to [EncryptionMethodByDriveType method 3](https://docs.microsoft.com/windows/client-management/mdm/bitlocker-csp#encryptionmethodbydrivetype) in the BitLocker configuration service provider (CSP). Only someone with the right encryption key (such as a password) can decrypt it or perform a data recovery. + + + +## Enable device encryption using MDM + +You can use your mobile device management (MDM) provider to apply a policy that requires device encryption. The policy used is the [Security/RequireDeviceEncryption setting](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-security#security-requiredeviceencryption) in the Policy CSP. + +In the following steps, Microsoft Intune is used as the example. For other MDM tools, see your MDM provider's documentation for instructions. + +1. Sign in to the [Microsoft Azure portal](https://portal.azure.com/). + +2. Use **Search** or go to **More services** to open the Intune blade. + +3. Go to **Device configuration > Profiles**, and select **Create profile**. + + ![Intune create profile option](images/encrypt-create-profile.png) + +4. Enter a name of your choice, select **Windows 10 and later** for the platform, select **Custom** for the profile type, and then select **Add**. + + ![Intune custom setting screen](images/encrypt-custom.png) + +5. In **Add Row OMA-URI Settings**, enter or select the following information: + - **Name**: a name of your choice + - **Description**: optional + - **OMA-URI**: `./Vendor/MSFT/Policy/Config/Security/RequireDeviceEncryption` + - **Data type**: integer + - **Value**: `1` + + ![Intune OMA-URI settings for encryption](images/encrypt-oma-uri.png) + +6. Select **OK**, select **OK**, and then select **Create**. The blade for the profile opens automatically. + +7. Select **Assignments** to assign the profile to a group. After you configure the assignment, select **Save**. + +![Intune profile assignment screen](images/encrypt-assign.png) + +## Enable device encryption using a provisioning package + +Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device. + +### Create a provisioning package that upgrades the Windows Holographic edition + +1. [Create a provisioning package for HoloLens.](hololens-provisioning.md#create-a-provisioning-package-for-hololens) + +2. Go to **Runtime settings** > **Policies** > **Security**, and select **RequireDeviceEncryption**. + + ![Require device encryption setting configured to yes](images/device-encryption.png) + +2. Browse to and select the XML license file that was provided when you purchased the Commercial Suite. + + >[!NOTE] + >You can configure [additional settings in the provisioning package](hololens-provisioning.md). + +3. On the **File** menu, click **Save**. + +4. Read the warning that project files may contain sensitive information, and click **OK**. + + >[!IMPORTANT] + >When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed. + +3. On the **Export** menu, click **Provisioning package**. + +4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next**. + +5. Set a value for **Package Version**. + + >[!TIP] + >You can make changes to existing packages and change the version number to update previously applied packages. + +6. On the **Select security details for the provisioning package**, click **Next**. + +7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location. + + Optionally, you can click Browse to change the default output location. + +8. Click **Next**. + +9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status. + +10. When the build completes, click **Finish**. + + +### Apply the provisioning package to HoloLens + +1. Connect the device via USB to a PC and start the device, but do not continue past the **fit** page of the initial setup experience (the first page with the blue box). + +2. Briefly press and release the **Volume Down** and **Power** buttons simultaneously. + +3. HoloLens will show up as a device in File Explorer on the PC. + +4. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage. + +5. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page. + +6. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package. + +7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with device setup. + +>[!NOTE] +>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. + +## Verify device encryption + +Encryption is silent on HoloLens. To verify the device encryption status: + +- On HoloLens, go to **Settings** > **System** > **About**. **Bitlocker** is **enabled** if the device is encrypted. + +![About screen showing Bitlocker enabled](images/about-encryption.png) diff --git a/devices/hololens/hololens-provisioning.md b/devices/hololens/hololens-provisioning.md index cb53fd496d..44d24432f7 100644 --- a/devices/hololens/hololens-provisioning.md +++ b/devices/hololens/hololens-provisioning.md @@ -96,7 +96,7 @@ When you run ADKsetup.exe for Windows 10, version 1607, select **Configuration D 7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE. >[!NOTE] ->If the device was purchased before August 2016, you will need to sign into the device with aa Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. +>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. ## What you can configure diff --git a/devices/hololens/hololens-upgrade-enterprise.md b/devices/hololens/hololens-upgrade-enterprise.md index 32af3eb056..d85bb461aa 100644 --- a/devices/hololens/hololens-upgrade-enterprise.md +++ b/devices/hololens/hololens-upgrade-enterprise.md @@ -71,7 +71,7 @@ For more information about groups, see [Use groups to manage users and devices i ## Edition upgrade using a provisioning package -Provisioning packages are files created by the Windows Imaging and Configuration Designer (ICD) tool that apply a specified configuration to a device. +Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device. ### Create a provisioning package that upgrades the Windows Holographic edition @@ -106,7 +106,7 @@ Provisioning packages are files created by the Windows Imaging and Configuration 7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location. - Optionally, you can click Browse to change the default output location. + Optionally, you can click **Browse** to change the default output location. 8. Click **Next**. @@ -132,7 +132,7 @@ Provisioning packages are files created by the Windows Imaging and Configuration 7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with device setup. >[!NOTE] ->If the device was purchased before August 2016, you will need to sign into the device with aa Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. +>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package. diff --git a/devices/hololens/images/about-encryption.png b/devices/hololens/images/about-encryption.png new file mode 100644 index 0000000000..348e493503 Binary files /dev/null and b/devices/hololens/images/about-encryption.png differ diff --git a/devices/hololens/images/device-encryption.PNG b/devices/hololens/images/device-encryption.PNG new file mode 100644 index 0000000000..651429dfe0 Binary files /dev/null and b/devices/hololens/images/device-encryption.PNG differ diff --git a/devices/hololens/images/encrypt-assign.png b/devices/hololens/images/encrypt-assign.png new file mode 100644 index 0000000000..f5b0c85a3c Binary files /dev/null and b/devices/hololens/images/encrypt-assign.png differ diff --git a/devices/hololens/images/encrypt-create-profile.png b/devices/hololens/images/encrypt-create-profile.png new file mode 100644 index 0000000000..b0f06ef40f Binary files /dev/null and b/devices/hololens/images/encrypt-create-profile.png differ diff --git a/devices/hololens/images/encrypt-custom.png b/devices/hololens/images/encrypt-custom.png new file mode 100644 index 0000000000..b3635e9ee4 Binary files /dev/null and b/devices/hololens/images/encrypt-custom.png differ diff --git a/devices/hololens/images/encrypt-oma-uri.png b/devices/hololens/images/encrypt-oma-uri.png new file mode 100644 index 0000000000..e2754b7db4 Binary files /dev/null and b/devices/hololens/images/encrypt-oma-uri.png differ