mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 13:23:36 +00:00
Merge remote-tracking branch 'upstream/master' into v-miegge/manage-surface-driver
This commit is contained in:
v-miegge
@ -18,7 +18,7 @@
|
||||
## [Getting around HoloLens (1st gen)](hololens1-basic-usage.md)
|
||||
## [HoloLens (1st Gen) release notes](hololens1-release-notes.md)
|
||||
|
||||
# Deploy HoloLens and mixed-reality apps in commercial environments
|
||||
# Deploy HoloLens and mixed reality apps in commercial environments
|
||||
## [Commercial features](hololens-commercial-features.md)
|
||||
## [Deploy HoloLens in a commercial environment](hololens-requirements.md)
|
||||
## [Determine what licenses you need](hololens-licenses-requirements.md)
|
||||
@ -29,13 +29,13 @@
|
||||
## [Manage HoloLens updates](hololens-updates.md)
|
||||
## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
|
||||
|
||||
# Navigating Windows Holographic
|
||||
## [Start menu and mixed reality home](holographic-home.md)
|
||||
## [Use your voice with HoloLens](hololens-cortana.md)
|
||||
# Navigate the Windows Holographic environment
|
||||
## [Use the Start menu and mixed reality home](holographic-home.md)
|
||||
## [Use your voice to operate HoloLens](hololens-cortana.md)
|
||||
## [Find, open, and save files](holographic-data.md)
|
||||
## [Create mixed reality photos and videos](holographic-photos-and-videos.md)
|
||||
|
||||
# User management and access management
|
||||
# Manage users and access
|
||||
## [Manage user identity and sign-in for HoloLens](hololens-identity.md)
|
||||
## [Share your HoloLens with multiple people](hololens-multiple-users.md)
|
||||
## [Set up HoloLens as a kiosk](hololens-kiosk.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Start menu and mixed reality home
|
||||
title: Use the Start menu and mixed reality home
|
||||
description: Navigate the mixed reality home in Windows Holographic.
|
||||
ms.assetid: 742bc126-7996-4f3a-abb2-cf345dff730c
|
||||
ms.date: 08/07/2019
|
||||
@ -15,7 +15,7 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Start menu and mixed reality home
|
||||
# Use the Start menu and mixed reality home
|
||||
|
||||
Just like the Windows PC experience starts with the desktop, Windows Holographic starts with mixed reality home. Using the Start menu you can open and place app windows, immersive app launchers, and 3D content in mixed reality home, and their placement in your physical space will be remembered.
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ HoloLens 2 prompts a user to calibrate the device under the following circumstan
|
||||
|
||||
|
||||
|
||||
During this process, you'll look at a set of targets (gems). It's fine if you blink or close your eyes during calibration but try not to stare at other objects in the room. This allows HoloLens to learn about your eye position to render your holographic world.
|
||||
During this process, you'll look at a set of targets (gems). It's fine if you blink during calibration, but try to stay focused on the gems instead of other objects in the room. This allows HoloLens to learn about your eye position to render your holographic world.
|
||||
|
||||
|
||||
|
||||
@ -52,7 +52,7 @@ If calibration was successful, you'll see a success screen. If not, read more a
|
||||
|
||||
### Calibration when sharing a device or session
|
||||
|
||||
Multiple users can share a HoloLens 2 device, without a need for each person to go through device setup. When a new user puts the device on their head for th first time, HoloLens 2 automatically prompts the user to calibrate visuals. When a user that has previously calibrated visuals puts the device on their head, the display seamlessly adjusts for quality and a comfortable viewing experience.
|
||||
Multiple users can share a HoloLens 2 device, without a need for each person to go through device setup. When a new user puts the device on their head for the first time, HoloLens 2 automatically prompts the user to calibrate visuals. When a user that has previously calibrated visuals puts the device on their head, the display seamlessly adjusts for quality and a comfortable viewing experience.
|
||||
|
||||
### Manually starting the calibration process
|
||||
|
||||
@ -84,7 +84,7 @@ If calibration is unsuccessful try:
|
||||
- Moving objects in your visor out of the way (such as hair)
|
||||
- Turning on a light in your room or moving out of direct sunlight
|
||||
|
||||
If you followed all guidelines and calibration is still failing, please let us know by filing feedback in [Feedback Hub](hololens-feedback.md).
|
||||
If you followed all guidelines and calibration is still failing, you can disable the calibration prompt in Settings. Please also let us know by filing feedback in [Feedback Hub](hololens-feedback.md).
|
||||
|
||||
Note that setting IPD is not applicable for Hololens 2, since eye positions are computed by the system.
|
||||
|
||||
@ -92,6 +92,8 @@ Note that setting IPD is not applicable for Hololens 2, since eye positions are
|
||||
|
||||
Calibration information is stored locally on the device and is not associated with any account information. There is no record of who has used the device without calibration. This mean new users will get prompted to calibrate visuals when they use the device for the first time, as well as users who opted out of calibration previously or if calibration was unsuccessful.
|
||||
|
||||
The device can locally store up to 50 calibration profiles. After this number is reached, the device automatically deletes the oldest unused profile.
|
||||
|
||||
Calibration information can always be deleted from the device in **Settings** > **Privacy** > **Eye tracker**.
|
||||
|
||||
### Disable calibration
|
||||
|
||||
@ -45,10 +45,15 @@ HoloLens (1st gen) supports the following classes of Bluetooth devices:
|
||||
### HoloLens (1st gen): Pair the clicker
|
||||
|
||||
1. Use the bloom gesture to go to **Start**, and then select **Settings**.
|
||||
|
||||
1. Select **Devices**, and make sure that Bluetooth is on.
|
||||
|
||||
1. Use the tip of a pen to press and hold the clicker pairing button until the clicker status light blinks white. Make sure to hold down the button until the light starts blinking.
|
||||
|
||||
The pairing button is on the underside of the clicker, next to the finger loop.
|
||||
|
||||
|
||||
|
||||
1. On the pairing screen, select **Clicker** > **Pair**.
|
||||
|
||||
## HoloLens 2: Connect USB-C devices
|
||||
@ -64,7 +69,7 @@ HoloLens 2 supports the following classes of USB-C devices:
|
||||
- Combination PD hubs (USB A plus PD charging)
|
||||
|
||||
> [!NOTE]
|
||||
> Some mobile devices with USB-C connections present themselves to the HoloLens as ethernet adaptors, and therefore could be used in a tethering configuration, starting with the 20H1 OS. USB LTE modems that require a separate driver, and/or application installed for configuration are not supported
|
||||
> Some mobile devices with USB-C connections present themselves to the HoloLens as ethernet adaptors, and therefore could be used in a tethering configuration, starting with Windows Holographic, version 2004. USB LTE modems that require a separate driver, and/or application installed for configuration are not supported
|
||||
|
||||
## Connect to Miracast
|
||||
|
||||
@ -77,3 +82,10 @@ To use Miracast, follow these steps:
|
||||
|
||||
1. On the list of devices that appears, select an available device.
|
||||
1. Complete the pairing to begin projecting.
|
||||
|
||||
## Disable Bluetooth
|
||||
|
||||
This procedure turns off the RF components of the Bluetooth radio and disables all Bluetooth functionality on Microsoft HoloLens.
|
||||
|
||||
1. Use the bloom gesture (HoloLens (1st gen)) or the start gesture (HoloLens 2) to go to **Start**, and then select **Settings** > **Devices**.
|
||||
1. Move the slider switch for **Bluetooth** to the **Off** position.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use your voice with HoloLens
|
||||
title: Use your voice to operate HoloLens
|
||||
description: Cortana can help you do all kinds of things on your HoloLens
|
||||
ms.assetid: fd96fb0e-6759-4dbe-be1f-58bedad66fed
|
||||
ms.date: 03/10/2020
|
||||
@ -17,7 +17,7 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Use your voice with HoloLens
|
||||
# Use your voice to operate HoloLens
|
||||
|
||||
You can use your voice to do almost anything on HoloLens, such as taking a quick photo or opening an app. Many voice commands are built into HoloLens, while others are available through Cortana.
|
||||
|
||||
@ -34,14 +34,14 @@ Get around HoloLens faster with these basic commands. In order to use these, you
|
||||
|
||||
### General speech commands
|
||||
|
||||
Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying “select.”
|
||||
Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying "select."
|
||||
|
||||
> [!NOTE]
|
||||
> Hand rays are not supported on HoloLens (1st Gen).
|
||||
|
||||
| Say this | To do this |
|
||||
| - | - |
|
||||
| "Select" | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say “select” again. |
|
||||
| "Select" | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say "select" again. |
|
||||
|Open the Start menu | "Go to Start" |
|
||||
|Close the Start menu | "Close" |
|
||||
|Leave an immersive app | Say "Go to Start" to bring up the quick actions menu, then say "Mixed reality home." |
|
||||
|
||||
@ -41,7 +41,7 @@ When auto-enrollment is enabled, no additional manual enrollment is needed. When
|
||||
1. Select **Enroll into device management** and enter your organizational account. You will be redirected to your organization's sign in page.
|
||||
1. Upon successful authentication to the MDM server, a success message is shown.
|
||||
|
||||
Your device is now enrolled with your MDM server. The device will need to restart to acquire policies, certificates, and apps. The Settings app will now reflect that the device is enrolled in device management.
|
||||
Your device is now enrolled with your MDM server. The Settings app will now reflect that the device is enrolled in device management.
|
||||
|
||||
## Unenroll HoloLens from Intune
|
||||
|
||||
|
||||
@ -4,7 +4,11 @@ description: Create actionable feedback for HoloLens and Windows Mixed Reality d
|
||||
ms.assetid: b9b24c72-ff86-44a9-b30d-dd76c49479a9
|
||||
author: mattzmsft
|
||||
ms.author: mazeller
|
||||
ms.date: 09/13/2019
|
||||
ms.date: 05/14/2020
|
||||
ms.custom:
|
||||
- CI 116157
|
||||
- CSSTroubleshooting
|
||||
audience: ITPro
|
||||
ms.prod: hololens
|
||||
ms.topic: article
|
||||
keywords: feedback, bug, issue, error, troubleshoot, help
|
||||
@ -15,68 +19,66 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Give us feedback
|
||||
# Feedback for HoloLens
|
||||
|
||||
Use the Feedback Hub to tell us which features you love, which features you could do without, or when something could be better.
|
||||
Use the Feedback Hub to tell us which features you love, which features you could do without, and how something could be better. The engineering team uses the same mechanism internally to track and fix bugs, so please use Feedback Hub to report any bugs that you see. We are listening!
|
||||
|
||||
## Feedback for Windows Mixed Reality immersive headset on PC
|
||||
Feedback Hub is an excellent way to alert the engineering team to bugs and to make sure that future updates are healthier and more consistently free of bugs. However, Feedback Hub does not provide a response. If you need immediate help, please file feedback, take note of the summary that you provided for your feedback, and then follow up with [HoloLens support](https://support.microsoft.com/supportforbusiness/productselection?sapid=e9391227-fa6d-927b-0fff-f96288631b8f).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Before you report an issue, make sure that your environment meets the following requirements so that you can successfully upload logs and other information:
|
||||
>
|
||||
> - Have a minimum of 3GB free disk space available on the main drive of the device.
|
||||
> - To upload cabs or other large files, connect to a non-metered network.
|
||||
> [!NOTE]
|
||||
>
|
||||
> - Make sure you that you have the current version of Feedback Hub. To do this, select **Start** > **Microsoft Store**, and then select the ellipses (**...**). Then, select **Downloads and updates** > **Get updates**.
|
||||
>
|
||||
> - To provide the best possible data for fixing issues, we highly recommended that you set your device telemetry to **Full**. You can set this value during the Out-of-Box-Experience (OOBE), or by using the Settings app. To do this by using Settings, select **Start** > **Settings** > **Privacy** > **App Diagnostics** > **On**.
|
||||
|
||||
1. Make sure that you have the immersive headset connected to your PC, and then on the desktop, select **Feedback Hub**.
|
||||
1. In the left pane, select **Feedback**.
|
||||
|
||||
1. To enter new feedback, select **Add new feedback**.
|
||||
|
||||
1. To make feedback actionable, in **What kind of feedback is this?** select **Problem**.
|
||||
1. In **Summarize your issue**, enter a meaningful title for your feedback.
|
||||
1. In **Give us more detail**, provide details and repro steps.
|
||||
|
||||
## Use the Feedback Hub
|
||||
|
||||
As the top category, select **Mixed Reality**. Then select an applicable subcategory, as explained in the following table:
|
||||
|
||||
|Subcategory |Description |
|
||||
|----------|----------|
|
||||
| Apps | Issues about a specific application. |
|
||||
| Developer | Issues about authoring or running an app for Mixed Reality. |
|
||||
| Device | Issues about the head-mounted device (HMD) itself. |
|
||||
| Home experience | Issues about your VR environment and your interactions with the your mixed reality home. |
|
||||
| Input | Issues about input methods, such as motion controllers, speech, gamepad, or mouse and keyboard. |
|
||||
| Set up | Anything that is preventing you from setting up the device. |
|
||||
| All other issues | Anything else. |
|
||||
|
||||
1. If possible, add traces or video to your feedback to help us identify and fix the issue more quickly. To do this, follow these steps:
|
||||
1. To start collecting traces, select **Start capture**. The app starts collecting traces and a video capture of your mixed reality scenario.
|
||||
|
||||
|
||||
1. Do not close the Feedback Hub app, but switch to the scenario that produces the issue. Run through the scenario to produce the circumstances that you have described.
|
||||
1. After you finish your scenario, go back to the Feedback Hub app and select **Stop capture**. The app stops collecting information, stores the information in a file, and attaches the file to your feedback.
|
||||
1. Select **Submit**.
|
||||
|
||||
The Thank You page indicates that your feedback has been successfully submitted.
|
||||
|
||||
1. Use the **Start** gesture to open the **Start** menu, and then select **Feedback Hub**. The app opens in your environment.
|
||||
|
||||
To easily direct other people (such as co-workers, Microsoft staff, [forum](https://forums.hololens.com/) readers et al) to the issue, go to **Feedback** > **My Feedback**, select the issue, select **Share**. This action provides a shortened URL that you can give to others so that they can upvote or escalate your issue.
|
||||
|
||||
> [!NOTE]
|
||||
> If you don't see **Feedback Hub**, select **All Apps** to see the complete list of apps on the device.
|
||||
|
||||
## Feedback for HoloLens
|
||||
1. To see whether someone else has given similar feedback, enter a few keywords about the topic in the **Feedback** search box.
|
||||
1. If you find similar feedback, select it, add any additional information that you have in the **Write a comment** box, and then select **Upvote**.
|
||||
1. If you don't find any similar feedback, select **Add new feedback**.
|
||||
|
||||
1. Use the **bloom** gesture to open the **Start** menu, and then select **Feedback Hub**.
|
||||
|
||||
|
||||
|
||||
1. Place the app in your environment and then select the app to launch it.
|
||||
1. To see if someone else has given similar feedback, in the Feedback search box, enter a few keywords about the topic.
|
||||
1. In **Summarize your feedback**, enter a short summary of your feedback. Then add details in the **Explain in more detail** box. The more details that you provide, such as how to reproduce this problem and the effect that it has, the more useful your feedback is. When you're finished, select **Next**.
|
||||
|
||||
|
||||
1. If you find similar feedback, select it, add any details, then select **Upvote**.
|
||||
1. Select a topic from **Choose a category**, and then select a subcategory from **Select a subcategory**. The following table describes the categories that are available in the Windows Holographic category.
|
||||
|
||||
|
||||
1. If you don’t find any similar feedback, select **Add new feedback**, select a topic from **Select a category**, and then select a subcategory from **Select a subcategory**.
|
||||
> [!NOTE]
|
||||
> **Commercial customers**: To report a bug that is related to MDM, provisioning, or any other device management aspect, select the **Enterprise Management** category, and the **Device** subcategory.
|
||||
|
||||
|
||||
1. Enter your feedback.
|
||||
1. If you are reporting a reproducible issue, you can select **Reproduce**. Without closing Feedback Hub, reproduce the issue. After you finish, come back to Feedback Hub and select **I’m done**. The app adds a mixed reality capture of your repro and relevant diagnostic logs to your feedback.
|
||||
1. Select **Post feedback**, and you’re done.
|
||||
|Category |Description |
|
||||
| --- | --- |
|
||||
|Eye tracking |Feedback about eye tracking, iris sign-in, or calibration. |
|
||||
|Hologram accuracy, stability, and reliability |Feedback about how holograms appear in space. |
|
||||
|Launching, placing, adjusting, and exiting apps |Feedback about starting or stopping 2D or 3D apps. |
|
||||
|Miracast |Feedback about Miracast. |
|
||||
|Spaces and persistence |Feedback about how HoloLens recognizes spaces and retains holograms in space. |
|
||||
|Start menu and all apps list |Feedback about the **Start** menu and the all apps list. |
|
||||
|Surface mapping |Feedback about surface mapping. |
|
||||
|Taking pictures and videos |Feedback about mixed reality captures. |
|
||||
|Video hologram playback |Feedback about video hologram playback. |
|
||||
|All other issues |All other issues. |
|
||||
|
||||
1. You may be prompted to search for similar feedback. If your problem resembles feedback from other users, select that feedback. Otherwise, select **New feedback** and then select **Next**.
|
||||
|
||||
1. If you are prompted, select the best description of the problem.
|
||||
|
||||
1. Attach any relevant data to your feedback, or reproduce the problem. You can select any of the following options:
|
||||
|
||||
- **Attach a screenshot**. Select this option to attach a screenshot that illustrates the situation that you're describing.
|
||||
- **Attach a file**. Select this option to attach data files. If you have files that are relevant to your problem or that could help us to reproduce your problem, attach them.
|
||||
- **Recreate my problem**. Select this option if you can reproduce the problem yourself. After you select **Recreate my problem**, follow these steps:
|
||||
|
||||
1. Select **Include data about** and make sure that the most relevant types of data are listed. In most cases, the default selections are based on the category and subcategory that you selected for your feedback.
|
||||
1. Select **Start Recording**.
|
||||
|
||||
1. Reproduce your problem. Don’t worry if this means that you have to enter an immersive app. You will return to the feedback page when you're done.
|
||||
1. Select **Stop recording**. After recording stops, you can see the data that is attached to your feedback for the engineering team.
|
||||
|
||||
1. Make sure that you have an active internet connection so that we can receive your feedback. Select **Submit**, and you’re done.
|
||||
|
||||
@ -132,7 +132,7 @@ Many Windows apps now support both dark and light modes, and HoloLens 2 customer
|
||||
- 3D Viewer
|
||||
- Movies & TV
|
||||
|
||||
|
||||
|
||||
|
||||
### System voice commands
|
||||
|
||||
|
||||
@ -71,7 +71,7 @@ Review the "[Requirements](https://docs.microsoft.com/windows/deployment/windows
|
||||
Before you start the OOBE and provisioning process, make sure that the HoloLens devices meet the following requirements:
|
||||
|
||||
- The devices are not already members of Azure AD, and are not enrolled in Intune (or another MDM system). The Autopilot self-deploying process completes these steps. To make sure that all the device-related information is cleaned up, check the **Devices** pages in both Azure AD and Intune.
|
||||
- Every device can connect to the internet. You can use a wired or wireless connection.
|
||||
- Every device can connect to the internet. You can "USB C to Ethernet" adapters for wired internet connectivity or "USB C to Wifi" adapters for wireless internet connectivity.
|
||||
- Every device can connect to a computer by using a USB-C cable, and that computer has the following available:
|
||||
- Advanced Recovery Companion (ARC)
|
||||
- The latest Windows update: Windows 10, version 19041.1002.200107-0909 or a later version)
|
||||
@ -185,24 +185,7 @@ The Enrollment Status Page (ESP) displays the status of the complete device conf
|
||||
|
||||
|
||||
|
||||
### 8. Configure a custom configuration profile for HoloLens devices (known issue)
|
||||
|
||||
1. In [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com), select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
1. For **Platform**, specify **Windows 10 and later**, and for **Profile**, select **Custom**.
|
||||
1. Select **Create**.
|
||||
1. Enter a name for the profile, and then select **Settings** > **Configure**.
|
||||
|
||||
|
||||
1. Select **Add**, and then specify the following information:
|
||||
|
||||
- **Name**: SidecarPath
|
||||
- **OMA-URI**: ./images/Device/Vendor/MSFT/EnrollmentStatusTracking/DevicePreparation/PolicyProviders/Sidecar/InstallationState
|
||||
- **Data type**: Integer
|
||||
- **Value**: 2
|
||||
1. Select **OK** two times, and then select **Create** to create the profile.
|
||||
1. After Intune creates the configuration profile, assign the configuration profile to the device group for the HoloLens devices.
|
||||
|
||||
### 9. Verify the profile status of the HoloLens devices
|
||||
### 8. Verify the profile status of the HoloLens devices
|
||||
|
||||
1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment** > **Devices**.
|
||||
1. Verify that the HoloLens devices are listed, and that their profile status is **Assigned**.
|
||||
@ -234,7 +217,7 @@ At the end of OOBE, you can sign in to the device by using your user name and pa
|
||||
|
||||
## Known Issues
|
||||
|
||||
- The list of supported languages for Autopilot deployment profiles includes languages that HoloLens does not support. Select a language that [HoloLens supports](hololens2-language-support.md).
|
||||
- You cannot install applications that use the device security context.
|
||||
|
||||
## Feedback
|
||||
|
||||
|
||||
BIN
devices/hololens/images/DarkMode.jpg
Normal file
BIN
devices/hololens/images/DarkMode.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 104 KiB |
BIN
devices/hololens/images/hololens-feedback-1.png
Normal file
BIN
devices/hololens/images/hololens-feedback-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 343 KiB |
BIN
devices/hololens/images/hololens-start-feedback.png
Normal file
BIN
devices/hololens/images/hololens-start-feedback.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
BIN
devices/hololens/images/hololens2-feedbackhub-tile.png
Normal file
BIN
devices/hololens/images/hololens2-feedbackhub-tile.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
@ -53,7 +53,7 @@ appliesto:
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can share a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection) | Create a new support request for the business support team. |
|
||||
| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection?sapid=e9391227-fa6d-927b-0fff-f96288631b8f) | Create a new support request for the business support team. |
|
||||
| [More support options](https://support.microsoft.com/products/hololens) | Connect with Microsoft support resources for HoloLens in the enterprise. |
|
||||
|
||||
## Related resources
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Create Surface Hub 2S device account"
|
||||
description: "This page describes the procedure for creating the Surface Hub 2S device account."
|
||||
title: Create Surface Hub 2S device account
|
||||
description: This page describes the procedure for creating the Surface Hub 2S device account.
|
||||
keywords: separate values with commas
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
@ -15,15 +15,18 @@ ms.localizationpriority: Medium
|
||||
|
||||
# Create Surface Hub 2S device account
|
||||
|
||||
Creating a Surface Hub device account (also known as a Room mailbox) allows Surface Hub 2S to receive, approve, or decline meeting requests and join meetings using Microsoft Teams or Skype for Business. Configure the device account during OOBE setup. If needed you can change it later (without going through OOBE setup).
|
||||
Creating a Surface Hub device account (also known as a Room mailbox) allows Surface Hub 2S to receive, approve, or decline meeting requests and join meetings using either Microsoft Teams or Skype for Business. Configure the device account during Out-of-Box Experience (OOBE) setup. If needed, you can change it later (without going through OOBE setup).
|
||||
|
||||
Unlike standard Room mailboxes that remain disabled by default, you need to enable the Surface Hub 2S device account to sign on to Microsoft Teams and Skype for Business. Surface Hub 2S relies on Exchange ActiveSync, which requires an ActiveSync mailbox policy on the device account. Apply the default ActiveSync mailbox policy that comes with Exchange Online.
|
||||
|
||||
Create the account using the Microsoft 365 admin center or by using PowerShell. You can use Exchange Online PowerShell to configure specific features including:
|
||||
Create the account by using the Microsoft 365 admin center or by using PowerShell. You can use Exchange Online PowerShell to configure specific features including:
|
||||
|
||||
- Calendar processing for every Surface Hub device account.
|
||||
- Custom auto replies to scheduling requests.
|
||||
- If the default ActiveSync mailbox policy has already been modified by someone else or another process, you will likely have to create and assign a new ActiveSync mailbox policy
|
||||
- If the default ActiveSync mailbox policy has already been modified by someone else or by another process, you will likely have to create and assign a new ActiveSync mailbox policy.
|
||||
|
||||
> [!NOTE]
|
||||
> The Surface Hub device account doesn’t support third-party Federated Identity Providers (FIPs) and must be a standard Active Directory or Azure Active Directory account.
|
||||
|
||||
## Create account using Microsoft 365 admin center
|
||||
|
||||
@ -31,17 +34,17 @@ Create the account using the Microsoft 365 admin center or by using PowerShell.
|
||||
|
||||
2. Provide a name and email address for the device account. Leave remaining settings unchanged in the default state.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
3. Set the password for the device account. To set the password, choose **Users** and then select **Active Users**. Now search for the newly created user to set the password. Ensure that you **do not** select the option **Make this user change their password when they first sign in.**
|
||||
|
||||
|
||||
|
||||
|
||||
4. Assign the room with an Office 365 license. It’s recommended to assign the Office 365 **Meeting Room** license, a new option that automatically enables the account for Skype for Business Online and Microsoft Teams.
|
||||
|
||||
|
||||
|
||||
|
||||
### Finalize setup via PowerShell
|
||||
|
||||
@ -50,6 +53,7 @@ Create the account using the Microsoft 365 admin center or by using PowerShell.
|
||||
- **Microsoft Teams and Skype for Business Calendar:** Set [**Calendar Auto processing**](https://docs.microsoft.com/surface-hub/surface-hub-2s-account?source=docs#set-calendar-auto-processing) for this account.
|
||||
|
||||
## Create account using PowerShell
|
||||
|
||||
Instead of using the Microsoft Admin Center portal, you can create the account using PowerShell.
|
||||
|
||||
### Connect to Exchange Online PowerShell
|
||||
@ -59,13 +63,13 @@ $365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
|
||||
$ImportResults = Import-PSSession $365Session
|
||||
```
|
||||
|
||||
### Create a new Room Mailbox
|
||||
### Create a new Room mailbox
|
||||
|
||||
```powershell
|
||||
New-Mailbox -MicrosoftOnlineServicesID account@YourDomain.com -Alias SurfaceHub2S -Name SurfaceHub2S -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String "<Enter Strong Password>" -AsPlainText -Force)
|
||||
```
|
||||
|
||||
### Set Calendar Auto processing
|
||||
### Set Calendar auto-processing
|
||||
|
||||
```powershell
|
||||
Set-CalendarProcessing -Identity "account@YourDomain.com" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This room is equipped with a Surface Hub"
|
||||
@ -81,7 +85,7 @@ Set-MsolUserLicense -UserPrincipalName "account@YourDomain.com" -AddLicenses "co
|
||||
|
||||
## Connect to Skype for Business Online using PowerShell
|
||||
|
||||
### Install prerequisites
|
||||
### Install pre-requisites
|
||||
|
||||
- [Visual C++ 2017 Redistributable](https://aka.ms/vs/15/release/vc_redist.x64.exe)
|
||||
- [Skype for Business Online PowerShell Module](https://www.microsoft.com/download/confirmation.aspx?id=39366)
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: separate values with commas
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
|
||||
@ -37,7 +37,7 @@ This update is specific to the Surface Hub 2S and provides the driver and firmwa
|
||||
* Improves system stability.
|
||||
* Surface System driver - 1.7.139.0
|
||||
* Improves system stability.
|
||||
* Surface SMC Firmware update - 1.173.139.0
|
||||
* Surface SMC Firmware update - 1.176.139.0
|
||||
* Improves system stability.
|
||||
</details>
|
||||
|
||||
|
||||
@ -29,6 +29,7 @@
|
||||
|
||||
### [Deploy Surface devices](deploy.md)
|
||||
### [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md)
|
||||
### [Windows Virtual Desktop on Surface](windows-virtual-desktop-surface.md)
|
||||
### [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
|
||||
### [Surface Pro X app compatibility](surface-pro-arm-app-performance.md)
|
||||
### [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)
|
||||
@ -37,7 +38,6 @@
|
||||
### [Enable the Surface Laptop keyboard during MDT deployment](enable-surface-keyboard-for-windows-pe-deployment.md)
|
||||
### [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)
|
||||
### [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
|
||||
### [Using the Surface Deployment Accelerator deployment share](using-the-sda-deployment-share.md)
|
||||
### [Surface System SKU reference](surface-system-sku-reference.md)
|
||||
|
||||
## Manage
|
||||
|
||||
@ -11,7 +11,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -11,7 +11,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, store
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Surface System SKU Reference
|
||||
|
||||
@ -11,7 +11,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -11,7 +11,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
@ -52,8 +52,8 @@ landingContent:
|
||||
url: microsoft-surface-deployment-accelerator.md
|
||||
- text: Autopilot and Surface devices
|
||||
url: windows-autopilot-and-surface-devices.md
|
||||
- text: Deploying, managing, and servicing Surface Pro X
|
||||
url: surface-pro-arm-app-management.md
|
||||
- text: Windows Virtual Desktop on Surface
|
||||
url: windows-virtual-desktop-surface.md
|
||||
|
||||
# Card
|
||||
- title: Manage Surface devices
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -11,7 +11,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.audience: itpro
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: devices, surface
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
|
||||
@ -10,7 +10,7 @@ ms.mktglfcycl: support
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 09/26/2019
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 5/06/2020
|
||||
ms.reviewer: brrecord
|
||||
@ -16,7 +16,7 @@ audience: itpro
|
||||
|
||||
# Surface Book 3 Quadro RTX 3000 technical overview
|
||||
|
||||
Surface Book 3 for Business powered by the NVIDIA® Quadro RTX™ 3000 GPU is built for professionals who need real-time rendering, AI acceleration, and advanced graphics and compute performance in a portable form factor. Quadro RTX 3000 fundamentally changes what you can do with the new Surface Book 3:
|
||||
Surface Book 3 for Business powered by the NVIDIA® Quadro RTX™ 3000 GPU is built for professionals who need real-time rendering, AI acceleration, advanced graphics, and compute performance in a portable form factor. Quadro RTX 3000 fundamentally changes what you can do with the new Surface Book 3:
|
||||
|
||||
- **Ray Tracing** - Produce stunning renders, designs and animations faster than ever before with 30 RT Cores for hardware-accelerated ray tracing.
|
||||
- **Artificial Intelligence** - Remove redundant, tedious tasks and compute intensive work with 240 Tensor Cores for GPU-accelerated AI.
|
||||
@ -133,4 +133,4 @@ Surface Book 3 with Quadro RTX 3000 delivers the best graphics performance on an
|
||||
|
||||
- [Surface Book 3 GPU technical overview](surface-book-GPU-overview.md)
|
||||
- [Surface for Business](https://www.microsoft.com/surface/business)
|
||||
- [Microsoft Cognitive Toolkit (CNTK)](https://docs.microsoft.com/cognitive-toolkit/)
|
||||
- [Microsoft Cognitive Toolkit (CNTK)](https://docs.microsoft.com/cognitive-toolkit/)
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: cottmca
|
||||
manager: laurawi
|
||||
|
||||
@ -8,14 +8,14 @@ ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 5/06/2020
|
||||
ms.date: 5/29/2020
|
||||
ms.reviewer: brrecord
|
||||
manager: laurawi
|
||||
audience: itpro
|
||||
---
|
||||
# What’s new in Surface Dock 2
|
||||
|
||||
Surface Dock 2, the next generation Surface dock, lets users connect external monitors and multiple peripherals to obtain a fully modernized desktop experience from a Surface device. Built to maximize efficiency at the office, in a flexible workspace, or at home, Surface Dock 2 features seven ports, including two front-facing USB-C ports, with 15 watts of fast charging power for phone and accessories. Surface Dock 2 is designed to simplify IT management, enabling admins to automate firmware updates using Windows Update or centralize updates with internal software distribution tools. An extended set of management tools will be released via Windows update upon commercial distribution.
|
||||
Surface Dock 2, the next generation Surface dock, lets users connect external monitors and multiple peripherals to obtain a fully modernized desktop experience from a Surface device. Built to maximize efficiency at the office, in a flexible workspace, or at home, Surface Dock 2 features seven ports, including two front-facing USB-C ports, with 15 watts of fast charging power for phone and accessories. Surface Dock 2 is designed to simplify IT management, enabling admins to automate firmware updates using Windows Update or centralize updates with internal software distribution tools. Surface Enterprise Management Mode (SEMM) now enables IT admins to secure ports on Surface Dock 2. For more information, see [Secure Surface Dock 2 ports with Surface Enterprise Management Mode](https://techcommunity.microsoft.com/t5/surface-it-pro-blog/secure-surface-dock-2-ports-with-surface-enterprise-management/ba-p/1418999).
|
||||
|
||||
## General system requirements
|
||||
|
||||
@ -28,8 +28,7 @@ Surface Dock 2, the next generation Surface dock, lets users connect external mo
|
||||
- Surface Book 2
|
||||
- Surface Laptop 2
|
||||
- Surface Go
|
||||
- Surface Go with LTE Advanced
|
||||
- Surface Studio 2
|
||||
- Surface Go with LTE Advanced
|
||||
- Surface Pro 7
|
||||
- Surface Laptop 3
|
||||
- Surface Book 3
|
||||
@ -86,7 +85,7 @@ Surface Dock 2, the next generation Surface dock, lets users connect external mo
|
||||
|Surflink|Yes|Yes|
|
||||
|USB-A|2 front facing USB 3.1 Gen 1<br>2 rear facing USB 3.1 Gen 1|2 rear facing USB 3.2 Gen 2 (7.5W power)|
|
||||
|Mini Display port|2 rear facing (DP1.2)|None|
|
||||
|USB-C|None|2 front facing USB 3.2 Gen 2<br>[15W power]<br>2 rear facing USB 3.2 Gen 2 (DP1.4a)<br>[7.5W power]|
|
||||
|USB-C|None|2 front facing USB 3.2 Gen 2<br>(15W power)<br>2 rear facing USB 3.2 Gen 2 (DP1.4a)<br>(7.5W power)|
|
||||
|3.5 mm Audio in/out|Yes|Yes|
|
||||
|Ethernet|Yes, 1 gigabit|Yes 1 gigabit|
|
||||
|DC power in|Yes|Yes|
|
||||
@ -99,20 +98,18 @@ Surface Dock 2, the next generation Surface dock, lets users connect external mo
|
||||
|Wake-on-LAN from Connected Standby<sup>1</sup>|Yes|Yes|
|
||||
|Wake-on-LAN from S4/S5 sleep modes|No|Yes|
|
||||
|Network PXE boot|Yes|Yes|
|
||||
|SEMM host access control|No|Coming in Windows Update<sup>2</sup>|
|
||||
|SEMM port access control<sup>3</sup>|No|Coming in Windows Update|
|
||||
|SEMM host access control|No|Yes
|
||||
|SEMM port access control<sup>2</sup>|No|Yes|
|
||||
|Servicing support|MSI|Windows Update or MSI|
|
||||
||||
|
||||
|
||||
1. *Devices must be configured for Wake on LAN via Surface Enterprise Management Mode (SEMM) or Device Firmware Control Interface (DFCI) to wake from Hibernation or Power-Off states. Wake from Hibernation or Power-Off is supported on Surface Pro 7, Surface Laptop 3, Surface Pro X, Surface Book 3, and Surface Go 2. Software license required for some features. Sold separately.*
|
||||
|
||||
2. *Pending release via Windows Update.*
|
||||
|
||||
3. *Software license required for some features. Sold separately.*
|
||||
2. *Software license required for some features. Sold separately.*
|
||||
|
||||
## Streamlined device management
|
||||
|
||||
Following the public announcement of Surface Dock 2, Surface will release streamlined management functionality via Windows Update enabling IT admins to utilize the following enterprise-grade features:
|
||||
Surface has released streamlined management functionality via Windows Update enabling IT admins to utilize the following enterprise-grade features:
|
||||
|
||||
- **Frictionless updates**. Update your docks silently and automatically, with Windows Update or Microsoft Endpoint Configuration Manager, (formerly System Center Configuration Manager - SCCM) or other MSI deployment tools.
|
||||
- **Wake from the network**. Manage and access corporate devices without depending on users to keep their devices powered on. Even when a docked device is in sleep, hibernation, or power off mode, your team can wake from the network for service and management, using Endpoint Configuration Manager or other enterprise management tools.
|
||||
@ -120,5 +117,6 @@ Following the public announcement of Surface Dock 2, Surface will release stream
|
||||
|
||||
## Next steps
|
||||
|
||||
- [Secure Surface Dock 2 ports with Surface Enterprise Management Mode](https://techcommunity.microsoft.com/t5/surface-it-pro-blog/secure-surface-dock-2-ports-with-surface-enterprise-management/ba-p/1418999)
|
||||
- [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
||||
- [Best practice power settings for Surface devices](maintain-optimal-power-settings-on-Surface-devices.md)
|
||||
|
||||
@ -9,11 +9,11 @@ ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: scottmca
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
audience: itpro
|
||||
ms.date: 05/11/2020
|
||||
ms.date: 05/26/2020
|
||||
---
|
||||
|
||||
# Microsoft Surface Enterprise Management Mode
|
||||
@ -228,14 +228,27 @@ create a reset package using PowerShell to reset SEMM.
|
||||
|
||||
## Version History
|
||||
|
||||
The latest version of SEMM released May 11, 2020 includes:
|
||||
### Version 2.71.139.0
|
||||
|
||||
This version of SEMM adds support for Surface Dock 2 management features for Surface Book 3, Surface Laptop 3, and Surface Pro 7 including:
|
||||
|
||||
- Enabling audio (locking/unlocking), Ethernet and USB ports
|
||||
- Ability to create dock packages for both authenticated and unauthenticated hosts
|
||||
|
||||
### Version 2.70.130.0
|
||||
|
||||
This version of SEMM includes:
|
||||
|
||||
- Support for Surface Go 2
|
||||
- Support for Surface Book 3
|
||||
- Bug fixes
|
||||
|
||||
### Version 2.59.
|
||||
* Support to Surface Pro 7, Surface Pro X, and Surface Laptop 3 13.5" and 15" models with Intel processor. Note: Surface Laptop 3 15" AMD processor is not supported.
|
||||
- Support to Wake on Power feature
|
||||
|
||||
### Version 2.59.139.0
|
||||
|
||||
* Support for Surface Pro 7, Surface Pro X, and Surface Laptop 3 13.5" and 15" models with Intel processor. Note: Surface Laptop 3 15" AMD processor is not supported.
|
||||
|
||||
- Support for Wake on Power feature
|
||||
|
||||
### Version 2.54.139.0
|
||||
* Support to Surface Hub 2S
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 11/13/2019
|
||||
ms.reviewer: jesko
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: manage
|
||||
ms.localizationpriority: high
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 4/15/2020
|
||||
ms.reviewer: jessko
|
||||
|
||||
@ -6,7 +6,7 @@ ms.localizationpriority: medium
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 10/03/2019
|
||||
ms.reviewer: jessko
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 03/09/2020
|
||||
ms.reviewer:
|
||||
|
||||
@ -7,7 +7,7 @@ ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.audience: itpro
|
||||
ms.localizationpriority: medium
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: tokatz
|
||||
manager: laurawi
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,172 +0,0 @@
|
||||
---
|
||||
title: Using the Microsoft Surface Deployment Accelerator deployment share (Surface)
|
||||
description: Explore the scenarios where you can use SDA to meet the deployment needs of your organization including Proof of Concept, pilot deployment, as well as import additional drivers and applications.
|
||||
keywords: deploy, install, automate, deployment solution
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
---
|
||||
|
||||
# Using the Microsoft Surface Deployment Accelerator deployment share
|
||||
|
||||
With Microsoft Surface Deployment Accelerator (SDA), you can quickly and easily set up a deployment solution that is ready to deploy Windows to Surface devices. The prepared environment is built on powerful deployment technologies available from Microsoft, such as the [Microsoft Deployment Toolkit (MDT)](https://technet.microsoft.com/windows/dn475741), and is capable of immediately performing a deployment after configuration. See [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator) for a comprehensive walkthrough of using the SDA wizard to set up a deployment share and perform a deployment.
|
||||
|
||||
For more information about SDA and information on how to download SDA, see [Microsoft Surface Deployment Accelerator (SDA)](https://technet.microsoft.com/itpro/surface/microsoft-surface-deployment-accelerator).
|
||||
|
||||
> [!NOTE]
|
||||
> SDA is not supported on Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information refer to [Deploy Surface devices](deploy.md).
|
||||
|
||||
Using SDA provides these primary benefits:
|
||||
|
||||
* With SDA, you can create a ready-to-deploy environment that can deploy to target devices as fast as your download speeds allow. The wizard experience enables you to check a few boxes and then the automated process builds your deployment environment for you.
|
||||
|
||||
* With SDA, you prepare a deployment environment built on the industry leading deployment solution of MDT. With MDT you can scale from a relatively basic deployment of a few Surface devices to a solution capable of deploying to thousands of devices including all of the different makes and models in your organization and all of the applications required by each device and user.
|
||||
|
||||
This article explores four scenarios where you can use SDA to meet the needs of your organization. See [Deploy Windows 10](https://technet.microsoft.com/itpro/windows/deploy/index) to explore the capabilities of MDT and the Windows deployment technologies available from Microsoft in greater detail.
|
||||
|
||||
## Perform a Proof of Concept deployment
|
||||
|
||||
One of the primary scenarios for use of SDA is as a Proof of Concept. A *Proof of Concept* (PoC) enables you to test or evaluate the capabilities of a solution or technology. A PoC is often used to illustrate the benefits of the solution or technology to decision makers. For example, if you want to recommend Surface devices as a replacement of older point of sale (POS) systems, you could perform a PoC to demonstrate how Surface devices provide superior computing power, flexibility, and connectivity when compared to alternate options.
|
||||
|
||||
Using SDA to prepare a PoC of Surface devices enables you to very quickly prepare a demonstration of Surface device or devices, which gives you more time for customization or preparation. The flexibility of SDA even lets you import resources, like applications and drivers, from existing MDT deployment infrastructure. See the [Work with existing deployment shares](#work-with-existing-deployment-shares) section later in this article for more information.
|
||||
|
||||
SDA is also an excellent PoC of the capabilities of MDT. SDA demonstrates just how quickly an MDT deployment environment can be prepared and made ready for deployment to devices. It also shows just how flexible and customizable the MDT solution can be, with support for Windows 10 and Windows 8.1, for Microsoft Store and desktop applications, and several models of Surface devices.
|
||||
|
||||
Some recommendations for a successful PoC with SDA are:
|
||||
|
||||
* Keep your SDA deployment environment separate from your production network. This ensures optimal performance and reduces potential for conflicts during your PoC deployment.
|
||||
|
||||
* Use a fresh and updated instance of Windows Server to house your SDA deployment share to maintain the simplicity and performance of the demonstration environment.
|
||||
|
||||
* Test the deployment process before you demonstrate your PoC. This reduces the potential for unexpected situations and keeps the demonstration focused on the deployment process and Surface devices.
|
||||
|
||||
* Use offline files with SDA to further reduce installation times.
|
||||
|
||||
* For help with your PoC, contact [Surface Support](https://www.microsoft.com/surface/support/contact-us-business).
|
||||
|
||||
## Perform a pilot deployment
|
||||
|
||||
A pilot deployment differs from a PoC. Where a PoC is usually a closed demonstration that is performed prior to the deployment process in order to get approval for the use of certain technologies or solutions, a *pilot deployment* is performed during the deployment process as a limited scope deployment for testing and validation. The focus of a pilot deployment can be as narrow as only a handful of devices, or wide enough to include a significant portion of your organization.
|
||||
|
||||
>[!NOTE]
|
||||
>A pilot deployment should not replace the testing process that should be performed regularly in the lab as the deployment environment is built and developed. A deployment solution should be tested in virtual and physical environments as new applications and drivers are added and when task sequences are modified and before a pilot deployment is performed.
|
||||
|
||||
For example, you are tasked with deploying Surface devices to mobile workers and you want to test the organization’s MDT deployment process by providing a small number of devices to executives. You can use SDA to create an isolated Surface deployment environment and then copy the task sequence, applications, and drivers needed from the production deployment share. This not only enables you to quickly create a Surface deployment, but it also minimizes the risk to the production deployment process used for other types of devices.
|
||||
|
||||
For small organizations, the pilot deployment environment of SDA may suffice as a complete deployment solution. Even if you do not have an existing deployment environment, you can import drivers and applications (covered later in this article) to provide a complete deployment solution based on MDT. Even without previous knowledge of MDT or Windows deployment, you can follow the [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator) article to get started with a deployment to Surface devices.
|
||||
|
||||
## Import additional drivers
|
||||
|
||||
The SDA deployment share includes all of the drivers needed for Surface devices. This includes the drivers for the components inside the Surface device, such as the wireless network adapter and the main chipset, as well as drivers for Surface accessories, such as the Surface Dock or Surface USB Ethernet adapters. The SDA deployment share does not, however, include drivers for third-party devices or peripherals.
|
||||
|
||||
For example, you may intend to use your Surface device with a thermal printer, credit card reader, and barcode scanner as a POS terminal. In this scenario, the thermal printer, credit card reader, and barcode scanner will very likely require installation of drivers to operate properly. You could potentially download and install these drivers from Windows Update when each peripheral is connected, or you could install the driver package from the manufacturer manually on each Surface device, but the ideal solution is to have these drivers already present in Windows so that when the peripheral is connected, it will just work.
|
||||
|
||||
Because SDA is built on MDT, adding the drivers to the SDA deployment share is easy and simple.
|
||||
|
||||
>[!NOTE]
|
||||
>The drivers must be in the Setup Information File (.inf) format. If the drivers for your device come as an executable file (.exe), they may need to be extracted or installed to procure the .inf file. Some device drivers come packaged with applications, for example an all-in-one printer bundled with scan software. These applications will need to be installed separately from the drivers.
|
||||
|
||||
To import drivers for a peripheral device:
|
||||
|
||||
1. Download the drivers for your device from the manufacturer web site.
|
||||
|
||||
2. Open the MDT Deployment Workbench.
|
||||
|
||||
3. Expand the **Deployment Shares** node and expand the SDA deployment share.
|
||||
|
||||
4. Expand the **Out-of-Box Drivers** folder.
|
||||
|
||||
5. Select the folder of the Surface model for which you would like to include this driver.
|
||||
|
||||
6. Click **Import Drivers** to start the Import Drivers Wizard, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Provide the location of your driver files*
|
||||
|
||||
7. The Import Drivers Wizard presents a series of steps:
|
||||
|
||||
- **Specify Directory** – Click **Browse** and navigate to the folder where you stored the drivers in Step 1.
|
||||
- **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
|
||||
- **Progress** – While the drivers are imported, a progress bar is displayed on this page.
|
||||
- **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the Import Drivers Wizard.
|
||||
|
||||
8. Repeat Steps 5-7 for each Surface model on which you would like to include this driver.
|
||||
|
||||
9. Close the Deployment Workbench.
|
||||
|
||||
After the drivers are imported for the Surface model, the deployment task sequence will automatically select the drivers during the deployment process and include them in the Windows environment. When you connect your device, such as the barcode scanner in the example, Windows should automatically detect the device and you should be able to use it immediately.
|
||||
|
||||
>[!NOTE]
|
||||
>You can even import drivers for other computer makes and models to support other devices. See **Step 5: Prepare the drivers repository** in [Deploy a Windows 10 image using MDT 2013 Update 2](https://technet.microsoft.com/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt) for more information about how to import drivers for other makes and models.
|
||||
|
||||
## Import additional applications
|
||||
|
||||
As with drivers, the SDA deployment share can be pre-configured with apps like the Surface App and Microsoft Office 365. You can also add applications to the SDA deployment share and configure them to be installed on your Surface devices during deployment of Windows. In the ideal scenario, your Surface devices deployed with the SDA deployment share will include all of the applications needed to be ready for your end users.
|
||||
|
||||
In the previous example for including drivers for a POS system, you would also need to include POS software for processing transactions and recording the input from the barcode scanner and credit card reader. To import an application and prepare it for installation on your Surface devices during Windows deployment:
|
||||
|
||||
1. Download the application installation files or locate the installation media for your application.
|
||||
|
||||
2. Determine the command line instruction for silent installation, usually provided by the developer of the application. For Windows Installer files (.msi), see [Standard Installer Command-Line Options](https://msdn.microsoft.com/library/windows/desktop/aa372024) in the Windows Dev Center.
|
||||
|
||||
3. Open the MDT Deployment Workbench.
|
||||
|
||||
4. Expand the **Deployment Shares** node and expand the SDA deployment share.
|
||||
|
||||
5. Expand the **Applications** folder.
|
||||
|
||||
6. Click **New Application** to start the New Application Wizard, as shown in Figure 2.
|
||||
|
||||
|
||||
|
||||
*Figure 2: Provide the command to install your application*
|
||||
|
||||
7. Follow the steps of the New Application Wizard:
|
||||
|
||||
- **Application Type** – Click **Application with Source Files**, and then click **Next**.
|
||||
- **Details** – Enter a name for the application in the **Application Name** field. Enter publisher, version, and language information in the **Publisher**, **Version**, and **Language** fields if desired. Click **Next**.
|
||||
- **Source** – Click **Browse** to navigate to and select the folder with the application installation files procured in Step 1, and then click **Next**.
|
||||
- **Destination** – Enter a name for the folder where the application files will be stored in the **Specify the Name of the Directory that Should Be Created** field or click **Next** to accept the default name.
|
||||
- **Command Details** – Enter the silent command-line instruction, for example `setup.msi /quiet /norestart`
|
||||
- **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
|
||||
- **Progress** – While the installation files are imported, a progress bar is displayed on this page.
|
||||
- **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the New Application Wizard.
|
||||
|
||||
8. Click the **Task Sequences** folder, right-click **1 - Deploy Microsoft Surface**, and then click **Properties**.
|
||||
|
||||
9. Click the **Task Sequence** tab to view the steps that are included in the new task sequence.
|
||||
|
||||
10. Select the **Windows Update (Pre-Application Installation)** step, and then click **Add**.
|
||||
|
||||
11. Hover the mouse over **General** under the **Add** menu, and then click **Install Application**. This will add a new step after the selected step for the installation of a specific application as shown in Figure 3.
|
||||
|
||||
|
||||
|
||||
*Figure 3. A new Install Application step for Sample POS App*
|
||||
|
||||
12. On the **Properties** tab of the new **Install Application** step, enter **Install - Sample POS App** in the **Name** field, where *Sample POS App* is the name of your app.
|
||||
|
||||
13. Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
|
||||
|
||||
14. Select your app from the list of applications, and then click **OK**.
|
||||
|
||||
15. Click **OK** to close the task sequence properties.
|
||||
|
||||
16. Close the Deployment Workbench.
|
||||
|
||||
## Work with existing deployment shares
|
||||
|
||||
One of the many benefits of an MDT deployment share is the simplicity of how deployment resources are stored. The MDT deployment share is, at its core, just a standard network file share. All deployment resources, such as Windows images, application installation files, and drivers, are stored in a share that can be browsed with File Explorer, copied and pasted, and moved just like any other file share, provided that you have the necessary permissions. This makes working with deployment resources extremely easy. MDT even allows you to make it easier by allowing you to open multiple deployment shares from the Deployment Workbench and to transfer or copy resources between them.
|
||||
|
||||
This ability gives SDA some extra capabilities when used in an environment with an existing MDT infrastructure. For example, if you install SDA on an isolated server to prepare a PoC and then log on to your production MDT deployment share from the Deployment Workbench on your SDA server, you can copy applications, drivers, task sequences, and other components into the SDA deployment share that is prepared with Surface apps and drivers. With this process, in a very short amount time, you can have a deployment environment ready to deploy your organization’s precise requirements to Surface devices.
|
||||
|
||||
You can also use this capability in reverse. For example, you can copy the Surface drivers, deployment task sequences, and apps directly into a lab or testing environment following a successful PoC. Using these resources, you can immediately begin to integrate Surface deployment into your existing deployment infrastructure.
|
||||
@ -8,7 +8,7 @@ ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
author: coveminer
|
||||
ms.author: v-jokai
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: scottmca
|
||||
manager: laurawi
|
||||
|
||||
158
devices/surface/windows-virtual-desktop-surface.md
Normal file
158
devices/surface/windows-virtual-desktop-surface.md
Normal file
@ -0,0 +1,158 @@
|
||||
---
|
||||
title: Windows Virtual Desktop on Surface
|
||||
description: This article explains how Surface devices deliver an ideal end node for Windows Virtual Desktop solutions, providing customers with flexible form factors, Windows 10 modern device security and manageability, and support for persistent, on-demand & just-in-time work scenarios.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.date: 5/20/2020
|
||||
ms.reviewer: rohenr
|
||||
manager: laurawi
|
||||
audience: itpro
|
||||
---
|
||||
|
||||
# Windows Virtual Desktop on Surface
|
||||
|
||||
## Introduction
|
||||
|
||||
Windows Virtual Desktop on Surface lets you run Virtual Desktop Infrastructure (VDI) on a Surface device blurring the lines between the local desktop experience and the virtual desktop where touch, pen, ink, and biometric authentication span both physical and virtual environments. Representing another milestone in the evolution of computing, Windows Virtual Desktop on Surface <a href="#1"><sup>1</sup></a> combines Microsoft 365 - virtualized in the Azure cloud - with the advanced security protections, enterprise-level manageability, and enhanced productivity tools of Windows 10 on Surface. This fusion of premium form factor and Virtual Desktop Infrastructure in Azure provides exceptional customer value across user experiences, portability, security, business continuity, and modern management.
|
||||
|
||||
### Windows Virtual Desktop
|
||||
|
||||
Windows Virtual Desktop (WVD) is a comprehensive desktop and app virtualization service running in the Azure cloud. It’s the only virtual desktop infrastructure that delivers simplified management, multi-session Windows 10, optimizations for Office 365 ProPlus, and support for Remote Desktop Services (RDS) environments. With WVD you can quickly deploy and scale Windows desktops and apps on Azure and get built-in security and compliance features.
|
||||
|
||||
### Windows Virtual Desktop partner integrations
|
||||
|
||||
For a list of approved partner providers and independent software vendors for Windows Virtual Desktop, see [Windows Virtual Desktop partner integrations](https://docs.microsoft.com/azure/virtual-desktop/partners). Some partners also provide Virtual Desktop as a Service (DaaS). DaaS frees you from having to maintain your own virtual machines (VMs) by providing a fully managed, turnkey desktop and virtualization service. The ability to deliver customized desktops to users anywhere in the world enables companies to quickly adjust to changing market conditions by spinning up cloud desktops on-demand - when and where they’re needed.
|
||||
|
||||
## Microsoft Surface Devices
|
||||
|
||||
Surface engineering has long set new standards for innovation by going beyond the keyboard and mouse to imagine more natural ways of interacting with devices, whether by touch, voice, ink, or Surface Dial. And with chip-to-cloud integration of Microsoft 365 and the security and manageability of Windows 10 Pro, Surface delivers connected hardware, software, apps, and services the way they were intended. Although it’s possible to run WVD from Windows devices dating back to Windows 7, Microsoft Surface devices provide unique advantages including support for:
|
||||
|
||||
- **Flexible form factors** - like 2-in-1 devices such as Surface Go 2, Surface Pro 7 and Surface Pro X with pen, touch and detachable keyboard.
|
||||
- **Persistent, on-demand and just-in-time work scenarios** - with offline and on-device access for more productive experiences.
|
||||
- **Windows 10 modern device security and manageability** - providing the flexibility to be productive anywhere.
|
||||
|
||||
## Flexible form factors and premium user experience
|
||||
|
||||
The Microsoft Surface for Business family comprises a diverse portfolio of form factors including traditional laptops, all-in-one machines, and 2-in-1 devices. Surface devices deliver experiences people love with the choice and flexibility they need in order to work on their terms.
|
||||
|
||||
### The modern virtual desktop endpoint
|
||||
|
||||
Surface 2-in-1 devices, including [Surface Go 2](https://www.microsoft.com/p/surface-go-2) (10.5”), [Surface Pro 7](https://www.microsoft.com/surface/devices/surface-pro-7/) (12”) and [Surface Pro X](https://www.microsoft.com/p/surface-pro-x/) (13”), provide users with the ideal cloud desktop endpoint bringing together the optimal balance of portability, versatility, power, and all-day battery. From site engineers relying on Surface Go 2 in tablet mode to financial advisors attaching Surface Pro 7 to a dock and multiple monitors, 2-in-1 devices deliver the versatility that has come to define the modern workplace.
|
||||
|
||||
Unlike traditional, fixed VDI “terminals”, Surface devices allow users to work from anywhere and enable companies to remain viable and operational during unforeseen events -- from severe weather to public health emergencies. With support for persistent, on-demand and just-in-time scenarios, Surface devices effectively help companies sustain ongoing operations and mitigate risk from disruptive events. Features designed to enhance productivity on Surface 2-in-1 devices include:
|
||||
|
||||
- Vibrant, high resolution displays with 3:2 aspect ratio to get work done.
|
||||
- Natural inking and multi-touch for more immersive experiences.
|
||||
- With a wide variety of built-in and third-party accessibility features, Surface devices let you choose how to interact with your device, express ideas, and get work done.
|
||||
- Far-field mics and high-performance speakers for improved virtual meetings.
|
||||
- Biometric security including built-in, Windows Hello camera that comes standard on every Surface device.
|
||||
- Long battery life <a href="#2"><sup>2</sup></a> and fast charging.
|
||||
- LTE options <a href="#3"><sup>3</sup></a> on modern devices like Surface Pro X and Surface Go 2 for hassle-free and secure connectivity.
|
||||
- Support for a wide range of peripherals such as standard printers, 3D printers, cameras, credit card readers, barcode scanners, and many others. A large ecosystem of Designed for Surface partners provides licensed and certified Surface accessories.
|
||||
- Broad range of Device Redirection support.
|
||||
|
||||
### Device Redirection Support
|
||||
|
||||
The Surface-centric productivity experiences listed above become even more compelling in Windows Virtual Desktop environments by taking advantage of device redirection capabilities with Windows 10. Surface provides a broad range of device redirection support, especially when compared to OEM thin clients and fixed terminals, Android, iOS/macOS and Web-based access. The Windows Inbox (MSTSC) and Windows Desktop (MSRDC) clients provide the most device redirection capabilities including Input Redirection (keyboard, mouse, pen and touch), Port Redirection (serial and USB) and Other Redirections (cameras, clipboard, local drive/storage, location, microphones, printers, scanners, smart cards and speakers). For a detailed comparison of device redirection support refer to the [device redirection documentation](https://docs.microsoft.com/windows-server/remote/remote-desktop-services/clients/remote-desktop-app-compare#redirection-support).
|
||||
|
||||
### Familiar Desktop Experience
|
||||
|
||||
Not only does running the Windows Desktop Client on Surface devices provide users with a broad set of device redirection capabilities, it lets everyone launch apps in familiar ways — directly from the Start Menu or Search bar.
|
||||
|
||||
### Persistent, on-demand and just-in-time work scenarios
|
||||
|
||||
Windows Virtual Desktop on Surface helps customers meet increasingly complex business and security requirements across industries, employee roles, and work environments. These include:
|
||||
|
||||
- Multi-layered security of access to data and organizational resources.
|
||||
- Compliance with industry regulations.
|
||||
- Support for an increasingly elastic workforce.
|
||||
- Employee-specific needs across a variety of job functions.
|
||||
- Ability to support specialized, processor-intensive workloads.
|
||||
- Resilience for sustaining operations during disruptions.
|
||||
|
||||
### Table 1. Windows Virtual Desktop business conversations
|
||||
|
||||
| Security & regulation | Elastic workforce | Work Roles | Special workloads | Business continuity |
|
||||
| ---------------------------------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------- |
|
||||
| - Financial Services<br>- Healthcare<br>- Government | - Merger & acquisition<br>- Short term employees<br>- Contractors & partners | - BYOD & mobile<br>- Customer support/service<br>- Branch workers | - Design & engineering<br>- Support for legacy apps<br>- Software dev & test | - On demand<br>- Just-in-Time (JIT)<br>- Work @ Home |
|
||||
|
||||
### Offline and on-device access for more productive experiences
|
||||
|
||||
Traditionally, VDI solutions only work when the endpoint is connected to the internet. But what happens when the internet or power is unavailable for any reason (due to mobility, being on a plane, or power outages, and so on)?
|
||||
|
||||
To support business continuity and keep employees productive, Surface devices can easily augment the virtual desktop experience with offline access to files, Microsoft 365 and third-party applications. Traditional apps like Microsoft Office, available across .x86, x64, Universal Windows Platform, ARM platforms, enable users to stay productive in “offline mode”. Files from the virtual desktop cloud environment can be synced locally on Surface using OneDrive for Business for offline access as well. You can have the confidence that all locally “cached” information is up-to-date and secure.
|
||||
|
||||
In addition to adding support for offline access to apps and files, Surface devices are designed to optimize collaborative experiences like Microsoft Teams “On-Device”. Although some VDI solutions support the use of Teams through a virtual session, users can benefit from the more optimized experience provided by a locally installed instance of Teams. Localizing communications and collaboration apps for multimedia channels like voice, video, live captioning allows organizations to take full advantage of Surface devices’ ability to provide optimized Microsoft 365 experiences. The emergence of Surface artificial intelligence (AI) or “AI-on-device” brings new capabilities to life, such as eye gaze technology that adjusts the appearance of your eyes so the audience sees you looking directly at the camera when communicating via video.
|
||||
|
||||
An alternative to locally installing traditional applications is to take advantage of the latest version of Microsoft Edge, which comes with support for Progressive Web Apps (PWA). PWAs are just websites that are progressively enhanced to function like native apps on supporting platforms. The qualities of a PWA combine the best of the web and native apps by additional features, such as push notifications, background data refresh, offline support, and more.
|
||||
|
||||
### Virtual GPUs
|
||||
|
||||
GPUs are ideal for AI compute and graphics-intensive workloads, helping customers to fuel innovation through scenarios like high-end remote visualization, deep learning, and predictive analytics. However, this isn’t ideal for professionals who need to work remotely or while on the go because varying degrees of internal GPU horsepower are tied to the physical devices, limiting mobility and flexibility.
|
||||
|
||||
To solve for this Azure offers the N-series family of Virtual Machines with NVIDIA GPU capabilities (vGPU). With vGPUs, IT can either share GPU performance across multiple virtual machines, or power demanding workloads by assigning multiple GPUs to a single virtual machine. For Surface this means that no matter what device you’re using, from the highly portable Surface Go 2 to the slim and stylish Surface Laptop 3, your device has access to powerful server-class graphics performance. Surface and vGPUs allow you to combine all the things you love about Surface, to include pen, touch, keyboard, trackpad and PixelSense displays, with graphics capability only available in high performance computing environments.
|
||||
|
||||
Azure N-series brings these capabilities to life on your Surface device allowing you to work in any way you want, wherever you go. [Learn more about Azure N-Series and GPU optimized virtual machine sizes.](https://docs.microsoft.com/azure/virtual-machines/sizes-gpu)
|
||||
|
||||
## Microsoft 365 and Surface
|
||||
|
||||
Even in a virtualized desktop environment, Microsoft 365 and Surface deliver the experiences employees love, the protection organizations demand, and flexibility for teams to work their way. According to Forrester Research: <a href="#4"><sup>4</sup></a>
|
||||
|
||||
- Microsoft 365-powered Surface devices give users up to 5 hours in weekly productivity gains with up to 9 hours saved per week for highly mobile workers, providing organizations with 112 percent ROI on Microsoft 365 with Surface
|
||||
- 75 percent agree Microsoft 365-powered Surface devices help improve employee satisfaction and retention
|
||||
- agree that Microsoft 365- powered Surface devices have helped improve employee satisfaction and retention.
|
||||
|
||||
### Security and management
|
||||
|
||||
From chip to cloud, Microsoft 365 and Surface helps organizations stay protected and up to date.
|
||||
With both Surface hardware and software designed, built, and tested by Microsoft, users can be confident they’re productive and protected by leading technologies from chip to cloud. With increased numbers of users working remotely, protecting corporate data and intellectual property becomes more paramount than ever. Windows Virtual Desktop on Surface is designed around a zero-trust security model in which every access request is strongly authenticated, authorized within policy constraints, and inspected for anomalies before granting access.
|
||||
|
||||
By maximizing efficiencies from cloud computing, modern management enables IT to better serve the needs of users, stakeholders and customers in an increasingly competitive business environment. For example, you can get Surface devices up-and-running with minimal interaction from your team. Setup is automatic and self-serviced. Updates are quick and painless for both your team and your users. You can manage devices regardless of their physical location.
|
||||
|
||||
Security and management features delivered with Windows Virtual Desktop on Surface include:
|
||||
|
||||
- **Windows Update.** Keeping Windows up to date helps you stay ahead of new security threats. Windows 10 has been engineered from the ground up to be more secure and utilize the latest hardware capabilities to improve security. With a purpose-built UEFI <a href="#5"><sup>5</sup></a> and Windows Update for Business that responds to evolving threats, end-to-end protection is secure and simplified.
|
||||
|
||||
- **Hardware encryption.** Device encryption lets you protect the data on your Surface so it can only be accessed by authorized individuals. All Surface for Business devices feature a discrete Trusted Platform Module (dTPM) that is hardware-protected against intrusion while software uses protected keys and measurements to verify software validity.
|
||||
- **Windows Defender.** Windows Defender Antivirus brings together machine learning, big-data analysis, in-depth threat resistance research, and the Microsoft cloud infrastructure to protect devices. The tool is built in and needs no extra agents to be deployed on-devices or in the VDI environment, simplifying management and optimizing device start up. Windows Defender is built in and needs no extra agents to be deployed on-device or in the VDI environment, simplifying management and optimizing device start up. The true out-of-the-box experience.
|
||||
- **Removable drives** - A subset of newer Surface devices feature removable SSD drives <a href="#6"><sup>6</sup></a> providing greater control over data retention.
|
||||
- **Modern authentication -** Microsoft 365 and Surface is a unified platform delivering every Windows security feature (subject to licensing and enablement). All Surface portfolio devices ship with a custom-built camera, designed for Windows Hello for Business providing biometric security that persists seamlessly from on-device to VDI-based experiences.
|
||||
- **Modern firmware management** -Using Device Firmware Configuration Interface (DFCI),<a href="#7"><sup>7</sup></a> IT administrators can remotely disable hardware elements at a firmware level such as mics, USB ports, SD card slots, cameras, and Bluetooth which removes power to the peripheral. Windows Defender Credential Guard uses virtualization-based security so that only privileged system software can access them.
|
||||
- **Backward and forward compatibility** - Windows 10 devices provide backward and forward compatibility across hardware, software and services. Microsoft has a strong history of maintaining legacy support of hardware, peripherals, software and services while incorporating the latest technologies. Businesses can plan IT investments to have a long useful life.
|
||||
- **Bridge for legacy Windows 7 workloads** - For solution scenarios dependent on legacy Windows OS environments, enterprises can use VDI instances of Windows 7 running in Azure. This enables support on modern devices like Surface without the risk of relying on older Windows 7 machines that no longer receive the latest security updates. In addition to these “future proofing” benefits, migration of any legacy workloads becomes greatly simplified when modern Windows 10 hardware is already deployed.
|
||||
- **Zero-Touch Deployment** - Autopilot is the recommended modern management deployment option for Surface devices. Windows Autopilot on Surface is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot on Surface to remotely deploy and configure devices in a zero-touch process right out of the box. Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a hardware hash. They're automatically enrolled and configured by using modern management solutions such as Azure Active Directory (Azure AD) and mobile device management.
|
||||
|
||||
### Surface devices: Minimizing environmental impacts
|
||||
|
||||
Surface performs life cycle assessments to calculate the environmental impact of devices across key stages of product life cycle enabling Microsoft to minimize these impacts. Each Surface product has an ECO profile that includes details on greenhouse gas emissions, primary energy consumption and material composition data, packaging, recycling, and related criteria. To download profiles for each Surface device, see [ECO Profiles](https://www.microsoft.com/download/details.aspx?id=55974) on the Microsoft Download Center.
|
||||
|
||||
## Summary
|
||||
|
||||
Windows Virtual Desktop on Surface provides organizations with greater flexibility and resilience in meeting the diverse needs of users, stakeholders, and customers. Running Windows Virtual Desktop solutions on Surface devices provides unique advantages over continued reliance on legacy devices. Flexible form factors like Surface Go 2 and Surface Pro 7 connected to the cloud (or offline), enable users to be productive from anywhere, at any time. Whether employees work in persistent, on-demand, or just-in-time scenarios, Windows Virtual Desktop on Surface affords businesses with the versatility to sustain productivity throughout disruptions from public health emergencies or other unforeseen events. Using the built in, multi-layered security and modern manageability of Windows 10, companies can take advantage of an expanding ecosystem of cloud-based services to rapidly deploy and scale Windows desktops and apps. Simply put, Windows Virtual Desktop on Surface delivers critically needed technology to organizations and businesses of all sizes.
|
||||
|
||||
## Learn more
|
||||
|
||||
For more information, see the following resources:
|
||||
|
||||
- [Windows Virtual Desktop](https://azure.microsoft.com/services/virtual-desktop/)
|
||||
- [Surface for Business](https://www.microsoft.com/surface/business)
|
||||
- [Modernize your workforce with Microsoft Surface](https://boards.microsoft.com/public/prism/103849?token=754435c36d)
|
||||
- [A guide to Surface Technical Content and Solutions](https://boards.microsoft.com/public/prism/104362/category/90968?token=09e688ec4a)
|
||||
- [Microsoft zero-trust security](https://www.microsoft.com/security/business/zero-trust)
|
||||
|
||||
|
||||
----------
|
||||
|
||||
<a id="1">1.</a> Windows Virtual Desktop on Surface refers to running Azure Virtual Desktop Infrastructure on a Surface device and is described here as an architectural solution, not a separately available product.<br>
|
||||
<a id="2">2.</a> Battery life varies significantly with settings, usage and other factors.<br>
|
||||
<a id="3">3.</a> Service availability and performance subject to service provider’s network. Contact your service provider for details, compatibility, pricing, SIM card, and activation. See all specs and frequencies at surface.com.<br>
|
||||
<a id="4">4.</a> Forrester Consulting, “A Forrester Total Economic Impact™ Study: Maximizing Your ROI from Microsoft 365 Enterprise with Microsoft Surface,” commissioned by Microsoft, 2018.<br>
|
||||
<a id="5">5.</a> Surface Go and Surface Go 2 use a third-party UEFI and do not support DFCI. DFCI is currently available for Surface Book 3, Surface Laptop 3, Surface Pro 7, and Surface Pro X. Find out more about managing Surface UEFI settings.<br>
|
||||
<a id="6">6.</a> Removable SSD is available on Surface Laptop 3 and Surface Pro X. Note that hard drive is not user removable. Hard drive is only removable a by skilled technician following Microsoft instructions.<br>
|
||||
<a id="7">7.</a> DFCI is currently available for Surface Book 3, Surface Laptop 3, Surface Pro 7, and Surface Pro X. [Find out more](https://docs.microsoft.com/surface/manage-surface-uefi-settings) about managing Surface UEFI settings.
|
||||
|
||||
Reference in New Issue
Block a user