mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
huypub
GitHub
commit
bc699ba3d5
@ -20,16 +20,7 @@ Designed for team collaboration, Surface Hub 2S can transform the way you work
|
||||
|
||||
## Room considerations
|
||||
|
||||
Designed for interactive use in smaller conference rooms and huddle spaces, Surface Hub 2S provides a 4K camera, microphone array, crystal clear speakers, and a brilliant 4K+ resolution display. Optimizing the user experience in larger spaces with more people further away from the display may require peripherals such as an extra camera, microphone, or room systems solution such as Microsoft Teams Rooms. Use the following proximity guidance to determine if you need to plan for peripherals.
|
||||
|
||||
|
||||
| **Room/Space** | **Participants** | **Proximity** | **Additional peripherals** |
|
||||
| ---------------------------- | ------------ | -------------------- | -------------------------- |
|
||||
| Collaboration – Huddle space | 1-3 | 1–2 meters | None |
|
||||
| Collaboration – Lounge space | 3-6 | More than 2.3m | Peripherals Recommended |
|
||||
| Small meeting room | 4-6 | Up to 2.3 meters | None |
|
||||
| Medium, Larger meeting rooms | 6 + | More than 2.3 meters | Peripherals recommended |
|
||||
|
||||
Designed for interactive use in smaller conference rooms and huddle spaces, Surface Hub 2S provides a 4K camera, microphone array, crystal clear speakers, and a brilliant 4K+ resolution display. Optimizing the user experience in larger spaces with more people further away from the display may require peripherals such as an extra camera, microphone, or room systems solution such as Microsoft Teams Rooms.
|
||||
|
||||
As a general guideline, install Surface Hub 2S in a space that meets the following criteria:
|
||||
|
||||
|
||||
@ -218,37 +218,43 @@
|
||||
|
||||
## Update Windows 10
|
||||
### [Update Windows 10 in enterprise deployments](update/index.md)
|
||||
### [Windows as a service](update/windows-as-a-service.md)
|
||||
### Windows as a service
|
||||
#### [Windows as a service - introduction](update/windows-as-a-service.md)
|
||||
#### [Quick guide to Windows as a service](update/waas-quick-start.md)
|
||||
##### [Servicing stack updates](update/servicing-stack-updates.md)
|
||||
#### [Servicing stack updates](update/servicing-stack-updates.md)
|
||||
#### [Overview of Windows as a service](update/waas-overview.md)
|
||||
### [Prepare servicing strategy for Windows 10 updates](update/waas-servicing-strategy-windows-10-updates.md)
|
||||
### [Build deployment rings for Windows 10 updates](update/waas-deployment-rings-windows-10-updates.md)
|
||||
### [Assign devices to servicing channels for Windows 10 updates](update/waas-servicing-channels-windows-10-updates.md)
|
||||
### [Get started with Windows Update](update/windows-update-overview.md)
|
||||
### Get started
|
||||
#### [Get started with Windows Update](update/windows-update-overview.md)
|
||||
#### [How Windows Update works](update/how-windows-update-works.md)
|
||||
#### [Windows Update log files](update/windows-update-logs.md)
|
||||
#### [How to troubleshoot Windows Update](update/windows-update-troubleshooting.md)
|
||||
#### [Common Windows Update errors](update/windows-update-errors.md)
|
||||
#### [Windows Update error code reference](update/windows-update-error-reference.md)
|
||||
#### [Other Windows Update resources](update/windows-update-resources.md)
|
||||
### [Optimize Windows 10 update delivery](update/waas-optimize-windows-10-updates.md)
|
||||
### Optimize delivery
|
||||
#### [Optimize Windows 10 update delivery](update/waas-optimize-windows-10-updates.md)
|
||||
#### [Delivery Optimization for Windows 10 updates](update/waas-delivery-optimization.md)
|
||||
#### [Set up Delivery Optimization for Windows 10 updates](update/waas-delivery-optimization-setup.md)
|
||||
#### [Delivery Optimization reference](update/waas-delivery-optimization-reference.md)
|
||||
#### [Configure BranchCache for Windows 10 updates](update/waas-branchcache.md)
|
||||
#### [Whitepaper: Windows Updates using forward and reverse differentials](update/PSFxWhitepaper.md)
|
||||
### [Best practices for feature updates on mission-critical devices](update/feature-update-mission-critical.md)
|
||||
### Best practices
|
||||
#### [Best practices for feature updates on mission-critical devices](update/feature-update-mission-critical.md)
|
||||
#### [Deploy feature updates during maintenance windows](update/feature-update-maintenance-window.md)
|
||||
#### [Deploy feature updates for user-initiated installations](update/feature-update-user-install.md)
|
||||
#### [Conclusion](update/feature-update-conclusion.md)
|
||||
### [Deploy updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](update/waas-mobile-updates.md)
|
||||
### [Deploy updates using Windows Update for Business](update/waas-manage-updates-wufb.md)
|
||||
### Use Windows Update for Business
|
||||
#### [Deploy updates using Windows Update for Business](update/waas-manage-updates-wufb.md)
|
||||
#### [Configure Windows Update for Business](update/waas-configure-wufb.md)
|
||||
#### [Integrate Windows Update for Business with management solutions](update/waas-integrate-wufb.md)
|
||||
#### [Walkthrough: use Group Policy to configure Windows Update for Business](update/waas-wufb-group-policy.md)
|
||||
#### [Walkthrough: use Intune to configure Windows Update for Business](https://docs.microsoft.com/intune/windows-update-for-business-configure)
|
||||
### [Deploy Windows 10 updates using Windows Server Update Services](update/waas-manage-updates-wsus.md)
|
||||
### Use Windows Server Update Services
|
||||
#### [Deploy Windows 10 updates using Windows Server Update Services](update/waas-manage-updates-wsus.md)
|
||||
#### [Enable FoD and language pack updates in Windows Update](update/fod-and-lang-packs.md)
|
||||
### [Deploy Windows 10 updates using System Center Configuration Manager](update/waas-manage-updates-configuration-manager.md)
|
||||
### [Manage device restarts after updates](update/waas-restart.md)
|
||||
@ -256,15 +262,18 @@
|
||||
### [Determine the source of Windows updates](update/windows-update-sources.md)
|
||||
|
||||
## Windows Analytics
|
||||
## [Windows Analytics overview](update/windows-analytics-overview.md)
|
||||
### [Windows Analytics overview](update/windows-analytics-overview.md)
|
||||
### [Windows Analytics in the Azure Portal](update/windows-analytics-azure-portal.md)
|
||||
### [Windows Analytics and privacy](update/windows-analytics-privacy.md)
|
||||
### [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md)
|
||||
### Upgrade Readiness
|
||||
#### [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md)
|
||||
#### [Upgrade Readiness architecture](upgrade/upgrade-readiness-architecture.md)
|
||||
#### [Upgrade Readiness requirements](upgrade/upgrade-readiness-requirements.md)
|
||||
#### [Get started with Upgrade Readiness](upgrade/upgrade-readiness-get-started.md)
|
||||
#### Get started
|
||||
##### [Get started with Upgrade Readiness](upgrade/upgrade-readiness-get-started.md)
|
||||
##### [Upgrade Readiness deployment script](upgrade/upgrade-readiness-deployment-script.md)
|
||||
#### [Use Upgrade Readiness to manage Windows upgrades](upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md)
|
||||
#### Use Upgrade Readiness
|
||||
##### [Use Upgrade Readiness to manage Windows upgrades](upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md)
|
||||
##### [Upgrade overview](upgrade/upgrade-readiness-upgrade-overview.md)
|
||||
##### [Step 1: Identify apps](upgrade/upgrade-readiness-identify-apps.md)
|
||||
##### [Step 2: Resolve issues](upgrade/upgrade-readiness-resolve-issues.md)
|
||||
@ -272,7 +281,8 @@
|
||||
##### [Step 4: Monitor deployment](upgrade/upgrade-readiness-monitor-deployment.md)
|
||||
##### [Additional insights](upgrade/upgrade-readiness-additional-insights.md)
|
||||
##### [Targeting a new operating system version](upgrade/upgrade-readiness-target-new-OS.md)
|
||||
### [Monitor Windows Updates with Update Compliance](update/update-compliance-monitor.md)
|
||||
### Monitor Windows Updates
|
||||
#### [Monitor Windows Updates with Update Compliance](update/update-compliance-monitor.md)
|
||||
#### [Get started with Update Compliance](update/update-compliance-get-started.md)
|
||||
#### [Use Update Compliance](update/update-compliance-using.md)
|
||||
##### [Need Attention! report](update/update-compliance-need-attention.md)
|
||||
@ -281,7 +291,8 @@
|
||||
##### [Windows Defender AV Status report](update/update-compliance-wd-av-status.md)
|
||||
##### [Delivery Optimization in Update Compliance](update/update-compliance-delivery-optimization.md)
|
||||
##### [Update Compliance Perspectives](update/update-compliance-perspectives.md)
|
||||
### [Device Health](update/device-health-monitor.md)
|
||||
### Device Health
|
||||
#### [Device Health overview](update/device-health-monitor.md)
|
||||
#### [Get started with Device Health](update/device-health-get-started.md)
|
||||
#### [Using Device Health](update/device-health-using.md)
|
||||
### [Enrolling devices in Windows Analytics](update/windows-analytics-get-started.md)
|
||||
|
||||
@ -140,9 +140,10 @@ A [glossary](#glossary) of abbreviations used in this topic is provided at the e
|
||||
|Where is the Windows Autopilot data stored? |Windows Autopilot data is stored in the United States (US), not in a sovereign cloud, even when the AAD tenant is registered in a sovereign cloud. This is applicable to all Windows Autopilot data, regardless of the portal leveraged to deploy Autopilot.|
|
||||
|Why is Windows Autopilot data stored in the US and not in a sovereign cloud?|It is not customer data that we store, but business data which enables Microsoft to provide a service, therefore it is okay for the data to reside in the US. Customers can stop subscribing to the service any time, and, in that event, the business data is removed by Microsoft.|
|
||||
|How many ways are there to register a device for Windows Autopilot|There are six ways to register a device, depending on who is doing the registering: <br><br>1. OEM Direct API (only available to TVOs) <br>2. MPC via the MPC API (must be a CSP) <br>3. MPC via manual upload of CSV file in the UI (must be a CSP) <br>4. MSfB via CSV file upload <br>5. Intune via CSV file upload <br>6. Microsoft 365 Business portal via CSV file upload|
|
||||
|How many ways are there to create an Windows Autopilot profile?|There are four ways to create & assign an Windows Autopilot profile: <br><br>1. Through MPC (must be a CSP) <br>2. Through MSfB <br>3. Through Intune (or another MDM) <br>4. Microsoft 365 Business portal <br><br>Microsoft recommends creation and assignment of profiles through Intune. |
|
||||
| What are some common causes of registration failures? |<br>1. Bad or missing Hardware hash entries can lead to faulty registration attempts <br>2. Hidden special characters in CSV files. <br><br>To avoid this issue, after creating your CSV file, open it in Notepad to look for hidden characters or trailing spaces or other corruptions.|
|
||||
| Is Autopilot supported in all regions/countries? | <br>Autopilot only supports customers using public Azure. Public Azure does not include the three entities listed below:<br>- Azure Germany <br>- Azure China<br>- Azure Government<br>So, if a customer is set up in global Azure, there are no region restrictions. For example, if Contoso uses global Azure but has employees working in China, the Contoso employees working in China would be able to use Autopilot to deploy devices. If Contoso uses Azure China, the Contoso employees would not be able to use Autopilot.|
|
||||
|How many ways are there to create a Windows Autopilot profile?|There are four ways to create & assign an Windows Autopilot profile: <br><br>1. Through MPC (must be a CSP) <br>2. Through MSfB <br>3. Through Intune (or another MDM) <br>4. Microsoft 365 Business portal <br><br>Microsoft recommends creation and assignment of profiles through Intune. |
|
||||
| What are some common causes of registration failures? |1. Bad or missing Hardware hash entries can lead to faulty registration attempts <br>2. Hidden special characters in CSV files. <br><br>To avoid this issue, after creating your CSV file, open it in Notepad to look for hidden characters or trailing spaces or other corruptions.|
|
||||
| Is Autopilot supported on IoT devices? | Autopilot is not supported on IoT Core devices, and there are currently no plans to add this support. Autopilot is supported on Windows 10 IoT Enterprise SAC devices. Autopilot is supported on Windows 10 Enterprise LTSC 2019 and above; it is not supported on earlier versions of LTSC.|
|
||||
| Is Autopilot supported in all regions/countries? | Autopilot only supports customers using public Azure. Public Azure does not include the three entities listed below:<br>- Azure Germany <br>- Azure China<br>- Azure Government<br>So, if a customer is set up in global Azure, there are no region restrictions. For example, if Contoso uses global Azure but has employees working in China, the Contoso employees working in China would be able to use Autopilot to deploy devices. If Contoso uses Azure China, the Contoso employees would not be able to use Autopilot.|
|
||||
|
||||
## Glossary
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user