mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into FromPrivateRepo
This commit is contained in:
huaping yu
commit
c462984b63
@ -5421,6 +5421,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface/manage-surface-dock-firmware-updates.md",
|
||||
"redirect_url": "devices/surface/update",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md",
|
||||
"redirect_url": "/surface-hub/finishing-your-surface-hub-meeting",
|
||||
"redirect_document_id": true
|
||||
|
||||
@ -28,7 +28,6 @@ In order to switch to the Chinese or Japanese version of HoloLens, you’ll need
|
||||
8. Select **Install software** and follow the instructions to finish installing.
|
||||
9. Once the build is installed, HoloLens setup will start automatically. Put on the device and follow the setup directions.
|
||||
|
||||
When you’re done with setup, go to **Settings -> Update & Security -> Windows Insider Program** and check that you’re configured to receive the latest preview builds. The Chinese/Japanese version of HoloLens will be kept up-to-date with the latest preview builds via the Windows Insider Program the same way the English version is.
|
||||
|
||||
## Note for language support
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Microsoft HoloLens (HoloLens)
|
||||
description: Windows Holographic for Business gets new features in Windows 10, version 1803.
|
||||
description: Windows Holographic for Business gets new features in Windows 10, version 1809.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
|
||||
@ -14,7 +14,6 @@
|
||||
## [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)
|
||||
### [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)
|
||||
### [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)
|
||||
### [Surface Dock Updater](surface-dock-updater.md)
|
||||
### [Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md)
|
||||
## [Considerations for Surface and System Center Configuration Manager](considerations-for-surface-and-system-center-configuration-manager.md)
|
||||
|
||||
@ -1,124 +0,0 @@
|
||||
---
|
||||
title: Manage Surface Dock firmware updates (Surface)
|
||||
description: Read about the different methods you can use to manage the process of Surface Dock firmware updates.
|
||||
ms.assetid: 86DFC0C0-C842-4CD1-A2D7-4425471FFE3F
|
||||
ms.localizationpriority: medium
|
||||
keywords: firmware, update, install, drivers
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
---
|
||||
|
||||
# Manage Surface Dock firmware updates
|
||||
|
||||
|
||||
Read about the different methods you can use to manage the process of Surface Dock firmware updates.
|
||||
|
||||
The Surface Dock provides external connectivity to Surface devices through a single cable connection that includes Power, Ethernet, Audio, USB 3.0, and DisplayPort. The numerous connections provided by the Surface Dock are enabled by a smart chipset within the Surface Dock device. Like a Surface device’s chipset, the chipset that is built into the Surface Dock is controlled by firmware. For more information about the Surface Dock, see the [Surface Dock demonstration](https://technet.microsoft.com/mt697552) video.
|
||||
|
||||
Like the firmware for Surface devices, firmware for Surface Dock is also contained within a downloaded driver that is visible in Device Manager. This driver stages the firmware update files on the Surface device. When a Surface Dock is connected and the driver is loaded, the newer version of the firmware staged by the driver is detected and firmware files are copied to the Surface Dock. The Surface Dock then begins a two-phase process to apply the firmware internally. Each phase requires the Surface Dock to be disconnected from the Surface device before the firmware is applied. The driver copies the firmware into the dock, but only applies it when the user disconnects the Surface device from the Surface Dock. This ensures that there are no disruptions because the firmware is only applied when the user leaves their desk with the device.
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>You can learn more about the firmware update process for Surface devices and how firmware is updated through driver installation at the following links:
|
||||
>- [How to manage and update Surface drivers and firmware](https://technet.microsoft.com/mt697551) from Microsoft Mechanics
|
||||
>- [Windows Update Makes Surface Better](https://go.microsoft.com/fwlink/p/?LinkId=785354) on the Microsoft Devices Blog
|
||||
|
||||
|
||||
|
||||
|
||||
The Surface Dock firmware update process shown in Figure 1 follows these steps:
|
||||
|
||||
1. Drivers for Surface Dock are installed on Surface devices that are connected, or have been previously connected, to a Surface Dock.
|
||||
|
||||
2. The drivers for Surface Dock are loaded when a Surface Dock is connected to the Surface device.
|
||||
|
||||
3. The firmware version installed in the Surface Dock is compared with the firmware version staged by the Surface Dock driver.
|
||||
|
||||
4. If the firmware version on the Surface Dock is older than the firmware version contained in the Surface Dock driver, the main chipset firmware update files are copied from the driver to the Surface Dock.
|
||||
|
||||
5. When the Surface Dock is disconnected, the Surface Dock installs the firmware update to the main chipset.
|
||||
|
||||
6. When the Surface Dock is connected again, the main chipset firmware is verified against the firmware present in the Surface Dock driver.
|
||||
|
||||
7. If the firmware update for the main chipset is installed successfully, the Surface Dock driver copies the firmware update for the DisplayPort.
|
||||
|
||||
8. When the Surface Dock is disconnected for a second time, the Surface dock installs the firmware update to the DisplayPort chipset. This process takes up to 3 minutes to apply.
|
||||
|
||||
|
||||
|
||||
*1- Driver installation can be performed by Windows Update, manual installation, or automatically downloaded with Microsoft Surface Dock Updater*
|
||||
|
||||
*2 - The Surface Dock firmware installation process takes approximately 3 minutes*
|
||||
|
||||
Figure 1. The Surface Dock firmware update process
|
||||
|
||||
If the firmware installation process is interrupted (for example, if power is disconnected from the Surface Dock during firmware installation), the Surface Dock will automatically revert to the prior firmware without disruption to the user, and the update process will restart the next time the Surface Dock is disconnected. For most users this update process should be entirely transparent.
|
||||
|
||||
## Methods for updating Surface Dock firmware
|
||||
|
||||
|
||||
There are three methods you can use to update the firmware of the Surface Dock:
|
||||
|
||||
- [Automatic installation of drivers with Windows Update](#automatic-installation)
|
||||
|
||||
- [Deployment of drivers downloaded from the Microsoft Download Center](#deployment-dlc)
|
||||
|
||||
- [Manually update with Microsoft Surface Dock Updater](#manual-updater)
|
||||
|
||||
## <a href="" id="automatic-installation"></a>Automatic installation with Windows Update
|
||||
|
||||
|
||||
Windows Update is the method that most users will use. The drivers for the Surface Dock are downloaded automatically from Windows Update and the dock update process is initiated without additional user interaction. The two-phase dock update process described earlier occurs in the background as the user connects and disconnects the Surface Dock during normal use.
|
||||
|
||||
>[!NOTE]
|
||||
>The driver version that is displayed in Device Manager may be different from the firmware version that the Surface Dock is using.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="deployment-dlc"></a>Deployment of drivers downloaded from the Microsoft Download Center
|
||||
|
||||
|
||||
This method is used mostly in environments where Surface device drivers and firmware are managed separately from Windows Update. See [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md) for more information about the different methods to manage Surface device driver and firmware updates. Updating the Surface Dock firmware through this method involves downloading and deploying an MSI package to the Surface device that contains the updated Surface Dock drivers and firmware. This is the same method recommended for updating all other Surface drivers and firmware. The two-phase firmware update process occurs in the background each time the Surface Dock is disconnected, just like it does with the Windows Update method.
|
||||
|
||||
For more information about how to deploy MSI packages see [Create and deploy an application with System Center Configuration Manager](https://docs.microsoft.com/sccm/apps/get-started/create-and-deploy-an-application).
|
||||
|
||||
>[!NOTE]
|
||||
>When drivers are installed through Windows Update or the MSI package, registry keys are added that indicate the version of firmware installed on the Surface Dock and contained within the Surface Dock driver. These registry keys can be found in:
|
||||
> **HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WUDF\\Services\\SurfaceDockFwUpdate\\Parameters**
|
||||
|
||||
Firmware status is displayed for both the main chipset (displayed as **Component10**) and the DisplayPort chipset (displayed as **Component20**). For each chipset there are four keys, where *xx* is **10** or **20** corresponding to each chipset:
|
||||
|
||||
- **Component*xx*CurrentFwVersion** – This key displays the version of firmware that is installed on the currently connected or most recently connected Surface Dock.
|
||||
|
||||
- **Component*xx*OfferFwVersion** – This key displays the version of firmware staged by the Surface Dock driver.
|
||||
|
||||
- **Component*xx*FirmwareUpdateStatus** – This key displays the stage of the Surface Dock firmware update process.
|
||||
|
||||
- **Component*xx*FirmwareUpdateStatusRejectReason** – This key changes as the firmware update is processed. It should result in 0 after the successful installation of Surface Dock firmware.
|
||||
|
||||
>[!NOTE]
|
||||
>These registry keys are not present unless you have installed updated Surface Dock drivers through Windows Update or MSI deployment.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="manual-updater"></a>Manually update with Microsoft Surface Dock Updater
|
||||
|
||||
|
||||
The manual method using the Microsoft Surface Dock Updater tool to update the Surface Dock is used mostly in environments where IT prepares Surface Docks prior to delivery to the end user, or for troubleshooting of a Surface Dock. Microsoft Surface Dock Updater is a tool that you can run from any Surface device that is compatible with the Surface Dock, and will walk you through the process of performing the Surface Dock firmware update in the least possible amount of time. You can also use this tool to verify the firmware status of a connected Surface Dock.
|
||||
|
||||
For more information about how to use the Microsoft Surface Dock Updater tool, please see [Microsoft Surface Dock Updater](surface-dock-updater.md). You can download the Microsoft Surface Dock Updater tool from the [Surface Tools for IT page](https://www.microsoft.com/download/details.aspx?id=46703) on the Microsoft Download Center.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
author: heatherpoulsen
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 12/01/2016
|
||||
ms.date: 11/13/2018
|
||||
---
|
||||
|
||||
# Surface firmware and driver updates
|
||||
@ -22,7 +22,6 @@ Find out how to download and manage the latest firmware and driver updates for y
|
||||
|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | See how you can use Wake On LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically. |
|
||||
| [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)| Get a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.|
|
||||
| [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)| Explore the available options to manage firmware and driver updates for Surface devices.|
|
||||
| [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)| Read about the different methods you can use to manage the process of Surface Dock firmware updates.|
|
||||
| [Surface Dock Updater](surface-dock-updater.md)| Get a detailed walkthrough of Microsoft Surface Dock Updater.|
|
||||
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.sitesec: library
|
||||
author: Jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.date: 09/24/2018
|
||||
ms.date: 11/13/2018
|
||||
---
|
||||
|
||||
# Servicing stack updates
|
||||
@ -28,6 +28,9 @@ Having the latest servicing stack update is a prerequisite to reliably installin
|
||||
|
||||
Currently, the servicing stack update releases are aligned with the monthly quality update release date, though sometimes they are released on a separate date if required.
|
||||
|
||||
>[!NOTE]
|
||||
>You can find a list of servicing stack updates at [Latest servicing stack updates](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001).
|
||||
|
||||
## What's the difference between a servicing stack update and a cumulative update?
|
||||
|
||||
Both Windows 10 and Windows Server use the cumulative update mechanism, in which many fixes are packaged into a single update. Each cumulative update includes the changes and fixes from all previous updates.
|
||||
|
||||
@ -3,6 +3,7 @@
|
||||
### [Configuration requirements](windows-autopilot-requirements-configuration.md)
|
||||
### [Network requirements](windows-autopilot-requirements-network.md)
|
||||
### [Licensing requirements](windows-autopilot-requirements-licensing.md)
|
||||
### [Intune Connector (preview)](intune-connector.md)
|
||||
## [Scenarios and Capabilities](windows-autopilot-scenarios.md)
|
||||
### [Support for existing devices](existing-devices.md)
|
||||
### [User-driven mode](user-driven.md)
|
||||
|
||||
BIN
windows/deployment/windows-autopilot/images/connector-fail.png
Normal file
BIN
windows/deployment/windows-autopilot/images/connector-fail.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 83 KiB |
66
windows/deployment/windows-autopilot/intune-connector.md
Normal file
66
windows/deployment/windows-autopilot/intune-connector.md
Normal file
@ -0,0 +1,66 @@
|
||||
---
|
||||
title: Intune Connector (preview) requirements
|
||||
description: Intune Connector (preview) issue workaround
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: low
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 11/13/2018
|
||||
---
|
||||
|
||||
|
||||
# Intune Connector (preview) language requirements
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
Microsoft has released a [preview for Intune connector for Active Directory](https://docs.microsoft.com/intune/windows-autopilot-hybrid) that enables user-driven [Hybrid Azure Active Directory join](user-driven-hybrid.md) for Windows Autopilot.
|
||||
|
||||
In this preview version of the Intune Connector, you might receive an error message indicating a setup failure with the following error code and message:
|
||||
|
||||
**0x80070658 - Error applying transforms. Verify that the specified transform paths are valid.**
|
||||
|
||||
See the following example:
|
||||
|
||||
|
||||
|
||||
This error can be resolved by ensuring that the member server where Intune Connector is running has one of the following language packs installed and configured to be the default keyboard layout:
|
||||
|
||||
en-US<br>
|
||||
cs-CZ<br>
|
||||
da-DK<br>
|
||||
de-DE<br>
|
||||
el-GR<br>
|
||||
es-ES<br>
|
||||
fi-FI<br>
|
||||
fr-FR<br>
|
||||
hu-HU<br>
|
||||
it-IT<br>
|
||||
ja-JP<br>
|
||||
ko-KR<br>
|
||||
nb-NO<br>
|
||||
nl-NL<br>
|
||||
pl-PL<br>
|
||||
pt-BR<br>
|
||||
ro-RO<br>
|
||||
ru-RU<br>
|
||||
sv-SE<br>
|
||||
tr-TR<br>
|
||||
zh-CN<br>
|
||||
zh-TW
|
||||
|
||||
This solution is a workaround and will be fully resolved in a future release of the Intune Connector.
|
||||
|
||||
To change the default keyboard layout:
|
||||
|
||||
1. Click **Settings > Time & language > Region and language**
|
||||
2. Select one of the languages listed above and choose **Set as default**.
|
||||
|
||||
Note: If the language you need isn't listed, you can add additional languages by selecting **Add a language**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -7,8 +7,8 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
ms.date: 04/19/2017
|
||||
author: justinha
|
||||
ms.date: 11/13/2018
|
||||
---
|
||||
|
||||
# Minimum password age
|
||||
@ -20,7 +20,7 @@ Describes the best practices, location, values, policy management, and security
|
||||
|
||||
## Reference
|
||||
|
||||
The **Minimum password age** policy setting determines the period of time (in days) that a password must be used before the user can change it. You can set a value between 1 and 998 days, or you can allow changes immediately by setting the number of days to 0. The minimum password age must be less than the Maximum password age, unless the maximum password age is set to 0, indicating that passwords will never expire. If the maximum password age is set to 0, the minimum password age can be set to any value between 0 and 998.
|
||||
The **Minimum password age** policy setting determines the period of time (in days) that a password must be used before the user can change it. You can set a value between 1 and 998 days, or you can allow password changes immediately by setting the number of days to 0. The minimum password age must be less than the Maximum password age, unless the maximum password age is set to 0, indicating that passwords will never expire. If the maximum password age is set to 0, the minimum password age can be set to any value between 0 and 998.
|
||||
|
||||
### Possible values
|
||||
|
||||
@ -29,9 +29,16 @@ The **Minimum password age** policy setting determines the period of time (in da
|
||||
|
||||
### Best practices
|
||||
|
||||
Set **Minimum password age** to a value of 2 days. Setting the number of days to 0 allows immediate password changes, which is not recommended.
|
||||
[Windows security baselines](https://docs.microsoft.com/windows/security/threat-protection/windows-security-baselines) recommend setting **Minimum password age** to 1 day.
|
||||
|
||||
If you set a password for a user and you want that user to change the administrator-defined password, you must select the **User must change password at next logon** check box. Otherwise, the user will not be able to change the password until the number of days specified by **Minimum password age**.
|
||||
Setting the number of days to 0 allows immediate password changes, which is not recommended.
|
||||
Combining immediate password changes with password history allows someone to change a password repeatedly until the password history requirement is met and re-establish the original password again.
|
||||
For example, suppose a password is "Ra1ny day!" and the history requirement is 24.
|
||||
If the minimum password age is 0, the password can be changed 24 times in a row until finally changed back to "Ra1ny day!".
|
||||
The minimum password age of 1 day prevents that.
|
||||
|
||||
If you set a password for a user and you want that user to change the administrator-defined password, you must select the **User must change password at next logon** check box.
|
||||
Otherwise, the user will not be able to change the password until the number of days specified by **Minimum password age**.
|
||||
|
||||
### Location
|
||||
|
||||
@ -70,11 +77,11 @@ To address password reuse, you must use a combination of security settings. Usin
|
||||
|
||||
### Countermeasure
|
||||
|
||||
Configure the **Minimum password age** policy setting to a value of at least 2 days. Users should know about this limitation and contact the Help Desk if they need to change their password during that two-day period. If you configure the number of days to 0, immediate password changes would be allowed, which we do not recommend.
|
||||
Configure the **Minimum password age** policy setting to a value of 1 day. Users should know about this limitation and contact the Help Desk to change a password sooner. If you configure the number of days to 0, immediate password changes would be allowed, which we do not recommend.
|
||||
|
||||
### Potential impact
|
||||
|
||||
If you set a password for a user but wants that user to change the password when the user first logs on, the administrator must select the **User must change password at next logon** check box, or the user cannot change the password until the next day.
|
||||
If you set a password for a user but want that user to change the password when the user first logs on, the administrator must select the **User must change password at next logon** check box, or the user cannot change the password until the next day.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: andreabichsel
|
||||
ms.author: v-anbic
|
||||
ms.date: 09/03/2018
|
||||
ms.date: 11/13/2018
|
||||
---
|
||||
|
||||
# Enable and configure antivirus always-on protection and monitoring
|
||||
@ -42,7 +42,7 @@ Location | Setting | Description | Default setting (if not configured)
|
||||
---|---|---|---
|
||||
Real-time protection | Monitor file and program activity on your computer | The Windows Defender Antivirus engine makes note of any file changes (file writes, such as moves, copies, or modifications) and general program activity (programs that are opened or running and that cause other programs to run) | Enabled
|
||||
Real-time protection | Scan all downloaded files and attachments | Downloaded files and attachments are automatically scanned. This operates in addition to the SmartScreen filter, which scans files before and during downloading | Enabled
|
||||
Real-time protection | Turn on process scanning whenever real-time protection is enabled | You can independently enable the Windows Defender Antivirus engine to scan running processes for suspicious modifications or behaviors. This is useful if you have disabled real-time protection | Enabled
|
||||
Real-time protection | Turn on process scanning whenever real-time protection is enabled | You can independently enable the Windows Defender Antivirus engine to scan running processes for suspicious modifications or behaviors. This is useful if you have temporarily disabled real-time protection and want to automatically scan processes that started while it was disabled | Enabled
|
||||
Real-time protection | Turn on behavior monitoring | The AV engine will monitor file processes, file and registry changes, and other events on your endpoints for suspicious and known malicious activity | Enabled
|
||||
Real-time protection | Turn on raw volume write notifications | Information about raw volume writes will be analyzed by behavior monitoring | Enabled
|
||||
Real-time protection | Define the maximum size of downloaded files and attachments to be scanned | You can define the size in kilobytes | Enabled
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user