mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge pull request #911 from CoveMiner/surface-2s-update-vjokai
Surface 2s update vjokai
This commit is contained in:
@ -30,15 +30,16 @@
|
||||
### [Surface System SKU reference](surface-system-sku-reference.md)
|
||||
|
||||
## Manage
|
||||
### [Optimizing wireless connectivity for Surface devices](surface-wireless-connect.md)
|
||||
### [Best practice power settings for Surface devices](maintain-optimal-power-settings-on-Surface-devices.md)
|
||||
### [Battery Limit setting](battery-limit.md)
|
||||
### [Surface Brightness Control](microsoft-surface-brightness-control.md)
|
||||
### [Surface Asset Tag](assettag.md)
|
||||
### [Surface firmware and driver updates](update.md)
|
||||
### [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
### [Deploy the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
### [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)
|
||||
### [Surface Dock Updater](surface-dock-updater.md)
|
||||
### [Use System Center Configuration Manager to manage devices with SEMM](use-system-center-configuration-manager-to-manage-devices-with-semm.md)
|
||||
|
||||
|
||||
## Secure
|
||||
### [Manage Surface UEFI settings](manage-surface-uefi-settings.md)
|
||||
@ -46,12 +47,13 @@
|
||||
### [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
||||
### [Enroll and configure Surface devices with SEMM](enroll-and-configure-surface-devices-with-semm.md)
|
||||
### [Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
|
||||
### [Use System Center Configuration Manager to manage devices with SEMM](use-system-center-configuration-manager-to-manage-devices-with-semm.md)
|
||||
|
||||
## Support
|
||||
## Troubleshoot
|
||||
### [Fix common Surface problems using the Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-for-business-intro.md)
|
||||
### [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md)
|
||||
### [Use Surface Diagnostic Toolkit for Business in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
|
||||
### [Run Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
|
||||
#### [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md)
|
||||
#### [Use Surface Diagnostic Toolkit for Business in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
|
||||
#### [Run Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
|
||||
### [Surface Data Eraser](microsoft-surface-data-eraser.md)
|
||||
### [Top support solutions for Surface devices](support-solutions-surface.md)
|
||||
### [Change history for Surface documentation](change-history-for-surface.md)
|
||||
|
@ -15,6 +15,14 @@ ms.topic: article
|
||||
|
||||
This topic lists new and updated topics in the Surface documentation library.
|
||||
|
||||
## August 2019
|
||||
|
||||
| **New or changed topic** | **Description** |
|
||||
| ------------------------ | --------------- |
|
||||
| [Optimizing wireless connectivity for Surface devices](surface-wireless-connect.md) | New document highlights key wireless connectivity considerations for Surface devices in mobile scenarios. |
|
||||
| [Deploy the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md) | Updated to reflect minor changes in the file naming convention for Surface MSI files. |
|
||||
|
||||
|
||||
## July 2019
|
||||
|
||||
| **New or changed topic** | **Description** |
|
||||
|
BIN
devices/surface/images/wifi-band.png
Normal file
BIN
devices/surface/images/wifi-band.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 72 KiB |
BIN
devices/surface/images/wifi-roaming.png
Normal file
BIN
devices/surface/images/wifi-roaming.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 86 KiB |
@ -29,10 +29,9 @@ Before you run the diagnostic tool, make sure you have the latest Windows update
|
||||
**To run the Surface Diagnostic Toolkit for Business:**
|
||||
|
||||
1. Download the [Surface Diagnostic Toolkit for Business](https://aka.ms/SDT4B).
|
||||
2. Select Run and follow the on-screen instructions.
|
||||
|
||||
The diagnosis and repair time averages 15 minutes but could take an hour or longer, depending on internet connection speed and the number of updates or repairs required. For more detailed information on Surface Diagnostic Toolkit for Business, refer to [Deploy Surface Diagnostic Toolkit for Business](https://docs.microsoft.com/surface/surface-diagnostic-toolkit-business).
|
||||
2. Select Run and follow the on-screen instructions. For full details, refer to [Deploy Surface Diagnostic Toolkit for Business](https://docs.microsoft.com/surface/surface-diagnostic-toolkit-business).
|
||||
|
||||
The diagnosis and repair time averages 15 minutes but could take an hour or longer, depending on internet connection speed and the number of updates or repairs required.
|
||||
# If you still need help
|
||||
|
||||
If the Surface Diagnostic Toolkit for Business didn’t fix the problem, you can also:
|
||||
|
84
devices/surface/surface-wireless-connect.md
Normal file
84
devices/surface/surface-wireless-connect.md
Normal file
@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Optimizing wireless connectivity for Surface devices
|
||||
description: This topic provides guidance around recommended wireless connectivity settings for network admins and users.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 08/15/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
# Optimizing wireless connectivity for Surface devices
|
||||
|
||||
## Introduction
|
||||
|
||||
To stay connected with all-day battery life, Surface devices implement wireless connectivity settings that balance performance and power conservation. Outside of the most demanding mobility scenarios, users can maintain sufficient wireless connectivity without modifying default network adapter or related settings.
|
||||
|
||||
In congested network environments, organizations can implement purpose-built wireless protocols across multiple network access points to facilitate roaming. This page highlights key wireless connectivity considerations in mobile scenarios utilizing Surface Pro 3 and later, Surface Book, Surface Laptop, and Surface Go.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
This document assumes you have successfully deployed a wireless network that supports 802.11n (Wi-Fi 4) or later in accordance with best practice recommendations from leading equipment vendors.
|
||||
|
||||
## Configuring access points for optimal roaming capabilities
|
||||
|
||||
If you’re managing a wireless network that’s typically accessed by many different types of client devices, it’s recommended to enable specific protocols on access points (APs) in your WLAN, as described in [Fast Roaming with 802.11k, 802.11v, and 802.11r](https://docs.microsoft.com/en-us/windows-hardware/drivers/network/fast-roaming-with-802-11k--802-11v--and-802-11r). Surface devices can take advantage of the following wireless protocols:
|
||||
|
||||
- **802.11r.** “**Fast BSS Transition”** accelerates connecting to new wireless access points by reducing the number of frames required before your device can access another AP as you move around with your device.
|
||||
- **802.11k.** **“Neighbor Reports”** provides devices with information on current conditions at neighboring access points. It can help your Surface device choose the best AP using criteria other than signal strength such as AP utilization.
|
||||
|
||||
Surface Go devices can also use 802.11v “BSS Transition Management Frames,” which functions much like 802.11k in providing information on nearby candidate APs.
|
||||
|
||||
## Managing user settings
|
||||
|
||||
You can achieve optimal roaming capabilities through a well-designed network that supports 802.11r and 802.11k across all access points. Ensuring that your network is properly configured to provide users with the best wireless experience is the recommended approach versus attempting to manage user settings on individual devices. Moreover, in many corporate environments Surface device users won’t be able to access advanced network adapter settings without explicit permissions or local admin rights. In other lightly managed networks, users can benefit by knowing how specific settings can impact their ability to remain connected.
|
||||
|
||||
### Recommended user settings and best practices
|
||||
|
||||
In certain situations, modifying advanced network adapter settings built into Surface devices may facilitate a more reliable connection. Keep in mind however that an inability to connect to wireless resources is more often due to an access point issue, networking design flaw, or environmental site issue.
|
||||
|
||||
> [!NOTE]
|
||||
> How you hold your Surface Pro or Surface Go can also affect signal strength. If you’re experiencing a loss of bandwidth, check that you’re not holding the top of the display, where the Wi-Fi radio receiver is located. Although holding the top of the display does not block wireless signals, it can trigger the device driver to initiate changes that reduce connectivity.
|
||||
|
||||
### Keep default Auto setting for dual bandwidth capability
|
||||
On most Surface devices, you can configure client network adapter settings to only connect to wireless APs over 5 gigahertz (GHz), only connect over 2.4 GHz, or let the operating system choose the best option (default Auto setting).
|
||||
|
||||
**To access network adapter settings go to:**
|
||||
|
||||
- **Start** > **Control panel** > **Network and Sharing Center** > **your Wi-Fi adapter** > **Properties** > **Configure** > **Advanced**.
|
||||
|
||||
 <br>
|
||||
|
||||
Keep in mind that 2.4 GHz has some advantages over 5 GHz: It extends further and more easily penetrates through walls or other solid objects. Unless you have a clear use case that warrants connecting to 5 GHz, it’s recommended to leave the Band setting in the default state to avoid possible adverse consequences. For example:
|
||||
|
||||
|
||||
- Many hotspots found in hotels, coffee shops, and airports still only use 2.4 GHz, effectively blocking access to devices if Band is set to 5 GHz Only.
|
||||
- Since Miracast wireless display connections require the initial handshake to be completed over 2.4 GHz channels, devices won’t be able to connect at 5 GHz Only.
|
||||
|
||||
> [!NOTE]
|
||||
> By default Surface devices will prefer connecting to 5 GHz if available. However, to preserve power in a low battery state, Surface will first look for a 2.4 GHz connection.
|
||||
|
||||
You can also toggle the band setting as needed to suit your environment. For example, users living in high density apartment buildings with multiple Wi-Fi hotspots — amid the presence of consumer devices all broadcasting via 2.4 GHz — will likely benefit by setting their Surface device to connect on 5 GHz only and then revert to Auto when needed.
|
||||
|
||||
### Roaming aggressiveness settings on Surface Go
|
||||
|
||||
Front-line workers using Surface Go may wish to select a signal strength threshold that prompts the device to search for a new access point when signal strength drops (roaming aggressiveness). By default, Surface devices attempt to roam to a new access point if the signal strength drops below **Medium** (50 percent signal strength). Note that whenever you increase roaming aggressiveness, you accelerate battery power consumption.
|
||||
|
||||
Leave the roaming aggressiveness setting in the default state unless you’re encountering connectivity issues in specific mobile scenarios such as conducting environmental site inspections while also maintaining voice and video connectivity during a conference meeting. If you don’t notice any improvement revert to the default **Medium** state.
|
||||
|
||||
**To enable roaming aggressiveness on Surface Go:**
|
||||
|
||||
1. Go to **Start > Control Panel** > **Network and Internet** > **Network and Sharing Center.**
|
||||
2. Under **Connections** select **Wi-Fi** and then select **Properties.**
|
||||
3. Select **Client for Microsoft Networks** and then select **Configure**
|
||||
4. Select **Advanced** > **Roaming Aggressiveness** and choose ****your preferred value from the drop-down menu.
|
||||
|
||||
 <br>
|
||||
|
||||
## Conclusion
|
||||
|
||||
Surface devices are designed with default settings for optimal wireless connectivity balanced alongside the need to preserve battery life. The most effective way of enabling reliable connectivity for Surface devices is through a well-designed network that supports 802.11r and 802.11k. Users can adjust network adapter settings or roaming aggressiveness but should only do so in response to specific environmental factors and revert to default state if there’s no noticeable improvement.
|
Reference in New Issue
Block a user