mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 04:13:41 +00:00
Merge branch 'master' into Kellylorenebaker-patch-2
This commit is contained in:
Kelly Baker
GitHub
@ -32,6 +32,8 @@ HoloLens 2 prompts a user to calibrate the device under the following circumstan
|
||||
- The user is using the device for the first time
|
||||
- The user previously opted out of the calibration process
|
||||
- The calibration process did not succeed the last time the user used the device
|
||||
- The user has deleted their calibration profiles
|
||||
- The visor is raised and the lowered and any of the above circumstances apply (this may be disabled in **Settings > System > Calibration**.)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -42,6 +42,22 @@ To see your HoloLens files in File Explorer on your PC:
|
||||
>[!TIP]
|
||||
>To see info about your HoloLens, right-click the device name in File Explorer on your PC, then select **Properties**.
|
||||
|
||||
## View HoloLens files on Windows Device Portal
|
||||
|
||||
>[!NOTE]
|
||||
>To use Device Portal you must enable [Developer Mode](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal#setting-up-hololens-to-use-windows-device-portal).
|
||||
|
||||
1. Enable Developer Mode and Device Portal on your HoloLens. (See note above if not enabled.)
|
||||
|
||||
1. Navigate to the Device Portal page on your PC.
|
||||
1. To connect to a HoloLens connected to your PC type in 127.0.0.1:10080/ in your browser.
|
||||
1. To connect to a HoloLens wirelessly instead navigate to your IP address.
|
||||
|
||||
>[!TIP]
|
||||
>You may need to install a certificate, OR you may see more details and navigate to the website anyways. (Path per web broswer will differ.)
|
||||
|
||||
1. Once succesfully connected, on the left side of the windw you can navigate to the [File Explorer](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal#file-explorer) workspace.
|
||||
|
||||
## Sync to the cloud
|
||||
|
||||
To sync photos and other files from your HoloLens to the cloud, install and set up OneDrive on HoloLens. To get OneDrive, search for it in the Microsoft Store on your HoloLens.
|
||||
|
||||
@ -37,7 +37,7 @@ To use HoloLens, each user follows these steps:
|
||||
|
||||
1. If another user has been using the device, do one of the following:
|
||||
- Press the power button once to go to standby, and then press the power button again to return to the lock screen
|
||||
- Select the user tile on the upper right of the Pins panel to sign out the current user.
|
||||
- HoloLens 2 users may select the user tile on the top of the Pins panel to sign out the current user.
|
||||
|
||||
1. Use your Azure AD account credentials to sign in to the device.
|
||||
If this is the first time that you have used the device, you have to [calibrate](hololens-calibration.md) HoloLens to your own eyes.
|
||||
|
||||
@ -116,7 +116,7 @@ To use the tool, you’ll need a computer running Windows 10 or later, with at l
|
||||
|
||||
To recover your HoloLens
|
||||
|
||||
1. Download and install the [Windows Device Recovery Tool](https://dev.azure.com/ContentIdea/ContentIdea/_queries/query/8a004dbe-73f8-4a32-94bc-368fc2f2a895/) on your computer.
|
||||
1. Download and install the [Windows Device Recovery Tool](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq) on your computer.
|
||||
1. Connect the HoloLens (1st gen) to your computer using the Micro USB cable that came with your HoloLens.
|
||||
1. Run the Windows Device Recovery Tool and follow the instructions.
|
||||
|
||||
|
||||
@ -22,6 +22,13 @@ appliesto:
|
||||
> [!Note]
|
||||
> HoloLens Emulator Release Notes can be found [here](https://docs.microsoft.com/windows/mixed-reality/hololens-emulator-archive).
|
||||
|
||||
### December Update - build 18362.1042
|
||||
|
||||
- Introduces LSR (Last Stage Reproduction) fixes. Improves visual rendering of holograms to appear more stable and crisp by more accurately accounting for their depth. This will be more noticeable if apps do not set the depth of holograms correctly, after this update.
|
||||
- Fixes stability of exclusive apps and navigation between exclusive apps.
|
||||
- Resolves an issue where Mixed Reality Capture couldn't record video after device is left in standby state for multiple days.
|
||||
- Improves hologram stability.
|
||||
|
||||
### November Update - build 18362.1039
|
||||
|
||||
- Fixes for **"Select"** voice commands during initial set-up for en-CA and en-AU.
|
||||
|
||||
@ -51,7 +51,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Surface Hub"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -15,7 +15,7 @@ ms.localizationpriority: Medium
|
||||
|
||||
# Surface Hub 2S adoption and training guides
|
||||
|
||||
Whether you are a small or large business, a Surface Hub adoption plan is critical in generating the right use cases and helping your users become comfortable with the device. Check out these downloadable guides designed to help you deliver training across your organization.
|
||||
Whether you're a small or large business, a Surface Hub adoption plan is critical in generating the right use cases and helping your users become comfortable with the device. Check out these downloadable guides designed to help you deliver training across your organization.
|
||||
|
||||
## On-demand training
|
||||
|
||||
|
||||
@ -69,6 +69,6 @@ You can set the Microsoft Teams app mode using Intune. Surface Hub 2S comes inst
|
||||
To set modes, add the following settings to a custom Device Configuration Profile.
|
||||
|
||||
|**Name**|**Description**|**OMA-URI**|**Type**|**Value**|
|
||||
|:------ |:------------- |:--------- |:------ |:------- |
|
||||
|**Teams App ID**| App name | ./Vendor/MSFT/SurfaceHub/Properties/VtcAppPackageId | String | Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams |
|
||||
|**Teams App Mode**| Teams mode | ./Vendor/MSFT/SurfaceHub/Properties/SurfaceHubMeetingMode | Integer | 0 or 1 or 2 |
|
||||
|:--- |:--- |:--- |:--- |:--- |
|
||||
|**Teams App ID**|App name|./Vendor/MSFT/SurfaceHub/Properties/VtcAppPackageId|String| Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams|
|
||||
|**Teams App Mode**|Teams mode|./Vendor/MSFT/SurfaceHub/Properties/SurfaceHubMeetingMode|Integer| 0 or 1 or 2|
|
||||
|
||||
@ -29,9 +29,9 @@ Although the deployment and management of Surface devices is fundamentally the s
|
||||
|
||||
## Updating Surface device drivers and firmware
|
||||
|
||||
For devices that receive updates through Windows Update, drivers for Surface components (and even firmware updates) are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS), the option to install drivers and firmware through Windows Update is not available. For these managed devices, the recommended driver management process is the deployment of driver and firmware updates using the Windows Installer (.msi) files, which are provided through the Microsoft Download Center. You can find a list of these downloads at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices).
|
||||
|
||||
As .msi files, deployment of driver and firmware updates is performed in the same manner as deployment of an application. Instead of installing an application as would normally happen when an .msi file is run, the Surface driver and firmware .msi will apply the driver and firmware updates to the device. The single .msi file contains the driver and firmware updates required by each component of the Surface device. The updates for firmware are applied the next time the device reboots. You can read more about the .msi installation method for Surface drivers and firmware in [Manage Surface driver and firmware updates](https://technet.microsoft.com/itpro/surface/manage-surface-pro-3-firmware-updates). For more information about how to deploy applications with Configuration Manager, see [Packages and programs in System Center Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/packages-and-programs).
|
||||
For devices that recieve updates through Windows Update, drivers for Surface components (and even firmware updates) are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM), see [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-driver-and-firmware-updates/).
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> Surface device drivers and firmware are signed with SHA-256, which is not natively supported by Windows Server 2008 R2. A workaround is available for Configuration Manager environments running on Windows Server 2008 R2. For more information, see [Can't import drivers into System Center Configuration Manager (KB3025419)](https://support.microsoft.com/kb/3025419).
|
||||
@ -81,4 +81,3 @@ To apply an asset tag using the [Surface Asset Tag CLI Utility](https://www.micr
|
||||
When you deploy Windows to a Surface device, the push-button reset functionality of Windows is configured by default to revert the system back to a state where the environment is not yet configured. When the reset function is used, the system discards any installed applications and settings. Although in some situations it can be beneficial to restore the system to a state without applications and settings, in a professional environment this effectively renders the system unusable to the end user.
|
||||
|
||||
Push-button reset can be configured, however, to restore the system configuration to a state where it is ready for use by the end user. Follow the process outlined in [Deploy push-button reset features](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/deploy-push-button-reset-features) to customize the push-button reset experience for your devices.
|
||||
|
||||
|
||||
@ -47,7 +47,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Surface"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -31,9 +31,8 @@ Autopilot is the recommended deployment option for Surface devices including Sur
|
||||
Support for broad deployments of Surface devices using Windows Autopilot, including enrollment performed by Surface partners at the time of purchase, requires devices manufactured with or otherwise installed with Windows 10 Version 1709 (Fall Creators Update) or later. These versions support a 4000-byte (4k) hash value to uniquely identify devices for Windows Autopilot that is necessary for deployments at scale. All new Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3 ship with Windows 10 Version 1903 or above.
|
||||
|
||||
## Surface partners enabled for Windows Autopilot
|
||||
Enrolling Surface devices in Windows Autopilot at the time of purchase is a capability provided by select Surface partners that are enabled with the capability to identify individual Surface devices during the purchase process and perform enrollment on an organization’s behalf. Devices enrolled by a Surface partner at time of purchase can be shipped directly to users and configured entirely through the zero-touch process of Windows Autopilot, Azure Active Directory, and Mobile Device Management.
|
||||
|
||||
When you purchase Surface devices from a Surface partner enabled for Windows Autopilot, your new devices can be enrolled in your Windows Autopilot deployment for you by the partner. Surface partners enabled for Windows Autopilot include:
|
||||
Enrolling Surface devices in Windows Autopilot at the time of purchase is performed by select Surface partners that enroll devices on an organization’s behalf. Devices can then be shipped directly to users and configured entirely through the zero-touch process of Windows Autopilot, Azure Active Directory, and Mobile Device Management.
|
||||
Surface partners enabled for Windows Autopilot include:
|
||||
|
||||
- [ALSO](https://www.also.com/ec/cms5/de_1010/1010_anbieter/microsoft/windows-autopilot/index.jsp)
|
||||
- [Atea](https://www.atea.com/)
|
||||
|
||||
Reference in New Issue
Block a user